update-constitution

Constitution updates are enforced by validating entries and gating changes behind explicit ratification. You submit a ratified proposal in the human decisions folder, and the skill updates constitution.md accordingly while preventing unauthorized alterations.

Validating new constitution entries involves checking entries against predefined sections and timelessness rules. During bootstrap population, the skill ensures identity and sections are honored, applying validation rules before writing to the document.

Appending ratified amendments to a Change Log requires a write workflow that activates after ratification. The skill enforces the Change Log policy by validating entries first, then appending the ratified changes to maintain document consistency.

Constitution document validation fails without frontmatter because the skill requires name and description fields in SKILL.md. This metadata ensures identity and sections are honored, preventing task-work or debrief-induced alterations from bypassing ratification.

Yes, this governance skill prevents task-work or debrief-induced alterations by gating changes behind explicit ratification. It validates entries against predefined sections and timelessness rules, ensuring only bootstrap or approved amendments populate the document.

Using a memory-bank for constitution governance limits updates to bootstrap or explicitly ratified amendments. The skill prevents unauthorized task-work alterations and requires strict validation, meaning no changes occur without a ratified proposal in the human decisions folder.