Skip to content

The 9 Constitutional Articles

The constitution is the governance layer of Charter-Orchestrated Engineering. It defines non-negotiable rules that every charter, plan, and task list must satisfy.

#ArticlePurpose
ILibrary-FirstPrefer existing libraries over custom code
IICLI InterfaceAll tools must have CLI interfaces
IIITest-FirstWrite tests before implementation
IVIntegration TestingTest components together, not just in isolation
VObservabilityBuild in logging, metrics, and tracing
VIVersioningTrack versions for all artifacts
VIISimplicityMinimize moving parts and complexity
VIIIAnti-AbstractionDon’t abstract until you must
IXIntegration-FirstDefine contracts before building components

Articles act as phase gates — checkpoints that charters must pass before moving to the next phase.

Gate 1: Charter to Plan Pass -> Plan

Fail path returns to Charter for corrections.

Gate 2: Plan to Tasks Pass -> Tasks

Fail path returns to Plan for architectural adjustment.

Gate 3: Tasks to Implement Pass -> Implement

Fail path returns to Tasks for sequencing and coverage fixes.

Each gate verifies that the output of a phase doesn’t violate any constitutional article. For example:

  • A plan that introduces an ORM when direct SQL works violates Article VIII (Anti-Abstraction)
  • A task list with no test tasks violates Article III (Test-First)
  • A charter requiring 5 microservices for a simple CRUD app violates Article VII (Simplicity)

Three articles have the most day-to-day impact:

The default constitution works for most projects. You can customize it with:

/auro.constitution

Common customizations:

  • Relaxing Test-First for prototypes or spikes
  • Adding domain articles like “HIPAA Compliance” or “Offline-First”
  • Adjusting complexity thresholds for larger teams