Core Settlement Engine Post-Mortem Dispatch
Draft an executive post-mortem email detailing root-cause debugging and containment for a critical transaction settlement failure.
Use this template when an asynchronous settlement engine or order matching system encounters high-severity transactional failures in a production banking environment. It guides engineering leaders in communicating technical root cause, state reconstruction, and regulatory safeguards directly to executive stakeholders.
Role: Principal Infrastructure Reliability Engineer specializing in ultra-low latency settlement architectures.
Context
- Target System: {{trading_system_name}}
- Incident Window: {{incident_timestamp}}
- Observed Telemetry & Symptoms: {{observed_failure_symptom}}
- Root Cause Discovery: {{root_cause_technical_details}}
- Regulatory Compliance Scope: {{regulatory_reporting_scope}}
- Mitigation & Rollback Status: {{immediate_mitigation_applied}}
Task
Draft an authoritative technical post-mortem email for senior leadership and compliance officers, detailing the exact debugging sequence, underlying failure mechanism, system restoration verification, and long-term architectural remediations.
Method
- Translate {{observed_failure_symptom}} into an executive-level summary of operational and capital impact.
- Detail the systematic debugging path taken across distributed logs, thread dumps, and memory profiling that uncovered {{root_cause_technical_details}}.
- Deconstruct the underlying state corruption or lock contention failure within {{trading_system_name}}.
- Explain how {{immediate_mitigation_applied}} restored deterministic state and verified idempotency across pending transaction queues.
- Detail the audit ledger reconciliation status according to the constraints in {{regulatory_reporting_scope}}.
- Outline a prioritized three-tier engineering roadmap to eliminate this defect class.
- Provide an open technical Q&A schedule and contact matrix for impacted desk heads.
Constraints
- MUST express all timestamps in UTC and currency values in standardized ISO formats.
- MUST NOT expose sensitive customer personally identifiable information or raw cryptographic secrets.
- MUST differentiate explicitly between transient network anomalies and deterministic logic bugs.
- Keep the overall email body under 650 words while preserving technical rigor.
Output format
Send-ready executive email composed of:
- Subject Line: High-severity incident identifier, system name, and status tag.
- Executive Summary (max 100 words).
- Technical Diagnostic Timeline (bulleted chronology of discovery and isolation).
- Root Cause Anatomy (in-depth explanation of bug mechanics).
- Remediation & Verification State (bulleted actions completed).
- Regulatory & Audit Footprint.
- Next Steps & Incident Review Schedule.
Self-review
- Are all references to {{trading_system_name}} and {{regulatory_reporting_scope}} technically precise?
- Does the debugging narrative clearly distinguish between symptom and root cause?
- Is the tone sufficiently objective, accountable, and transparent for compliance oversight?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.