Volume I Demonstrations · DE Pillar · 1002 live components

The Compendium

Every component is a DoCoDeGo specification compiled into a working artefact.
Live, spec, code — wired to the intent that produced them.

Built

1002

762 atoms · 240 scenes

⌕ Search the library 1002 Browse 762 atoms Browse 240 scenes

№ 101 · The Headline

Three Paradigms

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 full detail

№ 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.

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.

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.

Section II · The Quartet

Four pillars,
four atoms.

The smallest unit of the framework's vocabulary, rendered four ways. DO documents. CO composes. DE demonstrates. GO governs.

Document DO · #001

#001 do

SPEC-014 v1.3.0

@author

Authenticate via OAuth

Issue a session for verified Google identities. Reject everything else without disclosing why.

Verified emails create a session
Unverified emails are rejected silently
Sessions expire after 24 hours

SEALED

Compose CO · #017

#017 co

Dept. № II

Architect

COmpose

Charter

Human owns the architecture; AI implements it.

Pillar II

✓

Issued · Charter Office

Seal · CO-002

Demonstrate DE · #002

#002 de

ICS READY

Govern GO · #004

#004 go

EXHIBIT B / THREAT MODEL v1.3.0

SEV	THREAT	MITIGATION	OUT-OF-SCOPE
HIGH	Credential stuffing on /auth	Rate-limit + lockout @ 10/min	Botnet behind residential proxies
MED	Session token replay	Bind to UA + IP fingerprint	Mobile NAT roaming churn
LOW	OAuth open-redirect	Allowlist redirect domains	Subdomain takeover detection
HIGH	PII in error responses	Sanitise + opaque error codes	Error timing oracles

Section III · The Index

12 families.
Pick one.

Each family is a self-contained concern. Click through to its dedicated page — no scrolling past dozens you don't care about.

⌕ Or search them all

Section IV · Triptych

Three scenes
from the library.

A process flow, a dashboard, a scoring rubric — three families, three different visual registers.

All 240 compositions

Scene 01 / 03 · process-flows

№ 106

IRAF Expanded

Scene STA

Procedure № IRAF cyclic · four signatures

Every loop turn
has a contract.

Intent, Reasoning, Action, Feedback. At each stage a human owns a decision, an agent does the labour, and an artefact is signed before the baton passes.

Turn count

∞

Intent

DECLARE

Human: Authors the spec — intent, acceptance, constraints, failure modes.
AI: Drafts spec scaffolds, flags ambiguity, scores ICS.

Reasoning

DELIBERATE

Human: Architects the approach — picks the design within the spec’s constraints.
AI: Generates plan, surfaces trade-offs, simulates likely failure modes.

III

Action

EXECUTE

Human: Owns the merge gate. Reads the PR, asks the awkward questions.
AI: Writes the change, runs tests, opens the PR, self-reviews against spec.

Feedback

REVIEW

Human: Decides whether intent was met, whether to widen autonomy, where to clamp it.
AI: Logs telemetry, drafts AAR, surfaces drift against approved spec.

Scene 02 / 03 · dashboards

№ 116

Governance Dashboard

Scene STA

Governance · LIVE tenant · acme-prod

14:02:14 UTC · uptime 41d

// Drift · intent vs impl

34% Watch

// Autonomy ceiling

62% L2 · Review-gated

SuggestReviewAuto

// Kill switch

armed · 2-key

// Sign-off queue

3 pending

SPEC-019 @author 4m
SPEC-021 @gatekeeper 11m
SPEC-024 @ari 38m

// Audit trail · live tail

last 5

14:02:11 agent-04A wrote auth-handler.ts
14:01:48 agent-02B requested human sign-off
14:01:09 governor raised ceiling SPEC-019 → L3
14:00:31 agent-01A reasoning · SPEC-021 §2
13:59:55 agent-03C blocked · ambiguous AC #4

Scene 03 / 03 · score-rubrics

№ 1301

ICS Explainer

Scene STA do

DO · Rubric ICS · v2

Intent Completion Score
four dimensions. one number.

Aggregate

79/100

DEVELOPING

C Completeness

w · 30

All five canonical sections present and non-empty.

Sample sub-score 26/30

T Testability

w · 25

Each acceptance criterion is independently verifiable.

Sample sub-score 21/25

U Unambiguity

w · 25

No "should", "where appropriate", or pronoun ambiguity.

Sample sub-score 18/25

X Threat coverage

w · 20

STRIDE classes named, abuse cases enumerated.

Sample sub-score 14/20

// Formula


ICS = 1.0·C(30) + 1.0·T(25) + 1.0·U(25) + 1.0·X(20)

band(ICS): READY ≥ 85 · DEVELOPING ≥ 60 · UNFIT < 60

— Full detail →

—

// source

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.

The Compendium

Waterfall

Agile

DoCoDeGo

Authenticate via OAuth

The framework is real.The community is forming now.

The framework is real.
The community is forming now.