Constitution

This manages your project's architectural DNA through two shared documents: architecture.md for your tech stack, security rules, and AI guardrails, and ontology.md for your domain glossary. Run it before your first brainstorm to lock down stack choices and security constraints, then use constitution check to validate specs and tasks against those rules. The check operation outputs a detailed report mapping violations to specific CWEs and OWASP categories, which is honestly more thorough than most teams do manually. It's file-based by design to survive context rot, meaning it reads from disk every time instead of trusting conversation memory. If you work on projects where "we don't use that library" or "that's not our terminology" comes up repeatedly, this prevents those conversations from happening again.