Skip to main content
Compendium · Compositions

Compositions

Scenes
240
of 1002 total · 15 families

Full-featured composed scenes — heroes, dashboards, marketing sections, onboarding flows. Each family below opens onto its own page.

Featured 14 Atoms 762 Compositions 240
The Headline · #101

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.

All heroes →
№ 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 ↗
The fifteen families

Pick a family

Each family is a different kind of composition. Heroes are the page-covers; dashboards are the consoles; case studies are the stories.

  1. 01
    Heroes

    Full-bleed hero strips — the page-cover shots.

    Scenes
    16 →
  2. 02
    Process Flows

    Phase-strip walkthroughs of multi-step DoCoDeGo processes.

    Scenes
    16 →
  3. 03
    Comparison Strips

    Two-column or matrix layouts that frame a decision.

    Scenes
    16 →
  4. 04
    Dashboards

    Operational consoles — signals, queues, controls.

    Scenes
    16 →
  5. 05
    Feature Panels

    Focused feature explainers — what it is, what you get.

    Scenes
    16 →
  6. 06
    Marketing Sections

    Landing-page sections — why now, who for, proof points.

    Scenes
    16 →
  7. 07
    Onboarding

    Day-one paths — checklists, wizards, walkthroughs.

    Scenes
    16 →
  8. 08
    Audit & Telemetry

    Audit chains, postmortems, telemetry explorers.

    Scenes
    16 →
  9. 09
    Pillar Layouts

    DO / CO / DE / GO deep-dives and quartets.

    Scenes
    16 →
  10. 10
    Case Studies

    Anonymised stories — greenfield, brownfield, pivots.

    Scenes
    16 →
  11. 11
    Score Rubrics

    ICS, CCS, SDS and other rubrics explained.

    Scenes
    16 →
  12. 12
    Autonomy Ladders

    L1 → L4 autonomy levels and their boundaries.

    Scenes
    16 →
  13. 13
    Hat Orchestration

    How the four hats distribute across team shapes.

    Scenes
    16 →
  14. 14
    Worked Examples

    Concrete stories: notification service, contract, brief.

    Scenes
    16 →
  15. 15
    Signal Trends

    AAR / GTR / SDL / DDL trend dashboards.

    Scenes
    16 →
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.