Postmortem action example: delivered is not verified
Track a configuration validation action from delivery to an evidence-backed review.
Illustrative dataset · Tool version 2 · Reviewed September 29, 2026
What would show that the fix reduced the stated risk?
The illustrative action adds a configuration validation gate after a stale configuration causes failures. Its status begins at Delivered. The proposed test replays a stale configuration in staging. Evidence is intentionally blank so the difference between delivery and verification remains visible.
| Field | Illustrative action |
|---|---|
| scenario | Illustrative stale configuration causes checkout failures |
| treatment | Add a configuration validation gate |
| owner | Platform team |
| due | Not recorded |
| test | Replay a stale configuration in staging and verify rejection |
| evidence | Not recorded |
| remaining | Other configuration failure modes remain untested |
| status | Delivered |
What this example does not establish
The tool checks whether evidence is recorded, not whether it is true or sufficient. Risk acceptance needs explicit residual-risk and owner information.
Try a variation
Open the example, change one input, and review the result. Keep definitions and denominators constant when comparing scenarios. Save a named draft before changing to a different dataset.
Read the related guide · Source and further reading
These datasets and worksheets may be adapted for your team or training. Attribute AIOpsSRE and link to this example when redistributing. Third-party sources retain their own terms.
Get AIOpsSRE by email · Report a calculation or explanation issue