E.20:4.9 - Step 9: Terminology continuity (alias docking)
If the introduction renames any public token or changes canonical naming:
- Use lexical alias docking (F.18) so old tokens remain citeable.
- Update registers and twin labels per lexical discipline.
- To avoid silent rewrites, the MIP-run manifest SHALL state the alias relation and the successor relation.
E.20:4.9.1 - Deprecation / supersession / retirement (preserve citeability)
If the change class includes deprecation, supersession, or retirement (E.20:4.1 #8), the author SHALL preserve reference continuity and state the status change:
- Preserve each identifiable target. A deprecated
U.Mechanismepisteme, reference-reservation stub, suite description, exact WorkPlan edition, or wiring module SHALL remain resolvable at its canonical location. Deprecation MUST NOT remove it and break citations. A declaration-local planned-filling row is not another canonical target. - Keep the public token citeable. A deprecated token such as a
MechanismDefinitionRef, suite token, WorkPlan token, public local-content locator, or wiring token SHALL remain citeable. If a successor token or name is introduced, alias-dock the old token under F.18 (E.20:4.9). A local-content locator still resolves only through its WorkPlan edition and creates no independent row identity or edition. - Declare a successor or state that none is current. Apply that obligation to the deprecated mechanism episteme, reference-reservation stub, suite description, WorkPlan edition, wiring module, public locator, or alias under its direct supersession or deprecation pattern. A changed planned-filling row contributes to changed WorkPlan claim content; it has no separate successor relation.
- Update the definition that owns each change. Make each needed change to suite denotation, closure, obligation, pin, protocol semantics, WorkPlan content, or wiring semantics at its definition locus in E.20:4.2. Prefer a suite variant to an unannounced change in kernel membership.
- Emit RSCR triggers. Deprecation or supersession SHALL emit typed RSCR triggers and extend the regression envelope (E.20:4.10), including checks for dangling references and alias coverage.