Incident Postmortem Generator — illustrative example

INPUT
Verified fictional timeline: 10:00 deployment; 10:04 export errors detected; 10:12 rollback started; 10:16 service restored. Verified mechanism: new code expected a field absent in older records. Assigned owner: export team.

RESULT
Impact window: 10:04–10:16 observed, 12 minutes; earlier impact not established.
Mechanism: older records lacked the field expected by the new code.
Mitigation: rollback restored exports.
Follow-up for export team: add an old-record compatibility fixture and verify the corrected code against it before release.
Open question: how many exports failed? Retrieve the relevant logs before publishing an impact count.

REVIEW
A postmortem should distinguish timeline facts, contributing factors and corrective actions. A blameless review still needs clear ownership for follow-up.

This is a teaching example, not a live execution record.