Day 100: Capstone Ship: Demo, Postmortem, Next 90 Days

Capstone Ship: Demo, Postmortem, Next 90 Days

Ship day is not a slide deck. Demo the real path, capture what broke, freeze v1, and schedule the boring work that keeps it alive.

⚡ TL;DR: Demo on staging/prod-with-flag with traces visible. Write a short postmortem even if it “went fine.” Freeze prompt/tool versions. Publish a 90-day roadmap: eval growth, cost, hardening — not ten new agents.

Demo script (30–40 min)

1. Problem + non-goals (2 min)
2. Diagram + trust boundaries (5)
3. Live happy path with trace link (10)
4. Failure path: injection or throttle → safe refuse (5)
5. Kill switch / rollback (3)
6. Eval + cost dashboard (5)
7. Ask for freeze decision (5)

## v1 Freeze record
- Prompt pin: prompt_x@vN
- Tool allowlist SHA: ...
- Flag: feature_capstone=true (squads: ...)
- Owners: ...
- Review date: +30 days

Postmortem light (same day)

## What went well
## What broke (even small)
## Metrics vs SLO
## Customer/user risk
## Actions (owners, dates)

Next 90 days (boring on purpose)

❌ Celebrating ship by starting three unrelated agents next week.

Failure modes

Demo heroics on a laptop with local env vars nobody else has. Rehearse from a clean staging identity. Skipping postmortem because “it worked” loses the learning — still write five bullets.

Closing checklist

• [ ] Demo completed with trace evidence
• [ ] v1 freeze record filed
• [ ] Postmortem notes published internally
• [ ] 90-day roadmap agreed with owners
• [ ] Kill switch and on-call docs linked from the runbook
• [ ] You finished the 100-day bootcamp — keep the rails, not the hype

Series navigation

Day 99: Capstone Build Week Checklist

Last updated September 11, 2026