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?"
À utiliser lorsque les modèles architecturaux évoluent, que la pile technologique change ou que les règles fondamentales nécessitent des mises à jour : crée un nouveau répertoire de versions de constitution, migre/organise le contenu en fichiers modulaires, met à jour le lien symbolique et documente les modifications. Source : arittr/spectacular.