---
type: atlas-artifact
artifact_type: postmortem
project: "{{project}}"
status: draft
owner: "{{owner}}"
created: {{date}}
updated: {{date}}
source: "{{source}}"
reviewer: "{{reviewer|TBD}}"
tags: [atlas, artifact, postmortem]
---
# Postmortem: {{title}}

Parent project: [[{{project}}]]
Source incident/task: {{source}}

## Incident summary

What happened, when, and how it was detected.

## Impact

Who/what was affected, duration, and severity.

## Timeline

| Time | Event | Source/evidence |
|---|---|---|
| YYYY-MM-DD HH:MM TZ |  |  |

## Root cause

Primary cause and contributing factors.

## What went well

- ...

## What went poorly

- ...

## Corrective actions with owners

| Action | Owner | Due | Verification |
|---|---|---|---|
|  |  |  |  |

## Follow-up verification date

YYYY-MM-DD.

## Blamelessness note

This postmortem focuses on system/process improvement, not blame.

## Postmortem-specific review checklist

- [ ] Timeline separates fact from interpretation.
- [ ] Root cause is specific enough to act on.
- [ ] Corrective actions have owners, due dates, and verification.
- [ ] No secrets or raw sensitive logs are included.

## Universal reviewer checklist

Before accepting this artifact, verify:

- [ ] Clear owner, status, date, source, and next action.
- [ ] Saved in the correct durable destination and named using the convention.
- [ ] Links back to the relevant project note and source task/issue/PR/session/incident.
- [ ] Claims are backed by evidence links, command output, or labeled assumptions.
- [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant.
- [ ] No secrets, tokens, raw PII, private keys, or unredacted credentials are included.
- [ ] A new specialist can understand the artifact without rereading the whole chat.
