ops__maintain-incident-postmortem

An incident postmortem that links evidence to root-cause analysis requires a structured template to capture facts, inferences, ruled-out hypotheses, and verification states, turning scattered evidence into a source-backed narrative for future responders.

Organizing timeline notes and corrective actions for an outage postmortem involves structuring them under a defined incident path with a reusable template, ensuring accounts, evidence, and recurrence patterns are clearly documented from draft to final review.

Yes, a standard postmortem template can track ruled-out hypotheses and recurrence patterns by providing dedicated sections to document inferences, verification states, and learning outcomes alongside the causal narrative.

Structuring incident documentation from draft to completed review requires a workflow with validation checkpoints, capturing incident facts and corrective actions in a postmortem file under a defined docs/incidents path to ensure durability.

Yes, the postmortem workflow requires a defined incident path under docs/incidents, structured as a semantic domain and dated slug directory, containing a postmortem.md file to capture the evidence-backed narrative.

Maintaining durable postmortems for future incident responders requires composing a source-backed narrative with clear status and learning sections, ensuring that causal facts, inferences, and corrective actions remain accessible and verifiable.