0
Post-mortem writer that separates facts from blame
Help me write a blameless post-mortem for this incident: incident_description, which happened on incident_date and affected impact_description.
Structure it as:
1. Timeline: a factual, timestamped sequence of what happened, no interpretation or blame language, just events (use placeholders like time if I haven't given exact times).
2. Impact: concrete, quantified where possible (users affected, revenue, downtime duration).
3. Root cause: the actual mechanical cause, not "human error", trace it back to the system or process gap that allowed the error to matter.
4. Contributing factors: 2-3 secondary conditions that made this worse or harder to catch, stated as system gaps, not individual failings.
5. What went well: at least 2 things that limited the damage or sped up recovery, credited specifically.
6. Action items: each one a specific system change with an owner and due date, ranked by how directly it prevents recurrence.
Strip any language that assigns personal fault, even if I write it that way in my input.