Skip to main content
An ORCA runbook is generated from evidence: the mandatory chaos suite injects seven faults against production-sized state in your environment, and the documented recovery times become your on-call runbook. These are the reference targets a deployment must meet before go-live: Beyond component faults, the runbook covers the pipeline-shape invariant: a stage’s output exceeding its input (duplication), a stage dropping to zero (blocked consumer), and DLQ growth with the selective replay procedure. The full runbook — symptoms, dashboards, step-by-step recovery procedures, escalation paths — is customer documentation, generated per deployment from your own chaos results and delivered at Gate 6 sign-off.