F.8:4 - Solution
Treat mint-or-reuse as a decision about an already recovered subject, not a vote on wording. Start with four facts:
- the candidate expression;
- the governed value or relation;
- the subject pattern that defines or tests that value or relation; and
- the proposed naming use.
If a needed fact is missing, recover it through the subject pattern. Otherwise use the following dispositions to select a sufficient treatment. Reuse an already justified choice; examine another disposition when it could meet the use with less burden or preserve a distinction the proposed choice loses:
- keep a local phrase;
- reuse an existing designation;
- use an alias without changing the governed meaning;
- reuse the subject pattern’s name;
- reuse an admitted F.17 row within its stated use;
- name a separately justified
SystemRoleKindDescriptionwhen that is the governed object; - open a durable naming settlement;
- propose a public row;
- introduce a policy identifier for an already recovered policy specification; or
- block or lower the naming use.
The ordinary result states the governed subject, proposed naming use, selected disposition and resulting name when any. Add a reopen condition when continued reuse needs it, and an explicit non-use boundary when F.19’s grounded-contribution test warrants it.
For example, when a durable local designation is needed: “Under PatternReviewReferenceScheme-2026, use ReviewerRole as the Plain designation of ReviewerSystemRole for local review-method prose; select openDurableNamingSettlement and revisit the decision if the naming use becomes public or cross-local.”
The corresponding F.8 result labels are localPhraseOnly, reuseExistingDesignation, aliasOnly, reuseDirectPatternName, reuseAdmittedTermRow, nameSystemRoleKindDescription, openDurableNamingSettlement, proposePublicTermRow, introducePolicyIdentifier, and blockOrLowerUse. They are not new U.* kinds. A stronger result opens its subject pattern; it does not itself create a card, row, identifier, policy specification, or relation occurrence.
F.8:4.1 - Decision Targets
| If the candidate expression designates… | Smallest F.8 disposition | Subject pattern |
|---|---|---|
| A one-off phrase after local repair | localPhraseOnly | E.10 or the subject pattern |
| An existing selected designation for the governed value and use | reuseExistingDesignation | The subject pattern, with F.1, F.2, and F.3 for local-sense discovery; use F.5 or F.18 only when naming work is separately needed |
| A wording variant for the same value, kind, scope, occurrence identity, and use | aliasOnly | F.5, F.13, and F.18 |
| An adequate name already supplied by the subject pattern | reuseDirectPatternName | The subject pattern |
| A cross-local or public reading admitted by one F.17 row | reuseAdmittedTermRow only for its declared use | F.17; F.9 only when an obtaining Bridge between the named cells is used |
| A new designation for a recovered local system-role kind | localPhraseOnly when local wording is enough; otherwise openDurableNamingSettlement when durable reuse is needed | A.2 and C.3 for the kind, then F.5; F.18 only for a durable settlement |
A label for a separately justified SystemRoleKindDescription episteme about that kind | nameSystemRoleKindDescription | F.4 for the description, then F.5; F.18 only when the description’s own name must be durable |
| Any other governed subject | reuseDirectPatternName, or openDurableNamingSettlement only after that subject is recovered | Its subject pattern, then F.5 or F.18 when needed |
| A durable naming settlement not served by lighter dispositions | openDurableNamingSettlement | F.14, then F.18; a NameCard is optional until its own enduring-use gate passes |
| A public, Core-facing, durable, or cross-local term not covered by an admitted row | proposePublicTermRow | F.17 after the F.18 inputs and row threshold are met |
| A policy identifier | reuse the existing identifier, or select introducePolicyIdentifier for a recovered policy specification; add a mint-occurrence basis only for the stronger history uses in §8.1 | F.8:8.1 and the subject pattern for the policy use |
| An expression offered as a new cross-family primitive before its admission disposition is stable | blockOrLowerUse; no naming disposition is available yet | E.24.CD when the governed object is still unclear; if a U-kind proposal remains, E.24.UK decides admission. Return only after the governed object is recovered or one stable root, same-individual-dependent, identity-dependent, reuse, local-kind, or reject result is available. |
F.8:4.2 - Decision Sequence
Use the following questions to recover an adequate disposition without hiding a governed distinction. Skip questions already settled by the available basis.
- 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.
- 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.
- State the naming locality. Supply the naming reference scheme’s designation and interpretation rules by value, and state the local-sense claim. Cite a
SchemeSenseCell, an obtainingLocalSenseBasisRelation, or a selected bounded-model-use Structure only when the naming use needs that object. - Apply F.14 when the needed naming treatment is unsettled. If ordinary local wording supports the use, choose
localPhraseOnlyand stop; use an already justified stronger treatment when the receiving use needs it. - Try an existing designation. Reuse it only when the value, kind, scope, occurrence identity, local sense, and proposed use match.
- Try an alias. Use
aliasOnlywhen the governed meaning is unchanged and lineage can expose the wording variation. An alias may not change kind, scope, occurrence identity, use, or authority. - 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. - 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. - Create the next naming object only when its use justifies the cost. 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.
- 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. If the occurrence cannot be established, give the applicable §4.5 outcome for the history claim. Keep any C.11 result, decision-making Work, result episteme, and record separate.
- 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 stableroot,same-individual-dependent,identity-dependent,reuse,local-kind, orrejectdisposition, re-enter F.8 only if the admitted or reused kind, local kind, or recovered non-kind object needs a designation. - Block or lower. If no disposition is justified, keep the expression local, quote it as source wording, or lower the claim.
F.8:4.3 - Role Expression Boundary
A role expression is not enough to choose the object. For a system-role naming case, keep these four objects distinct:
| Symbol | Object |
|---|---|
L | The candidate or selected designation, interpreted under the effective naming ReferenceScheme. |
K | The local system-role kind recovered through A.2 and C.3, with its work-facing contribution distinction and KindSignature. |
D | An optional F.4 SystemRoleKindDescription episteme whose EntityOfConcern is K. |
A | An optional A.2.1 assignment occurrence in which an admitted system is assigned under K. |
Under the effective naming scheme, L designates K. Needing L does not create or require D; D may receive its own designation when a separate description is justified. Naming either object creates no A. The naming ReferenceScheme interprets the expression; it neither defines the kind nor assigns a system.
After A.2 and C.3 have recovered K, apply the naming ladder. Keep a one-off expression local when that is enough, and reuse an existing designation when it fits. If the kind needs a durable designation, select openDurableNamingSettlement, use F.5 to name K, and use F.18 for the durable settlement. Use nameSystemRoleKindDescription and F.4 only when the governed object is a separately justified description episteme D.
| Source expression | Recovered case | F.8 result |
|---|---|---|
ReviewerRole in a review method | A recovered review-system-role kind needs a durable designation; that naming need requires no description episteme | openDurableNamingSettlement; A.2 and C.3 govern the kind, F.5 its designation, and F.18 the durable settlement; use F.4 only for a separately needed description |
Alice as reviewer | A system is assigned to a local system-role kind for an interval | Not a name decision until A.2.1 recovers the U.SystemRoleAssignment occurrence |
review happened | Dated performed Work | Use A.15.1; open naming only if the admitted Work occurrence needs a designation |
EvidenceRole | An episteme used as evidence | Use the evidence-use pattern; only then consider a name for the governed relation |
AccessRole | Permission or policy grouping | Use access, policy, status, or deontic pattern; do not mint a local system-role kind by suffix |
ProviderRole in a signature | Relation position | Use A.6.5 SlotSpec discipline; name a slot only if needed |
RoleEnactment in source prose | Source wording around a U.SystemRoleAssignment plus a Work occurrence | Recover the exact actual performer through A.13 and let A.15.1 independently admit the Work; use F.6 only when the naming case expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment, and do not mint U.RoleEnactment |
F.8:4.4 - F.17 Row-Scope Consumption
F.8 consumes one named F.17 row and its declared use; it neither constitutes the row nor defines Bridge strength. F.17 keeps the row episteme, governed value, designations, cell, basis relation, any F.9 Bridge, edition relation, and publication package distinct. F.8 asks only whether AdmissibleUse covers the proposed naming use.
| Declared row use | F.8 admissible naming use | Other claims return to |
|---|---|---|
| Naming-only | Shared prose label, glossary text, teaching label | The subject pattern that governs the claim at issue—for example equivalence, assignment, performed Work, structural inference, or measurement equivalence. |
| System-role-kind designation naming | A designation may cite the row as a comparison aid after the local kind is recovered | The direct result for kind admission, cross-local kind identity, classification, or assignment. |
| System-role-kind-description naming | A label for a separately justified SystemRoleKindDescription may cite the row as a comparison aid | The direct result for kind identity, cross-local kind identity, or assignment; the separately justified description remains the object being named. |
| Measurement naming | Shared measurement label where units and procedure constraints remain visible | The measurement pattern for any claim of procedure interchange. |
| Type-structure naming | Name for an admitted structural relation under the row’s invariants | E.24.UK for U-kind admission. |
If the row does not admit the proposed use, lower the name’s use or repair the F.17 row and any needed F.9 relation. Wording alone establishes neither a stronger use nor cross-local sameness.
F.8:4.5 - Accountable Decision Branch
Open this branch only when a receiving claim needs to cite, replay, or assign accountability to the mint-or-reuse decision occurrence itself. First recover that occurrence through the decision or choice pattern that admits it. The ordinary naming result remains valid without this branch.
Keep these objects distinct in the accountable branch:
- the governed value or relation and its subject pattern;
- the candidate expression, selected designation, and any alias;
- the effective naming reference scheme, local-sense claim, optional
SchemeSenseCell, and any obtaining two-participantLocalSenseBasisRelation; - the decision or choice occurrence and the pattern that admits it;
- any C.2.1 decision-result episteme and the record or carrier that designates it;
- any F.18 NameCard, F.17 row, policy specification, policy identifier, publication occurrence, form, or carrier; and
- a selected bounded-model-use Structure only when its organization changes interpretation for this naming use.
When a result episteme is needed, use the full projection below:
MintReuseDecisionResultEpisteme:
DecisionResultEpistemeId:
EntityOfConcernRef: [decision or choice occurrence already admitted by its direct pattern]
DecisionGovernorLocator:
DecisionPredicateRef:
DecisionParticipantRefs: [actual participants with their meanings]
DecisionApplicability:
DecisionOccurrenceIdentityBasis:
DecisionMakingWorkRef?: [separate A.15.1 Work only when current]
DecisionOrChoiceResultRef?: [separate result, such as a C.11 ChoiceResult, only when current]
CandidateExpression:
GovernedValueOrRelationRef:
GovernedKindOrRelationKindRef:
GovernedValueSubjectPatternLocator:
ProposedNamingUse:
EffectiveNamingReferenceScheme: [EpistemeInterpretationScheme (C.2.1:4.1.2), carried by value; rules for this naming use]
LocalSenseClaim:
LocalSenseCellRef?: [only when a current SchemeSenseCell is needed]
LocalSenseBasisRelationRef?: [only when the basis-episteme-to-cell support relation obtains]
SelectedModelUseStructureRef?: [only when a selected Structure changes this use]
ReuseCandidateRefs?:
SelectedDisposition:
ResultingNamingRefs?: [only objects current after the disposition]
NonAdmissibleOverread?: [only when admitted by `F.19`'s grounded-contribution test]
ReopenCondition:
The block describes the result episteme. EntityOfConcernRef resolves to the decision or choice occurrence admitted through DecisionGovernorLocator; the predicate, participants, applicability, and identity basis show why that occurrence exists. GovernedValueSubjectPatternLocator identifies the pattern for the value being named. NonAdmissibleOverread is included only when admitted by F.19’s grounded-contribution test. A C.11 ChoiceResult and dated decision-making Work keep their direct identities and relations.
To assert a decision occurrence, establish it under the rule for that occurrence. If no governing rule can state or test the claim, return missing-governor. If the rule exists but a deciding fact is missing, return missing-information. If sufficient facts fail the positive test, the positive claim is factually unsupported. Use A.6.RCD:0.1 for an inapplicable case or a negative claim with its own grounds. Leave an unestablished occurrence out of the block. When no separate result episteme is needed, state the warranted result in ordinary language.
F.8:8.1 - Policy-Identifier Mint-or-Reuse Discipline
FPF treats policy identifiers such as Phi(CL), Phi_plane, Psi(CL^k), Aut-Guard, EmitterPolicyRef, insertion-policy identifiers, and acceptance-clause identifiers as versioned references whose meaning must be recoverable. The identifier resolves to a separate policy specification; it does not itself assert a gate outcome or permission.
PolicyIdentifierReference:
PolicyIdentifier:
PolicySpecificationRef:
MintDecisionOrChoiceOccurrenceRef?: required only for cited, replayed, normative, cross-local reuse, or accountable mint history
MintDecisionSubjectPatternLocator?: paired with MintDecisionOrChoiceOccurrenceRef
MintDecisionPredicateRef?: paired with MintDecisionOrChoiceOccurrenceRef
MintDecisionParticipantRefs?: [actual participants with their meanings]
MintDecisionApplicability?:
MintDecisionOccurrenceIdentityBasis?:
MintDecisionMakingWorkRef?: [separate A.15.1 Work only when current]
MintDecisionOrChoiceResultRef?: [separate result, such as a C.11 ChoiceResult, only when current]
MintDecisionResultEpistemeRef?:
ScopeOrNamespaceRef:
PolicyIdentifier is the selected designator. PolicySpecificationRef resolves to the separate policy-definition episteme and pins an edition or equivalent digest when needed. A local non-accountable introduction can stop there with explicit local scope.
The conditional mint-occurrence fields are required when the use cites, replays, makes normative, reuses across the local boundary, or assigns accountability to the mint history; together they resolve one admitted decision or choice occurrence and the pattern, predicate, actual participants, applicability, and identity rule that establish it. If that use requires a mint history you cannot establish, apply §4.5 to that claim.
A C.11 ChoiceResult and any dated decision-making Work remain separate. MintDecisionResultEpistemeRef, when current, resolves to a C.2.1 episteme or accepted record describing the occurrence; the record does not perform the decision.
For FPF normative policy identifiers, the durable result episteme is usually an accepted E.9 decision record, but only after the decision or choice pattern has admitted the occurrence that record describes. A local non-exported and non-accountable identifier needs only its separately recoverable specification and explicit scope; it need not create a decision or result episteme. In every branch, the policy specification, identifier, any decision or choice occurrence, any C.11 result, any decision-making Work, and any record remain distinct.
Rules:
- No silent policy-identifier introduction. Every new identifier resolves the separate
PolicySpecificationRefand states its scope. A local non-accountable introduction stops there. A cited, replayed, normative, cross-local, or accountable mint history additionally resolves the decision or choice occurrence plus the pattern, predicate, participants, applicability, and identity rule that establish it; if the occurrence cannot be established, leave the history unasserted and apply §4.5. - Reuse is reference use. Reusing an existing identifier resolves the same identifier and policy specification. Resolve the original mint occurrence only when the current reuse consumes or asserts that history. Reusing the identifier does not restate policy semantics, turn a record into the occurrence, or silently create another decision.
- Gate checkability. A gate, crossing, Bridge, assurance, or publication claim that depends on a policy identifier includes
PolicyIdentifierReferenceor an equivalent resolvable structure admitted by its subject pattern. - Policy authority stays with the subject pattern. F.8 selects introduction or reuse of the identifier; it does not decide whether the policy permits Work, passes a gate, makes a relation obtain, or provides evidence.
- The identifier grants nothing by itself. Name, namespace, suffix, source prestige, specification publication, or decision record grants no permission, status, equivalence, or authority beyond the policy claim defined by its subject pattern.