Mastery: ship checklist

From a fresh clone/directory, run the commands that prove replay day shows −32% $ with groundedness drop ≤ 0.01 vs all-frontier baseline. A second person plays finance partner capping July LLM spend at $12k and follows your script without coaching. The demo includes limitations: what token+router cost controller for mixed FAQ vs complex research traffic still will not do.

Bundle: contract snippet, passing tests, metric snapshot for usd_per_successful_answer and groundedness, security negative probe, rollback note, owner name. Reference COST-ROUTER-MISCLASS-14 as the drill you rehearsed. If any item is missing, the ship gate fails even if the happy path dazzles.

For Cost optimization lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint POST /v1/answer remains the production surface you operate for token+router cost controller for mixed FAQ vs complex research traffic — not a slide. Keep COST-ROUTER-MISCLASS-14 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 COST-ROUTER-MISCLASS-14 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 token+router cost controller for mixed FAQ vs complex research traffic, the human stakeholder is finance partner capping July LLM spend at $12k, and the incident id you design against is COST-ROUTER-MISCLASS-14. Re-state the oracle in your notes — replay day shows −32% $ with groundedness drop ≤ 0.01 vs all-frontier baseline — and keep the invariant visible: simple FAQs route to mini model; monthly forecast alerts at 80% budget. Track usd_per_successful_answer and groundedness as the scoreboard. Surface under change control: POST /v1/answer. If you only have forty minutes, finish the fixture for router sends long research prompts to mini — quality collapses, retries inflate spend before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.