Skip to content

Your Constitution

A project constitution is a set of governing principles that constrain all development decisions. Every charter, plan, task, and line of code must comply.

Without a constitution, AI agents make their own architectural decisions. They pick frameworks you did not ask for. They add abstractions you do not need. A constitution gives the agent explicit boundaries.

Auro ships with 9 articles. Customize, remove, or add your own.

#ArticleRule
ILibrary-FirstPrefer existing libraries over custom code
IICLI InterfaceAll functionality accessible via CLI
IIITest-FirstWrite tests before implementation (NON-NEGOTIABLE)
IVIntegration TestingIntegration tests over unit tests
VObservabilityStructured, queryable logs for everything
VIVersioningSemantic versioning, no exceptions
VIISimplicitySimplest solution that meets requirements
VIIIAnti-AbstractionNo abstractions until 3+ concrete cases need them
IXIntegration-FirstBuild integration layer before business logic
/auro.constitution

The agent walks you through each article, asking whether to keep, modify, or remove it. The result saves to .auro/constitution.md.

Constitution -> Charter Gate Pass -> Plan

Fail path loops back to Charter for correction.

Constitution -> Plan Gate Pass -> Tasks

Fail path loops back to Plan for redesign.

Constitution -> Task Gate Pass -> Implement

Fail path loops back to Tasks for restructuring and test coverage.

At each gate, output is checked against the constitution. A charter violating Simplicity? Gate fails, revise the charter. A plan violating Library-First? Gate fails, revise the plan. Problems caught early, when they are cheap to fix.

Common modifications:

  • Remove CLI Interface for pure library projects
  • Add a Security article for user data handling
  • Add a Performance article for latency requirements
  • Modify Test-First to charter coverage thresholds

Edit .auro/constitution.md directly. All slash commands use the updated version.

With your constitution in place, head to the Charter phase to write structured charters. See Principles for deep dives on each article.