Canary and operate runbooks

From a fresh clone/directory, run the commands that prove drill INC-INGEST-9021: lag 60→5 minutes in ≤ 25m following runbook v1.4. A second person plays secondary on-call clearing ingest.lag_minutes > 45 and follows your script without coaching. The demo includes limitations: what executable queue-backlog runbook for embedding ingestion pipeline still will not do.

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

For Runbook lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint ingest worker + queue metrics remains the production surface you operate for executable queue-backlog runbook for embedding ingestion pipeline — not a slide. Keep INC-INGEST-9021 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-INGEST-9021 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 executable queue-backlog runbook for embedding ingestion pipeline, the human stakeholder is secondary on-call clearing ingest.lag_minutes > 45, and the incident id you design against is INC-INGEST-9021. Re-state the oracle in your notes — drill INC-INGEST-9021: lag 60→5 minutes in ≤ 25m following runbook v1.4 — and keep the invariant visible: every command is copy-pasteable; mutating steps need change ticket; verify after each step. Track drill_completion_minutes and lag_minutes as the scoreboard. Surface under change control: ingest worker + queue metrics. If you only have forty minutes, finish the fixture for runbook says 'restart something' without naming deployment or verifying lag before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.