Glossary
Every acronym, every metric, every threshold. Short form, full form, meaning. If a term appears anywhere on this site, it is defined here.
- AARAgent Alignment RateGO pillar
Percentage of AI agent outputs that pass acceptance criteria on first attempt, without regeneration or human correction.
Threshold: ≥ 70 %
- COCOmposeCO pillar
The judgment about what to build — human owns architecture; AI implements within it.
- DDLDrift Detection LatencyGO pillar
Elapsed time between when behavioural drift begins and when it is detected by governance processes.
Threshold: Trending down
- DEDEmonstrateDE pillar
The willingness to stop when what is being built does not match intent — value flows at the speed of validation.
- DODOcumentDO pillar
The clarity to say what you mean — specification as command interface for AI agents.
- DoCoDeGoDOcument · COmpose · DEmonstrate · GOvernWhole framework
The four pillars in order; also an anagram of "Good Code".
- GOGOvernGO pillar
The commitment to stand behind what was built — autonomy with accountability.
- GTRGovernance Trigger RateGO pillar
Percentage of delivery cycles that required governance escalation — a kill-switch event, an Intent Review override, or a spec-conflict resolution.
Threshold: < 10 %
- ICSIntent Clarity ScoreDO pillar
A 0–100 rubric-based score measuring spec quality across completeness, testability, unambiguity, and threat coverage.
Threshold: ≥ 60 to begin composition
- IRAFIntent → Reasoning → Action → FeedbackDE pillar
The delivery cycle model used in the DE pillar. Each cycle begins with approved intent, proceeds through agent reasoning, executes a demonstration, and returns feedback to governance and intent.
- RCRegeneration ConfidenceCO pillar
Verified confidence that a system regenerated from an updated spec matches the prior version in all unmodified areas — a checklist of behavioural, integration, and invariant tests.
Threshold: ≥ 90 % before production
- SDLSpec-to-Delivery LatencyDE pillar
Elapsed time from specification approval to first production deployment of the specified behaviour.
Threshold: Trending down
The canonical glossary in the framework repo defines additional terms (Drift, Intent Archaeology, Same-Person Rule, Kill-Switch, Provenance, and others) that appear in the operational practice docs. Those are documented inline on their relevant practice pages.
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.
Discord is where specs are debated, the framework gets sharper, and decisions land in writing. The conversation is the artefact.