#Mint-or-Reuse Decision

F.8 · Stable · Architectural pattern · Normative unless marked informative · Part F - The Unification Suite (U-Suite): Concept Sets, SenseCells, and System-Role Kinds and Assignments

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Architectural pattern Status: Stable Normativity: Normative unless marked informative

Plain name. Keep, reuse, or strengthen a name.

#Keywords

• subject before name
• governed value or relation
• proposed naming use
• local phrase
• designation
• alias
• row use
• durable naming
• admission before naming.

#Relations

#Content

#Use This When

Plain name. Keep, reuse, or strengthen a name.

Use F.8 after the subject is known and a project must decide the smallest naming treatment for one expression and one use. Start only when these four facts are available: the expression, the governed value or relation, its subject pattern, and the proposed naming use.

Typical triggers include:

• a familiar source word may be useful locally but would import the source ontology if promoted;
• a role-like word such as ReviewerRole, AccessRole, or EvidenceRole may name a system-role kind, another governed value or relation, or only ordinary wording;
• an alias, subject-pattern name, or F.17 row may already serve the use, but only within its stated meaning and scope;
• a governed value may need a durable name, public row, or policy identifier; and
• pressure for a new U-kind appears. That last case stops before naming until E.24.UK has returned a stable admission disposition.

Primary working object. One F.8 disposition for the expression and proposed use. Ordinary use creates no decision occurrence or result episteme. If a later claim must cite, replay, or assign accountability to the decision itself, use the separately triggered branch in §4.5.

Primary working reader. An engineer-manager, analyst, method author, pattern author, or terminology steward choosing whether an expression should stay local, reuse a name, or open a stronger naming path.

First useful move. Write the four starting facts. Then try, in order, a local phrase, an existing designation, an alias, the subject pattern's name, and an admitted F.17 row. Stop at the first sufficient result. Open a cell, NameCard, public row, or policy identifier only when the receiving use needs it.

What goes wrong if missed. A convenient expression is treated as the subject it merely names. Local or source wording becomes durable ontology; a row or alias gains uses it never admitted; a role-like word hides a kind, description, assignment, Work occurrence, or another governed relation; or a record is mistaken for the decision it describes.

What this buys. Teams get short usable names without creating duplicate kinds or naming records. Stronger names are harder to introduce but easier to trust because the governed subject and use remain visible.

Not this pattern when.

• For one-off wording repair, use F.19; use E.10, E.10.ARCH, A.6.P, or the subject pattern when a meaning still needs recovery.
• If the governed subject or relation is not yet known, recover it first. For an unsettled U-kind proposal, use E.24.CD when the object is unclear and E.24.UK for admission.
• To constitute a SystemRoleKindDescription, use F.4. To assign a system, use A.2.1. For precise performed Work, recover each exact actual performer through A.13 and let A.15.1 independently admit the dated occurrence; add F.6 only when the naming case or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment.
• For an obtaining relation between different local-sense projections, use F.9. Use F.17 when a public, Core-facing, durable, or cross-local row is needed.
• For a status, evidence use, policy, Method, Work, publication, or any other governed subject, use its subject pattern before naming it.
• After F.8 has selected a name family, use F.5 for its naming discipline and F.18 only for a durable naming settlement.

#Problem Frame

Name pressure often reveals an unresolved subject. One word may be offered for different things—for example, a designation, local system-role kind, optional description of that kind, assignment occurrence, status value, policy identifier, or Work label. Shared spelling proves none of these identities.

F.8 therefore asks what the expression will designate and for which use before judging the wording. It is the gate from a local expression to a stronger naming treatment. It neither defines the governed value nor performs the later naming work.

#Problem

Without this pattern:

1. Local or source wording becomes durable ontology. A temporary phrase or familiar standard term survives without a recovered subject and use.
2. Role-like wording collapses different objects. A local system-role kind, its optional F.4 description, an A.2.1 assignment, performed Work, or another governed relation receives one misleading label.
3. Reuse widens silently. An alias changes meaning, or an F.17 row admitted for naming is reused for equivalence, assignment, measurement, or structural inference.
4. Naming is asked to admit ontology. A proposed U-kind enters F.8 before E.24.UK has settled whether the result is an admitted kind, reused kind, local kind, or recovered non-kind object.
5. Identifiers and records act by proxy. A policy identifier lacks a resolvable specification, or a filled record is treated as the decision occurrence or result it describes.
6. Locality labels become subjects. A review, team, project, or date label is used as if it created Work, assignment, evidence, status, or authority.

#Forces

#Solution

Treat mint-or-reuse as a decision about an already recovered subject, not a vote on wording. Start with four facts:

1. the candidate expression;
2. the governed value or relation;
3. the subject pattern that defines or tests that value or relation; and
4. the proposed naming use.

If any fact is missing, stop at the subject-recovery route; naming cannot supply it. Otherwise try the dispositions in this order and stop at the first one that supports the proposed use:

1. keep a local phrase;
2. reuse an existing designation;
3. use an alias without changing the governed meaning;
4. reuse the subject pattern's name;
5. reuse an admitted F.17 row within its stated use;
6. name a separately justified SystemRoleKindDescription when that is the governed object;
7. open a durable naming settlement;
8. propose a public row;
9. introduce a policy identifier for an already recovered policy specification; or
10. block or lower the naming use.

The smallest result is one readable sentence, not a mandatory record: state the governed subject, proposed naming use, selected disposition, resulting name when any, and the change that would reopen the decision. Add a non-use boundary only when F.19's grounded-contribution test admits it. For example, when no lighter disposition supports a needed durable local designation: “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.

#Decision Targets

#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.

#Role Expression Boundary

A role expression is not enough to choose the object. For a system-role naming case, keep these four objects distinct:

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.

#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.

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. Attractive wording supplies neither a stronger use nor cross-local sameness.

#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 U.ReferenceScheme, local-sense claim, optional SchemeSenseCell, and any obtaining two-participant LocalSenseBasisRelation;
• 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: [U.ReferenceScheme carried by value]
  LocalSenseClaim:
  LocalSenseCellRef?: [only when a current SchemeSenseCell is needed]
  LocalSenseBasisRelationRef?: [only when the cell-to-basis-episteme 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](/generated/patterns/F.19)'s grounded-contribution test. A C.11 ChoiceResult and dated decision-making Work keep their direct identities and relations. If the occurrence and its governor cannot be recovered, do not instantiate the block: return the A.6.RCD missing-governor result. If no result episteme is needed, state the ordinary result and stop.

#Invariants

1. Four facts, one use. Every disposition names the expression, governed value or relation, its subject pattern, and one proposed use. Split an expression that covers more than one governed subject or use.
2. Lightest sufficient result. Try the ordinary reuse ladder before creating a cell, NameCard, row, or policy identifier. An unsettled U-kind proposal stops before naming.
3. Reuse preserves meaning. Reuse or aliasing changes no kind, scope, occurrence identity, local-sense claim, admitted use, authority, or lineage. Shared spelling under another scheme establishes neither sameness nor an F.9 Bridge.
4. Kind, description, assignment, and Work stay distinct. A designation may name a recovered local system-role kind K without creating the optional F.4 description D. Neither name classifies a candidate, creates an A.2.1 assignment A, or demonstrates Work. Other governed uses remain with their subject patterns.
5. Rows stay within admitted use. Reusing an F.17 row supplies only its AdmissibleUse and no equivalence.
6. Ordinary and accountable decisions stay distinct. Ordinary F.8 use needs no decision occurrence or result episteme. The §4.5 branch opens only after the decision or choice pattern admits the occurrence; otherwise it returns missing-governor.
7. Naming objects imply none of one another. A designation, cell, basis relation, NameCard, row, identifier, publication occurrence, form, or carrier is created only for its receiving use. A selected Structure appears only when its organization changes interpretation of this naming use.
8. Admission precedes naming. Before E.24.UK returns a stable disposition, F.8 can only block or lower the proposed naming use. Afterward it may name only the admitted, reused, local, or recovered non-kind object identified by that result.
9. Policy identifiers remain references. Every identifier resolves a policy specification. Its mint occurrence and history are required only for the stronger uses stated in §8.1 and remain distinct from any C.11 result, decision-making Work, result episteme, or record.
10. Labels grant no authority. A source title, suffix, row, record, or identifier creates no governed subject, obtaining relation, permission, evidence, equivalence, or publication authority.

#Reasoning Checks

Use these as reading checks, not as a required notation or record.

#Archetypal Grounding - worked cases

#ReviewerRole Expression vs Review Report

The source label PatternReview_2026 is not a context object. Classify the actual claim before using it:

• ReviewWork-82 can be one dated U.Work occurrence under A.15.1;
• ReviewPlan-2026-v3 can be a separately constituted plan episteme or edition under its subject pattern;
• PatternReviewReferenceScheme-2026 can be an effective by-value U.ReferenceScheme for interpreting review terminology; and
• "used while deciding the label for the 2026 review method" can be claim content describing the decision-use setting without minting any context entity.

If the recovered ReviewerSystemRole kind needs a durable local designation, F.8 returns openDurableNamingSettlement: A.2 and C.3 keep governing the kind, F.5 governs its designation, and F.18 supplies the settlement. The recovered kind is the governed subject; F.4 enters only for a separately needed description, A.2.1 for an assignment, and A.15.1 for performed review Work.

The expression "review report has reviewer role" is a different case. ReviewReport-82 is an episteme. An evidence, source, or publication relation may later use it for an adequacy claim about a reviewed pattern; the report is not a U.System, is not classified by the review-system-role kind, and cannot enter its assignment relation. Its title establishes neither evidence use nor publication authority.

#Actor Across BPMN and PROV

A manager wants one word, "actor", for a BPMN participant and a PROV agent in a diagram. First recover the two local senses under their ReferenceSchemes. If an obtaining F.9 Bridge relates the named cells and an F.17 row admits naming-only use, F.8 returns reuseAdmittedTermRow for prose and diagram labels only. This supports no governed-value identity, substitution, system-role assignment, or Work.

If the project later needs a local system-role kind under one scheme, it first recovers the kind through A.2 and C.3. F.5 then governs any new designation, with F.18 only for durable reuse; F.4 is added only if a separate description episteme is needed.

#Access Role

An access-control source says ApproverRole. Under its naming ReferenceScheme, the expression may designate a permission grouping or policy relation. First recover the access, policy, status, or deontic claim and predicate. Only if A.2 and C.3 recover a local approval-system-role kind does F.8 consider a name for that kind. F.5 governs its designation, F.18 applies only for durability, and F.4 remains optional for a separately needed description.

Otherwise any needed durable designation belongs to the access, policy, status, or gate pattern. The Role suffix, a source card, or a selected model-use Structure creates no local system-role kind or assignment.

#Policy Identifier

A gate profile proposes Aut-Guard-2026. F.8 treats this as a policy-identifier question only after the policy specification is recovered. Ordinary reuse resolves the identifier and specification. Recover the mint decision or choice occurrence only when reuse relies on that history for citation, replay, accountability, supersession, or another named relation. If a new introduction makes that stronger claim without an occurrence basis, return missing-governor. Any C.11 result, decision-making Work, result episteme, or record stays separate.

The identifier is not the specification, local system-role kind, Method, gate result, evidence value, permission, or source authority. It is a reference used by the pattern that defines or constrains the governed policy claim.

#New U-kind Candidate

A team proposes U.InfluenceEdge because many documents use "influence". At F.8 entry there is no recovered governed value with a stable admission disposition, so F.8 returns blockOrLowerUse and stops naming. If the expression still hides whether the subject is an existing relation or claim—for example, a causal, evidence, Method, or Bridge relation—or a characteristic, structural name, publication form, local frame, or another object, E.24.CD recovers that object or the unresolved proposal. A recovered governed object returns to its subject pattern; a surviving U-kind proposal goes to E.24.UK for root, same-individual-dependent, identity-dependent, reuse, local-kind, or reject. Only after that result is stable may F.8 reopen for a name of the admitted or reused kind, bounded local kind, or recovered non-kind object. F.8 creates neither the proposal object nor a public spelling and admits no kind.

#Readable Disposition and Explicit Stops

The ReviewerRole case closes with one readable result. The recovered kind is a local U.Kind for U.System candidates, distinguished by its stable review contribution and tested by its KindSignature; any assignment remains separate. The result is:

Under PatternReviewReferenceScheme-2026, use ReviewerRole as the Plain designation of ReviewerSystemRole for local review-method prose. No existing designation or alias supports that use, so select openDurableNamingSettlement: A.2 and C.3 continue to govern the kind, F.5 governs its designation, and F.18 supplies the durable settlement. Reopen it if the proposed use becomes evidential, status-bearing, access-related, source-facing, published, or cross-local, or if another change of use or audience exceeds this local settlement's scope.

That sentence is the F.8 result. It needs no decision occurrence or result episteme. If a later claim must cite, replay, or assign accountability to the decision, use §4.5. No naming-decision governor is available in this case, so that branch returns missing-governor rather than inventing ReviewerSystemRoleNamingDecision-2026-07-31. C.11 applies only to a genuine local choice among available options. For any precise decision-making Work, A.13 first recovers the exact actual performer and A.15.1 independently admits the dated Work; F.6 follows only when the later claim expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment.

EvidenceRole stops earlier and does not enter F.8. The known subject is ReviewReport-82 : U.Episteme, proposed for evidence use concerning an adequacy claim. Still missing are the target claim and polarity, the evidence-use relation and relation kind, the provenance and any assurance or reliance use and validity window, and one subject pattern that defines the relation. Apply that pattern and keep the wording local until those facts are recovered. PatternReviewReferenceScheme-2026 may interpret the source wording, but the review label creates no evidence relation, system-role kind, description, assignment, authority, or publication. No SchemeSenseCell, LocalSenseBasisRelation, or selected Structure is needed merely to record this stop.

Re-enter F.8 only after one governed relation, its kind, its subject pattern, and the proposed naming use are available. If the target claim, polarity, provenance, assurance or reliance use, or validity window changes, reopen the subject claim rather than the name.

#Bias-Annotation

F.8 counters two shortcuts: a familiar word is treated as proof that a stronger name is needed, or a record is treated as the subject or decision it describes. Recover the four starting facts, choose the lightest disposition, and add a Structure, decision result, NameCard, row, or publication object only when its own receiving use requires it.

#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. They are not "just strings", system-role-kind names, gate decisions, permissions, or policy specifications.

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 stronger use is requested and those facts are absent, return missing-governor for it rather than inventing an occurrence. 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](/generated/patterns/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:

1. No silent policy-identifier introduction. Every new identifier resolves the separate PolicySpecificationRef and 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; without that basis, return missing-governor for the stronger branch and do not claim it.
2. 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; it does not restate policy semantics, turn a record into the occurrence, or silently create another decision.
3. Gate checkability. A gate, crossing, Bridge, assurance, or publication claim that depends on a policy identifier includes PolicyIdentifierReference or an equivalent resolvable structure admitted by its subject pattern.
4. 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.
5. 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.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

Good consequences:

• vocabulary grows only when a receiving use needs a stronger name;
• role-like, source, and record-like expressions return to their governed subjects before naming;
• aliases and F.17 rows retain their admitted meaning and scope;
• F.5 and F.18 receive a recovered subject and a selected naming path; and
• accountable decisions and policy identifiers remain inspectable without making their records act.

Costs:

• authors must recover the subject, pattern, use, scheme, and local sense before naming;
• mixed expressions need separate decisions, and some attractive words stay local or remain aliases;
• durable or public use may require its own NameCard, Bridge, row, reliance, decision result, or publication object; and
• a proposed U-kind receives no F.8 name before E.24.UK settles admission.

Refresh by meaning, not by neighbour edition.

• If F.14, F.5, F.17, or F.18 changes the lightest-sufficient naming ladder, row-entry threshold, AdmissibleUse, or escalation to a stronger naming object, revisit §§0 and 4.1–4.4, case 7.2, checks 03–09, and the compact corpus entry.
• If A.2, C.3, F.4, A.2.1, A.13, A.15.1, or F.6 changes how a local system-role kind is recovered, how L, K, D, and A relate, how an exact actual performer and Work are admitted, or when precise assignment-bound attribution enters, revisit the corresponding target rows, step 7, §4.3, cases 7.1, 7.3, and 7.6, invariant 4, and checks 06–08.
• If A.6.RCD, C.11, C.2.1, or A.15.1 changes how a decision or choice occurrence, result, result episteme, decision-making Work, or missing governor is established, revisit §4.5, the accountable stop in 7.6, invariant 6, and check 10.
• If E.24.CD, E.24.UK, A.8, or A.11 changes object recovery, admission dispositions, or the admission-before-naming order, revisit the entry and ordinary conditions for use, stopping, or returning, the pre-admission target and step 11, case 7.5, invariant 8, and check 12.
• If the policy subject pattern, E.9, A.6.RCD, C.11, or C.2.1 changes the policy specification–identifier distinction or the support required for mint history, revisit the policy target, step 10, case 7.4, §8.1, invariant 9, and checks 10 and 13.
• If a source used in §12 changes a distinction that F.8 adopted, or a better current source preserves the needed precision and readability at lower use cost, revisit that source row and only the F.8 loci named by it.

A new edition number, publication status, link, harmless wording repair, or added example does not reopen F.8 when these meanings stay unchanged. A changed disposition, governed subject, kind or relation, admitted use, ordering dependency, or better solution reopens only the dependent loci named above.

#Rationale

A naming mistake is often a subject or use mistake. Asking “what name should we use?” too early lets wording decide ontology, scope, or authority. F.8 therefore recovers the subject and proposed use before selecting a naming treatment.

F.8 is narrower than F.18. It decides whether the expression stays local, reuses something available, or opens one stronger naming path. F.18 runs a durable settlement, candidate comparison, NameCard, lineage, and any later public-row gate. F.8 creates neither the governed value nor the objects produced by the stronger path.

The system-role branch shows why the ordering matters. A designation L, local system-role kind K, optional F.4 description D, and any assignment A are different objects. The word role can also point to another governed subject. Recovering that subject first keeps naming from creating a false kind or assignment.

The accountable branch follows the same rule. A decision occurrence, C.2.1 result episteme about it, C.11 result, decision-making Work, and rendered record answer different questions. Section 4.5 opens only when a receiving claim needs that stronger traceability; ordinary F.8 use stops earlier.

#SoTA-Echoing - Source-Use

Qualification and selection rule. These decisions are qualified on 2026-08-15 for the cited editions and the F.8 questions below. The set is deliberately small. ISO 704 and SKOS are current standards or durable lineage, not claimed as research frontiers. The gUFO–OBO row combines a current formal comparator with an operational ontology-maintenance practice. The Cedar row is a current research-and-practice comparator. A source belongs here because it changes an F.8 disposition or boundary, not because it is official, popular, or easy to find.

Internal FPF basis, not external SoTA.

• F.14, F.5, F.17, and F.18 supply the local-phrase, designation, alias, row-use, and durable-naming ladder.
• A.2, C.3, and F.4 keep designation L, local system-role kind K, and optional description D distinct; A.2.1 governs assignment A. For precise performed Work, A.13 recovers each exact actual performer and A.15.1 independently admits the dated occurrence; F.6 is a later separate relation only when precise assignment-bound attribution is expressly consumed.
• E.24.CD, E.24.UK, A.8, and A.11 recover an unclear object and decide kind admission before F.8 names the result.
• A.6.RCD, C.11, C.2.1, and E.9 govern any accountable decision occurrence, separate result, result episteme, and policy-history record.
• F.1–F.3 and F.9 govern local-sense discovery and an obtaining Bridge; A.1.1 and A.22 govern any selected bounded-model-use Structure. F.8 cites those objects only when the naming use needs them.

Source-use boundary. External sources can supply candidate expressions, a comparison pressure, or a narrow representation test. They do not select the F.8 disposition, establish the governed subject, make a relation obtain, admit a kind, or grant authority. Those results remain with the named FPF pattern and the recovered facts.

#Relations

Builds on. A.7, E.24.UK, A.8, A.11, E.10, E.10.ARCH, F.19, F.1, F.2, F.3, F.5, F.9, F.14, F.17, and F.18.

Coordinates with. A.2, A.2.1, A.2.5, A.2.7, A.6.5, A.6.RCD, A.15, A.15.1, C.11, F.4, F.6, F.10, F.13, F.15, C.2.1, C.3, E.9, E.24.CD, and E.24.PUB, plus the subject pattern for any other governed value.

Constrains.

• F.5 names only after F.8 has selected the naming case.
• Use F.4 only for a separately needed SystemRoleKindDescription; naming the local kind itself does not require that episteme.
• F.9 governs an obtaining Bridge between F.17 cells; F.17 governs admitted public-row use before F.8 reuses it.
• F.18 expands durable naming only after lighter dispositions have failed.
• F.14 supplies the anti-explosion stop before every stronger F.8 disposition.
• F.15 may check the resulting distinctions; it neither chooses the disposition nor creates a naming object.

Does not replace. The subject pattern for any governed value or relation. For example, it does not replace the rules for a system-role kind, assignment, performed Work, decision occurrence, status, evidence use, policy, relation slot, selected Structure, or description episteme.

#Didactic Memory

Name the subject and use before judging the word. Try the light naming ladder and stop at the first sufficient result. An unsettled U-kind goes to E.24.UK before naming; an accountable decision opens §4.5 only when the decision occurrence itself must be used. A name, card, row, identifier, publication, or record creates neither the subject nor any relation or authority it mentions.

#F.8:End

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)