Day 99: Capstone Build Week Checklist

Day 99: Capstone Build Week Checklist

Capstone Build Week Checklist

You have a spec (Day 98). This is the build-week gate list — security, traces, budgets, dual control, docs — before anyone schedules a demo.

⚡ TL;DR: Do not demo what you cannot kill, trace, budget, or roll back. Walk this checklist daily. Red items block Day 100.

Daily board

Area Gate Owner
Auth Service identity only; no god keys Platform
Tools Allowlist + dry-run default Squad
Dual control Mutate requires second human Squad
Traces OTel from UI → gateway → model → tool Platform
Budgets Hard reject at cap Platform
Prompts Pinned version in gateway Squad
Eval CI green on golden set Squad
Kill switch Flag tested in staging Both
Docs README + runbook + ADR Squad
Privacy Redaction on logs/memory Both
# ✅ Pre-demo smoke
curl -f "$GATEWAY/health"
curl -f "$GATEWAY/v1/complete" -H "Authorization: Bearer $TOK" -d @fixtures/golden1.json
# expect: trace id header, cost dims logged, dry-run tools only

Red-flag stops

  • Mutate tool reachable without dual control
  • No tenant filter on retrieval
  • Prompt edited live in prod console
  • Eval suite skipped “for speed”
  • Kill switch never flipped in staging

Failure modes

Green CI with empty golden set. Require minimum N cases and a coverage note (injection, throttle, happy path). Staging that uses prod IAM “temporarily” — block demo if so.

Closing checklist

  • [ ] All table gates green or waived in writing
  • [ ] Staging demo rehearsal recorded
  • [ ] Rollback exercised once
  • [ ] Cost dashboard shows the feature tag
  • [ ] On-call briefed on kill switch names

Series navigation

Day 98: Capstone Spec: Pick One Production Problem · Day 100: Capstone Ship: Demo, Postmortem, Next 90 Days

Last updated September 11, 2026


Discover more from CheatCoders

Subscribe to get the latest posts sent to your email.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply