Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:55:17 UTC
F.18:3 - Forces
Force
Naming tension
Local sense and reuse across different semantic-context projections
A name must be interpretable under one effective by-value U.ReferenceScheme while remaining bridgeable to a different <ReferenceScheme, LocalSenseClaim> projection without spelling-based identity. The projections can differ under one scheme.
Brevity and ontology recovery
A short label helps conversation, but the NameCard must keep governed kind, effective reference scheme, local sense, subject pattern, and intended use recoverable.
Continuity and correction
Readers need stable public names, while authors must be able to rename, split, merge, or retire names without erasing earlier uses.
Familiarity and precision
Familiar words are easier to adopt, but some familiar words import wrong prototypes from another discipline.
System-role recognition and ontology expansion
SystemRole morphology helps identify one exact local system-role kind, but it must not absorb assignment, capability, method, work, evidence, status, participant, declaration-place, or representation-position claims.