Compendium · Compositions · Process Flows

Process Flows

Items

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.

Featured 14 Atoms 762 Compositions 240

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

№ 107

Spec Lifecycle

Scene STA

Spec Lifecycle 6 stages · 6 gates

From paragraph
to production.

A spec moves through six named stages. Each stage names its artefact, its owner, and the ICS gate that lets the baton continue.

Baton

01
Draft

Artefact

spec.md

Owner

Author

ICS ≥ 40
02
Review

Artefact

spec.md + diff

Owner

Author + peer

ICS ≥ 60
03
Approved

Artefact

spec @ v1.0

Owner

Architect

Sign-off
04
Composed

Artefact

PR + tests

Owner

Composer

CI green
05
Demonstrated

Artefact

Demo + telemetry

Owner

Gatekeeper

AC met
06
Governed

Artefact

AAR + GTR delta

Owner

Governor

No drift

№ 108

Maturity Journey

Scene STA

Maturity Journey 4 stages · each builds on the last

You don't adopt DoCoDeGo.
You climb it.

Every stage adds one capability. No stage is skipped — and no team is "behind" for sitting on a rung that fits them.

Current stage

2 / 4

STAGE 1 ✓ Done

Augmented

Any team, any size

What's added

DO + CO: spec-first, AI-assisted. Manual review.
STAGE 2 ◉ Here

Collaborative

Growing team, shipping regularly

What's added

+ DE: validation-gated delivery, observability

You are here
STAGE 3 ○ Ahead

Orchestrated

Multi-agent, multi-team

What's added

+ GO: alignment checks, scope limits, agent monitoring
STAGE 4 ○ Ahead

Autonomous

Autonomous agent systems

What's added

Full GO: confidence thresholds, audit trails, kill switches

№ 109

Governance Loop

Scene STA

Governance Loop continuous · never closes

Approval expires.
The loop does not.

Sign-off grants autonomy under a ceiling. Drift detection compares behaviour to intent. When drift crosses the threshold, the loop returns to re-sign — narrower, wider, or revoked.

Sign-off

Trigger: New spec or revised intent
Artefact: Approval record + scope

Autonomy ceiling

Trigger: Agent operating in scope
Artefact: Confidence + budget limits

Governance · continuous

III

Drift detection

Trigger: Telemetry vs intent diff
Artefact: Drift report + severity

Re-sign-off

Trigger: Drift over threshold
Artefact: Renewed approval or revoke

№ 110

AI Compose Cycle

Scene STA

Agent Trace approved spec → shipped PR

Six steps. Six signatures.
One PR.

Each named agent runs one operation, leaves one artefact, and hands the baton to the next. Total wall-clock from approved spec to merged change: ten to fifteen minutes — most of it spent waiting on the human review.

Total budget

~12 min

01
Read spec

Duration

~30s

Agent

reader-1.2

Output

Parsed intent + constraints
02
Reason

Duration

~2m

Agent

planner-4.7

Output

Plan + file diff outline
03
Produce PR

Duration

~6m

Agent

composer-4.7

Output

Branch + commits + PR
04
Self-check

Duration

~1m

Agent

checker-1.0

Output

CI green + ICS ≥ 75
05
Human review

Duration

human

Agent

Gatekeeper

Output

Approve / request changes
06
Ship

Duration

~1m

Agent

shipper-1.0

Output

Merged + deployed + AAR

✓ Shipped

№ 1121

Red Green Refactor Flow

Scene STA co

Red Green Refactor 4 phases · permanent loop

Fail first.
Pass minimally.
Shape it. Repeat.

The TDD loop is not a ceremony — it is the only honest way to prove a spec has teeth. Each phase has one job, one verb, one ledger state.

Loop pulse

01
Red

Intent

Write a failing test

Verb

add spec

1 failing · 0 passing
02
Green

Intent

Make it pass — minimum

Verb

add impl

0 failing · 1 passing
03
Refactor

Intent

Clean up without breaking

Verb

shape code

0 failing · 1 passing
04
Repeat

Intent

Next failing test

Verb

loop back

queue +1

№ 1122

Spec Grilling Flow

Scene STA do

Spec Grilling three acts · adversarial

Specs survive
by being attacked.

Pre · author readies. During · reviewers attack. After · author rewrites. The grilling is the work — the spec is the residue.

ICS delta

+38

01
Pre
Setup

Author submits the spec cold

Questions
- › Is the intent one sentence?
- › Are AC binary?
- › Is the failure mode named?
spec.md @ draft
02
During
Setup

Reviewers attack every claim

Questions
- › What does it not do?
- › How will it fail?
- › Who pays the cost?
spec.md + annotated diff
03
After
Setup

Author revises and re-submits

Questions
- › Was every question answered?
- › Did AC narrow?
- › Did scope shrink?
spec.md @ v1.0 + AAR

№ 1123

Plan Approval Flow

Scene STA go

Plan Approval 4 steps · 1 return loop

Plans don't pass.
They get re-passed.

Submit. Review. Revise. Approve. The loop between review and revise is the work — sign-off is just the bookmark that says the loop has stopped for now.

01
Submit

Actor

Author

Artefact

plan.md @ draft

Plan complete
02
Review

Actor

Reviewers

Artefact

plan.md + notes

Pass or return
03
Revise

Actor

Author

Artefact

plan.md @ rN

Address every note
04
Approve

Actor

Governor

Artefact

plan @ v1.0 + sig

Sign-off recorded

return loop · review ⇒ revise

№ 1124

Drift Routing Flow

Scene STA de

Drift Routing detect · classify · route

Drift is data,
not disaster.

Detect the delta. Classify by shape. Route to the queue that can act. Every drift has a destination — none gets lost.

Detection

Observed delta

spec.AC#4 → expected: idempotent
impl.observed: side-effect on retry

02
Classification
- Cosmetic
  
  no behaviour change
- Semantic
  
  AC moved, spec stale
- Structural
  
  failure mode unprovable
severity tag
03
Routing
- Auto-fix
  
  Composer · if cosmetic
- Human review
  
  Reviewer · if semantic
- Block
  
  Governor · if structural
queue write

№ 1125

Brownfield Archaeology Flow

Scene STA do

Brownfield Archaeology dig · write · characterise

The code is the artefact.
The intent is buried.

Find what the system does. Write the spec it should have had. Name the gap between the two. That gap is the backlog.

01
Find the code
- › Trace entry points
- › Walk call graph by usage
- › Read tests as oracles
inventory.csv

Write the spec

Spec scaffold

## Intent
What the code is for.

## AC
- [ ] Observed behaviour 1
- [ ] Observed behaviour 2

## Constraints
- Inherited from system

03
Characterise gaps
- Undocumented
  
  no spec yet
  
  14
- Contradicted
  
  spec disagrees with code
  
  3
- Orphan
  
  code without intent
  
  6
gap-report.md

№ 1126

Convention Extraction Flow

Scene STA co

Convention Extraction pattern · candidate · review · promote

Habits become rules
only on purpose.

A pattern is just repetition. A convention is repetition reviewed and signed off. The pipeline makes the difference deliberate.

Promotion ratio

11/27

01
Pattern

Artefact

observation log

Exit

≥3 recurrences

step 01
02
Candidate

Artefact

convention draft

Exit

AC + rationale

step 02
03
Review

Artefact

review notes

Exit

pass or kill

step 03
04
Promote

Artefact

convention @ v1.0

Exit

in canon · indexed

step 04

№ 1127

Release Gate Flow

Scene STA go

Release Gates 4 gates · all closed by default

A gate is evidence,
not a checkbox.

Build produces the binary. Audit produces the report. Sign-off produces the signatures. Deploy produces the rollout. Skip a gate, lose the chain.

01
Build

Artefact

binary + sbom

Criterion

reproducible · signed

Composer
02
Audit

Artefact

audit report

Criterion

no critical findings

Auditor
03
Sign-off

Artefact

release manifest

Criterion

two-key sign

Governor
04
Deploy

Artefact

live release

Criterion

rollback ready

Operator

№ 1128

Spec Lifecycle Flow

Scene STA do

Spec Lifecycle 4 stages · versioned · aged

Specs are born, lived,
and retired.

Draft is cheap. Review is honest. Impl is expensive. Archive is real. Every stage stamps a version and waits for its exit condition.

01
Draft

Version

v0.x

Age

0-14d

ICS ≥ 40
02
Review

Version

v0.x

Age

1-7d

ICS ≥ 60 · sign
03
Impl

Version

v1.x

Age

2-12w

AC met · GTR clear
04
Archive

Version

v∞

Age

forever

superseded or retired

№ 1129

Composition Pipeline Flow

Scene STA co

Composition Pipeline plan · execute · review

AI proposes.
AI executes.
Human signs.

The agent plans steps from the spec, runs them under a budgeted sandbox, and presents a diff. Human authority lives at one gate — review.

01
Plan

Input

spec.md @ approved

Action

propose steps + budget

Artefact

plan.json

budget · 5 min
02
Execute

Input

plan.json

Action

compose under sandbox

Artefact

PR + diff

budget · 30 min
03
Review

Input

PR + diff

Action

AC check + sign-off

Artefact

merge or kill

budget · 15 min

№ 1130

Governance Action Flow

Scene STA go

Governance Action anomaly · review · action · audit

Action without audit
did not happen.

Telemetry surfaces an anomaly. Review judges severity. Action chooses a response. Audit binds the decision to the record. Skip the audit step and the chain breaks.

01
Anomaly

Input

telemetry signal

Decision

is it real?

anomaly ticket
02
Review

Input

anomaly ticket

Decision

severity + ownership

review note
03
Action

Input

review note

Decision

fix · throttle · revoke

change record
04
Audit

Input

change record

Decision

sign + retain

audit-log.jsonl

№ 1131

Continuous Convergence Flow

Scene STA de

Continuous Convergence 4 beats · permanent loop

Small batches.
Permanent loop.

Observe. Compare. Adjust. Redeploy. The cycle never closes — it just keeps catching the next delta before it becomes a disaster.

Median cycle

42m

01
Observe

Action

collect signals

Artefact

telemetry slice

continuous
02
Compare

Action

diff vs intent

Artefact

delta report

< 5 min
03
Adjust

Action

small patch · small risk

Artefact

PR · scoped

< 1 day
04
Redeploy

Action

ship + watch

Artefact

release · v+1

< 1 hour

loop · redeploy ⇒ observe

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

Process Flows

Augmented

Collaborative

Orchestrated

Autonomous

The framework is real.The community is forming now.

The framework is real.
The community is forming now.