Scenarios
Two control points, one dependency
New saved-views feature: a fresh API endpoint plus the UI that calls it. Outcome: shipped · 3 days. 4 held · 0 adaptations · 0 escapes
one control point a woven topology
“a one-line bugfix” ●shipped · 41 min“a CLI release to every laptop” ↶re-pinned in 51 s · then shipped“a mobile feature stuck behind store review” ●shipped · one binary“a rewrite that claims it’s 10× faster” ●proven · 2.1M comparisons“a risky change to a feature most orgs ignore” ●verdict · 5 h“a new skill for your agent fleet” ●fleet-wide · 0 broken sessions“a feature that spans API and UI” ●shipped · 3 days“one contract across three services” ●zero drift · one 40-min hold“a feature built on another feature” ●2 ships · 1 graph“the change that looked safe” ↶reversed · 43 s
saved-views-fe-be
UI NEVER 404EDTwo control points, one dependency
New saved-views feature: a fresh API endpoint plus the UI that calls it.
The plan — drafted before anyone saw it
Strategy Two control points, sequenced — API dark-launches, UI never leads it
Control points views-api + webapp, parent-child sequence
Gates API 100% dark · 24 h of synthetic calls green
Guardrails 404 rate · endpoint p95 · adoption
Rollback either point breaches → both step back together
Ramp — planned outline, actual fill
dark
10%
50%
100%
The run — from the decision log
T+0m read: diff spans views-api and webapp — UI 404s without the endpointheld
T+2h ramped: API to 100% dark; synthetic calls green for 24 hheld
T+1d identified: feature cohort: 214 dashboard power users — the UI opens thereheld
T+3d done: UI at 100% against an endpoint already proven darkheld
4 held · 0 adaptations · 0 escapes
learnedendpoint-leads-UI saved as this repo’s coordinated-pair template.