## Goal

Reduce MTTR, protect data consistency, and maintain clear communication during incidents.

## Runbooks in this section

- [Reliability model](/docs/operations/reliability-model)
- [Incident response runbook](/docs/operations/incident-response-runbook)
- [Checkout failure runbook](/docs/operations/checkout-failure-runbook)
- [Webhook backlog runbook](/docs/operations/webhook-backlog-runbook)

## Standard operations flow

<Steps>
  <Step title="1) Detection">Automated alerts and domain-level error signals.</Step>
  <Step title="2) Classification">Classify impact and severity in less than 10 minutes.</Step>
  <Step title="3) Mitigation">Apply safe workaround without breaking reconciliation.</Step>
  <Step title="4) Recovery">Run replay and validate end-to-end consistency.</Step>
  <Step title="5) Learning">Publish preventive actions and update runbooks.</Step>
</Steps>

## Mandatory guardrails

- Every incident has technical owner and communication owner.
- Any replay path must be idempotent and auditable.
- Emergency changes must generate hardening follow-up tasks.