Canary and operate on-call operations

From a fresh clone/directory, run the commands that prove game day: primary misses ACK → secondary owns INC-OC-554 in 15m with access grant. A second person plays primary engineer receiving SEV2 after hours and follows your script without coaching. The demo includes limitations: what humane escalation path for production AI answer platform still will not do.

Bundle: contract snippet, passing tests, metric snapshot for ack_minutes and pages_per_week, security negative probe, rollback note, owner name. Reference INC-OC-554 as the drill you rehearsed. If any item is missing, the ship gate fails even if the happy path dazzles.

For On-call lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint PagerDuty schedule ai-answer-primary remains the production surface you operate for humane escalation path for production AI answer platform — not a slide. Keep INC-OC-554 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 INC-OC-554 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 humane escalation path for production AI answer platform, the human stakeholder is primary engineer receiving SEV2 after hours, and the incident id you design against is INC-OC-554. Re-state the oracle in your notes — game day: primary misses ACK → secondary owns INC-OC-554 in 15m with access grant — and keep the invariant visible: missed ACK in 15m escalates; SEV1 pages dual; handoff includes timeline + next action. Track ack_minutes and pages_per_week as the scoreboard. Surface under change control: PagerDuty schedule ai-answer-primary. If you only have forty minutes, finish the fixture for everyone paged for SEV3 noise → real SEV1 ignored before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.