Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:20:20 UTC

F.18 - Local-First Unification Naming Protocol

Status: Stable For practitioners who need a durable reusable name for an already governed value.

F.18:0 - Use This When

Use F.18 when a name must become stable, public, Core-facing, reusable under more than one named source, practice, or reference scheme, or durable enough that later work can cite it without guessing. Typical cases:

  • a local expression becomes a durable name for an already governed value;
  • two teams use different words for the same candidate sense and need one reusable term plus preserved local wording;
  • one tempting head word is useful under one recovered local meaning but misleading under another;
  • a proposed name implies a different kind from the value it is meant to designate.

First useful move.

  1. Recover the exact value and the pattern containing its defining or testing rule.
  2. Decide whether ordinary local wording is enough or later use needs a durable name.
  3. For a durable name, reuse a current naming settlement that already covers this value and use. Otherwise compare the plausible names and record the Tech label, any Plain designation needed for a stated didactic use, the selection reason and the condition for reconsidering the choice in a NameCard.

If bare claim-bearing role still hides the object, use E.10.ROLE; if relation, slot, interface, port, or signature wording hides it, use section 5.6. Open section 4.4 only for a public, Core-facing, durable-across-context, or cross-context use. A public row is a later result, never part of the first naming move.

For one-off wording repair, use F.19. Return to E.10, E.10.ARCH, A.6.P, A.6.RSIR, C.2.P, or the subject pattern only if the object or claim remains unresolved. Use F.18 when a reusable name is needed.

For example, say in ordinary words whether one exact Bridge is suitable for one named use; do not create a NameCard, public claim kind, or durable CamelCase head merely to abbreviate that C.2.1 claim. Reopen F.18 for that claim only when an independent later use needs a reusable name beyond the local statement.

F.18:1 - Context

A name lets people refer to an independently governed value. The naming decision selects designations for that value; its subject pattern supplies the rules for identifying it and testing claims about it.

FPFCoreReferenceScheme names the EpistemeInterpretationScheme value used to interpret current FPF Core Tech labels and relation names; a name under another scheme carries that scheme by value. C.2.1:4.1.1–4.1.2 identifies the actual rules, domains and semantic dependencies and supplies the range. Recover those rules for the naming claims being made; the scheme’s label or a document about it does not supply the value.

Most naming work stays within one <ReferenceScheme, LocalSenseClaim> projection and needs no Bridge. If one named use must relate different projections, follow the later cross-projection branch in section 4.4.1. Shared spelling, another scheme, or a selected model-use structure alone creates no Bridge, use claim, reliance, governed-value identity, or U.BoundedContext.

F.18 supplies the naming discipline for Part F and for any FPF pattern that needs a durable public term. It coordinates with:

  • F.5 for type-name and system-role-kind-description label form;
  • F.8 for the prior decision that an expression should become a durable name rather than remain local, reused, or aliased;
  • F.9 for an actual sense Bridge between different <ReferenceScheme, LocalSenseClaim> projections;
  • F.13 for renames, aliases, splits, and merges;
  • F.14 for anti-explosion control;
  • F.17 only as a later public-row consumer whose current entry and result must accept the exact F.18 objects named below;
  • E.10.ROLE when bare claim-bearing role hides its object; A.6.5 and A.6.RSIR when relation, signature, interface, or slot wording hides the governed object; A.6.P.WMR when Work and Method boundary wording still hides the exact relation; and A.15.1 when a candidate performed-work name still lacks occurrence grounding.

One F.18 naming decision concerns one independently governed value. F.18 supplies the candidate comparison, selected Tech designation, any Plain designation needed for a stated didactic use, declared naming use and reopen conditions. The value’s direct pattern retains its kind, identity, obtaining and other subject semantics.

The NameCard’s complete claim graph records the selected designation expressions, exact local sense, covered and rejected alternatives, rationale, lineage, and reopen condition.

F.18:2 - Problem

FPF texts fail when names are treated as if they carried ontology by themselves.

  1. A short label appears in another context and gets treated as the same value although no obtaining Bridge establishes the exact sense relation, no separate claim says that Bridge suits this reuse, and no current reliance supports that claim.
  2. A role-looking name bundles a system-role kind, assignment occurrence, capability, method fit, work evidence, or authorization.
  3. A status-like or evidence-like phrase becomes a fake role or fake type because the row says “evidence role”, “status role”, or similar wording.
  4. A relation, declaration-local slot, interface, port, or signature name hides the exact governed object, relation-participant meaning, or rules that define or constrain the claim.
  5. A term chosen for convenience becomes a permanent Core-facing name without candidate comparison, rejected alternatives, or lineage.
  6. Local names proliferate until the corpus has several almost-synonyms and no recoverable reason for choosing one.

Recover the governed value, then record a naming settlement whose kind, effective reference scheme, exact local sense, intended use, and selected designations remain visible. Publication is a separate later relation.

F.18:3 - Forces

ForceNaming tension
Local sense and reuse across different semantic-context projectionsA name must be interpretable under one effective by-value ReferenceScheme while remaining bridgeable to a different <ReferenceScheme, LocalSenseClaim> projection without spelling-based identity. The projections can differ under one scheme.
Brevity and ontology recoveryA short label helps conversation, but the NameCard must keep governed kind, effective reference scheme, local sense, subject pattern, and intended use recoverable.
Continuity and correctionReaders need stable public names, while authors must be able to rename, split, merge, or retire names without erasing earlier uses.
Familiarity and precisionFamiliar words are easier to adopt, but some familiar words import wrong prototypes from another discipline.
System-role recognition and ontology expansionSystemRole 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.

F.18:4 - Solution

Use a local-first naming protocol:

  1. Recover the governed value, its kind, and its subject pattern.

  2. Decide whether the expression should remain local or the current use needs a durable reusable name; apply F.14 before adding a card, cell, or row.

  3. For a durable name, constitute one NameCard episteme under C.2.1; keep the value, its kind, the card, selected designations, exact local sense, and any basis or Bridge relation distinct.

  4. Choose the Tech label and any Plain designation needed for a stated didactic use from the smallest candidate set that covers the live head-term families and plausible neighbouring objects.

  5. Record the covered alternatives, rejected candidates, selection reason, lineage, and the condition that reopens the settlement.

  6. Only for public, Core-facing, durable-across-context, or cross-context reuse, test the then-current F.17 entry. It must accept the exact governed value and kind, NameCard episteme, by-value scheme, local sense, and any actual Bridge. Public or durable reuse alone creates no Bridge.

    When the named use relates different <ReferenceScheme, LocalSenseClaim> projections, F.17 must also accept the separate affirmative C.2.1 claim and current A.10 or B.3 reliance through the row rationale or notes rather than treating either as NameCard content.

    The F.17 result must supply the required public row. If any required input or result is absent, retain the durable name and NameCard locally, mark the public row pending, and stop.

  7. Keep each cited subject, relation and later operation under its own rules. In particular, distinguish the Bridge, the separate claim about its named use, A.10 or B.3 reliance, and authorization. F.18 governs the naming settlement.

F.18:4.1 - Naming Invariants

Every durable name must satisfy these invariants.

InvariantRequired content
Governed value firstName the governed value or value family before naming the label.
Direct pattern visibleCite the pattern description containing the exact defining or constraining ClaimGraph for the value: for example A.2 with C.3 for a local system-role kind, A.2.1 for one system-role assignment species, A.6.5 for relation slot discipline, F.10 or A.19.SPR for status-value use, and A.10 for evidence use.
Reference scheme visibleThe NameCard carries its effective EpistemeInterpretationScheme value, with the rules needed to interpret the naming claims and local sense; a model-use structure, claim scope, project work, or other locality relation remains separate and appears only when the naming use needs it.
Local sense visibleEvery card states one exact local-sense claim under the effective scheme. A progressive-minimum card may state it directly as LocalSenseRef; an expanded card uses LocalSenseCellRef only when it resolves to the current F.17 scheme-based coordinate. Any basis episteme and local-sense basis relation remain separate.
Registers serve the useThe Tech label is precise. Add a Plain designation when the stated didactic use needs it; it names the same governed value under the same local meaning.
Candidate comparison visibleCompare the live head families and plausible neighbouring-object readings that could change the choice. A cited external standard may fix the label; its fit to the governed value and intended use still needs examination.
Bridge only between different semantic-context projectionsCompare the exact <ReferenceScheme, LocalSenseClaim> pairs. Same scheme plus same claim plus another expression is a designation question and creates no Bridge. Same scheme plus another claim opens the F.9 question and, for a named use, the separate claim-and-reliance branch. Different scheme also opens only the Bridge question. No current correspondence use creates no Bridge or use claim regardless of scheme count. An obtaining Bridge establishes only the exact sense relation; it establishes neither governed-value identity nor authorization.
Lineage visibleRename, split, merge, retirement, and alias decisions are recorded.

F.18:4.2 - NameCard Fields

A NameCard is complete when its full interpreted naming-settlement content (ClaimGraph) is recoverable under C.2.1. That value satisfies NonemptyClaimContent; membership alone does not supply the narrower naming-settlement claims required here.

A compact card states the governed value and subject pattern, effective scheme and local-sense claim, the selected Tech designation and any Plain designation needed for a stated didactic use, candidate set, rejections, rationale, lineage, and reopen condition. The subject pattern can make the governed kind unambiguous. These claims together constitute the complete semantic content; an omitted expanded field contributes no hidden claim.

The compact cards NC-U-RELATION, NC-PROBLEM-CRITERION-APPLICABILITY-RELATION, and NC-PROBLEMATIC-FOR-RELATION use this form. Section 4.2a carries four expanded bounded-model-use cards.

Use the expanded form only when the current naming use needs the additional position:

NameCard:
  NameCardId:
  GovernedValueRef:
  GovernedValueKindRef: [add when the kind is not unambiguous from the value and subject pattern, or a consumer needs the exact kind reference]
  SubjectPatternLocator:
  ReferenceScheme: EpistemeInterpretationScheme, byValue
  ClaimContent: NonemptyClaimContent // complete naming-settlement content; a designated input resolves under C.2.1:4.2.6
  LocalSenseCellRef: [add when a separately recoverable F.17 scheme-based SenseCell is current; otherwise LocalSenseRef carries the direct local-sense claim]
  LocalSenseBasisRelationRef: [add only for an actual separately governed basis relation]
  TechLabel:
  PlainLabel: [add when the naming use needs a Plain designation]
  CandidateSet:
  CandidateCoverage: [add when family coverage, an open alternative, or a forced exception must be explicit]
  RejectedCandidates:
  SelectionRationale:
  BridgeRefs: [add only for actual F.9 Bridge occurrences used to align exact local senses; no use direction, rule, tolerance, polarity, or reliance lives here]
  PublicRowStatus: [add when public-row use is current]
  UnifiedTermRowRef: [add only for a current row admitted under section 4.4]
  LineageEntries:
  RefreshCondition:

Field discipline:

  • The card is a C.2.1 episteme. GovernedValueRef resolves to its exact EntityOfConcern; ClaimContent is the complete interpreted naming-settlement content in NonemptyClaimContent; and ReferenceScheme is the effective by-value EpistemeInterpretationScheme under which those claims are interpreted. Changing any of those three values identifies another card episteme. Changing only a content or card designator, carrier, field order, or layout does not.

  • The expanded form’s ClaimContent names the complete semantic value expressed by its readable sibling fields. The examples’ .ClaimGraph labels are local content designators; a label or graph encoding is not the value.

    When a representation instead supplies a stored constituent designation, declare a C.2.1:4.2.6 ClaimContentDesignation whose exact source edition and selection resolve to that complete naming-settlement content. The source may supply its whole content or an intrinsic semantic selection; resolve it before applying the content-range and naming-completeness tests.

    Changing a selected Tech/Plain name asserted by the card, declared use, local-sense claim, coverage, rejection, rationale, lineage, or reopen claim changes the content and therefore the card episteme even if the displayed content or card designator stays the same.

  • NameCardId designates the card episteme. It is not another identity discriminator and does not create a card kind.

  • GovernedValueRef resolves to the exact already-governed object or value being named. GovernedValueKindRef is added when the kind is not already unambiguous from that value and its subject pattern, or when a receiving use needs the exact kind reference. For relation-facing wording the value reference resolves to exactly one of the objects distinguished in section 5.6; a field label, card, table row, or local phrase is not a proxy for that object.

  • subjectPatternLocator names the pattern description containing the exact ClaimGraph that defines or constrains the value. F.18 defines only the naming-settlement predicate recorded in the card; a pattern that merely presents or teaches the name defines neither the value nor this settlement.

  • LocalSenseRef in a progressive-minimum card states the exact local-sense claim directly under the card’s by-value scheme. LocalSenseCellRef in an expanded card resolves to the current F.17 coordinate <ReferenceScheme by value, LocalExpression, LocalSenseClaim> and does not require a context holon. LocalSenseBasisRelationRef is present only when a separately governed relation to a basis episteme is current; a source title, card field, or publication is not that relation.

  • CandidateSet records the plausible labels considered by head-term family. When family coverage or an exception is not already recoverable from the set, rejections, and rationale, add CandidateCoverage to state which live families and neighbouring-object readings were tested and whether any plausible alternative remains open.

  • RejectedCandidates records why tempting names were not selected. A usable alias is recorded in lineage as an alias, not left as a second selected Plain label.

  • BridgeRefs contains only actual F.9 Bridge occurrences whose relation-semantic profiles obtain for the exact endpoint senses. It carries no naming-use direction, use-specific rule, tolerated loss, polarity, reliance, or permission. When naming across different semantic-context projections relies on a Bridge, recover the separate C.2.1 claim and its current A.10 or B.3 reliance outside the NameCard; omit BridgeRefs when the settlement makes no Bridge claim.

  • PublicRowStatus is exactly one of localOnly, pending, or current when public-row use is current. UnifiedTermRowRef separately resolves to the exact row and is present only when status is current after the section 4.4 F.17 entry/result gate passes. Omission in a compact card claims no row. A pending public use does not imply that a row already exists.

  • RefreshCondition names a change to the value, kind, scheme, local sense, Bridge, subject pattern or receiving use, or a repeated reader error, that requires reconsidering this settlement.

An eligible partial scheme can leave a naming claim or reference uninterpreted; resolve that gap before the exact settlement or public-row use. Known typography-only rules fail the scheme criterion. Content and scheme membership establish neither a supported local sense, an obtaining basis relation or Bridge, suitability for a named cross-local use, nor actual use.

Names such as “foundational principle pattern set”, “FPF Core”, “domain principle framework”, and “local practice framework” require ordinary NameCard work before public stabilization under an effective reference scheme. Source aliases such as ZPF, SPF, TPF, or broad xPF labels remain intake aliases until F.18 has settled the governed value and kind, by-value reference scheme, exact local sense, rejected candidates, and admissible short form.

F.18:4.2a - Current Bounded-Model-Use NameCards

The four expanded cards below record the FPFCoreReferenceScheme naming settlements used in F.17:12.4d-12.4e. Each resolves to one scheme-based F.17 cell and its separately governed local-sense basis relation. The cards state selected designations for already governed values. Establish the subject relations under A.1.1 and use E.24.PUB when a row edition must be made available.

NameCard:
  NameCardId: NC-BOUNDED-MODEL-USE-STRUCTURE
  GovernedValueRef: BoundedModelUseStructure
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.1.1
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-BOUNDED-MODEL-USE-STRUCTURE.ClaimGraph — the NonemptyClaimContent value expressed by all identity-bearing naming-settlement claims below
  LocalSenseCellRef: SenseCell.BoundedModelUseStructure.FPFCore.2026-07-25
  LocalSenseBasisRelationRef: LocalSenseBasisRelation.BoundedModelUseStructure.FPFCore.2026-07-25
  TechLabel: BoundedModelUseStructure
  PlainLabel: bounded context
  CandidateSet: BoundedModelUseStructure; ModelApplicabilityStructure; ModelUseRelationStructure; BoundedContextStructure; U.BoundedContext
  CandidateCoverage: exact dependent-structure head; applicability-only neighbour; use-only neighbour; DDD retrieval head; false holon-kind neighbour; no plausible live head family remains untested
  RejectedCandidates: ModelApplicabilityStructure omits actual use and fixed-content expression coherence; ModelUseRelationStructure collapses the wider organization into one relation family; BoundedContextStructure hides what is bounded and invites a container reading; U.BoundedContext falsely claims another holon kind
  SelectionRationale: the Tech label names the A.1.1 dependent U.Structure specialization selected from one exact model edition, admitted model-use holons, obtaining applicability, actual-use, and fixed-content expression-coherence occurrences, exact applied constraint claims, and one named frame; the Plain label retains DDD retrieval without adding a context bearer or any crossing to that identity
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.BoundedModelUseStructure.FPFCore.2026-07-25
  LineageEntries: DDD bounded-context wording retained as the Plain retrieval label; U.BoundedContext holon, boundary-container, semantic-frame-bundle, and crossing-bearing readings retired; any crossing belongs only to a distinct A.22 structure over already identified bounded model-use structures
  RefreshCondition: reopen when the A.1.1/A.22 membership or continuity rule, one of the three direct relation kinds, the exact constituent, selected-occurrence, applied-constraint, or frame discriminator, FPFCoreReferenceScheme, the current F.17 cell or row, or repeated container or crossing overreading changes
NameCard:
  NameCardId: NC-MODEL-APPLICABILITY-RELATION
  GovernedValueRef: ModelApplicabilityRelation
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.1.1
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-MODEL-APPLICABILITY-RELATION.ClaimGraph — the NonemptyClaimContent value expressed by all identity-bearing naming-settlement claims below
  LocalSenseCellRef: SenseCell.ModelApplicabilityRelation.FPFCore.2026-07-25
  LocalSenseBasisRelationRef: LocalSenseBasisRelation.ModelApplicabilityRelation.FPFCore.2026-07-25
  TechLabel: ModelApplicabilityRelation
  PlainLabel: this model applies to this holon within this claim scope
  CandidateSet: relation-kind heads {ModelApplicabilityRelation, ModelAppliesToRelation, ModelScopeRelation}; claim-or-predicate heads {ModelApplicabilityClaim, ModelApplicabilityPredicate}; temporal head {ModelApplicabilityInterval}
  CandidateCoverage: direct ternary relation kind; readable predicate direction; claim or predicate neighbour; scope-membership neighbour; derived temporal-extent neighbour; no plausible live head family remains untested
  RejectedCandidates: ModelAppliesToRelation suggests a binary relation and hides the participating claim scope; ModelScopeRelation mistakes A.2.6 scope membership for model applicability; ModelApplicabilityClaim and ModelApplicabilityPredicate name epistemic or semantic content; ModelApplicabilityInterval names the derived maximal continuous extent
  SelectionRationale: the Tech label names the direct relation kind over one model episteme, exact holon, and participating claim scope; the Plain sentence exposes the predicate; applicability holds only when the A.1.1 predicate is satisfied, and the A.1.1 identity rule reidentifies the maximal continuous occurrence, leaving scope membership, assertion, interval, and structure separate
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.ModelApplicabilityRelation.FPFCore.2026-07-25
  LineageEntries: retains the A.1.1 relation-kind label; earlier broad applicable-model and context-boundary wording is not an alias; ModelApplicabilityInterval remains a local derived extent
  RefreshCondition: reopen when A.1.1 changes the participant kinds, applicability predicate, scope-alignment or model-scheme interpretation rule, temporal occurrence identity, FPFCoreReferenceScheme, the current F.17 cell or row, or the public receiving use
NameCard:
  NameCardId: NC-MODEL-USE-RELATION
  GovernedValueRef: ModelUseRelation
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.1.1
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-MODEL-USE-RELATION.ClaimGraph — the NonemptyClaimContent value expressed by all identity-bearing naming-settlement claims below
  LocalSenseCellRef: SenseCell.ModelUseRelation.FPFCore.2026-07-25
  LocalSenseBasisRelationRef: LocalSenseBasisRelation.ModelUseRelation.FPFCore.2026-07-25
  TechLabel: ModelUseRelation
  PlainLabel: this assignment's holder uses this model during this work concerning this holon
  CandidateSet: relation-kind heads {ModelUseRelation, ModelUsageRelation, ModelApplicationRelation}; work-or-assignment heads {ModelUseWork, ModelUserRoleAssignment}; claim-or-record heads {ModelUseClaim, ModelUseRecord}
  CandidateCoverage: direct actual-use relation; availability-or-usage neighbour; applicability neighbour; Work neighbour; assignment neighbour; claim or record neighbour; no plausible live head family remains untested
  RejectedCandidates: ModelUsageRelation invites availability, access-count, or generic usage readings; ModelApplicationRelation collides with applicability and can suggest applying a method; ModelUseWork and ModelUserRoleAssignment name participants; ModelUseClaim and ModelUseRecord name epistemes about use
  SelectionRationale: the Tech label names the direct relation kind over one system-role-assignment occurrence, model episteme, performed Work occurrence, and use-locus holon; the Plain sentence exposes actual use by the derived assignment holder without adding that system as a fifth participant, while A.1.1 keeps applicability, assignment, Work, method application, claim, and record distinct
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.ModelUseRelation.FPFCore.2026-07-25
  LineageEntries: retains the A.1.1 relation-kind label; availability, mention, method application, performed Work, system-role assignment, and use-claim readings remain separate and are not aliases
  RefreshCondition: reopen when A.1.1 changes the participant kinds, an expressly consumed F.6 performed-under-assignment attribution condition, actual-use predicate, actor derivation, maximal-continuous-use identity, FPFCoreReferenceScheme, the current F.17 cell or row, or the public receiving use
NameCard:
  NameCardId: NC-MODEL-EXPRESSION-COHERENCE-RELATION
  GovernedValueRef: ModelExpressionCoherenceRelation
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.1.1
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-MODEL-EXPRESSION-COHERENCE-RELATION.ClaimGraph — the NonemptyClaimContent value expressed by all identity-bearing naming-settlement claims below
  LocalSenseCellRef: SenseCell.ModelExpressionCoherenceRelation.FPFCore.2026-07-25
  LocalSenseBasisRelationRef: LocalSenseBasisRelation.ModelExpressionCoherenceRelation.FPFCore.2026-07-25
  TechLabel: ModelExpressionCoherenceRelation
  PlainLabel: this model content and this expression content satisfy this declared coherence criterion under this comparison scheme
  CandidateSet: relation-kind heads {ModelExpressionCoherenceRelation, ModelConformanceRelation, ModelImplementationRelation, ModelExpressionAlignmentRelation}; predicate-or-assessment heads {ModelExpressionCoherencePredicate, ModelExpressionCoherenceAssessment}
  CandidateCoverage: direct fixed-content relation; conformance neighbour; implementation or realization neighbour; weaker alignment neighbour; local predicate-value neighbour; evaluation or result neighbour; no plausible live head family remains untested
  RejectedCandidates: ModelConformanceRelation invites compliance or status readings and hides the declared criterion and permitted loss; ModelImplementationRelation suggests realization, production, or causation; ModelExpressionAlignmentRelation is weaker than the declared Boolean condition; ModelExpressionCoherencePredicate names the five-part criterion participant; ModelExpressionCoherenceAssessment names evaluation Work or a result episteme
  SelectionRationale: the Tech label names the participant-determined direct relation over one model episteme, expression episteme, admitted five-part predicate value, and comparison scheme; the Plain sentence exposes the truth test after either the same-scheme branch or the predicate-declared bridged branch is established, while maintenance, transformation, evaluation, result, evidence, and assertion remain separate
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.ModelExpressionCoherenceRelation.FPFCore.2026-07-25
  LineageEntries: retains the A.1.1 relation-kind label; earlier maintenance-alignment and implementation wording is narrowed to separate Work, transformation, evaluation, result, evidence, and assertion objects
  RefreshCondition: reopen when A.1.1 changes the participant kinds, five-part predicate-value membership, same-scheme or bridged-comparison branch, permitted-loss rule, participant-determined identity, FPFCoreReferenceScheme, the current F.17 cell or row, or the public receiving use

These four naming settlements require no correspondence between different <ReferenceScheme, LocalSenseClaim> projections, so they add no Bridge or use claim.

If a named current use relates different <ReferenceScheme, LocalSenseClaim> projections, apply the F.9 predicate to the possible Bridge, identify the affirmative bounded-use claim separately under C.2.1, and apply A.10 or B.3 to the relied-on evidence or assurance claim; without that use, add no Bridge or use claim.

For ModelExpressionCoherenceRelation, an A.1.1 predicate may require an obtaining Bridge in its bridged interpretation branch; a receiving assertion or structure selection that relies on that occurrence still needs its own bounded-use claim and reliance path. The NameCard records the naming settlement; a row may cite the separate Bridge, bounded-use claim and reliance when its use needs them.

F.18:4.2b - Current Role-Precision NameCards

The eight cards below record Core-facing designations for values defined or constrained by their subject patterns. They share FPFCoreReferenceScheme and need no Bridge for these naming uses. Each card cites the E.10 token-class, allowed-use and collision rules on which its designations depend.

NameCard:
  NameCardId: NC-U-SYSTEM-ROLE-ASSIGNMENT
  GovernedValueRef: U.SystemRoleAssignment
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.2.1
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-U-SYSTEM-ROLE-ASSIGNMENT.ClaimGraph
  LocalSenseCellRef: SenseCell.U.SystemRoleAssignment.FPFCore.2026-08-09
  TechLabel: U.SystemRoleAssignment
  PlainLabel: assignment to a system role
  CandidateSet: U.SystemRoleAssignment; U.RoleAssignment; U.SystemAssignment; U.SystemRoleHoldingRelation
  RejectedCandidates: U.RoleAssignment leaves role ambiguous; U.SystemAssignment loses the assigned kind; U.SystemRoleHoldingRelation suggests possession
  SelectionRationale: Assignment names the relation family and SystemRole identifies the assigned local-kind family
  DeclaredUse: Core-facing citation of the retained direct assignment family and its directly declared species
  NonAdmissibleUse: no system-role kind, assignment record, field, occurrence, authority, responsibility, or Work follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for U.SystemRoleAssignment; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.U.SystemRoleAssignment.FPFCore.2026-08-09
  LineageEntries: U.RoleAssignment is retired as a positive Tech designation and remains only in marked lineage, rejection, or historical evidence
  RefreshCondition: reopen when A.2.1 changes the family, direct-species grammar, or participant rule; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when repeated reader interpretation changes

NameCard:
  NameCardId: NC-KIND-USE-ADAPTATION-DECLARATION
  GovernedValueRef: KindUseAdaptationDeclaration
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: C.3.4
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-KIND-USE-ADAPTATION-DECLARATION.ClaimGraph
  LocalSenseCellRef: SenseCell.KindUseAdaptationDeclaration.FPFCore.2026-08-09
  TechLabel: KindUseAdaptationDeclaration
  PlainLabel: declaration of a local use of a kind
  CandidateSet: RoleMask; KindUseMask; KindUseProfile; KindUseAdaptationDeclaration
  RejectedCandidates: RoleMask suggests a system-role object; Mask hides the declaration episteme; Profile suggests a container or another governed kind
  SelectionRationale: the selected head exposes a declaration that adapts one named use of one exact base kind
  DeclaredUse: Core-facing citation of the C.3.4 declaration episteme family
  NonAdmissibleUse: no kind, assignment, scope, profile, system role, guard decision, or candidate judgment follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for KindUseAdaptationDeclaration; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.KindUseAdaptationDeclaration.FPFCore.2026-08-09
  LineageEntries: RoleMask is retired as a positive designation and remains only in marked lineage, rejection, or historical evidence
  RefreshCondition: reopen when C.3.4 changes the declaration identity, pinned inputs, or guard use; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when reader interpretation changes

NameCard:
  NameCardId: NC-KIND-USE-ADAPTATION-CORRESPONDENCE-DECLARATION
  GovernedValueRef: KindUseAdaptationCorrespondenceDeclaration
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: C.3.4
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-KIND-USE-ADAPTATION-CORRESPONDENCE-DECLARATION.ClaimGraph
  LocalSenseCellRef: SenseCell.KindUseAdaptationCorrespondenceDeclaration.FPFCore.2026-08-09
  TechLabel: KindUseAdaptationCorrespondenceDeclaration
  PlainLabel: declaration of how two local ways of using kinds correspond and what is lost
  CandidateSet: MaskAdapter; KindUseAdaptationAdapterDeclaration; KindUseAdaptationMappingDeclaration; KindUseCorrespondenceDeclaration; KindUseAdaptationCorrespondenceDeclaration
  RejectedCandidates: Adapter suggests execution; Mapping can name a Method or representation; KindUseCorrespondenceDeclaration loses the endpoint family
  SelectionRationale: Correspondence names the declared rule and loss while Declaration keeps the object epistemic
  DeclaredUse: Core-facing citation of the C.3.4 cross-context declaration episteme family
  NonAdmissibleUse: no obtaining F.9 Bridge, executable adapter, mapping Method, representation correspondence, assignment, or target truth follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for KindUseAdaptationCorrespondenceDeclaration; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.KindUseAdaptationCorrespondenceDeclaration.FPFCore.2026-08-09
  LineageEntries: MaskAdapter is retired as a positive designation and remains only in marked lineage, rejection, or historical evidence
  RefreshCondition: reopen when C.3.4 changes the endpoint families, correspondence or loss content, or non-Bridge boundary; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when reader interpretation changes

NameCard:
  NameCardId: NC-KIND-USE-ADAPTATION-JUDGMENT
  GovernedValueRef: KindUseAdaptationJudgment
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: C.3.4
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-KIND-USE-ADAPTATION-JUDGMENT.ClaimGraph
  LocalSenseCellRef: SenseCell.KindUseAdaptationJudgment.FPFCore.2026-08-09
  TechLabel: KindUseAdaptationJudgment
  PlainLabel: judgment of whether a candidate fits a local use of a kind
  CandidateSet: masked judgment; J_mask; KindUseJudgment; KindUseAdaptationJudgment
  RejectedCandidates: masked judgment and J_mask retain the old metaphor; KindUseJudgment loses the adaptation-declaration reading
  SelectionRationale: the selected name identifies the exact three-valued judgment family; J_kindUse remains local notation
  DeclaredUse: Core-facing citation of the C.3.4 three-valued result family
  NonAdmissibleUse: no declaration, candidate, guard disposition, evidence result, or kind-membership relation follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for KindUseAdaptationJudgment; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.KindUseAdaptationJudgment.FPFCore.2026-08-09
  LineageEntries: masked judgment and J_mask are retired positive designations; J_kindUse is declaration-local notation and receives no row
  RefreshCondition: reopen when C.3.4 changes the pinned inputs, truth-value set, or judgment identity; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when reader interpretation changes

NameCard:
  NameCardId: NC-SYSTEM-ROLE-KIND-DESCRIPTION
  GovernedValueRef: SystemRoleKindDescription
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: F.4
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-SYSTEM-ROLE-KIND-DESCRIPTION.ClaimGraph
  LocalSenseCellRef: SenseCell.SystemRoleKindDescription.FPFCore.2026-08-09
  TechLabel: SystemRoleKindDescription
  PlainLabel: description of a system-role kind
  CandidateSet: RoleDescription; SystemRoleDescription; SystemRoleKindDescription; SystemRoleKindDescriptionEpisteme
  RejectedCandidates: RoleDescription is trigger-ambiguous; SystemRoleDescription leaves kind and assignment readings open; the Episteme suffix repeats the Description head
  SelectionRationale: Kind identifies the exact EntityOfConcern and Description identifies the episteme
  DeclaredUse: Core-facing citation of the F.4 description-episteme construction
  NonAdmissibleUse: no described kind, assignment, NameCard, row, publication form, or carrier follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for SystemRoleKindDescription; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.SystemRoleKindDescription.FPFCore.2026-08-09
  LineageEntries: RoleDescription is retired as a positive Tech designation and remains only in marked lineage, rejection, or historical evidence
  RefreshCondition: reopen when F.4 changes the described EntityOfConcern or description identity; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when reader interpretation changes

NameCard:
  NameCardId: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-RELATION
  GovernedValueRef: SystemRoleAssignmentStateRelation
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.2.5
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-RELATION.ClaimGraph
  LocalSenseCellRef: SenseCell.SystemRoleAssignmentStateRelation.FPFCore.2026-08-09
  TechLabel: SystemRoleAssignmentStateRelation
  PlainLabel: this assignment to a system role satisfies this state condition
  CandidateSet: RoleStateRelation; SystemRoleStateRelation; AssignmentStateRelation; SystemRoleAssignmentStateRelation
  RejectedCandidates: RoleStateRelation and SystemRoleStateRelation lose the assignment occurrence; AssignmentStateRelation is too broad
  SelectionRationale: the name identifies the direct relation kind over one exact assignment occurrence and one predicate value
  DeclaredUse: Core-facing citation of the A.2.5 direct relation kind and its exact occurrences
  NonAdmissibleUse: no state assertion, displayed status, predicate value, assignment, or obtaining occurrence follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for SystemRoleAssignmentStateRelation; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.SystemRoleAssignmentStateRelation.FPFCore.2026-08-09
  LineageEntries: RoleStateRelation is retired as a positive Tech designation and remains only in marked lineage, rejection, or historical evidence
  RefreshCondition: reopen when A.2.5 changes the relation participants, predicate, or identity; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when reader interpretation changes

NameCard:
  NameCardId: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-PREDICATE
  GovernedValueRef: SystemRoleAssignmentStatePredicate
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.2.5
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-PREDICATE.ClaimGraph
  LocalSenseCellRef: SenseCell.SystemRoleAssignmentStatePredicate.FPFCore.2026-08-09
  TechLabel: SystemRoleAssignmentStatePredicate
  PlainLabel: state condition for an assignment to a system role
  CandidateSet: RoleStatePredicate; SystemRoleStatePredicate; AssignmentStatePredicate; SystemRoleAssignmentStatePredicate
  RejectedCandidates: RoleStatePredicate and SystemRoleStatePredicate name the wrong subject; AssignmentStatePredicate is too broad
  SelectionRationale: the name identifies the truth-condition family over exact system-role assignments
  DeclaredUse: Core-facing citation of the A.2.5 predicate-value family
  NonAdmissibleUse: no relation occurrence, assertion, displayed result, state label, or assignment follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for SystemRoleAssignmentStatePredicate; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.SystemRoleAssignmentStatePredicate.FPFCore.2026-08-09
  LineageEntries: RoleStatePredicate is retired as a positive Tech designation and remains only in marked lineage, rejection, or historical evidence
  RefreshCondition: reopen when A.2.5 changes the truth condition, value family, or relation use; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when reader interpretation changes

NameCard:
  NameCardId: NC-SYSTEM-ROLE-KIND-RELATION-STRUCTURE
  GovernedValueRef: SystemRoleKindRelationStructure
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.2.7
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-SYSTEM-ROLE-KIND-RELATION-STRUCTURE.ClaimGraph
  LocalSenseCellRef: SenseCell.SystemRoleKindRelationStructure.FPFCore.2026-08-09
  TechLabel: SystemRoleKindRelationStructure
  PlainLabel: structure of relations among system-role kinds
  CandidateSet: RoleRelationStructure; SystemRoleRelationStructure; SystemRoleKindRelationStructure; SystemRoleAssignmentRelationStructure
  RejectedCandidates: RoleRelationStructure is ambiguous; SystemRoleRelationStructure loses the kind substrate; SystemRoleAssignmentRelationStructure names the wrong substrate
  SelectionRationale: the designation names A.2.7's relation-defined structure kind; Kind in the compound identifies its system-role-kind constituents, not one selected instance
  DeclaredUse: Core-facing designation of the relation-defined kind specified by A.2.7; citing one member still requires its exact constituents, selected obtaining relation occurrences, applied constraints, and named selection-use frame
  NonAdmissibleUse: no new root kind, selected structure instance, assignment configuration, taxonomy episteme, graph, table, or system collection follows from the name or card
  LexicalPrerequisiteRefs: E.10:7.5b KernelToken classification and allowed-use rule for SystemRoleKindRelationStructure; E.10:7.5a reserved-name collision rule
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.SystemRoleKindRelationStructure.FPFCore.2026-08-09
  LineageEntries: RoleRelationStructure is retired as a positive Tech designation and remains only in marked lineage, rejection, or historical evidence
  RefreshCondition: reopen when A.2.7 changes the substrate or selected-relation identity; when FPFCoreReferenceScheme, the E.10 token classification or allowed-use rule, or the current F.17 cell or row changes; when a new collision appears under E.10:7.5a; or when reader interpretation changes

Each card has one exact governed value and one selected Tech/Plain pair. No card is created for the SystemRole morphology, J_kindUse, a declaration-local slot, or a context field.

F.18:4.2c - Demonstrative wording without a fabricated value or scheme

A.22.CGUS:4.4 permits one exact C.2.1 episteme to show a traversal through an already qualified CGUS. It does not define a demonstrative-slice U.Kind, and DemonstrativeUnfoldingSlice@Context does not identify an exact slice by itself. Before using a label such as FPFSeminarTeachingReferenceScheme-2026-07-11 for another scheme, recover that scheme by value and identify any interpretation that differs from FPFCoreReferenceScheme.

Keep demonstrative walkthrough as ordinary readable wording when a sentence already makes the exact shown slice clear. Keep mantra as bounded seminar or pattern-local recall wording when repetition and attention are the point. These local recall uses need no durable naming settlement or public row.

If a later use needs stable citation of one exact slice, first recover that C.2.1 episteme from its claim content, the qualified CGUS it concerns, and its effective scheme. Then make one NameCard only if durable naming is useful. When a second exact scheme-and-sense projection changes the interpretation, reuse its naming settlement or make a card if it needs a durable name. If a named use depends on correspondence between the projections, test that relation under F.9 and follow §4.4.1.

Availability remains a separate E.24.PUB operation. mantra move stays E.10.MOVE Plain wording for a shown E.11.PUA continuation description; it is not a durable value or a second scheme.

F.18:4.2d - Rule-content names with unresolved lexical prerequisites

Consider the following R7 naming candidates under the by-value FPFCoreReferenceScheme. Keep each governed U.NameToken separate from the predicate or designation value it names.

Suppose the E.10 TokenClass, reserved-name and allowed-scope prerequisites have not yet been established for these candidates. They remain naming candidates. There is no current NameCard or public row to cite until the lexical prerequisites and naming decisions for that row are settled. These naming uses require no semantic correspondence and make no Bridge claim.

Candidate expressionExact local sense and governed valueCovered head families and rejected overreadThree-arena invarianceReopen/close condition
SelectedRuleContentSubgraphDesignationuse-relative designation resolving the exact nonempty base subgraph selected in one identified derivation or criterion-selection claim; governed node SelectedRuleContentSubgraphDesignation@RuleContentBasisFindingDefinition-R7selected subgraph/designation, selected basis/reference, and rule-bearing classifier families were compared; reject intrinsic RuleBearing..., generic Base, and reference-only heads because the value is selection-relative and by-valuemanufacturing assembly-rule selection; healthcare protocol-premise selection; cloud deployment-policy criterion selectionclose only when exact LEX.TokenClass, LEX.Reserved-Names, and LEX.AllowedScopes values and assertions pass under FPFCoreReferenceScheme; reopen on R7 semantic or scheme change
derivedUsingRuleContentpredicate true only when an identified derivation claim used exact base content as a formal premise under a declared inference rule/application to produce exact dependent content; governed node derivedUsingRuleContent@RuleContentBasisFindingDefinition-R7derived-using, derived-from, supported-by, and based-on families were compared; reject derivedFrom because source/provenance and semantic derivation are broader, and reject supportedBy/basedOn because they hide actual formal-premise usemanufacturing configuration derivation; healthcare dosage derivation with evidence kept separate; cloud configuration derivationsame lexical prerequisites as above, plus exact R7 predicate identity
evaluatedAgainstRuleContentpredicate true only when an identified criterion-selection claim selected exact base content for one bounded evaluation claim concerning exact dependent content; governed node evaluatedAgainstRuleContent@RuleContentBasisFindingDefinition-R7evaluated-against, assessed-under, governed-by, and checked-with families were compared; reject governedBy and generic checkedWith because they hide criterion selection and can imply authority, Work, or tool usemanufactured configuration evaluation; healthcare protocol-conformance evaluation; cloud release evaluation against deployment policy while operational Work stays separatesame lexical prerequisites as above, plus exact R7 predicate identity

A collision-free text search does not establish the missing governed lexical values. In this situation, quote the spellings as candidates when discussing the R7 declaration; cite a current NameCard or public term row only after the lexical prerequisites and naming settlement are established.

F.18:4.2e - Architectural Reference NameCard

This card names the architectural-reference form governed by E.4:4.1, E.11.PFP:4.7 and E.11.DSG: a public account of a named method language’s architecture, reasons and shared explanation. The governed value is this functional publication-unit form, not one framework, Suite, Library, product series, edition, answer, lookup activity or publication occurrence. The form can be embedded or separately carried.

NameCard:
  NameCardId: NC-ARCHITECTURAL-REFERENCE
  GovernedValueRef: E.4:4.1 architectural-reference publication-unit form
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: E.4:4.1; E.11.PFP:4.7; E.11.DSG
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NC-ARCHITECTURAL-REFERENCE.ClaimGraph
  LocalSenseCellRef: SenseCell.ArchitecturalReference.FPFCore.2026-10-12
  TechLabel: ArchitecturalReference
  PlainLabel: architectural reference
  CandidateSet: Reference; Architectural Reference; Architecture Reference; Framework Reference; Overview; Preface; Handbook; Companion; Manual; Guide; architecture decision record; index; catalogue
  CandidateCoverage: functional account, introductory location, question-led reference, instructional publication, decision history and finding-aid readings were compared for embedded and separately carried accounts at framework, Suite and Library levels
  RejectedCandidates: bare Reference leaves the explained whole and architectural function unclear; Framework Reference alone does not cover Suite and Library names; Preface names a placement without specifying the function; Overview can understate the developed rationale and shared explanation; Handbook, Manual and Guide invite a broad instructional reading; Companion does not say what is explained; architecture decision record implies decision history; index and catalogue omit the account; Architecture Reference is possible ordinary wording but does not improve the selected qualified title
  SelectionRationale: architectural reference names a consultable public account of the structure, connections and reasons of an already identified method language; Architectural states the function while the whole's name states its subject, regardless of carrier
  DeclaredUse: use <name of the explained whole> Architectural Reference as the full public title; use a shorter mention only while the whole is unambiguous; cite the generic form across E.4, E.11.PFP and E.11.DSG without creating a name family for each carrier or assembly level
  NonAdmissibleUse: the name establishes no disciplinary parthood, composite Method, independent product series, edition admission, availability or maintenance; a reference entry cannot substitute for a missing E.8 Method, and an architectural reference is not a separate teaching Guide or decision-history record
  BridgeRefs: none
  PublicRowStatus: current
  UnifiedTermRowRef: UTS.ArchitecturalReference.FPFCore.2026-10-12
  LineageEntries: DPFSuiteReference names the narrower cross-DPF answer-publication sense and is not an alias for this broader function; a shared host or section number establishes no identity or historical edition relation between the naming objects
  RefreshCondition: reopen when the explained-language function, required public rationale, carrier independence, product boundary or title use changes; when readers confuse the account with a Method, Guide, decision record or new discipline; or when the governing scheme, exact sense cell or row changes

This naming use requires no correspondence between different local senses, so the settlement adds no F.9 Bridge or correspondence-use claim. FPF Library Architectural Reference, Engineering Suite Architectural Reference and Method Engineering Principle Framework Architectural Reference qualify the same functional designation by the explained whole. They do not name new kinds or independently maintained series.

The full title, filename, declared publication-unit key and stable SectionRef are separate; changing a title does not by itself preserve an old Markdown fragment.

F.18:4.3 - Candidate Selection

Build the smallest candidate set that covers the live head-term families and plausible neighbouring-object readings that could change the decision. A cited external standard may fix the label under §4.1. One supported candidate is enough when examination leaves no live alternative that could change the choice. Stop when the relevant comparison is sufficient. If a deadline forces closure while a plausible alternative remains untested, record that exception in CandidateCoverage and make it part of RefreshCondition.

Judge candidates on:

  • semantic fidelity: does the label preserve the governed value without adding or losing required conditions?
  • reader ergonomics: can the intended reader recognize, say, and remember it in the current situation?
  • morphology fit: does the word shape fit the kind being named?
  • alias risk: will a careful reader import a wrong sense from nearby FPF patterns or external practice?

Use these as ordinal comparisons. Do not average them into one score. If a Pareto-front or quality-diversity method is used, the dimensions and dominance rule must be visible on the card.

A candidate can be selected despite a remaining weakness. The SelectionRationale must say what it buys, what risk remains, and why the covered set is sufficient for this use.

F.18:4.4 - Public Term Rows

A durable local name needs no row. When public, Core-facing, durable-across-context, or cross-context reuse is current, test the then-current F.17 entry with the exact objects already recovered here. Public or durable reuse alone creates no Bridge.

The F.17 entry must be able to recover:

  • the governed value and its kind;
  • the locator for the pattern containing its defining or testing rule;
  • the NameCard episteme, selected Tech designation and any Plain designation needed for the naming use;
  • the effective by-value reference scheme, exact F.17 scheme-based SenseCell, and any separate local-sense basis relation;
  • any F.9 Bridge that obtains.

If the row use relates different <ReferenceScheme, LocalSenseClaim> projections, its rationale or notes must cite the separate affirmative C.2.1 claim for the exact action, direction, rule, and tolerance, plus that claim’s current A.10 or B.3 reliance.

The F.17 result must contain one row for one naming decision and state its supported citation use. Add a blocked-use claim only when an independently grounded overreading changes understanding or action, as F.19 explains.

If the entry cannot do this, keep the durable name and NameCard local and mark the public row pending. Do not repair or emulate the missing row inside F.18.

F.18:4.4.1 - Cross-Projection Use and Reliance

Open this branch only when one named reuse must relate different <ReferenceScheme, LocalSenseClaim> projections. Compare the exact F.17 cells. Another expression under the same projection is a designation question and gets no Bridge. Different projections open the F.9 question; a different scheme is only one way projections can differ and proves no relation.

Test the F.9 predicate and cite a Bridge only when it obtains. With no current correspondence use, create no Bridge or use claim regardless of scheme count.

State the proposed naming use in a separate current C.2.1 claim whose EntityOfConcern is that Bridge. Record the action, direction, correspondence rule, tolerated loss, and polarity.

For an affirmative named-use claim, recover the independently established direct evidence relations and their descriptive A.10 evidence-provenance account. RelianceDisposition=pass supports only this bounded use and requires the evidence demanded by the claim and its direct rule.

Use B.3 only when an actual named assurance claim is current. If a direct rule requires such a claim and it is missing, return assurance-needed and recover that claim before opening B.3; materiality alone creates neither a claim nor a positive result.

A failed or non-passing claim or reliance stops or narrows the use. Neither the A.10 nor the B.3 route authorizes the use or proves that it occurred.

If the reuse did occur, recover the claimed result under its own rule: actual Work through section 5.3, an assertion episteme under C.2.1, publication under E.24.PUB, a direct relation under its predicate, or an operation application under A.6.1. Name a BoundedModelUseStructure only when that selected structure changes the sense or naming use.

Until the Bridge, separate claim, and required reliance are current, keep the names local or record the unresolved alignment. A reference-scheme or model-use-structure difference alone supplies neither a premise nor governed-value identity.

F.18:4.5 - Model refinement, abstraction and relative levels

Use these NameCards when project or teaching texts need a shared name for a model comparison. B.5.MR defines two relation kinds and one kind of inquiry-relative level, each a local U.Kind. A pair of models can stand in one of the relations. Constructing or selecting a model is Work.

For the shared ReferenceScheme fix an inquiry and an interpretation. Each admissible completion satisfies its model’s assertions and yields an answer to that inquiry. Include the probability claims when they matter. Refinement requires at least one completion of C, with every completion of C satisfying A under the interpretation. A is then an abstraction of C. For strictness A must allow an answer C excludes. Within a chain established this way, models admitting the same answers share a level. Equal answers across branches can coexist with incompatible constraints.

NameCard and governed valueExact local sense and selected Tech designationCandidate comparison and selectionLineage and reopening
NC-MODEL-REFINEMENT; B.5.MR:4.2 refinement relation kindmodel refinement: C refines A exactly when the feasible-preservation test above holds. Strictness adds exclusion.Refinement retains the specification-theory comparison. Stronger model can suggest quality; specialization can mean type restriction; detailing can change expression alone. Concretization has a separately defined mathematical use in abstract interpretation and is not an unqualified English alias here.Retains the established English designation and states its converse. Reopen when the predicate, inquiry interpretation or supported construction changes, or repeated use confuses preservation with accuracy.
NC-MODEL-ABSTRACTION; B.5.MR:4.2 converse relation kindmodel abstraction: A is an abstraction of C exactly when C refines A under the same comparison.Abstraction names the converse without promising a unique inverse construction. Generalization can mean a wider empirical claim; weakening can suggest lower quality; lifting has source-dependent direction and may construct a fine-scale state.Makes the converse of the existing comparison explicit. Reopen when the predicate changes or readers repeatedly recover omission of visible detail without comparing assertions.
NC-MODEL-ABSTRACTION-LEVEL, B.5.MR:4.3 inquiry-relative level of model abstractionLevel of model abstraction when reading towards more abstract models. Level of model refinement when reading the same order towards more concrete models. In an established chain, a strict step changes the answers the models admit for the inquiry.These names identify what is ordered and the direction of reading. A level of detail concerns a representation, a holonic level concerns constituent–whole organization, and a metamodel can govern construction of a model. Each has its own comparison.F.17:12.6 records both expressions for one governed value. Reopen the choice if the comparison changes or readers apply it as a global rank of disciplines, publications or languages.

In ordinary speech a team can say “the local model is more concrete about where the check may take place” and name the choice it has fixed. Refining a model and abstracting a model name the work of constructing or selecting one. The comparative adjectives describe the models once a strict difference has been established.

F.17:12.6 gives the three citable rows and the exact sense cells for this comparison. Source-specific uses of concretization, idealization and lifting retain their own definitions.

F.18:5 - System-Role-Kind, Assignment, Slot, and Status Naming Settlement

This settlement keeps naming aligned with the object already recovered. Bare role is a trigger handled by E.10.ROLE, not a reusable kind head.

F.18:5.1 - System-Role-Kind Names

A durable system-role-kind name designates one exact local kind admitted through C.3 and A.2. Recover that kind through its candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule. A practice or source reference can locate the definition or signal that two definitions should be compared; it does not identify the kind. Candidates are entities already admitted under A.1 as U.System.

The Tech designation normally ends in ...SystemRole, for example ReviewerSystemRole. SystemRole is compound morphology, not a universal governed value. The name creates no system admission, kind membership, assignment, agency, capability, or Work.

A system-role-kind name preserves the distinctions in its operative membership condition. Keep a current holder, particular assignment or Work occurrence, temporary status, and current evidence or assurance claim separate from the kind name. A skill, Method-family or other qualifier belongs in the label when the admitted kind’s definition makes that distinction necessary, under §6.

If a phrase such as SeniorReviewer, NightOperator, or source wording such as evidence role appears, recover the current claim first. The result may be an exact local system-role kind, one direct assignment occurrence, a status assertion, an evidence-use relation, a Work admission condition, another governed value, or a local source phrase. Do not force all of them into one system-role-kind name.

F.18:5.2 - System-Role-Assignment Names

A system-role-assignment name designates one already recoverable obtaining occurrence of an exact direct species under U.SystemRoleAssignment and A.2.1; the system-role-kind name does not identify that occurrence. Recover the admitted holder system, the exact assigned local system-role kind, and only additional participants needed to distinguish that direct species. A taxonomy, reference scheme, description, display, or generic context episteme is not a mandatory assignment participant.

Assignment extent follows uninterrupted predicate truth; an assertion or occurrence-description episteme may state a known interval separately.

A durable assignment name uses a NameCard whose GovernedValueRef resolves to that occurrence. If public or cross-context reuse is needed, apply section 4.4; until it passes, retain the card locally and mark the row pending. Neither a name, card, row, nor publication occurrence makes the assignment obtain.

Holder#Role:Context@Window is source notation only. Recover the holder System, local system-role kind, assignment occurrence and its declared species when one exists, and any separately applicable context, schedule, interpretation, or Work relation. The source token is neither a Tech name nor proof of assignment, capability, or performed Work.

F.18:5.3 - Capability, Method, and Work Names

Keep these separate:

  • ShipbuilderSystemRole names one exact local system-role kind;
  • ShipbuildingCapability names a capability of an admitted U.System, including an acting holon admitted as a system for that capability claim;
  • ShipbuildingMethod names a method or method family;
  • HullAssemblyWork names a work family or planning-level work label until an exact performed occurrence is current.

A role-derived or role-method-coupled expression is only a naming cue. First recover the exact value it refers to. If that value is an exact Method or Method family under A.3.1, choose a Method name. If it is an exact U.MethodDescription, U.WorkPlan, or dated U.Work occurrence, name that description episteme, plan episteme, or occurrence separately under A.3.2, A.15.2, or A.15.1; those names are not Method names. If the expression refers to another value, use the rule that defines or tests that value.

After identifying the value, use F.18 if a durable name is needed. An exact relation involving a system-role kind or assignment may constrain who may use a Method or perform Work; it neither creates nor names the Method, description, plan, or Work occurrence.

Treat an action nominal such as testing as a morphology cue, not a governed kind. Placement in function- or flow-structure prose identifies no U.Function. If the function-like use remains claim-bearing while its exact object or relation is hidden, apply A.6.F; if it is already recoverable, name that value under the rule that defines or tests it. Only then use F.18 to choose a durable name.

In a plan or assignment, a WBS element, activity or Work Package can identify intended work. To identify a performed occurrence, recover its A.15.1 basis.

A durable name for performed Work points to one dated occurrence already grounded under A.15.1. An action word, plan row, local work-family label, or U.WorkPlan does not create that occurrence or an assignment.

Every System claimed as an actual performer must already have its A.13 core, including the obtaining assignment for the exact action and any scope, situation and window required by the receiving use. A.15.1 independently admits the dated Work from its Method, temporal extent, containing System and other required direct facts.

Add F.6 only when the naming account or receiving use needs precise attribution through that same assignment; the assignment must cover the Work interval, have the recovered performer as holder and retain every participant required by its declared species. Missing or failed F.6 attribution alone leaves independently admitted Work and its durable name intact; if the same finding invalidates a consumed A.13 or A.15.1 premise, recheck that premise and its dependent conclusions.

A compact naming account cites only the identities its receiving use needs. Add a continuity policy only when interruption, retry, a changed Method or binding, or competing designators make occurrence identity material.

Name any other result separately under its subject pattern, such as A.15.PROD for a production claim or C.11 for a decision.

When the underlying boundary wording still hides the relation, apply A.6.P.WMR. Use F.18 only after an exact governed value and its use are recovered through a direct subject relation, an exact A.6.1 application binding, or an exact local A.15.PROD/A.6.RCD claim.

An exact non-assertability result retains its reason under A.6.P.WMR:4.3; it does not authorize durable naming of the attempted relation. A missing subject rule may identify a future pattern or declaration need; unavailable constructor semantics retain their separate derivation question. This section selects and tests a name. It does not define a second work-occurrence or work-result recovery algorithm.

For a method-relation or method-composition name, first decide whether the phrase names a Method, relations among Methods, a selected structure, or an episteme describing one of those objects.

  • If admitted submethods make one composite way of doing, name the composite U.Method. Use A.3.1 for that Method and B.1.5 or another direct composition pattern for its exact composition relation.
  • If the phrase names relations among methods without making one whole Method, name the relations first. When a named use depends on how several such relations are organized, select that U.Structure under A.22 and designate it MethodRelationStructure; state the question and the limits that bound the selection. Identify and constrain each included method-side relation through its A.3.1, G.5, or other defining rule. A claim-bearing episteme that describes such a relation remains separate under C.2.1, and any Work-use relation remains under A.15.
  • If the current object is a separately identified episteme that describes one exact admitted Method, A.3.2 may classify it as U.MethodDescription; F.18 names that episteme separately from the Method.
  • If an episteme instead describes the selected relation structure, C.2.1 keeps that structure as its exact EntityOfConcern; the episteme is not thereby a U.MethodDescription.

F.18 settles a durable name only after one of those exact objects has been recovered. Name a mathematical lens or representation only when it is the governed value.

F.18:5.4 - System-Role-Kind Relations, Method Relations, System-Role–Method Relations, and Lens Names

System-role-kind-relation expressions remain ordinary expressions or direct relations unless their exact local kinds and relation predicates are already admitted. A mathematical description can represent a selected SystemRoleKindRelationStructure; distinguish that description from the object it represents.

First recover what the name is for:

Expression or source phraseWhat can be namedNaming rule
R1 <= R2one exact directional admission-substitution relation occurrence between two independently admitted local system-role kinds, identified by the ordered kinds, receiving-use rule, applicability, and only meaning-changing semantic-basis editionsName or cite the exact relation occurrence or a selected SystemRoleKindRelationStructure; keep any assertion or policy record, current assignment, receiving check, and outcome separate. Admit another system-role kind only when its own C.3 identity and membership basis warrant it.
R1 incompatibleWith R2one exact symmetric incompatibility relation occurrence between two independently admitted local system-role kinds, identified by the unordered pair, same- or different-holder rule, Work identity, overlap test, applicability, and only meaning-changing semantic basisName or cite the exact relation occurrence or a selected SystemRoleKindRelationStructure, not another system-role kind. Exact assignments and the receiving Work remain separate inputs and do not replace the two kind participants.
R1 and R2two independently admitted system-role kinds; any assignment occurrences are separate and are required only when the receiving sentence also claims themUse “and” in ordinary prose. Keep the two kind claims recoverable, and do not infer assignments or make a compound kind by hyphenating the labels.
R1 bundle R2, or quoted source shorthand RoleBundle := R1 and R2one order-insensitive finite-set relation among exact system-role kinds, with a joint-admission and holder-allocation predicateKeep it as a bundle relation. A convenient bundle name does not admit a compound system-role kind; such a kind would need its own independent C.3 identity and use.
R1 qualified by a domain, practice, Method family, or ordinary work fieldeither one independently admitted local system-role kind or a residual A.2.7 qualification relation between two kindsBefore naming a kind, recover its C.3 candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule. A domain, practice, ordinary work field, Method, Work family, or performed Work occurrence remains a separate value or comparison cue. Keep a non-monotonic restriction as its exact relation and do not infer admission substitution.
Method-like phrase derived from a system-role labelMethod, Method family, MethodDescription, WorkPlan, or Work occurrenceName the recovered object through A.3.1, A.3.2, or A.15; cite the exact system-role-kind relation separately when it constrains admission or performance.
representation of system-role kinds or their relationsmathematical or representation description of a selected SystemRoleKindRelationStructureName the lens only when the representation itself is the object being named; otherwise name the recovered kind, relation occurrence, selected structure, Method, assignment, or Work.
representation of Methods or their relations, such as a Method algebramathematical or representation description of exact method-side relations or their selected MethodRelationStructureName the lens only when the representation itself is the object being named; otherwise name the exact relation, selected structure, Method family, MethodDescription, WorkPlan, Work occurrence, or neighboring relation.

Ordinary speech may say “reviewer” when the local sentence makes the intended system-role kind or assignment obvious. Use the concrete ...SystemRole designation when stable technical reference to the kind is needed. Do not infer kind identity, assignment, relation, Method, capability, or Work from the ordinary word alone. Add a qualifier only when it distinguishes a live neighboring reading.

F.18:5.5 - Status, Evidence, Source, and Publication Names

Status-like and evidence-like wording must go to direct patterns:

  • status value or status assertion: F.10 or A.19.SPR;
  • evidence-use relation: A.2.4 or its other direct subject pattern; A.10 for the descriptive evidence-provenance account and bounded reliance;
  • assurance use: B.3;
  • source use: E.10.D2 or source-use patterns;
  • description-episteme identity: C.2.1;
  • multi-view publication face or form: E.17;
  • availability of one selected edition through a particular expression and carrier, with reusable form conformance and form-mediated claims when current: E.24.PUB;
  • gate or admission result: the relevant gate, decision, or assurance pattern.

Do not name these as system-role kinds or assignments unless that separate work-facing classification or direct assignment occurrence is current. “This standard plays the role of evidence” is repaired to the appropriate evidence-use, source-use, or status-use relation; it is not an assignment of the standard.

F.18:5.6 - Relation, Slot, Interface, Port, and Signature Names

Use the direct subject pattern when the named relation, slot, interface, port, boundary, protocol, API or signature is already clear. Open A.6.RSIR when that wording still hides which object or relation is being named.

  • Use A.6.5 for relation slot discipline and SlotSpec declarations.
  • Use A.6.0 for signatures and law-defined declarations.
  • A.6.M and architecture patterns define or constrain module interfaces and architecture interfaces.
  • A.6.F, transformation, and architecture patterns define or constrain functional ports and functional structures.
  • A.6.C, protocol, service-access, and commitment patterns define or constrain API, protocol, and service-access cases.
  • Use C.2.1 for the identity and content of a claim-bearing interface-description episteme.
  • Use E.17 for a multi-view publication face or form.
  • Use E.24.PUB for availability of the selected edition, exact expression and carrier-bearing relations, and reusable-form conformance when needed. A selected form-mediated availability claim retains one shared expression witness.

Before naming a relation-facing object, keep these settlements distinct:

Object to nameRequired prior settlement
reusable predicate-definition epistemeAn A.6.RCD result records a reusable definition and C.2.1 gives it one truthful exact EntityOfConcern; the name denotes the definition, not a relation kind
derived or primitive relation kindA.6.RCD, E.24, and E.24.UK have admitted the kind and its direct subject pattern states obtaining, applicability, and occurrence identity
one obtaining relation occurrencethe case facts or constituting history satisfy the subject pattern’s predicate, and A.6.REL applies the admitted kind’s occurrence-identity rule
formula, query, path, graph, diagram, or other representation elementThe domain identifies the representation element and the correspondence needed by the receiving use; use C.29 when mathematical representation choice, transfer or reliance remains unresolved. Name the represented relation separately when that is the intended subject.
designator or referencethe exact designation or reference relation resolves to the already settled object under its reference scheme

One token may be reused only where the reference scheme and local sense preserve these distinctions; it cannot collapse definition, kind, occurrence, representation, and designator into one object.

F.18 can settle a durable name for the recovered value. It does not decide which value the interface word names, create a public row, or make that row available.

Words such as member, membership, belongs to, and in do not by themselves identify one reusable relation. First use E.10 to recover whether the sentence concerns mathematical inclusion, kind classification, relation participation, collection belonging, or constructive parthood.

For a collection, an ordinary sentence such as “this edition belongs to this product series” is enough unless another use needs a reusable relation name. Name a reusable predicate only under the pattern that states who or what may belong, what makes belonging begin and end, and how recurrence and past belonging are handled. Do not create a NameCard or public name for generic MemberOf merely to abbreviate the ordinary sentence.

F.18:6 - What Belongs In The Label

Choose a head that helps the reader recognize the governed value and only the qualifiers needed to distinguish its local meaning. Use SystemRole morphology for an exact local system-role kind, and relation, slot, Method, Work or characteristic morphology only for the corresponding recovered value.

For a kind or value-family name, do not pack a current holder, temporary admission state, particular Work occurrence, evidence claim or gate result into the label as though it defined that family. A stable number, threshold or other qualifier belongs only when the subject’s definition makes it part of the distinction the name must preserve.

When naming an exact assignment or performed Work occurrence under §§5.2–5.3, an occurrence designator may include an identifier, holder cue or date when needed to distinguish that occurrence. For example, the worked-case designator HullAssemblyWork-42@2026-07-15T09:10–11:35 still resolves through the independent Work-admission and identity basis. The token does not establish that basis.

Quick check: identify the value being named, remove each optional word, and retain it only when the reader would otherwise lose a needed distinction. Put current evidence, permission, status and other neighboring claims under their own rules.

F.18:7 - Worked Cases

F.18:7.1 - System-Role Kind, Assignment, Capability, Method, and Work

A shipyard team wants one reusable name for the local system-role kind used in shipbuilding Work. It first separates the values that the source word shipbuilder could hide.

Recovered values:

  • ShipbuilderSystemRole, one local C.3 kind whose admitted-system candidates count when they satisfy the current shipbuilding condition; the member/non-member probes and continuity rule expose the boundary, while the ShipyardProduction source only locates the definition;
  • one direct assignment occurrence under A.2.1 whose admitted holder system and assigned ShipbuilderSystemRole kind are explicit, while any work area, schedule, interpretation, or reference scheme remains separate unless that direct species needs it for occurrence identity;
  • ShipbuildingCapability with envelope and measures under the capability pattern;
  • ShipbuildingMethod or a method family under A.3.1; if a separately identified ShipbuildingMethodDescription : U.MethodDescription episteme is current, name it separately under A.3.2 only when its exact EntityOfConcern is that Method;
  • HullAssemblyWork under the Work patterns.

Here HullAssemblyWork is a work-family label or a label in a plan or assignment episteme. A designator such as HullAssemblyWork-42@2026-07-15T09:10–11:35 names performed Work only when each exact actual performer has its A.13 core and A.15.1 independently admits the occurrence from the Method actually used, temporal extent, containing System, affected hull referent, material bindings, resource-use facts, and any current continuity policy.

If the naming record also expressly represents which assignment covered that Work, it cites that same obtaining A.13 assignment and adds the F.6 attribution relation; missing or failed attribution alone leaves independently admitted Work and its name intact, subject to the premise recheck in section 5.3.

A changed hull state, measurement result, evaluation verdict, delivery occurrence, or acceptance verdict remains a separately defined and separately named value.

The local card is:

NameCard:
  NameCardId: NameCard.ShipbuilderSystemRole.ShipyardProduction.2026
  GovernedValueRef: ShipbuilderSystemRole
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.2 with C.3
  ReferenceScheme: Shipyard-Production-Scheme
  ClaimContent: NameCard.ShipbuilderSystemRole.ShipyardProduction.2026.ClaimGraph
  LocalSenseRef: local expression `shipbuilder (system role)`; sense claim: the C.3 kind whose admitted-system candidates satisfy the current shipbuilding condition, member/non-member boundary, and continuity rule; ShipyardProduction provenance locates this settlement but does not identify the kind
  LocalSenseBasisRelationRef: absent; no independent local-sense basis relation is current
  TechLabel: ShipbuilderSystemRole
  PlainLabel: shipbuilder (system role)
  CandidateSet: ShipbuilderSystemRole; ShipbuilderRole; ShipbuilderSystemRoleKind; ShipbuildingCapability; HullAssemblyWorker; CertifiedShipbuilder
  CandidateCoverage: system-role-kind head; ambiguous role head; redundant kind suffix; capability head; holder-or-work head; certification-or-status head
  RejectedCandidates: ShipbuilderRole; ShipbuilderSystemRoleKind; ShipbuildingCapability; HullAssemblyWorker; CertifiedShipbuilder
  SelectionRationale: the selected label designates the already recovered local kind without claiming admission, assignment, capability, performed Work, or certification
  BridgeRefs: absent; this local settlement makes no semantic-correspondence claim
  PublicRowStatus: localOnly
  UnifiedTermRowRef: absent
  LineageEntries: `ShipbuilderRole` is retained only as predecessor wording; source word `shipbuilder` remains ordinary where no stable kind reference is needed
  RefreshCondition: reopen if the local kind identity changes or repeated readers infer a non-human-only system, admission, assignment, agency, capability, or Work from the name

The candidate comparison meets the section 4.3 stopping condition: each live head family is represented, and the recovered Method and Work objects are not synonyms for the local kind. If public or cross-context reuse becomes current, apply section 4.4; until it passes, keep this card local.

F.18:7.1a - Reviewer in a Journal Context

ReviewerSystemRole designates the local kind whose admitted-system candidates count when they supply a substantive review judgment that meets the current JournalReview acceptance conditions. The candidate range, operative condition, member/non-member probes, and continuity rule recover the kind; JournalReview-2026 provenance only locates the definition. A review assignment, responsibility, authority, capability, permission, and performed review Work remain separate claims.

NameCard:
  NameCardId: NameCard.ReviewerSystemRole.JournalReview.2026
  GovernedValueRef: ReviewerSystemRole
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.2 with C.3
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NameCard.ReviewerSystemRole.JournalReview.2026.ClaimGraph
  LocalSenseRef: local expression `reviewer (system role)`; sense claim: the C.3 kind whose admitted-system candidates satisfy the current substantive-review condition, member/non-member boundary, and continuity rule; JournalReview-2026 provenance locates this settlement but does not identify the kind
  TechLabel: ReviewerSystemRole
  PlainLabel: reviewer (system role)
  CandidateSet: ReviewerSystemRole; ReviewerRole; ReviewerSystemRoleKind; ReviewerSystemWorkRole; reviewer
  RejectedCandidates: ReviewerRole; ReviewerSystemRoleKind; ReviewerSystemWorkRole
  SelectionRationale: `SystemRole` exposes the system-classification reading; `Kind` is already stated by `U.Kind`, while `Work` would add a false occurrence claim
  BridgeRefs: absent
  PublicRowStatus: localOnly
  UnifiedTermRowRef: absent
  LineageEntries: `ReviewerRole` is predecessor wording only; ordinary `reviewer` remains available when no stable technical reference is needed
  RefreshCondition: reopen on a changed local kind or repeated non-human-only, admission, assignment, agency, capability, participation, or Work overread

No F.17 row is created without a named public or cross-local reader use.

F.18:7.2 - Engineer-Roboticist and Musician

A lab says: “Vasya is an engineer, does robot engineering, is therefore an engineer-roboticist. These are musical robots, and Vasya is also a musician, performs music, and teaches robots music.”

Recovered values:

  • Vasya as an admitted system; MusicalRobotLab_2026 is the lab and Work locus in its direct relations, not a generic assignment participant;
  • RoboticsEngineerSystemRole, one local system-role kind whose admitted-system candidates count when they satisfy the current robotics-engineering condition, boundary probes, and continuity rule; MusicalRobotLab provenance locates the definition but does not identify the kind;
  • robotics as the qualification that distinguishes this local engineering kind, with any non-monotonic restriction retained as a separate A.2.7 relation;
  • MusicianSystemRole as another exact local kind when its own music-performance condition and boundary matter separately;
  • any current engineering or musician assignments as occurrences of their declared A.2.1 species;
  • robot-engineering Method or Work, music-performance Work, and robot-music-teaching Method or Work under their direct patterns;
  • an optional representation only if the project uses it to describe the selected system-role-kind relation structure.

If the exact robotics-qualified local kind has been admitted, its local naming settlement is:

NameCard:
  NameCardId: NameCard.RoboticsEngineerSystemRole.MusicalRobotLab.2026
  GovernedValueRef: RoboticsEngineerSystemRole
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: A.2 with C.3 and A.2.7 for the separately current qualification relation
  ReferenceScheme: MusicalRobotLab-Scheme
  ClaimContent: NameCard.RoboticsEngineerSystemRole.MusicalRobotLab.2026.ClaimGraph
  LocalSenseRef: local expression `engineer-roboticist`; sense claim: the C.3 kind whose admitted-system candidates satisfy the current robotics-engineering condition, member/non-member boundary, and continuity rule; MusicalRobotLab provenance locates this settlement but does not identify the kind
  LocalSenseBasisRelationRef: absent; no separate source-bearing basis relation is current for this use
  TechLabel: RoboticsEngineerSystemRole
  PlainLabel: engineer-roboticist
  CandidateSet: RoboticsEngineerSystemRole; RoboticsEngineerRole; engineer-roboticist; robotics engineer; engineer and roboticist; RobotEngineeringMethod; engineer-roboticist-musician
  CandidateCoverage: system-role-kind head; ambiguous role head; two ordinary expressions; method neighbour; compressed multi-kind neighbour
  RejectedCandidates: RoboticsEngineerRole; engineer and roboticist; engineer-roboticist-musician; RobotEngineeringMethod
  SelectionRationale: the Tech label exposes one local system-role kind; the Plain label preserves recognizable lab speech; musician classification or assignment, Method, and Work remain separate
  BridgeRefs: absent; the card makes no semantic-correspondence claim
  PublicRowStatus: localOnly
  UnifiedTermRowRef: absent
  LineageEntries: `RoboticsEngineerRole` is predecessor wording only; ordinary `robotics engineer` remains available in local prose when no stable technical reference is needed
  RefreshCondition: reopen if the local kind or A.2.7 qualification changes, or readers merge musician classification or assignment, Method, or Work into this name

If no durable qualified kind is admitted, keep engineer-roboticist as local ordinary wording rather than filling the card. Ordinary project communication may say “Vasya is our engineer-roboticist and musician” when the separate claims about his engineering and musicianship remain recoverable; any assignment is another claim.

Name a current Method, MethodDescription, or performed Work through A.3.1, A.3.2, or A.15.1. If public reuse becomes current, apply section 4.4; do not infer an F.17 row from this local card.

F.18:7.2a - Method Relation Structure and Method Algebra Name

A lab says: “Use the robot-engineering method algebra: choose scouting, then calibration, then training; fall back to teleoperation if training fails.”

Recovered values:

  • one or more robot-engineering methods or method families under A.3.1;
  • a method-family registry or selector outcome under G.5 when the family registry or selector result is current;
  • MethodRelationStructure for the named MusicalRobotLab_2026 use when the current claim concerns serial composition, guarded fallback, or family selection among exact methods;
  • a C.2.1 description episteme whose EntityOfConcern is that selected MethodRelationStructure; it is not thereby a U.MethodDescription;
  • a C.29 mathematical-lens use when “algebra” is the selected representation for checking composition, fallback, or preserved/lost structure;
  • work plan or dated work only when a concrete plan or occurrence is current.

F.18 settlement: RobotEngineeringMethod names a Method or method family only when that is the governed value. RobotEngineeringMethodRelationStructure may name the selected method relation structure when durable naming is needed.

RobotEngineeringMethodAlgebra names the lens only when the algebraic representation itself is the governed value. Do not use a system-role-kind label such as RoboticsEngineerSystemRole to name the method relation structure, and do not use method algebra to hide a WorkPlan or performed Work.

F.18:7.3 - Evidence-Like Source Phrase

A review table contains the phrase “model card evidence role”.

Recovered values:

  • a model-card episteme;
  • an evidence-use relation to a target claim;
  • possible source-currentness and assurance-use relations;
  • no system-role kind, assignment, or acting system merely because the episteme is used as evidence.

F.18 settlement: mint no system-role-kind or assignment name. Recover the exact evidence-use relation under A.2.4 or another direct subject rule, including its participants and obtaining condition. A.10 supplies only its descriptive evidence-provenance account and bounded-reliance disposition.

If durable naming is needed, compare names for that independently recovered relation; ModelCardEvidenceUse can be a candidate, not a relation created by the phrase or card. Then apply §4.4 only when a public row is needed; otherwise retain the local settlement.

F.18:7.4 - Interface-Like Source Phrase

A software team says “the payment interface owns customer identity”.

Recovered candidates:

  • module interface under A.6.M;
  • API description or protocol under A.6.C;
  • signature or SlotSpecs under A.6.0 and A.6.5;
  • claim-bearing interface description under C.2.1;
  • multi-view publication face or form under E.17;
  • publication availability, exact expression, reusable form conformance, form-mediated expression, or carrier bearing under E.24.PUB;
  • a system-role assignment under A.2.1 only when an occurrence belongs to a declared species, has an admitted System as holder, and has the local kind as assigned-kind value; any responsibility or authority relation remains separate.

Do not mint PaymentInterfaceRole from the ambiguous phrase. If the speakers mean that the API specifies a customer identifier, name that field through its declaration. If they mean responsibility for the identity data, identify who holds that responsibility and under which rule. Ask which claim they mean if the phrase leaves it open. Apply F.18 when the recovered value needs a durable name.

F.18:7.5 - Cross-Context Name

Two teams use component, module, and unit for nearby meanings.

Recovered values:

  • structural component under architecture and part-whole patterns;
  • deployable module under module-interface patterns;
  • management unit under organizational patterns.

F.18 settlement: first keep the three recovered values and their local labels separate. If only local speech is needed, stop there; do not name a claim merely because one team wants to explain the difference.

If a public term use is proposed between different <ReferenceScheme, LocalSenseClaim> projections, identify the exact source and receiving F.17 cells and test the F.9 Bridge predicate between them. The same scheme with different LocalSenseClaim values qualifies; a different scheme only opens the question and never establishes the relation.

When the Bridge obtains, state in ordinary C.2.1 wording whether it is suitable for this naming use, naming the direction, label-correspondence rule, tolerated loss, and polarity, and establish the current A.10 or B.3 reliance required by section 4.4.1. The Bridge does not choose the Tech label, the claim does not identify the governed value, and neither authorizes or performs publication.

For this cross-projection use, apply F.17 as specified in section 4.4 only after the Bridge, the use claim and the required reliance are current. If that public-row use lacks a required input, keep the name and card local and mark the row pending. A team that wants to publish its own term without claiming correspondence can use §4.4 directly. If only local speech is needed, keep the local wording.

F.18:8 - Anti-Patterns And Repairs

Anti-patternOntological failureRepair
“Same spelling means same value.”Treats string identity or a sense Bridge as governed-value identity and lets the Bridge silently license reuse.Compare the exact <ReferenceScheme, LocalSenseClaim> projections. Same projection plus another expression stays with designation. Different projections open the F.9 question; only an obtaining Bridge can then support a separate C.2.1 naming-use claim with current A.10 or B.3 reliance. Apply the direct object subject pattern for any governed-value identity claim, or keep the values separate.
“Evidence role” for a report, source, or standard.Turns an episteme or source-use relation into a work-facing classification or assignment.Recover evidence-use, source-use, status-use, publication-use, or assurance-use relation.
“Night operator role” when only schedule differs.Bakes temporal admission into local-kind identity.Keep the exact operator system-role kind; put the time window in the assignment, status, or WorkPlan.
“Certified engineer role” when certification is evidence or admission.Bakes capability evidence or admission into the kind name.Keep EngineerSystemRole only when that exact local kind is admitted; record capability evidence, admission, or status relation separately.
“Role-derived method” treated as a role-relation result.Confuses role wording with Method identity.Name the Method or Method family under A.3.1. If a separately identified U.MethodDescription episteme is current, name it separately under A.3.2 only when its exact EntityOfConcern is that Method; cite the exact system-role-kind or assignment requirement separately when it is current.
“Method algebra” treated as the method or plan.Confuses a mathematical or representation lens with exact method-side relations, their optional A.22-selected MethodRelationStructure, a MethodDescription, WorkPlan, or performed Work.Before naming, recover the exact relation, optional selected structure, method description, C.29 lens use, work plan, or work occurrence through the rule that identifies or tests that value.
Action nominal, WBS element, or Work Package treated as performed work.Function/method morphology or intended-work content is mistaken for one dated occurrence; a nearby result is folded into the work name.Recover the exact A.15.1 occurrence basis, apply A.6.P.WMR if the relation is still hidden, and name neighboring production claims, measurement results, evaluation results, delivery occurrences, and acceptance verdicts separately.
Role-looking interface wording for API, port, or boundary.Uses role morphology to avoid recovering port, signature, boundary, or interface-specific relation.Use A.6.RSIR and the subject-pattern locator; name the recovered relation, signature, port, or bounded interface value only when its exact admission predicate is satisfied.
“Unscoped glossary.”A glossary episteme carries or lists words without an exact governed value and kind, by-value reference scheme, local sense, and any Bridge needed for the use.Use a NameCard for a durable local settlement. Open a public row only through the section 4.4 gate. When availability is current, establish the E.24.PUB claim for the selected row or glossary edition, its audience and bounded use through an expression and carrier. Include reusable-form conformance when needed.

F.18:9 - Conformance Checks

Use these checks before a durable name is reused in a pattern. If an F.17 row is current, run its own row checks after the section 4.4 gate; these F.18 checks neither create that row nor establish a publication occurrence for it.

CheckPassing condition
Governed valueThe named value is recoverable and belongs to a subject pattern.
InterpretationThe effective EpistemeInterpretationScheme value interprets the complete naming content and named local sense; model-use structure, claim scope, project work, and other locality relations remain separate.
KindThe kind is not inferred from spelling, source, or practice. A system-role kind is already recoverable through its candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule.
Candidate setThe smallest set covers the live head families and plausible neighbouring-object readings that could change the choice. The retained label, including a standard-fixed label, fits the governed value and intended use. Any forced untested exception is explicit in CandidateCoverage and RefreshCondition.
System-role boundarySystem-role kind, classification, assignment, holder, capability, Method, Work, evidence, status, participant meaning, declaration place, and representation position are not collapsed.
Relation-object boundaryPredicate-definition episteme, admitted relation kind, obtaining occurrence, representation element, and designator are named only after their separate settlements; relation slot, interface, port, and signature names cite the applicable direct patterns.
Public rowA durable local card is enough unless public, Core-facing, durable-across-context, or cross-context reuse is current. The section 4.4 gate passes before any F.17 row is cited; the row is neither the value nor the publication occurrence.
Bridge and bounded useApply the F.9 predicate only to exact local senses whose <ReferenceScheme, LocalSenseClaim> projections differ. Same projection plus another expression is designation; same scheme plus another claim can open the F.9 question; scheme difference opens only the question; no current correspondence use creates no Bridge or use claim. A separate C.2.1 claim says whether an obtaining Bridge suits the named naming use, and A.10 or B.3 supplies the reliance rule. None authorizes or proves that reuse occurred.
Local-plain non-useA one-off claim about whether an exact Bridge suits a named use stays in ordinary wording. No NameCard, public claim kind, or durable CamelCase name is created unless an independent later reuse need reopens F.18.
Lineage and reopenRename, alias, split, merge, and retirement history is recorded under F.13, and the card names the change or repeated reader error that reopens this settlement.
Reader useA practitioner can tell what to say, the relevant use limits, and where to go if the name is not enough.
Work-name boundaryAn action nominal remains a morphology cue: a hidden claim-bearing function-like use goes through A.6.F, while an already recovered value is named under its direct pattern. A WBS or Work Package label remains plan- or assignment-episteme content. A performed-Work name is accepted only for one occurrence whose exact actual performers have A.13 cores and which A.15.1 independently grounds. Add assignment and F.6 refs only when the naming record or receiving use expressly represents precise assignment-bound attribution; missing or failed attribution alone leaves independently admitted Work and its name intact, subject to the premise recheck in section 5.3. Neighbouring production claims, measurement results, evaluation results, decisions, delivery occurrences, and acceptance verdicts stay under their direct patterns.

Regression checks:

  • When either the effective reference-scheme edition or the LocalSenseClaim changes, compare the resulting semantic-context projections. Re-check any obtaining Bridge, the separate claim about the named use between different projections, and that claim’s current reliance; same-projection expression changes stay with designation, and no current correspondence use creates no Bridge or use claim.
  • When a system-role-kind description changes in a way that may alter the C.3 candidate domain, membership distinction, member/non-member boundary, continuity, or the naming settlement’s reader meaning, re-check the local kind name and any assignment name that depends on it. A provenance-only edit does not split the kind.
  • When a subject pattern changes the named value or the interpretation of borrowed morphology, re-check the affected name.
  • When repeated reader errors occur, reopen candidate comparison instead of adding aliases indefinitely.

F.18:10 - SoTA-Echoing

Question and selected answer. How should one already identified value receive a durable name without turning a convenient word into a different object or making every local phrase into a maintained record? Under E.8:11, the best-known answer for this bounded use is a local-first settlement. Stop at sufficient ordinary wording. Otherwise compare plausible head-term families against the same value and reader situation, keep the Tech designation and any Plain designation needed for a stated didactic use, and record why it was chosen and what would reopen it.

Serious alternative. A low-cost option is a compact preferred-label entry with alternatives and a scope note. SKOS Reference, lexical labels, documentation, and mapping properties supplies that comparator and the useful separation of labels, concepts, notes, and mappings. It can carry a careful explanation and does not claim that a shared label proves identity. F.18 does not reject it for lacking FPF field names or require a different storage format.

The remaining choice is about the naming decision. A preferred label and scope note can state what a term means while leaving unclear why a neighbouring head was rejected, whether ordinary wording would suffice, and which later use needs a durable settlement. F.18 makes those distinctions explicit in the naming decision.

The additional comparison and note are needed only for a reusable name. When a terminology entry already carries the same value, candidate comparison, use boundary, and reopen reason, reuse that content; neither a second naming decision nor corpus-wide normalization is warranted.

Adapt and reject by value. Section 0 and steps 1–3 of section 4 keep the value and ordinary-wording exit before the card. Sections 4.1–4.3 require semantic fidelity before reader familiarity and make candidate coverage and the remaining risk inspectable.

Cases 7.1 and 7.2 expose the concrete cost of a short head that confuses a system-role kind with an assignment, capability, Method, or Work; 4.2e compares the architectural-reference function with introductory placement, instructional, decision-history and finding-aid readings for one publication-unit form. The cases show which object distinctions the candidate comparison preserves.

Section 7.5 and the public-use branch in 4.4/4.4.1 preserve local wording and test a needed correspondence separately; a label or generic mapping is not authority for that use. Reject choosing by familiarity alone, adding a card for every phrase, or treating a source’s preferred label as the identity or admission rule for the named thing.

Judge reader ergonomics in 4.3 against the actual candidate and intended readers. Prefer a shorter label when it still fits the governing naming rule and helps the intended readers recognize the same value for the same admitted use. C.18 supplies comparison discipline only if Pareto or quality-diversity methods are used; it is not independent evidence that this name wins.

Reopen. Compare again if a lighter naming procedure preserves the same object distinctions and later reuse with less effort; if readers still infer the wrong object from the chosen head; or if the actual use needs linguistic or multilingual modeling that the simple settlement does not support. Use evidence about the naming procedure and its receiving use to make that comparison.

Currentness rule: when the pattern containing a value’s direct rule, C.2.1, F.9, A.10, B.3, or E.24.PUB changes the value, card, sense, Bridge, bounded-use claim, reliance, or publication boundary, reopen only the affected invariant, field, case, or check. A future F.17 edition is consumed only through section 4.4; its change does not reopen local NameCards unless their supported public citation use or object references change.

F.18:11 - Relations

Builds on F.0.1, F.1, F.2, F.3, F.5, F.8, F.9, F.13, F.14, F.15, C.2.1, and E.24.PUB.

Coordinates with:

  • A.2, A.2.1, A.2.5, A.2.7, A.15, A.15.1, and F.6 for system-role kinds, system-role assignments, assignment-state predicates and direct state relations, relations among system-role kinds and selected SystemRoleKindRelationStructure, system-role–Method–Work alignment, performed-Work occurrence grounding, and the separate Work-to-assignment attribution;
  • A.3.1 for method and method-family names; A.3.2 for a separately identified U.MethodDescription episteme whose exact EntityOfConcern is that Method, and for the description episteme’s separate name;
  • A.6.P, A.6.P.WMR, A.6.RCD, A.6.REL, A.6.5, A.6.RSIR, A.6.0, A.6.M, A.6.F, and A.6.C for relation-claim settlement, work/method-boundary relation recovery, relation-kind and occurrence boundaries, slot, signature, interface, port, and protocol names;
  • A.2.4 or another direct subject pattern for evidence-use relations; A.10 for their descriptive provenance and bounded reliance; B.3 for an actual named assurance claim; F.10, E.10.D2, and C.2.1 for status-use, source-use, and description-episteme names;
  • E.17 for multi-view publication-face and publication-form use;
  • F.17 only after its current entry accepts the exact F.18 value, kind, card, and sense result and, for reuse between different semantic-context projections, the separate obtaining Bridge, affirmative C.2.1 use claim, and current A.10 or B.3 reliance; otherwise the local NameCard remains sufficient and the public row stays pending;
  • E.24.PUB for the separate occurrence, form, carrier, audience, bounded-use, and currentness objects needed when an exact row-episteme edition is made available;
  • C.16, C.18, and Part G search patterns when candidate comparison uses Pareto or quality-diversity vocabulary.

Constrained non-use:

  • F.18 names independently governed values. A NameCard is a separately constituted U.Episteme under C.2.1; its constitution does not establish the value it names.
  • Do not use F.18 to decide whether two locally interpreted values are identical. A Bridge between exact F.17 cells can obtain only under the F.9 predicate; a separate C.2.1 claim states one proposed naming use between those cells, A.10 or B.3 supplies its reliance rule, and any governed-value identity claim must independently satisfy the direct value rules.
  • F.18 does not turn a publication row, card, table, or glossary entry into the thing being named.

F.18:End

Referenced in the corpus

399 literal mentions in other sections. Read their context to establish the relation.