versioning-constitutions

When foundational rules change (patterns, tech stack, architecture), create a new version rather than editing in place. This preserves history, enables rollback, and makes changes explicit.

CRITICAL: Removing or relaxing a mandatory pattern ALWAYS requires a new version, even if existing code would still work. "Non-breaking" is not sufficient - any change to mandatory patterns needs versioning for audit trail.

Before adding content to constitution, ask: "If we violate this rule, does the architecture break?"

当架构模式演变、技术堆栈变化或基础规则需要更新时使用 - 创建新的宪法版本目录、将内容迁移/组织到模块化文件中、更新符号链接和文档更改 来源：arittr/spectacular。