Runbooks Index

Operational playbooks for Oshun V1 and V6 launch-critical systems. Each runbook is owned by one team and lists its applicable services, the incident shape it handles, and the rough severity that should trigger it. When paging on-call, link directly to the relevant runbook below — don't ask the responder to hunt through ls.

When to use this index#

• An alert fires and you don't know which runbook applies — search this table by service or incident type.
• You're writing a new runbook — add a row here in the same PR.
• You're auditing operational readiness — every domain should appear at least once.

Index#

Severity definitions#

• SEV-1 — User-visible outage or data loss; page on-call immediately, page the secondary at the 15-minute mark.
• SEV-2 — Significant degradation (≥10% of users); page on-call.
• SEV-3 — Internal degradation or non-blocking regression; ticket during business hours.
• n/a — Operational task that doesn't represent an active incident (setup, scheduled work, debt cleanup).

Adding a new runbook#

1. Create docs/runbooks/<short-name>.md following the structure of an existing runbook (header with owner + last-reviewed; "When to use"; "Step-by-step"; "Common failures").
2. Add a row to the table above in the same PR.
3. Cross-reference any new env vars or scripts in the runbook itself so future readers don't have to chase them down.
4. If the runbook covers a SEV-1 incident, also add it to the docs/operations/on-call.md cheat-sheet (once that doc lands).