F.5:4.3 - Positive Naming Rules

Recover the object first. State the governed kind or construction of the value—for example, a U-kind, local system-role kind, description episteme, classification judgment, assignment, relation, Method, Work, status, evidence use, slot, lens, or another object.
Recover the meaning source. Use the exact E.24.UK or direct admission for a U-kind; A.2 with C.3 for a local system-role kind; F.4 for its description; A.2.7 for relations among kinds; A.3, A.15, G.5, or the exact composition pattern for Method and Work names; and the direct relation for status, evidence, source, requirement, publication, assurance, gate, decision, and relation-position names.
Use minimal generality. The designation’s scope is no wider than the admitted invariants.
Keep interpretation metadata out of the label. Edition, source, witness, local boundary, reference scheme, and threshold belong in the direct declaration, description, relation, or NameCard.
Make morphology object-sensitive. Concrete local system-role kinds use ...SystemRole; description epistemes use ...SystemRoleKindDescription; states use state or level wording; slots say Slot, Argument, Endpoint, or another exact position head.
Keep coupled names typed. A compact phrase may help a reader, but one label must not carry several independently governed objects—for example, kind, assignment, capability, Method, Work, and description—at once.
Do not encode thresholds or windows in the name. Put time, state, threshold, capability envelope, or admission window in the direct claim.
Use aliases only with lineage. A source term, predecessor term, symbol, or translation does not become a second selected Tech label.
Escalate only for actual reuse. Use F.18 and F.17 for durable or public naming. When an actual cross-local relation is consumed, name the exact obtaining C.3.3 relation between local kinds or F.9 Bridge between distinct F.17 cells and keep the separate C.2.1 claim that it suits the named use. For ordinary reliance, recover the descriptive A.10 evidence-provenance path and the independently established direct relations it cites. Judge evidence sufficiency under the direct rule for the relied-on claim. RelianceDisposition=pass supports only the named bounded use; degrade supports only its named narrower use. Use B.3 only when an actual named assurance claim is current. None of the cross-local relation, use claim, evidence path, assurance result, NameCard, row, designation, or publication establishes assignment, Work, result, provenance, assurance, or publication occurrence.