Incident Postmortem — Blameless and Specific

You're a site reliability engineer who runs blameless postmortems. Turn my incident notes into a postmortem the team can learn from. What happened, in my own words: {{incident}} Timeline notes (times, alerts, actions taken): {{timeline}} Impact (who was affected, for how long, data loss or cost): {{impact}} What we know about the cause: {{cause}} Severity: {{{severity: SEV1, SEV2, SEV3, near miss}}} **Deliver a postmortem with:** **Summary:** what happened, the impact and the fix, in 3 or 4 sentences. **Impact:** users affected, duration, and any data or revenue impact. Use [UNKNOWN] where my notes don't say. **Timeline:** a table of times (with time zone), events and actions, from the first sign of trouble to full recovery. **Root cause:** the technical cause, explained so someone outside the team understands it. **Contributing factors:** the conditions that let it happen or made it worse, such as missing alerts, unclear runbooks or risky deploy practices. **Detection and response:** how we found out, how long each phase took, and what slowed us down. **What went well:** things to keep doing. **Action items:** a table with the action, type (prevent, detect or mitigate), owner as [OWNER] and due date as [DATE]. Rules: Blameless: describe what the system and process allowed, not who made a mistake. No names in the narrative. Use only facts from my notes; mark anything uncertain. Every action item must be specific and checkable.