200apps · how we work · volume v of v

◔ After We Build

The loop closing. Watching the first hours, checking the prediction against reality, classifying bugs by which level of the chain produced them, learning from incidents, writing the model update, growing the team, reading the portfolio — and starting the next cycle from a less wrong place than this one.

Read the opening →

---

Part One — The First 48 Hours

The period between the flag being enabled and the first honest picture.

• The First 48 Hours — what to watch, when to act

Part Two — Signal and the Prediction

The check that was promised before the cycle ran. Four outcomes — three are valuable.

• Signal and the Prediction — running the check, the four outcomes, the signal reading

Part Three — Bugs and Their Roots

Every defect traces to a level of the chain. Six dimensions classify it.

• Bugs and Their Roots — defects vs bugs, the two-question rule
• Severity × Impact — priority auto-calculated, the four other dimensions
• Root causes — operational and chain-aware — the two layers
• Worked example — the wallet balance bug

Part Four — Incidents and Postmortems

Contain before diagnose. Postmortems that produce structural changes, not feelings.

• Incidents and Postmortems — the process, escalation matrix
• The postmortem and de-escalation
• Worked example — the JWT outage

Part Five — The Retrospective

Three questions. One change. Compounding rather than listing.

• The Retrospective — held / broke / one change

Part Six — The Model Update

The step most teams skip. Where learning survives the conversation.

• The Model Update — what gets updated, and where

Part Seven — The Ongoing Relationship

Where the chain meets the people who pay for it.

• The Ongoing Relationship — three support levels, support-to-bug pipeline
• The SLA — the operational contract — SLO→SLA, breach protocol
• Helpdesk metrics as chain signals — and the SLA review cadence
• Client cadence — weekly · bi-weekly · quarterly

Part Eight — The Team

The chain is operated by people.

• The Team — onboarding, T-shaped, small teams
• The human side — psychological safety, departures, joining

Part Nine — The Portfolio

The view across features and products.

• The Portfolio — DORA, technical debt as chain gaps, VRI
• Client trust and when to stop

Part Ten — Adoption

How to start. Which practice first. The minimum viable chain.

• Adoption — the 5-step practice sequence
• Resistance and maturity

Closing

• The Loop — five volumes, one cycle, the model update reopens the loop

---

Supplementary

Pre-restructure corpus pages preserved while their operational depth is absorbed into the source-aligned pages above. The /cycle/did-we-serve/ pages are also kept available for stable inbound links — their content is folded into Parts Seven through Ten above.

Did We Serve? — pre-restructure index · Ongoing Relationship (legacy) · Team (legacy) · Portfolio (legacy) · Adoption (legacy)