constitution-enforcer

Pre-implementation validation enforces the 9 Constitutional Articles and Phase -1 Gates to catch design and compliance violations before code is written. The constitution-enforcer applies automated checks across requirements, architecture, tests, and project structure to detect misalignment and provide remediation guidance.

The 9 Constitutional Articles establish governance rules for libraries, CLI interfaces, tests, EARS-formatted requirements, traceability, project memory, simplicity, anti-abstraction, and integration-first testing. Phase -1 Gates validate these rules as mandatory checkpoints before implementation begins.

Yes. The constitution-enforcer detects governance violations automatically, documents justified exceptions, and generates compliance reports. It tracks complexity and provides actionable remediation planning to keep design and implementation aligned with constitutional standards.

Run compliance validation before any code is written. Phase -1 Gates catch violations early in requirements, architecture, and test design stages, preventing costly rework and ensuring governance standards are met from project inception.

The enforcer identifies misalignment across EARS-formatted requirements, traceability gaps, library and CLI interface violations, test structure issues, and anti-abstraction breaches. It reports deviations from the 9 Constitutional Articles with specific remediation guidance for each violation type.

No. The enforcer generates actionable compliance reports with clear violation detection and remediation steps. Governance teams and developers can use the structured output immediately to resolve violations and document justified exceptions before proceeding to implementation.