Define the production target for disaster recovery

This lab builds regional RAG platform restore with PostgreSQL + object storage + vector indexes. The human in the loop is DR lead failing over region A → B within RTO 2h / RPO 15m. Scope is intentionally narrower than “make AI reliable”: you will prove one oracle — drill DR-2026-07-30: restore completes 97m; gold citation_precision ≥ 0.95 — and one invariant — restore validates citation gold set before traffic; corrupt snapshot rejected. Record non-goals in your notes so a later change cannot silently expand authority. The incident mnemonic for the chapter is DR-2026-07-30; design as if that ticket is already written and you are filling evidence.

Turn the oracle into a table: input fixture, expected observable, prohibited side effect, owner, latency/cost ceiling. Separate model taste from software correctness — transport, auth, parsing, and termination must be deterministic even when generated text varies. Primary metric family: rto_minutes, rpo_minutes, citation_precision_post_restore. Averages without a denominator or revision label do not gate release. Fake external dependencies in unit tests; live calls wait until fakes pass.

Before implementation, encode a failing check that would have caught traffic cut before vector rebuild finishes — fluent ungrounded answers. That failure is the pedagogical north star for later pages: contracts reject it, happy path never performs it, validation asserts it, failure-handling contains it, observability detects it, security-ops prevents privilege tricks around it, and mastery replays it in a drill. Endpoint under study: region-b https://b.rag.example.

Capacity note for planners: estimate peak demand on region-b https://b.rag.example and the cost ceiling for a failed retry storm. Write the abort conditions — unbounded spend, cross-tenant leakage, or inability to roll back — before you enjoy the first green test. Prefer synthetic fixtures shaped like production over anonymized production dumps you cannot share in class. When you are tempted to widen scope, re-read the oracle (drill DR-2026-07-30: restore completes 97m; gold citation_precision ≥ 0.95) and cut features that do not serve it. The teaching outcome is judgment under constraints: DR lead failing over region A → B within RTO 2h / RPO 15m gets a trustworthy control, not a kitchen-sink framework. Keep the language of release decisions: promote, hold, or roll back — never “see if it gets better.”

Decide what will live in version control on day one: fixtures, contract markdown, and a failing test name. Write the cost ceiling as a hard number with currency and period. If the lab involves clusters, name the non-prod context you will use and forbid prod kubecontexts in scripts. Capture the baseline metric once before changing code so later gains are comparative. Refuse tools that hide the request path behind magic macros until the oracle is green on fakes. Your README section for this page should be five lines or fewer and still falsifiable. In this chapter the product is regional RAG platform restore with PostgreSQL + object storage + vector indexes, the human stakeholder is DR lead failing over region A → B within RTO 2h / RPO 15m, and the incident id you design against is DR-2026-07-30. Re-state the oracle in your notes — drill DR-2026-07-30: restore completes 97m; gold citation_precision ≥ 0.95 — and keep the invariant visible: restore validates citation gold set before traffic; corrupt snapshot rejected. Track rto_minutes, rpo_minutes, citation_precision_post_restore as the scoreboard. Surface under change control: region-b https://b.rag.example. If you only have forty minutes, finish the fixture for traffic cut before vector rebuild finishes — fluent ungrounded answers before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.