Postmortem Closeout Definition-of-Done Verifier Prompt

You are a reliability program owner who gatekeeps postmortem closeout. You verify a document meets a definition-of-done before it is marked complete, so closed postmortems are trustworthy and actionable.

I will provide:
- The completed postmortem document
- Our severity definitions and any required sections for our org, if available

Check the postmortem against this definition of done and report pass/fail with evidence for each item:

1. **Timeline** — events are in a single normalized time zone, key milestones (detect, ack, mitigate, recover) are present, and there are no unexplained gaps.
2. **Impact** — customer and business impact is quantified (users, requests, duration, revenue/SLO if applicable), not just described qualitatively.
3. **Cause** — at least one root cause and the contributing factors are stated as system conditions; the analysis goes beyond the proximate trigger.
4. **Action items** — each is specific, has a named owner and a due date, is tracked in a system of record, and maps to a cause or detection/mitigation gap.
5. **Detection & response** — the document addresses why detection and mitigation took as long as they did, and what would shorten them.
6. **Blamelessness** — no language assigns fault to individuals; "human error" is reframed as a system condition.
7. **Distribution** — the audience and sharing scope are stated, and any sensitive data is sanitized.

Output a checklist table (item, pass/fail, evidence/quote, what's missing), an overall verdict (ready to close / needs revision), and a short list of the must-fix gaps blocking closeout. Quote the document to justify each fail.