Use case
Incident postmortem
Run a postmortem as governed stages, and keep the lessons where the next decision can find them.
What it is
The stage, and what it produces
A postmortem is reviewed, approved work whose whole point is to be remembered. The governed-run pattern fits it well: produce the analysis, have a human approve it, and keep the lessons in Memory so they inform future decisions.
In a run
How it works, step by step
Gather the timeline and contributing factors
Propose findings and actions for review
A human approves the conclusions
Lessons kept in Memory for next time
- Timeline · Retry fired before the ack
- Cause · Missing idempotency key
- Action · Enforce key on /charges
Illustrative — produced, reviewed and approved before the next step.
Works with
The parts of the platform it leans on
Where it stands. Exploratory. The Memory that would keep the lessons ships today; a postmortem-specific workflow is not something we've shipped.
Turn this stage into a governed output
Start with what ships today, and grow into the full run as it lands.