Run acceptance tests and make the ship call

From a fresh clone/directory, run the commands that prove 5% canary healthy 20m → promote to 25%; guardrail breach → weight 0 in < 2m. A second person plays release commander watching revision-sliced error rate and follows your script without coaching. The demo includes limitations: what containerized answer API releasing image v2 at 5%→25%→100% weights still will not do.

Bundle: contract snippet, passing tests, metric snapshot for canary_weight, error_rate_by_revision, grounded_rate_by_revision, security negative probe, rollback note, owner name. Reference CANARY-PROMOTE-BLIND-6 as the drill you rehearsed. If any item is missing, the ship gate fails even if the happy path dazzles.

For Canary deploy lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint POST /answer remains the production surface you operate for containerized answer API releasing image v2 at 5%→25%→100% weights — not a slide. Keep CANARY-PROMOTE-BLIND-6 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 CANARY-PROMOTE-BLIND-6 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 answer API releasing image v2 at 5%→25%→100% weights, the human stakeholder is release commander watching revision-sliced error rate, and the incident id you design against is CANARY-PROMOTE-BLIND-6. Re-state the oracle in your notes — 5% canary healthy 20m → promote to 25%; guardrail breach → weight 0 in < 2m — and keep the invariant visible: promote only if canary error_rate ≤ baseline+0.5pp and groundedness ≥ baseline−1pp for two 10m windows. Track canary_weight, error_rate_by_revision, grounded_rate_by_revision as the scoreboard. Surface under change control: POST /answer. If you only have forty minutes, finish the fixture for automation promotes while scrape_up{revision=v2}==0 before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.