F.13:7 - Invariants (normative)

1. Locality of alias. aliases(-) and renames(-) preserve the exact naming use’s effective scheme, local-sense claim and any governed value. Distinct expressions may have distinct F.17 cells; an external row or description label keeps its independently recovered target.
2. Truth over comfort. If meaning changes, recover the corresponding revision, replacement, split, merge or retirement under the subject rule before settling the later name. A rename cannot hide that change.
3. Non‑retroactivity. Past texts remain phrased as written; continuity only adds read‑paths, never rewrites.
4. Alias parsimony. per Context and per row, keep ≤ 1 legacy alias per register (Tech/Plain); prefer the one readers will most likely encounter.
5. Prefer present for writing. In normative writing, use the current preferred label (F.5). Aliases are for reading comprehension.
6. Bridge discipline. A different <ReferenceScheme, LocalSenseClaim> projection is not an alias or pure rename. Use F.9 only for a needed semantic correspondence; recover any obtaining Bridge, bounded-use claim and reliance separately.
7. Epoch honesty. When declaring continuity, attach a succinct epoch note (“pre‑2023 usage”) if it aids readers.