Skip to main content
Compendium · Compositions · Heroes

Heroes

Items
16
of 1002 total

Full-featured composed scenes — one per row so each design has room to breathe. Click for the live render, the spec, and the source.

№ 101

Three Paradigms

Scene STA
The Lineage 3 paradigms · 70 years

Three paradigms.
Three cost-equation shifts.

Each paradigm is a deliberate response to what the previous one made expensive. DoCoDeGo is the third in that lineage.

1956 Era 1 / 3

Waterfall

Solved
Formalised investigation. Sequential phases produced predictability where there was chaos.
Cost it created
Investigation cost. Every change became expensive to absorb once a phase had closed.
Chaos → Predictability
2001 Era 2 / 3

Agile

Solved
Iterated. Distributed investigation across short cycles, brought the customer into the loop.
Cost it created
Coordination cost. Standups, ceremonies, the certification industries that fed on them.
Predictive → Adaptive
2026 Era 3 / 3

DoCoDeGo

Solved
AI made investigation cheap. Intent became the highest-leverage human work.
Cost it created
We do not yet know. Honesty about that is part of the framework.
Implementation → Intent
// Each shift answers the previous era's accumulated cost — never refutes it.
Compositions / heroes

Three eras of how teams ship software — Waterfall, Agile, DoCoDeGo — as a full-bleed hero strip with scroll-revealed era cards, paradigm shift labels and a clockwise progression motif.

open ↗
№ 102

Manifesto Axiom

Scene STA
The Axiom
Three clauses · one thesis
  1. 01

    Intent is the primary artefact.

    // What we mean — written, versioned, owned.

  2. 02

    Implementation is a compiled derivative.

    // Code is the output of intent under constraint, not the source.

  3. 03

    Governance is earned through the loop.

    // Trust accrues from review cycles that actually closed.

DOcument · COmpose · DEmonstrate · GOvern

The four pillars compile from the axiom →

Compositions / heroes

The DoCoDeGo axiom rendered as an editorial hero — three clauses revealed in sequence, each anchored to its pillar accent, framed for the manifesto landing page.

open ↗
№ 103

Four Pillars Grid

Scene STA
The Four Pillars All load-bearing

Document · Compose · Demonstrate · Govern.

Four pillars, four human roles, four artefacts that must exist before the next one begins. Skip one and the loop breaks.

DO
DOcument
Human role
Author

Specification is the only source of truth.

What gets shipped

A versioned spec with intent, acceptance criteria, and failure modes.

Pillar 1 / 4
CO
COmpose
Human role
Architect

Human owns the architecture; AI implements it.

What gets shipped

Reviewed implementation that maps to architecture, not vibes.

Pillar 2 / 4
DE
DEmonstrate
Human role
Gatekeeper

Value flows at the speed of validation, not schedules.

What gets shipped

A passed acceptance run — proof intent was actually met.

Pillar 3 / 4
GO
GOvern
Human role
Governor

Autonomy without accountability is catastrophe.

What gets shipped

An audit trail and a sign-off that someone stands behind.

Pillar 4 / 4
// The pillars are sequential at first, then concurrent — each one earns the next.
Compositions / heroes

A 2×2 hero grid of the four DoCoDeGo pillars — each tile carries the human role, the principle, and what gets shipped — with cascading entrance and a lift-on-hover affordance.

open ↗
№ 104

Cost Equation Graph

Scene STA
The Cost Equation

Generation went to zero.
Validation did not move.

The crossover is when validation became the dominant cost. Everything DoCoDeGo asserts compiles from this graph.

  • Generation cost
  • Validation cost
  • Drift surface
COST 0 2010 2020 2025 2026 CALLOUT THE BOTTLENECK MOVED
Before crossover

Writing the code was the work.

After crossover

Proving the code meets intent is the work.

If validation lags

The drift surface is where incidents come from.

Compositions / heroes

An animated hero chart showing generation cost collapsing as AI matures while validation cost stays flat — the crossing point is the bottleneck moving, with a "the bottleneck moved" callout pinned to the drift surface.

open ↗
№ 105

Maturity Ladder (Vertical)

Scene STA
Maturity Ladder 4 rungs

A ladder, not a destination.

Each rung adds one pillar's load. Climb only when the rung below is paying off — and locate yourself honestly.

  1. 4

    Stage 4 — Autonomous

    Adds Full GO
    Who runs it

    Autonomous agent systems

    What that means

    Confidence thresholds, audit trails, kill switches. Humans bound the envelope.

  2. 3

    Stage 3 — Orchestrated

    Adds + GO (light)
    Who runs it

    Multi-agent, multi-team

    What that means

    Alignment checks, scope limits, agent monitoring. Humans still sign every release.

  3. 2

    Stage 2 — Collaborative

    Adds + DE
    Who runs it

    Growing team, shipping regularly

    What that means

    Validation-gated delivery. Observability proves intent landed in production.

    You are here →
  4. 1

    Stage 1 — Augmented

    Adds DO + CO
    Who runs it

    Any team, any size

    What that means

    Spec-first work. AI assists generation; humans review every change.

// Most teams sit at stage 1 or 2. That is the right answer for most work.
Compositions / heroes

A vertical four-rung maturity ladder — Augmented → Collaborative → Orchestrated → Autonomous — with a "you are here" callout, who-runs-it descriptors, and rung-by-rung reveal from the ground up.

open ↗
№ 1101

Axiom Hero

Scene STA go
DoCoDeGo Axiom 01

Human intent governs AI output.

The axiom is not a wish. It is a contract — and the four pillars are how the contract is kept.

Before Pre-AI

Humans write intent.

Humans write output.

The bottleneck was generation — and that is where every methodology lived.

After Post-AI

Humans write intent.

Humans write output.

Generation collapsed. Intent is the only thing left for a human to own.

Spec

Intent, written and versioned.

Audit

Output checked against intent.

Sign-off

A human stands behind the result.

// The axiom is enforced through artefacts, not intentions.
Compositions / heroes

A full-bleed hero stating the framework axiom — "Human intent governs AI output" — split into a monumental headline, an inversion explainer, and a triple-stamp evidence row.

open ↗
№ 1102

Four Pillar Hero

Scene STA
The Framework Four pillars, one loop

Document. Compose. Deliver. Govern.

DO
1 / 4

Document

Write the intent before the code.

CO
2 / 4

Compose

Architect the build; let AI render it.

DE
3 / 4

Deliver

Ship at the speed of validation.

GO
4 / 4

Govern

Earn autonomy through accountability.

// Each pillar earns the next; together they form a closed loop.
Compositions / heroes

A 2×2 hero of the four pillars — each tile carries letters, mandate, and the verb the pillar enforces — flanked by a description column that frames the whole as a compiler from intent to evidence.

open ↗
№ 1103

Paradigm Shift Hero

Scene STA de
The Shift Agile → DoCoDeGo

The rituals were the symptom. The signals were the work.

Every Agile ceremony was an attempt to surface a signal that the team could not measure directly. We can now measure it directly.

Before Agile rituals
  • Standup
  • Sprint
  • Retro
  • Backlog
  • Demo
After DoCoDeGo signals
  • Drift signal Drift is detected, not described.
  • Convergence cycle Cycle ends when intent is met.
  • After-action review Anchored in evidence, not feelings.
  • Spec queue Specs replace ticket archaeology.
  • Acceptance run Proof, not performance.

Ceremonies → Signals

Compositions / heroes

A before/after hero contrasting Agile rituals with DoCoDeGo signals — two columns side by side, an arrow between them, and a verdict strip that names the shift.

open ↗
№ 1104

Spec As Artefact Hero

Scene STA do
The Artefact Five files, one spec

A spec is not a paragraph. It is a small library.

Each file owns a different question — intent, proof, scope, investigation, sequence — and together they survive an AI's literal interpretation.

spec.md

Intent

What we mean, written and versioned.

File 1 / 5
assurance.md

Acceptance

How we will know the intent was met.

File 2 / 5
deliverables.md

Scope

The exact artefacts the build emits.

File 3 / 5
explore.md

Investigation

What we learned before committing to a plan.

File 4 / 5
plan.md

Sequence

The order in which the build unfolds.

File 5 / 5
// The spec is a directory, not a document.
Compositions / heroes

A hero presenting five artefacts a real spec carries — spec.md, assurance, deliverables, exploration, plan — as a row of hard-bordered cards under a single banner.

open ↗
№ 1105

Flow Not Schedule Hero

Scene STA de
DE · Deliver Flow, not schedule

Cycles close when intent is met. Not when the calendar says so.

Schedule
Wk 1–2
Sprint 1
Wk 3–4
Sprint 2
Wk 5–6
Sprint 3
Wk 7–8
Sprint 4

Fixed-length sprints terminate on a date, regardless of whether intent was met.

Flow
Signal closed
Signal closed
Signal closed

Cycles close on signal — convergence with intent, not the end of a fortnight.

Calendar → Convergence

Compositions / heroes

A hero contrasting calendar-driven sprints with signal-driven flow — a stamped-out sprint grid alongside a single live flow track, ending in a verdict band.

open ↗
№ 1106

Accountability Hero

Scene STA go
GO · Govern Four hats, four humans

Every artefact has a human behind it.

AI does the labour. A human still owns the call — and that human is named by a hat, not by a job title.

Author
DO

Writes the intent.

Hat 1 / 4
Architect
CO

Owns the build.

Hat 2 / 4
Gatekeeper
DE

Signs the proof.

Hat 3 / 4
Governor
GO

Holds the boundary.

Hat 4 / 4
Sign-off Four hats, four marks
Author Initial here
Architect Initial here
Gatekeeper Initial here
Governor Initial here
// A signature is not a formality — it is the boundary AI cannot cross.
Compositions / heroes

A hero displaying the four human hats — Author, Architect, Gatekeeper, Governor — as prominent stamped chips above a single accountability sentence and a sign-off strip.

open ↗
№ 1107

Signal Driven Hero

Scene STA co
CO · Compose Signal-driven

Signals replace ceremonies.

Every meeting was a poll. Now the readout is live — and the meeting is the exception, not the floor.

Drift Signal 1 / 4
18 %

0–100% intent gap

Replaces Standup.

Coverage Signal 2 / 4
82 %

0–100% spec mapped

Replaces Planning.

Latency Signal 3 / 4
41 h

0–168h intent → ship

Replaces Review.

Audit Signal 4 / 4
95 %

0–100% events captured

Replaces Retro.

// Meetings remained when the signals stopped agreeing. Until then, the dashboard governs.
Compositions / heroes

A hero where four live-looking signal meters (drift, coverage, latency, audit) replace the four meeting-shaped ceremonies they used to surface.

open ↗
№ 1108

Autonomy Spectrum Hero

Scene STA go
GO · Govern Autonomy spectrum

Autonomy is a setting. Pick the rung you can govern.

L1 Rung 1 / 4

Assisted

Human

Human writes; AI suggests.

AI scope

Inline completion.

L2 Rung 2 / 4

Supervised

Human

Human reviews every diff.

AI scope

Multi-file edits.

L3 Rung 3 / 4

Delegated

Human

Human reviews at task boundary.

AI scope

Whole tasks.

L4 Rung 4 / 4

Autonomous

Human

Human governs the envelope.

AI scope

Long-running goals.

// The rung is a contract — earn the next one through evidence, not enthusiasm.
Compositions / heroes

A horizontal autonomy banner with four labelled rungs — assisted, supervised, delegated, autonomous — under a single headline and a sentinel boundary marker.

open ↗
№ 1109

ROI Claim Hero

Scene STA co
ROI Cost equation, shifted

Generation collapsed. Validation did not. The bottleneck moved.

Generation Metric 1 / 2
−92%

cost per line, last 24 months

AI did the work humans used to do — and did it overnight.

Validation Metric 2 / 2
±0%

cost per accepted intent

No tool replaced a reviewer. Validation is still a human surface.

The bottleneck moved.

Generation → Validation

// The framework is what you adopt when the cost equation has already shifted under you.
Compositions / heroes

A hero stating the cost-equation shift in monumental type — generation cost falling, validation cost dominant — with a paired metric panel and a "the bottleneck moved" verdict.

open ↗
№ 1110

Intent Compiles Hero

Scene STA do
The Pipeline Intent → Evidence

Intent compiles to evidence.

Four stages, four pillars, one direction. The hero shows the compiler — the pillars are its passes.

Intent 1 / 4

Author writes the spec.

Plan 2 / 4

Architect sequences the build.

Build 3 / 4

AI labour, human review.

Evidence 4 / 4

Acceptance run is signed.

stdout compile · 1.2s
  • $ [do] spec.md parsed — 12 acceptance criteria
  • $ [co] plan.md sequenced — 4 stages, 0 conflicts
  • $ [de] build complete — 412 changes, 0 deferred
  • $ [go] sign-off recorded — 4 hats, 4 marks
  • $ ok — intent compiled to evidence
// Evidence is the artefact intent emits — nothing more, nothing less.
Compositions / heroes

A hero rendering "Intent compiles to evidence" as a four-stage pipeline — intent, plan, build, evidence — with arrows and a compiler-output strip.

open ↗
№ 1111

Governance Overlay Hero

Scene STA go
GO · Govern The outer frame

Govern the loop, not the labour.

GO is not a fourth step — it is the frame around the other three, observing what they emit and refusing to ship what it cannot vouch for.

GO · Governance Wraps DO · CO · DE
DO Inner 1 / 3

Spec authored, versioned, owned.

CO Inner 2 / 3

Build composed, reviewed, merged.

DE Inner 3 / 3

Acceptance run, evidence emitted.

Observed · audited · signed GO · Govern
Audit trail 5 events · 1 loop
  • T+0 spec accepted · 4 hats present
  • T+18m plan published · 0 unresolved threats
  • T+2h build cycle 1 closed · drift 4%
  • T+5h acceptance run passed · all criteria met
  • T+5h12 sign-off recorded · loop closed
// GO is the only pillar a vendor cannot ship for you.
Compositions / heroes

A hero where GO wraps a stacked row of DO/CO/DE as an outer governance frame — three inner tiles, one outer green border, and an audit-trail strip closing the composition.

open ↗
Alpha · Honest about it

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.

Two doors in
Join the Discord

Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.