Canary and operate service-level objectives

From a fresh clone/directory, run the commands that prove 3% provider timeout for 20m trips fast-burn; monthly budget math matches calc-budget.py. A second person plays reliability owner gating releases on error budget and follows your script without coaching. The demo includes limitations: what AI support-answer service with 99.5% availability + TTFT SLO still will not do.

Bundle: contract snippet, passing tests, metric snapshot for slo:availability:ratio and burn_rate1h, security negative probe, rollback note, owner name. Reference SLO-VANITY-200-18 as the drill you rehearsed. If any item is missing, the ship gate fails even if the happy path dazzles.

For SLO lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint POST /v1/support/answer remains the production surface you operate for AI support-answer service with 99.5% availability + TTFT SLO — not a slide. Keep SLO-VANITY-200-18 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 SLO-VANITY-200-18 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 AI support-answer service with 99.5% availability + TTFT SLO, the human stakeholder is reliability owner gating releases on error budget, and the incident id you design against is SLO-VANITY-200-18. Re-state the oracle in your notes — 3% provider timeout for 20m trips fast-burn; monthly budget math matches calc-budget.py — and keep the invariant visible: bad events include malformed upstream + timeout fallbacks; auth 4xx excluded. Track slo:availability:ratio and burn_rate1h as the scoreboard. Surface under change control: POST /v1/support/answer. If you only have forty minutes, finish the fixture for HTTP 200 fallbacks counted as good while citations empty — vanity availability before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.