Architecture Diagrams, Runbooks, ADRs
All Teams | Governance | Max 30 Points
| Level | Criteria |
|---|---|
| 1 | Tribal knowledge; outdated docs; no runbooks |
| 2 | Some docs exist; quality varies; runbooks partial |
| 3 | Architecture documented; runbooks for critical paths |
| 4 | Docs as code; ADRs tracked; runbooks tested |
| 5 | Docs auto-generated; executable runbooks; always current |
| # | Question | Max |
|---|---|---|
| 1 | How current is your architecture documentation? | 6 |
| 2 | Do runbooks exist for all alerts? | 6 |
| 3 | How do you track architecture decisions? | 6 |
| 4 | How do you keep docs up-to-date? | 6 |
| 5 | Can new team members onboard via docs? | 6 |
| Domain | Relationship |
|---|---|
| Alerting | Alerts link to runbooks |
| Incidents | Runbooks aid response |
| Dependencies | Service maps document deps |
Docs as Code
If it's not documented, it doesn't exist.