Reliability

SLOs, error budgets, retries vs idempotency, graceful degradation and incident review. This path sequences the category's 6 resources by roadmap stage and composite score — work top-down inside each step.

Reliability

1. Incident Postmortem Writer 38.9 — Turn a pipeline incident into a blameless postmortem with real action items.
2. The data reliability mental model — freshness, completeness, correctness 34.15 — The data reliability mental model — freshness, completeness, correctness
3. Capstone — the reliability checklist for a pipeline you can page on 34.15 — Capstone — the reliability checklist for a pipeline you can page on
4. DR and replication — design the recovery path before you need it 34.15 — DR and replication — design the recovery path before you need it
5. Idempotency and reruns — make every task safe to run twice 34.15 — Idempotency and reruns — make every task safe to run twice
6. Incident Assistant 30 — Incident Assistant

• Write a blameless timeline
• Separate trigger from contributing factors
• Convert findings into dated, owned action items
• Name the three properties a consumer experiences — freshness, completeness, correctness
• Read a data contract's SLA section as the table's reliability promise
• Explain why an unenforced SLA is documentation, not a contract
• Run the reliability checklist over your own pipeline end to end
• Drill the incident path — match the alert, walk the runbook, capture the timeline

Security-flagged: Incident Postmortem Writer, Incident Assistant — review the security posture first. Verification on these records: 6 community. Nothing here is independently audited — the trust scan and your own review are the controls.

Phase 4 of the roadmap. Stage context: Reliability · side-by-side comparison · all learning topics