- ✓
- 2
- 3
- 4
Maturity & Process
Atomic primitives in the maturity & process family. Click any tile for the live render, the spec it was built from, and the code that fell out.
- 4 AutonomousAgent systems
- 3 OrchestratedMulti-team AI
- 2 CollaborativeShipping team
- ✓ AugmentedSpec-first start
- ✓ Augmentedhuman drives
- ✓ Supervisedreview each
- 3 Boundedscoped autonomy
- 4 Strategicagent-led
- ×
- ×
- DRAFTED
- APPROVED
- BUILT
- OPERATING
- RETIRED
// audit cycle 12 · scorecard
- spec coverage ··· 88%
- drift handled ··· 92%
- ceremony hit ··· 76%
- autonomy rung ·· supervised
// metric · ICS-threshold
Threshold last calibrated when team size was 6 and cycle was weekly. Both have since changed. Drift in the ground truth.
last calibrated → 2026-02-12
- SOLO
- SMALL
- MEDIUM
- LARGE
- ENTERPRISE
- DAILY
- WEEKLY
- BIWEEKLY
- MONTHLY
- QUARTERLY
- SPEC-014 ICS scorer v2
- SPEC-021 threat validator
- SPEC-019 GTR dashboard (carry)
Threat templates need worked examples before they bind reviewers.
- 08:02 SPEC @author SPEC-014 opened
- 09:17 COMP @claude compose pr#218
- 10:41 VAL+ @platform AC 7/7 green
- 11:03 GOV @gatekeep gate approved
- 11:08 SHIP @cd v0.4.0 deployed
- 11:09 AAR @team cycle logged
Threat templates need worked examples before they bind reviewers.
AC #4 conflates rate-limit with quota. Split or collapse?
- feature-flagged at 10% rollout
- GTR breaker armed at 95% AC pass
REVIEW-118 / SPEC-038
AC #4 conflates rate-limit with quota. Split into two acceptance criteria, or fold quota into a constraint. Either route is fine — pick one and resubmit.
roles, not people
Split AC #4 into rate-limit + quota acceptance criteria
not a calendar · pressure-driven
Re-grill SPEC-038; consider rate-limit tightening.
// trigger pip
on: spec.mergedStep arms when the upstream signal fires. No clock, no standup.
CARD-118 / SPEC-044
Compose stage emitting tokens, validator subscribed, ship signal idle. Card moves the moment validate.passed publishes.
CARD-091 / waiting
Awaiting threat-review.signed from governance. Upstream queue depth 2. No work in progress on this card since the signal arms.
// step status
waiting on validate.passedThe step is subscribed; arrival of the named signal advances flow.
// lane: compose-on-demand
Lane stays cold until demand pulls. The notch fires the trigger; the arrow shows direction of pull.
// assignment model
Pull is the framework default. Push remains available for legacy lanes; teams should audit any push-mode work monthly.
// lane: validate
WIP 3 /4SATURATING
Pulls into this lane pause once current reaches the limit. The cap forces closure before opening.
CARD-074 / SPEC-039
Cycle began on pull at 09:12, validate.passed published at 18:47. Unit moved through five stations without re-entry.
// rebalance
capacity rebalance · governance act
The framework is real.
The community is forming now.
DoCoDeGo is in Alpha. The framework is documented, the practices are battle-tested at small scale, and the next release is being shaped in public.
If it produces anything, it should produce engineers and teams who think more clearly about what they are building and why.
Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.