Atomic primitives — single-concern components. Pick a category below to drill in.
A single approved specification with ICS score, version pin and acceptance criteria — the framework's atomic unit of work.
Issue a session for verified Google identities. Reject everything else without disclosing why.
Each category is a family of atomic components sharing a concern. Click through to see the full set.
Spec cards, ICS gauges, intent statements, lifecycle states.
Pillar tiles, role badges, hat identifiers, loops.
Stage indicators, AAR/GTR receipts, instruments, flow signals.
Kill-switches, autonomy sliders, audit trails, sign-off chips.
Agent cards, confidence meters, reasoning traces, handoffs.
Charts, gauges, badges, strips — at-a-glance signal.
Text inputs, pickers, builders, sliders — the authoring layer.
Pillar nav, command palette, breadcrumbs, tabs.
Era cards, paradigm markers, version timelines.
Alerts, stamps, empty states, confirmation prompts.
Drift signals, change routing, retroactive specs, conventions.
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.