F.8:4.2 - Decision Sequence

Use this order and stop at the first disposition that supports the proposed use without hiding a governed distinction.

1. Recover the four starting facts. Name the expression, governed value or relation, its subject pattern, and the proposed use. If the value or relation is not available, stop and use its subject-recovery route; F.8 cannot establish it.
2. Split mixed candidates. If one expression covers more than one governed subject or use—for example, a kind, assignment, evidence use, policy, Method, or Work—make separate naming decisions.
3. State the naming locality. Carry the naming U.ReferenceScheme by value and state the local-sense claim. Cite a SchemeSenseCell, an obtaining LocalSenseBasisRelation, or a selected bounded-model-use Structure only when the naming use needs that object.
4. Apply F.14 and try a local phrase. If ordinary local wording supports the use, choose localPhraseOnly and stop.
5. Try an existing designation. Reuse it only when the value, kind, scope, occurrence identity, local sense, and proposed use match.
6. Try an alias. Use aliasOnly when the governed meaning is unchanged and lineage can expose the wording variation. An alias may not change kind, scope, occurrence identity, use, or authority.
7. Try the subject’s existing name. Use the name supplied for the governed subject. A.2 and C.3 govern a local system-role kind and F.5 governs its designation; use F.18 only for a durable settlement and F.4 only for a separately needed SystemRoleKindDescription. A.2.1 continues to govern any assignment. For precise performed Work, A.13 first recovers each exact actual performer and A.15.1 independently admits the occurrence; F.6 follows only when the naming case or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment.
8. Try one admitted F.17 row. Reuse only the row’s declared AdmissibleUse. Local-sense reuse does not imply cross-local sameness; a row and equal spelling create no F.9 Bridge.
9. Open only the next naming object that pays for itself. A stable local address may justify a cell; an enduring naming settlement may justify a NameCard; a public/Core/durable/cross-local need may justify an F.17 row. None implies the next object.
10. Introduce a policy identifier only for a recovered policy specification. A local identifier can stop with that specification and its scope. If the mint history is cited, replayed, normative, cross-local, or accountable, recover its decision or choice occurrence through the subject pattern; otherwise return missing-governor for that stronger history claim. Keep any C.11 result, decision-making Work, result episteme, and record separate.
11. Stop before naming an unsettled U-kind proposal. Select blockOrLowerUse. If the governed object is still unclear, use E.24.CD; otherwise send the recovered proposal episteme or source construct to E.24.UK. F.8 does not test or admit the candidate. After E.24.UK returns a stable root, same-individual-dependent, identity-dependent, reuse, local-kind, or reject disposition, re-enter F.8 only if the admitted or reused kind, local kind, or recovered non-kind object needs a designation.
12. Block or lower. If no disposition is justified, keep the expression local, quote it as source wording, or lower the claim.