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。