Run acceptance tests and make the ship call

From a fresh clone/directory, run the commands that prove ship v1.2.0: smoke+readyz pass; kill switch drill < 60s; on-call roster non-empty. A second person plays solo builder operating pka.example for 50 beta users and follows your script without coaching. The demo includes limitations: what Personal Knowledge Assistant API with flags, probes, secrets, on-call owner still will not do.

Bundle: contract snippet, passing tests, metric snapshot for readyz_ok, kill_switch_seconds, secret_age_days ≤ 30, security negative probe, rollback note, owner name. Reference CAP-OPS-PKA-12 as the drill you rehearsed. If any item is missing, the ship gate fails even if the happy path dazzles.

For Capstone ops lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint https://pka.example/v1/ask remains the production surface you operate for Personal Knowledge Assistant API with flags, probes, secrets, on-call owner — not a slide. Keep CAP-OPS-PKA-12 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 CAP-OPS-PKA-12 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 Personal Knowledge Assistant API with flags, probes, secrets, on-call owner, the human stakeholder is solo builder operating pka.example for 50 beta users, and the incident id you design against is CAP-OPS-PKA-12. Re-state the oracle in your notes — ship v1.2.0: smoke+readyz pass; kill switch drill < 60s; on-call roster non-empty — and keep the invariant visible: versioned release with readyz, flag kill switch, rotated secret, named on-call. Track readyz_ok, kill_switch_seconds, secret_age_days ≤ 30 as the scoreboard. Surface under change control: https://pka.example/v1/ask. If you only have forty minutes, finish the fixture for app runs on laptop only — no probes, no owner, secret in .env committed before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.