Canary and operate postmortems

From a fresh clone/directory, run the commands that prove postmortem published with 3 actions; action A1 verified by test that fails on old tokenizer pin. A second person plays EM facilitating review of INC-SUM-TOK-87 and follows your script without coaching. The demo includes limitations: what blameless postmortem for tokenizer-induced summarization outage still will not do.

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

For Postmortem lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint summarization service remains the production surface you operate for blameless postmortem for tokenizer-induced summarization outage — not a slide. Keep INC-SUM-TOK-87 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-SUM-TOK-87 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 blameless postmortem for tokenizer-induced summarization outage, the human stakeholder is EM facilitating review of INC-SUM-TOK-87, and the incident id you design against is INC-SUM-TOK-87. Re-state the oracle in your notes — postmortem published with 3 actions; action A1 verified by test that fails on old tokenizer pin — and keep the invariant visible: actions are owned, dated, verifiable; contributing factors include process not only code. Track actions_closed_on_time and recurrence_90d as the scoreboard. Surface under change control: summarization service. If you only have forty minutes, finish the fixture for action 'be more careful' with no owner — recurrence in 6 weeks before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.