The Twelve Statutes
The foundational laws that govern the DoCoDeGo framework. Immutable, actionable, non-negotiable.
The Statutes
These are the immutable laws that guide every DoCoDeGo implementation. They are not guidelines — they are statutes.
Intent Is Absolute
Never exceed specification. Refine intent, don't patch symptoms.
When AI output doesn't match what you wanted, the fix isn't to patch the code — it's to improve the specification that led to the wrong output. The specification is the source of truth.
→ Halt delivery, surface reasoning trace, refine specification
Code Is Regenerable
Preserve logic, not code. Regenerate from improved intent.
Code is increasingly disposable. When you need changes, regenerate from an improved specification rather than patching existing code. Preserve invariants, not syntax.
→ Cross-validate against independent sources, freeze spec updates on anomalies
The Spec Is the Contract
Every interaction begins with structured specification.
No agent should begin work without a clear, structured specification. This is the contract between human intent and AI execution. Ambiguity here creates defects everywhere.
→ Surface the ambiguous section, clarify, then regenerate
Zero-Latency Evolution
Changes deliver as fast as validation permits. No release days.
When intent is updated and governance passes, delivery should be immediate. No artificial delays. The bottleneck is validation speed, not calendar coordination.
→ Automatic rollback to last known-good, no partial state without human authorization
The Human as Governor
Humans are stewards. Primary skill: clarity of thought.
The human's primary role shifts from writing code to governing systems. Your most valuable contribution is clear thinking about what should be built and why.
→ Escalate to human with full context — automated systems must never resolve governance conflicts autonomously
Transparent Reasoning
Every agent produces auditable traces. No black boxes.
Every AI action must produce a reasoning trace that can be audited. You should always be able to understand why an agent made a decision.
→ Full trace audit, identify decision point, escalate with context
Quality Through Context
AI succeeds with complete context. Ambiguity causes defects.
AI output quality is directly proportional to context quality. Incomplete or ambiguous specifications produce poor results. Invest in comprehensive context.
→ Review specification for gaps, add missing context, regenerate
Resilience Over Robustness
Design for reconstruction. Rebuilding beats maintaining.
Instead of trying to make code that never breaks, design systems that can be quickly regenerated from specifications. The ability to rebuild is more valuable than the ability to patch.
→ Regenerate from verified specification with corrected constraints
Security by Design
Every spec includes threat models. No exceptions.
Security isn't an afterthought or a separate review phase. Every specification must include threat modeling and security constraints from the start. EU AI Act compliance is non-negotiable.
→ Block delivery, update specification with security requirements, regenerate
Alignment Before Delivery
No delivery without governance validation.
Nothing ships until governance confirms alignment with intent. This is non-negotiable. Speed comes from better specifications and faster validation, not from skipping checks.
→ Hold delivery, resolve conflict through human escalation, then proceed
Feedback Closes the Loop
Telemetry informs next cycle. System learns.
Production telemetry and feedback must flow back into specifications. The system evolves based on real-world behavior. Without feedback, there is no improvement.
→ Verify data pipeline, cross-validate sources, then incorporate feedback
Simplicity of Spec
Complexity signals unclear intent.
If your specification is complex, your intent isn't clear yet. Simple specifications produce predictable results. Complex specifications produce surprises. Decompose until simple.
→ Simplify specification, decompose into smaller pieces, clarify intent
Statutes by Pillar
Intent Is Absolute
Never exceed specification. Refine intent, don't patch symptoms.
The Spec Is the Contract
Every interaction begins with structured specification.
Quality Through Context
AI succeeds with complete context. Ambiguity causes defects.
Simplicity of Spec
Complexity signals unclear intent.
Code Is Regenerable
Preserve logic, not code. Regenerate from improved intent.
Resilience Over Robustness
Design for reconstruction. Rebuilding beats maintaining.
Zero-Latency Evolution
Changes deliver as fast as validation permits. No release days.
Feedback Closes the Loop
Telemetry informs next cycle. System learns.
The Human as Governor
Humans are stewards. Primary skill: clarity of thought.
Transparent Reasoning
Every agent produces auditable traces. No black boxes.
Security by Design
Every spec includes threat models. No exceptions.
Alignment Before Delivery
No delivery without governance validation.
When Things Go Wrong
The statutes define clear response protocols to common failure modes. These are non-negotiable.
Intent Misinterpretation
Output is technically correct but misaligned with actual goal.
- 1 Halt delivery immediately
- 2 Surface reasoning trace to human
- 3 Refine specification at the ambiguous section
Telemetry Corruption
Production metrics are inaccurate, reinforcing incorrect behavior.
- 1 Cross-validate against independent sources
- 2 Freeze spec updates on anomalous patterns
- 3 Verify data pipeline before resuming
Governance Conflict
Two governance rules contradict (e.g., security vs. compliance deadline).
- 1 Escalate to human with full context
- 2 Automated systems must NEVER resolve governance conflicts autonomously
- 3 Document resolution decision
Mid-Stream Deployment Failure
Partially deployed change creates inconsistent state.
- 1 Maintain atomic deployment where possible
- 2 Automatic rollback to last known-good
- 3 No partial state without explicit human authorization
Live by the Statutes
These twelve statutes form the immutable core of DoCoDeGo. They guide every decision and ensure alignment between intent and implementation.
Help Shape v1 of the Framework
DoCoDeGo is in Alpha. The framework is real and battle-tested — the next release is being shaped in the open. Join the Discord and be part of the evolution.