speckit-constitution

To update a project constitution, you provide desired governance principles as inputs and the system synchronizes memory placeholders with concrete values. It then propagates amendments across dependent templates to maintain consistency.

Template propagation in governance documentation ensures that when a constitution is amended, changes are automatically pushed to dependent artifacts. This keeps project templates aligned with the latest governance principles.

Versioning for project constitution changes generates an audit-ready change history. It tracks amendments over time and applies governance checks to maintain consistency across the project lifecycle.

Yes, you can use interactive inputs to resolve constitution placeholders. The system derives concrete values from your provided principles or repo context, replacing placeholders to generate a synchronized memory constitution.

The best way to manage governance principles across templates is using a versioned constitution system. It ensures memory-template synchronization and propagates amendments automatically, eliminating manual updates across artifacts.

Constitution documentation fails governance checks when memory-template synchronization is incomplete or placeholders remain unresolved. Ensure all principle inputs are provided so the system can validate consistency before propagating changes.