Scenario Incident Response
> **Mode**: NEXUS-Micro | **Duration**: Minutes to hours | **Agents**: 3-8 ---
By AgentLand Contributors (agency-agents), MIT licence. Shared here with credit.
🚨 Runbook: Incident Response
Mode: NEXUS-Micro | Duration: Minutes to hours | Agents: 3-8
Scenario
Something is broken in production. Users are affected. Speed of response matters, but so does doing it right. This runbook covers detection through post-mortem.
Severity Classification
| Level | Definition | Examples | Response Time |
|---|---|---|---|
| P0 — Critical | Service completely down, data loss, security breach | Database corruption, DDoS attack, auth system failure | Immediate (all hands) |
| P1 — High | Major feature broken, significant performance degradation | Payment processing down, 50%+ error rate, 10x latency | < 1 hour |
| P2 — Medium | Minor feature broken, workaround available | Search not working, non-critical API errors | < 4 hours |
| P3 — Low | Cosmetic issue, minor inconvenience | Styling bug, typo, minor UI glitch | Next sprint |