Done means your team can run it without us

1. evals/1/6

   An evaluation suite that runs in CI

   • A golden set of real cases with the expected answer written down.
   • Every prompt, model or retrieval change is judged against it in CI.
   • A regression shows up in the build, not in a demo.
2. infra/2/6

   Infrastructure as code, versioned and reversible

   • Your Google Cloud project, your identity provider, your logging.
   • Model and prompt deploys are versioned and reversible.
   • The rollback path is documented in the runbook.
3. RUNBOOK.md3/6

   A runbook written for the person on call

   • Each alert: what it means, the first action, the rollback command, who to call.
   • How to operate, monitor, and roll back.
   • What “normal” looks like on the dashboards.
4. decisions/4/6

   One record per model, prompt and data decision

   • What was chosen, what was rejected, and the evidence from the evaluation suite.
   • Data-handling implications reviewed before production.
   • Written so your team can defend the decision later without us.
5. dashboards5/6

   Cost, latency and quality your team reviews weekly

   • Cost and latency, reviewed weekly by your team.
   • Quality from the evaluation suite over time, not a one-off demo.
   • Alerting and runbooks in place before launch.
6. your repo6/6

   All of it in your repositories and accounts from the first commit

   • Nothing transfers at the end because nothing ever left.
   • A repository with a green build.
   • Your engineers pair with ours until they run it alone.

The boxes are for you. Nothing is stored or sent. Print the page to keep a copy.