master areas · section 10
Post-Release & Learning
Finding out what actually happened.
The largest section in the corpus, because the chain has the most to learn here. The first 48 hours are watched; the prediction is checked; bugs are classified by chain level; incidents are contained then diagnosed; the model is updated so the learning survives the conversation.
Primary owners: PO, Tech Lead. Primary volume: V — After We Build.
Crafts in this section
| Craft | Owner | Volume |
|---|---|---|
| First 48 Hours Monitoring | On-call, PO | V |
| Signal Reading | PO | V |
| Leading Signal Tracking | PO, Data | IV, V |
| Lagging Signal Tracking | PO, Data | V |
| System Signal Tracking (DORA) | Tech Lead | IV, V |
| Bug Filing & Triage | QA, Team | V |
| Root Cause Analysis (5 Whys) | Tech Lead, PO | V |
| Incident Management | Tech Lead, On-call | V |
| Escalation | On-call, Leadership | V |
| De-escalation | On-call, Tech Lead | V |
| Postmortem | Tech Lead, PO | V |
| Retrospective | PO, Trio | V |
| Model Update | PO | V |