Ship and explain the canary plus rollback unit

From a fresh clone/directory, run the commands that prove kubectl rollout status shows ready; /readyz 200 only when index pin matches. A second person plays platform engineer shipping faq-index@sha256:a1b2 to staging and follows your script without coaching. The demo includes limitations: what containerized café FAQ RAG with readiness probes and versioned index pin still will not do.

Bundle: contract snippet, passing tests, metric snapshot for ready_ratio == 1 and citation_miss_rate ≤ 0.02 during rollout, security negative probe, rollback note, owner name. Reference DEPLOY-EMPTY-INDEX-5 as the drill you rehearsed. If any item is missing, the ship gate fails even if the happy path dazzles.

For Deploy a RAG app, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint GET /readyz remains the production surface you operate for containerized café FAQ RAG with readiness probes and versioned index pin — not a slide. Keep DEPLOY-EMPTY-INDEX-5 in the handoff template so the next owner inherits the drill.

After the peer demo, schedule the next threshold review date. File a short changelog that mentions DEPLOY-EMPTY-INDEX-5 and the control that addresses it. Archive the evidence pack where your team already stores launch records. Resist rewriting everything “for real production” in one weekend — operate this slice until the metrics bore you, then widen. Final self-check: if telemetry vanished, would you still know to hold? If yes, you learned the operating posture this lane teaches.

Trim the demo script until every command is necessary. Record a peer signature line: name, date UTC, pass/fail. File known limitations as bullets, not apologies. Link the evidence pack from the README. Schedule the next game day on a calendar, even if it is solo. Archive the branch tag or release digest you actually shipped. In this chapter the product is containerized café FAQ RAG with readiness probes and versioned index pin, the human stakeholder is platform engineer shipping faq-index@sha256:a1b2 to staging, and the incident id you design against is DEPLOY-EMPTY-INDEX-5. Re-state the oracle in your notes — kubectl rollout status shows ready; /readyz 200 only when index pin matches — and keep the invariant visible: readyz fails if index digest ≠ pinned digest; rollback restores previous digest in < 2 min. Track ready_ratio == 1 and citation_miss_rate ≤ 0.02 during rollout as the scoreboard. Surface under change control: GET /readyz. If you only have forty minutes, finish the fixture for new pods serve empty index while old pods terminate — citation miss spike before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.