F.13:4 - Core idea (didactic)

Keep the named value, its meaning and its expression distinct. Recover the old and proposed expression, effective ReferenceScheme, local-sense claim, intended use and any independently governed value being named. When only wording changes, record the rename or alias and retain a path for interpreting the old text.

An F.17 SchemeSenseCell is the exact coordinate <ReferenceScheme by value, LocalExpression, LocalSenseClaim>. Changing LocalExpression creates another cell even when the <ReferenceScheme, LocalSenseClaim> projection stays the same. Retain both coordinates in the naming lineage; do not call them the same cell. An external display label or address can change while its unchanged target cell remains the same.

A Concept-Set row under F.7 displays established comparison content; the row does not constitute a Cross-context relation. A SystemRoleKindDescription under F.4 describes an independently identified exact system-role kind. Recover any continuity of the named value, description episteme, or F.17 UnifiedTermRow under its own rule. Changed identity-bearing claims require the corresponding later object or episteme.

If meaning changes, first apply that subject rule and settle the later naming use under F.18. Split or merge only when there are actually one-to-many or many-to-one senses or rows. A one-to-one revision needs its own subject-governed revision or replacement decision. Preserve the earlier meaning and read-path; when that decision is missing, stop the dependent continuity claim.

Keep aliases local. Compare the exact <ReferenceScheme, LocalSenseClaim> projections. A different projection opens F.9 only when a current semantic correspondence is needed. Establish the relation and any bounded-use claim and reliance separately; shared names create none of them.