constitution

To define a project constitution, use guided elicitation to capture 3–7 core principles across Core Principles, Development Conventions, and Constraints categories. This process locks in invariants and governance rules before downstream workflow skills execute.

Capturing development conventions and external constraints is handled through a template-driven elicitation process that records them in a formal project constitution. This ensures all governance rules are structured and versioned before development begins.

Yes, you can route decisions to ADRs during planning and implementation. The constitution applies non-intrusive updates that automatically direct architectural decisions to ADRs, maintaining structured governance throughout the workflow.

Versioning and updating a project constitution requires applying version bumps with structured updates. The template-driven creation includes metadata like version, created, and updated dates to track amendments without disrupting existing invariants.

Yes, a constitution must exist before downstream skills can run. This guardrail enforces that core principles, development conventions, and constraints are formally established and versioned prior to subsequent workflow execution.

You need a formal governance file when enforcing invariant principles and governance rules across maxi workflows. It is required for new and existing projects to ensure structured elicitation and decision routing before planning and implementation skills run.