as we build — opening
Opening
What We Shape ended with a slice — stories ready, scenarios defended, ADRs current, the technical drawings on the wall. After We Build opens with the flag enabled. This phase is the work that fills the gap.
Execution is where most teams operate by default. It is the part of the chain that has the most tools, the most automation, the most visible progress. The corpus's discipline in this phase is not to invent more tooling — the world has plenty — but to keep the machinery aligned with the chain. The pipeline catches different levels of mistake at different stages. The release gate is not a meeting; it is a state. The runbook is not paperwork; it is the on-call's only friend at 3am.
Execution is the work of carrying a prediction from a signed brief through code, test, integration, and release — without losing the meaning that was named in Before We Build.
What this phase covers
Nine parts.
- Domain Language in Code — the names from the brief survive the trip into the codebase.
- Trunk-Based Development — short-lived branches, continuous integration.
- Feature Flags — wrapping new behavior; rollback is one switch.
- The CI/CD Pipeline — six stages, each catching a different chain level.
- Testing Layers — unit, contract, integration, visual regression — each for a different gap.
- Release Gate — the named conditions the chain must satisfy.
- Gradual Rollout — pilot, percentage ramp, full enablement.
- Runbooks & Rollback — written before the incident, rehearsed in staging.
- Observability — logs, traces, metrics, events. The instrumentation After We Build reads.