speckit-constitution

To keep a project constitution in sync, you must update the .specify/memory/constitution.md file by replacing placeholders with current repository context, ensuring versioning and mandatory sections remain consistent across templates.

Automatic constitution hydration is the process of filling placeholders in the .specify/memory/constitution.md file using current repository context and principle inputs, preventing drift between living documents and scripted workflows.

To propagate governance amendments, the system applies changes to related artifacts within the specify workflow and templates, ensuring versioned governance maintains a clear amendment process and provenance across all documents.

Yes, the constitution update process enforces token replacement, version increments, and formatting validation checks for placeholders to ensure consistent versioning and mandatory sections are maintained correctly.

The best way to prevent drift is to maintain and synchronize the project constitution across templates and governance rules using automated hydration, version increments, and placeholder validation checks.

Yes, you can manage versioned governance by updating the project constitution to reflect current rules, which automatically handles version increments and tracks amendment provenance across related template files.