F.17 - Make a Settled Naming Decision Recoverable for Reuse (Unified Term Sheet)
Type: Lexical row pattern (F) Status: Stable
Use this when. An independently governed value has a settled durable name and public, Core-facing, durable, or cross-local reuse needs a reader-facing term row.
First useful move. Point to the exact governed value, its kind, the pattern that defines or constrains it, one proposed row use, the selected Tech designation and any Plain designation needed for that use. Then apply F.14 at the row gate. If no durable row is needed, reuse the designation, alias, local expression or name already supplied for that value and stop.
Primary working object. One C.2.1 UnifiedTermRow episteme whose exact EntityOfConcern is the independently governed value. Its claim graph cites the separate F.18 naming-settlement episteme and selected designation expressions. Section 5.1 explains the identities and relations needed to recover this decision and distinguish the row from its publication.
What goes wrong if missed. A table entry becomes an ontology claim; a stable identifier looks like identity evidence; one source title or file stands in for a local sense; a NameCard automatically creates a cell and row; or a row is mistaken for the publication occurrence that makes it available.
What this buys. A compact, durable navigation row through which readers can recover the naming decision and the rules that define or constrain the governed value without letting the row create, merge, prove, or publish that value.
Not this pattern when. Keep private wording, local synonyms or aliases, and names already supplied where the value is defined or constrained in their local use. Use F.14 before every naming object, F.8 for one unresolved mint-or-reuse choice, F.18 for the durable naming settlement, F.9 only for an actual relation between exact cells, and E.24.PUB only when a selected row edition must be made available.
For any stronger ontology, obtaining, equivalence, authority, system-role-kind, assignment, relation-position, status, evidence, Work, or subject-use claim, use the pattern that defines or constrains it.
F.17:1 - Intent and applicability
UnifiedTermSheet is a reader-facing collection of independently identified term-row epistemes for one useful naming thread. Each row makes one selected naming decision easy to find: it names the governed value, its kind, where that value is defined or constrained, selected designations, exact local senses, any actual Bridge needed by the declared use, admitted citation use and any grounded blocked-use claim, and reopen condition.
Use it especially for:
- public system-role-kind and status names whose underlying values are already governed;
- durable relation, slot, interface, signature, or FPF kind names;
- Core-facing names used by examples, training material, project standards, dashboards, checks, tool interfaces, Part G search packs, architecture, transformation, or evaluation work;
- one exact naming use between independently recovered local senses;
- row identifiers that must remain usable across row-episteme editions.
F.17 constitutes the row episteme. Claims about the named value and its use remain governed by their defining or constraining patterns. A table can display the row, but its position, filled cells, suffix, source prestige, or row count does not establish the value’s identity or permitted use.
F.17:2 - Problem frame
Naming work often succeeds locally and then fails in reuse. A term looks stable, but the receiving reader cannot recover which value was named, which pattern defines or constrains it, which naming decision selected the expressions, which effective scheme and local-sense claim are current, or whether a cited Bridge obtains.
Five shortcuts follow:
- shared spelling is treated as shared value;
- a row combines unlike system-role-kind, assignment, status, relation, Work, evidence, or publication concerns;
- a card, cell, row, id, and publication are minted as one automatic chain;
- a source title, document, or table layout substitutes for the exact sense and basis relation;
- the row itself is said to make the term public, current, authoritative, or obtaining.
F.17 repairs those shortcuts by making every row a separately identified claim-bearing episteme whose references lead back to the exact naming settlement and governed value.
F.17:2.1 - Problem
The practical problem is to make one durable naming decision recoverable without turning its row, representation, or availability into the named object. If a row is needed, it carries one decision. Split a row that combines decisions. For any stronger claim, use the rule that defines or constrains it.
F.17:3 - Forces
| Force | F.17 settlement |
|---|---|
| Reader memory vs full provenance | Keep one compact row while retaining exact reopening references. |
| Local expression vs durable reuse | Prefer the light local disposition; use F.17 only at the public/Core/durable/cross-local threshold. |
| Local sense vs globalized wording | Identify every cell under one exact by-value scheme and sense claim; spelling establishes neither sameness nor Bridge. |
| Naming settlement vs governed value | The NameCard describes the naming decision; it neither defines nor constrains the value or its kind. |
| Didactic grouping vs ontology | Optional blocks help navigation and create no subtype, part, system-role kind, relation position, or priority. |
| Row stability vs revision and availability | Row id, row episteme, edition relation, publication occurrence, form, and carrier remain distinct. |
F.17:4 - Solution
Recover the naming objects needed for the declared reuse, then constitute a row only when its separate gate is met:
- Recover the value. Identify one exact already-governed value or relation, its kind, the pattern that defines or constrains it, its identity or obtaining semantics, and one proposed use. Split a mixed candidate before naming.
- Apply the anti-explosion gate. Use F.14 to establish what the receiving use needs before minting a card, cell, row or family. Reuse an adequate local expression, existing designation, alias or admitted row directly. A stronger object needs a contribution that those adequate treatments do not supply.
- Settle only the durable name that is needed. If one expression remains unresolved, use F.8. If a durable naming settlement is justified, F.18 constitutes one C.2.1 NameCard and selects the Tech designation and any Plain designation needed for a stated didactic use. The card creates neither the value nor its kind and does not require a cell or row.
- Address a local sense only when useful. Create one
SchemeSenseCellonly when the exact local expression and sense claim need a stable address under an effective by-valueReferenceScheme. Cite a selected bounded-model-use Structure only when its organization changes this naming use. The cell does not require a NameCard or row. - Open the public-row gate independently. Apply F.14 again when public, Core-facing, durable, or cross-local reuse needs a row. The current F.18 public-row interface supplies the exact NameCard, selected designations, governed value and kind, the locator for its defining or constraining pattern, effective scheme, and exact cell. None of those inputs alone requires the row.
- Add a Bridge only for an actual cross-local relation. Compare the exact
<ReferenceScheme, LocalSenseClaim>projections. When the proposed row use relates different projections, cite an obtaining F.9 Bridge between the exact cells and separately cite the affirmative C.2.1 use claim plus its current A.10 or B.3 reliance. Same spelling, scheme difference, or cell presence proves no Bridge. - Constitute one row episteme. Its C.2.1 EntityOfConcern is the exact independently governed value; its claim graph cites the separate naming-settlement episteme, selected designations, admitted citation use, any grounded blocked-use claim, rationale, and reopen condition. Split unlike governed values or independently different uses into separate rows.
- Keep succession and availability downstream. Use
EpistemeEditionRelationonly when a later row episteme historically continues an earlier one under C.2.1. When availability is current, use the exact E.24.PUB expression, bearing, and publication relations. A row, row id, form, carrier, upload, or rendering establishes neither succession nor publication by itself.
Apply the static and regression checks to the affected row, then stop. The result makes the naming decision recoverable for its stated citation use. Establish claims about the named value, its use or publication through their governing patterns.
F.17:5 - Minimal vocabulary
F.17:5.1 - Scheme-based local-sense coordinate, basis relation, and row episteme
A selected expression, an exact local sense, the episteme supporting that sense, the naming decision, and the reader-facing row answer different questions. Keep them independently recoverable.
SchemeSenseCell:
ValueKind: F.17-local composite coordinate; not a root U-kind
ReferenceScheme: an EpistemeInterpretationScheme value carried by value
LocalSenseId: address designator only
LocalExpression: selected expression in this local use
LocalSenseClaim: exact local meaning under the scheme
Identity: <ReferenceScheme by value, LocalExpression, LocalSenseClaim>
LocalSenseBasisRelation <: U.Relation
SlotSpecs:
LocalSenseCellSlot:
ValueKind: F.17 SchemeSenseCell coordinate
RefKind: SenseCellAddressRef resolving the exact scheme, expression, and sense claim
Field: localSenseCellRef
BasisEpistemeSlot:
ValueKind: U.Episteme
RefKind: U.EpistemeRef resolving one exact basis-episteme edition
Field: basisEpistemeRef
Direction: basisEpistemeRef -> localSenseCellRef
Obtaining: the exact basis episteme supports the cell's exact LocalSenseClaim under its by-value ReferenceScheme for the stated admitted use
NonObtaining: the basis episteme does not support this cell’s sense claim under its scheme for the stated use. Shared spelling, an accepted name, a card, a source title, a file, a carrier, publication availability or completed fields alone do not decide this.
Identity: <localSenseCellRef, basisEpistemeRef>
OccurrenceIdentity: participant-determined; another exact cell or basis-episteme edition identifies another occurrence
LocalSenseBasisRelationDescription <: U.Episteme:
entityOfConcernRef: U.EntityRef resolving one exact LocalSenseBasisRelation occurrence
entityOfConcernKindRef: U.KindRef resolving LocalSenseBasisRelation
viewpointRef?: U.ViewpointRef
subjectRef?: U.SubjectRef, only when independently governed
basisPublicationUnitRef?: U.EntityRef resolving one exact source unit as description/provenance content, never as relation participant or identity discriminator
claimGraph: a NonemptyClaimContent value carrying supported-sense and admitted-use claims, with any grounded blocked-use claim or exact source-unit qualifier
referenceScheme: an EpistemeInterpretationScheme value; exactly the scheme in localSenseCellRef
editionId: designator only
UnifiedTermRow <: U.Episteme:
UTSRowId: stable designator only
UnificationThreadId: sheet-local navigation designator
Block?: optional didactic navigation label
GovernedValueRef: U.EntityRef; the same exact referent fills the C.2.1 EntityOfConcern position
ClaimContent: a NonemptyClaimContent value containing all the identity-bearing row claims designated below
ReferenceScheme: an EpistemeInterpretationScheme value carried by value
GovernedValueKindRef: U.KindRef
SubjectPatternLocator: U.EntityRef resolving the pattern that defines or constrains the governed value
UnifiedTechName: selected Tech designation expression
UnifiedPlainName?: selected Plain designation expression for a stated didactic use
NameCardRef: U.EpistemeRef resolving the separate exact F.18 naming-settlement episteme
SenseCellRefs[]: exact SenseCellAddressRefs
BridgeRefs[]?: actual F.9 Bridge occurrences only
RowRationale
AdmissibleUse
BlockedUse?: grounded overreading whose exclusion changes understanding or action
RowEditionId: designator only
EpistemeEditionRelationRef?: exact C.2.1 occurrence only when historical continuation obtains
CurrentnessCondition
Notes?
SenseCellAddressRef designates one SchemeSenseCell; it does not create that cell or a universal context object. A legacy address is usable only through an explicit lossless adapter to the exact effective scheme, expression, and local-sense claim. Otherwise stop the row.
Resolve each reference in the source edition selected for that use. The enclosing publication can supply this selection; retain it when transferring the reference. A pattern locator such as E.17.0 supplies an exact basis only when the selected edition and cited claims recover one episteme. If they do not, leave the reference unresolved instead of substituting the currently available edition.
The basis relation has exactly two participants. basisEpistemeRef resolves the exact selected basis-episteme edition; its exact kind is derived from that referent and is not copied as another participant.
A relation reference resolves the exact LocalSenseBasisRelation occurrence rather than its description or designator.
basisPublicationUnitRef, when present, is a provenance qualifier that narrows the supporting episteme; it neither participates in nor identifies the relation. A source publication occurrence, its form, and its carrier remain separate E.24.PUB objects.
The relation says only that this basis episteme supports this cell’s exact sense claim for the admitted use. Its description states the supported uses, any grounded blocked-use claim, and any exact source-unit qualifier.
A changed NameCard reopens the selected expression. A changed scheme, expression, sense claim, or basis-episteme edition identifies another cell or basis-relation participant pair. A changed source-unit or supported-use claim creates another relation-description episteme without silently changing the basis relation.
Any description of a SchemeSenseCell is a separate C.2.1 episteme whose EntityOfConcern is that exact cell. The cell’s identifier, description, source publication, NameCard, and basis relation neither replace nor identify the cell.
UnifiedTermRow is another C.2.1 episteme, not a root U-kind, value container, or publication occurrence. Its EntityOfConcern is the exact governed value. Its displayed identity-bearing row claims jointly constitute the complete ClaimContent; a scalar graph-ref line need not be repeated in the readable fixture when that graph is recoverable from them.
The claim graph cites the separate NameCard and the governed value’s kind, locates the rules that define or constrain that value, and projects the selected designation expressions.
The row, card, designations, governed value, external row reference, and UTSRowId designator remain distinct; UnificationThreadId, Block, and RowEditionId are navigation or edition designators rather than additional identity discriminators.
To establish historical continuation between two row epistemes, test C.2.1’s EpistemeEditionRelation(earlierRowEpisteme, laterRowEpisteme). An independently established refinement or supersession claim does not by itself supply that continuity. Stable row spelling, id, table position, shared carrier, or later publication establishes no such relation. A CurrentnessCondition is row claim content; it is not the edition relation and does not make itself true.
When a selected row edition must be made available, E.24.PUB supplies PublicationExpressionRelation(selectedRowEdition, expression, boundedUseDeclaration), PublicationExpressionBearingRelation(carrier, expression) and EpistemePublicationRelation(selectedRowEdition, audienceDeclaration, boundedUseDeclaration, expression, carrier).
A selected reusable form constrains that expression through form conformance. Form-mediated availability uses the same expression as witness for expression, bearing and conformance; broader availability retains its permitted alternatives.
The row is the claim-bearing episteme, X is its particular expression and C is independently identified under its carrier-domain rule. Any asserted rendering or upload Work has its separately established performer and occurrence.
GovernedValueRef and GovernedValueKindRef are separate. A kind token has kind U.Kind. An exact local system-role kind, obtaining system-role-assignment or other relation occurrence, status value, slot kind, representation position, or local concept retains its own kind; the row points to the pattern that defines or constrains that value. A row or card cannot admit a U-kind or make a direct relation obtain.
NameCardRef resolves the F.18 C.2.1 naming-decision episteme consumed by the current public-row gate. UnifiedTechName and any UnifiedPlainName are designation expressions selected by that decision, not values or references. Aliases and rejected candidates stay in the NameCard or local lexicon rather than becoming rival selected names in the row.
BridgeRefs cites only actual F.9 occurrences between exact cells. Direction, use-specific rule, loss tolerance, polarity, evidence, reliance, permission, and receiving action remain in their own claims and relations. Local senses do not globalize; same spelling or a different scheme provides neither governed-value identity nor Bridge obtaining.
A.22.CGUS:4.4 permits a separately constituted demonstrative-slice episteme after CGUS qualification. The token DemonstrativeUnfoldingSlice@Context is neither a U.Kind nor an exact slice by itself. F.17 records a row only after one exact C.2.1 slice episteme and its current F.18 naming settlement are recoverable; a local phrase or seminar expression alone creates neither.
UnifiedTermSheet is the reader-facing collection or layout through which rows are found. A selected table layout, optional block plan, or carrier is not the row episteme and does not prove that every needed decision is present.
F.17:6 - When to create or update a UTS row
Create or revise one row only when all entry objects are exact and at least one receiving need is current:
- public or Core-facing citation of the selected naming decision;
- durable reuse outside the immediate local repair;
- cross-local reuse whose exact cells, any actual Bridge, separate use claim, and reliance are recoverable;
- stable citation from examples, checks, dashboards, training material, a project standard, or a tool interface;
- a change to the rules that define or constrain this value, or an F.18 change, that alters this row’s value, name, sense, admitted use, or blocked use.
Before the row, apply F.14 again. A noticed word, accepted designation, stable local sense, NameCard, Bridge description, source publication, or desire for a tidy table does not by itself meet the gate. A durable local NameCard can remain local; a cell can remain a cell; an existing row can be reused only within its admitted use.
F.17:7 - Row schema
Use these positions when they are current. Presence means that the exact referenced object or claim is independently recoverable; it is not a form-completion target.
| Position | Presence condition | Meaning |
|---|---|---|
UTSRowId | yes | Stable row designator; an external row reference must resolve the exact C.2.1 episteme rather than trust this string. |
Unification thread | yes | Sheet-local navigation designator with no locality or ontology force. |
Block | optional | Didactic navigation label only. |
Governed value / C.2.1 EntityOfConcern | yes | Exact independently governed value named by the decision. |
NameCardRef | yes at the current F.18 public-row gate | Separate C.2.1 naming-settlement episteme whose selected designations this row projects. |
Governed value kind | yes | Exact kind of that value; U.Kind when the value is a kind token. |
Defining or constraining pattern | yes | Pattern whose rules define or constrain the value, its kind, its identity, or any obtaining semantics used by the row. |
Reference scheme | yes | Effective by-value naming ReferenceScheme used in this row’s C.2.1 constitution. |
Unified Tech name | yes | Selected Tech designation expression. |
Unified Plain name | when needed for a stated didactic use | Selected Plain designation expression for the same governed value and local meaning. |
SenseCellRefs | one or more | Exact scheme-based local-sense coordinates needed by this row. |
BridgeRefs | only for an actual cross-local relation used by the row | Exact obtaining F.9 occurrences; the separate use claim and reliance stay in rationale or notes. |
Row rationale | yes | Why these projections form one row decision. |
Admissible use | yes | Exact citation use supported by the row; it grants no authorization or occurrence. |
Not this use | when a grounded overreading changes understanding or action | A locally plausible use that the row does not support, with the distinction needed to avoid that error. |
Row edition id | yes | Designator for this exact row episteme edition. |
EpistemeEditionRelationRef | only when C.2.1 historical continuation obtains | Separate relation from an exact earlier row episteme to this later one. |
Currentness condition | yes | Claim stating what reopens review; not a self-proving currentness relation. |
Notes | optional | Short lineage, teaching, homonym, use-claim, or reliance note. |
For SenseCellRefs, recover the exact by-value scheme, expression, and local-sense claim. Cite LocalSenseBasisRelation only when the basis relation obtains. A NameCard selects designations; it does not fill the cell or basis positions. A source title, file, carrier, locality label, selected structure, row id, or description substitutes for none of them.
Publication availability is not a row column. When current, maintain the exact E.24.PUB relation occurrences, particular expression, carrier, audience and bounded use beside the selected row edition.
When a reusable publication form is selected, identify it and establish the expression’s conformance. Form-mediated availability uses that same expression as witness. Publication change does not silently change the row episteme or its C.2.1 edition relation.
F.17:8 - Optional block plan
A block plan is an optional navigation aid for a sheet with enough rows that grouping helps a reader. Use few memorable blocks and omit the plan when direct row search is clearer. Neither a declared plan, the number of blocks, nor filled row count proves coverage, completeness, usefulness, or semantic adequacy.
Example navigation plan for a system-role, Method, Work, and status thread:
- governed values and naming decisions;
- system-role kinds and their descriptions;
- system-role assignments and performed Work;
- methods, method descriptions, and work plans;
- status families and status windows;
- relation, slot, interface, and Bridge terms;
- evidence, assurance, source, and publication terms when those are the governed values.
This list defines no ontology. A sheet may use another small navigation plan for architecture, transformation flows, evaluation characteristics, Part G search packs, or another receiving use.
F.17:9 - Layouts
F.17 admits two common layouts.
Layout A, scheme-first: keep the left rail fixed and add one exact reference-scheme column per selected interpretation basis. Use this when the reader’s comparison concerns local senses under named schemes.
UTSRowId | Unification thread | Block | Governed value | Governed value kind | Defining or constraining pattern
Unified Tech name | Unified Plain name | NameCardRef
Reference scheme A | Reference scheme B | Reference scheme C
BridgeRefs | Row rationale | Admissible use | Not this use
Row edition | Currentness condition | Notes
Layout B, comparison-column: keep the scheme, local expression, and sense claim inside SenseCellRefs and use presentation columns such as tradition, discipline, language, publication family, or project family. For each compared entry, the reader must still be able to resolve its exact by-value scheme and local-sense claim. The column label helps organize the comparison; that recovered scheme and claim determine its interpretation.
Never mix a scheme column and a discipline or project-family column as if they had the same kind. A ReferenceScheme is an interpretation basis carried by value; a comparison column is a didactic view.
F.17:10 - Static conformance rules for a UTS
Use these checks before citing a row outside its immediate sheet.
| Rule | Check |
|---|---|
| UTS-SCR-01 | The row resolves to one C.2.1 row episteme whose EntityOfConcern is one exact governed value; it points separately to that value’s kind, the pattern that defines or constrains it, and the exact F.18 naming-settlement episteme. |
| UTS-SCR-02 | One row carries one naming decision and one governed value/use branch; mixed values or independently different uses are split. |
| UTS-SCR-03 | Every local sense resolves to one exact by-value ReferenceScheme, local expression, and local-sense claim; id, description, source publication, card, or basis relation replaces none of them. |
| UTS-SCR-04 | Each current card, cell and row meets a receiving need under F.14. Adequate ordinary wording or existing naming is reused where it supplies that result. |
| UTS-SCR-05 | The Tech designation and any Plain designation agree with the exact current F.18 NameCard without becoming the governed value; aliases and rejected candidates remain separate. |
| UTS-SCR-06 | Any cited LocalSenseBasisRelation has only its exact cell and basis episteme as participants; source-unit and publication facts remain qualifiers or neighboring objects. |
| UTS-SCR-07 | With the same scheme and sense claim, another expression raises a designation question. Different sense claims within one scheme, or different schemes, warrant an F.9 test when the row needs a semantic correspondence. If the proposed use relies on a Bridge, check that it obtains and assess the separate use claim and reliance. Without that correspondence question, no Bridge or use claim need be added. |
| UTS-SCR-08 | Any cited F.9 Bridge has exact endpoint cells and editions, an applicable relation-semantic profile, a true kind-defined predicate, and every required dependency. The separate affirmative C.2.1 use claim states direction, correspondence rule, and loss tolerance, with current A.10 or B.3 reliance. A negative use claim rejects that exact row use; non-passing reliance stops or narrows it; neither negates or reidentifies an otherwise obtaining Bridge. |
| UTS-SCR-09 | A system-role-kind row does not identify SystemRoleKindDescription, SystemRoleAssignment, capability, Method, or Work with the governed kind; a status row does not turn a status family, value, or window into a system-role kind. |
| UTS-SCR-10 | Evidence, assurance, source, publication, description, relation, slot, interface, authority, and equivalence claims use the patterns that define, constrain, or test them rather than becoming row truth. |
| UTS-SCR-11 | Row id, block, table position, source title, file, carrier, suffix, and filled-cell count create neither value identity nor row adequacy. |
| UTS-SCR-12 | The row states the exact scheme, receiving use, and reader breadth actually checked; a narrow row claims neither universal nor corpus-wide reuse. |
| UTS-SCR-13 | C.2.1 row succession and E.24.PUB availability are independently recovered; row, edition relation, publication occurrence, form, carrier, rendering Work, and upload Work stay distinct. |
A row succeeds when intended readers can recover the correct naming decision, governed value, and applicable defining or constraining rule for the declared use, and distinguish any grounded excluded use. Schema conformance and maintenance aids such as row counts, label uniformity and stable identifiers do not establish that recovery.
F.17:11 - Regression and stability rules
Recheck only the rows affected by the changed object, name, scheme, sense, Bridge, basis, or source.
| Rule | Trigger | Response when triggered |
|---|---|---|
| UTS-RSCR-01 | Reference-scheme value, local expression, or local-sense claim changes | Preserve the old coordinate when it is still cited and create or cite the new exact coordinate; do not silently reuse the old address. |
| UTS-RSCR-02 | The defining or constraining rule changes the underlying value kind or admissible use | Recheck the governed value, its kind, the applicable pattern, admitted use, and blocked use. |
| UTS-RSCR-03 | F.18 changes the selected name or NameCard decision | Recheck Tech name, Plain name, NameCardRef, aliases, coordinate expression, and rationale. |
| UTS-RSCR-04 | F.9 changes a Bridge endpoint or relation-semantic profile, or C.2.1/A.10/B.3 changes the bounded-use claim or reliance basis | Apply F.9:16 to changed endpoints or a changed profile, then reconsider every row use that depends on that Bridge. A changed direction, rule, tolerance or polarity changes the use claim; changed evidence or reliance reopens its support. Update affected references, rationale and notes; retain the Bridge and row uses whose grounds remain valid. |
| UTS-RSCR-05 | Row relocation between blocks | Keep the row id and meaning stable; clarify the new grouping if it could change the reader’s interpretation. |
| UTS-RSCR-06 | A system-role, status, evidence, source, publication, or description row is reused under another semantic-context projection or by another reader group | Recheck the pattern that defines or constrains the governed value, the exact sense coordinate, and any required Bridge before reuse. |
F.17:12 - Archetypal Grounding - worked cases
F.17:12.1 - System-role-kind name becomes public across two project contexts
One project has an exact local DesignReviewerSystemRole kind and another has an independently governed ExternalAuditReviewerSystemRole kind. Both local expressions say reviewer, but one classifies an admitted System that may perform design-review Work and the other classifies an admitted assurance System that may produce an audit report. Any actual assignment and Work are separately identified.
Create two rows, one for each independently governed local reviewer kind. If a named use needs correspondence between their two exact sense cells, cite an obtaining F.9 Bridge and an affirmative C.2.1 claim that names direction, label rule and tolerated loss. Each row cites the pattern that defines or constrains its local system-role kind, its SystemRoleKindDescription when current, and the F.18 NameCardRef. Use A.10 for ordinary reliance on the use claim and B.3 when a named assurance claim is current; the row and card establish neither assignment nor review Work.
F.17:12.2 - Status label looks like a system-role-kind name
A team proposes BlockedReviewer as a public label. F.17 does not accept it as a row until the two governed values are separated. ReviewerSystemRole is a local system-role kind; blocked is a status-family or status-window value. The sheet may record one system-role-kind row and one status row, with a note that a local UI may render their labels together. The table creates neither a BlockedReviewerSystemRole kind nor an assignment. If either exact row edition must later be made available, use a separate E.24.PUB publication package.
F.17:12.2a - Learning is an anti-row and split prompt
A DPF or dashboard proposes one public Learning row, perhaps with LearningProgress as its value. Apply E.10.LRN first. Teaching or practice Work, a holder’s capability, a fitted model edition, an inference result, acquired information, a representation relation, cultural change, and a course or other product are independently governed values and claims. Performance, capability evidence, information gain, model fit, prediction error, compression, and representation change are likewise different progress coordinates; shared spelling does not make them one governed value, one SchemeSenseCell, or an F.9 Bridge.
F.17 therefore creates no umbrella Learning or LearningProgress row. If one recovered value later needs a durable public designation, apply F.14 and F.18 to that exact value and create at most one row for its admitted use; another recovered value receives another row only under its own gate. When the direct claim is already readable or durable reuse is absent, stop with no UTS row.
F.17:12.3 - Relation and slot names become reusable
An architecture pattern needs public names for interfaceSlot, providedPort, and requiredPort. The UTS row cites A.6.5 for slot discipline, A.6.RSIR when the relation-signature-interface boundary is current, and F.18 for durable names. The row does not treat a slot name as a component, system-role kind, assignment, or capability. If a project context uses port differently, keep the two local senses explicit. Cite an F.9 Bridge only when its direct predicate between the exact F.17 cells obtains; keep the proposed naming use and any reliance separate.
F.17:12.4 - Misleading evidence-role row
A sheet has a row labelled Evidence role. Recover the governed object before choosing a name. For an episteme’s evidence use, establish the direct relation under A.2.4 or its other subject rule; A.10 describes the evidence-provenance path and classifies the bounded reliance, and B.3 enters only for an actual named assurance claim.
For dated evidence-producing Work, recover each precise performer’s A.13 core, including the same obtaining assignment, and independently admit the Work under A.15.1. Add F.6 only when the row or receiving use needs precise assignment-bound attribution. A separately needed local-kind claim uses A.2 with C.3.
The UTS may expose selected names for these distinct values; it does not admit a generic evidence-role row that fuses them.
F.17:12.4a - Manufacturing batch across material and planning contexts
A furnace team uses batch for one physically handled set of shafts that shares a heat-treatment run and traceability basis. A planning dashboard uses batch for a grouping of intended PlanItems. Spelling does not make these one governed value. Recover the physical batch under the material or production DPF pattern that supplies its identity and part-whole rules when the proposed comparison relies on either; recover the planning grouping and its relation to intended PlanItems under A.15.2.
When the row gate is met, record separate rows for the distinct governed values. A needed semantic comparison may cite an obtaining F.9 Bridge and a separate affirmative C.2.1 claim stating direction, correspondence rule and tolerated loss with current reliance; those facts do not combine the values into one row.
If either selected row edition must be made available, apply E.24.PUB separately. A batch row cannot turn a PlanItem grouping into a physical holon or make the physical batch a WorkPlan.
F.17:12.4b - Clinical discharge wording
A clinical publication proposes one row for discharge and discharge-ready. First separate the governed values. A patient-state classification uses A.19.SPR plus the clinical DPF pattern for its bearer, state frame, evidence, qualification window, and use. An accountable discharge decision remains a decision relation under the pattern that defines or tests that decision. A completed discharge is dated Work under A.15.1.
If the naming use needs a row for a patient state, discharge decision or completed discharge, record that value separately. Connect rows only through relations established for the clinical use. A later publication operation uses E.24.PUB for each row edition that must be made available. One familiar label does not make state, decision, and Work interchangeable.
F.17:12.4c - Demonstrative walkthrough and bounded mantra
A.22.CGUS:4.4 permits a separate C.2.1 episteme that shows one traversal through an already qualified CGUS for a declared teaching or comparison use. It does not define a demonstrative-slice U.Kind, and the token DemonstrativeUnfoldingSlice@Context does not identify one exact slice. A proposed seminar reference-scheme name must also resolve to an effective by-value scheme. These labels alone therefore supply no basis for a demonstrative-slice row, seminar SenseCell, Bridge or bounded-use claim.
Use demonstrative walkthrough as ordinary readable wording for a shown traversal when the sentence makes the exact slice clear. Keep mantra as bounded seminar or pattern-local recall wording when repetition and attention are the point. Neither expression creates a kind, episteme, scheme, cell, Bridge, row, or publication occurrence. mantra move remains E.10.MOVE Plain wording for an E.11.PUA practice-continuation description when such a description is shown; ordinary long and local mantras receive no F.17 row.
If a later use needs a durable public name, first recover one exact slice episteme under C.2.1 from its claim content, the qualified CGUS it concerns, and its effective scheme. F.18 may then record one naming settlement and F.17 may record one row after the ordinary gate. A second cell and F.9 Bridge are justified only when another exact scheme-and-sense projection and a named current correspondence use both exist. Availability of any selected row edition still requires a separate exact E.24.PUB publication package.
F.17:12.4d - Bounded model-use structure public row
This row records the selected A.1.1/F.18 names for the dependent U.Structure specialization. A.1.1 separately governs the identity and membership of structure individuals and the obtaining of their relations; E.24.PUB governs availability of the row edition.
UTSRowId: UTS.BoundedModelUseStructure.FPFCore.2026-07-25
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: R1.2-BoundedModelUse-Naming
Block: Architecture and model use
GovernedValueRef: BoundedModelUseStructure
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.1.1
UnifiedTechName: BoundedModelUseStructure
UnifiedPlainName: bounded context
NameCardRef: NC-BOUNDED-MODEL-USE-STRUCTURE
SenseCellRefs: SenseCell.BoundedModelUseStructure.FPFCore.2026-07-25
BridgeRefs: none; this row makes no semantic-correspondence or substitution claim
RowRationale: the governed value is the A.1.1 kind token; its admitted members are exactly the U.Structure individuals that satisfy the A.1.1/A.22 membership condition, and the selected names designate that organization of one model edition's governed applicability, actual use, and fixed-content expression coherence over exact admitted model-use holons, exact applied constraint claims, and the named frame; a claim scope or membership outcome is not an applied constraint by itself
AdmissibleUse: Core-facing designation of the A.1.1 dependent structure specialization and retrieval of the DDD plain term
BlockedUse: no generic context holon, no identity for a subsystem, team, claim scope, model episteme, description, or view, no relation occurrence, and no positive crossing-structure membership
RowEditionId: 2026-07-25
CurrentnessCondition: reopen when the A.1.1/A.22 membership or continuity rule, one of the three direct relation kinds, FPFCoreReferenceScheme, the NameCard, an exact applied constraint proposition or its use in selection, or the named bounded-model-use frame changes
SenseCell.BoundedModelUseStructure.FPFCore.2026-07-25:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: BoundedModelUseStructure-core
LocalExpression: BoundedModelUseStructure
LocalSenseClaim: the dependent U.Structure specialization selected over one exact model episteme, exact admitted model-use holons, obtaining applicability, actual-use, and fixed-content expression-coherence relations, exact applied constraint claims used by the selection judgment, and the named bounded-model-use frame; a claim scope participates only in its applicability relation unless a distinct constraint proposition refers to that scope or its membership predicate, and crossings belong only to a distinct A.22 structure over already identified bounded model-use structures
senseFamily: BoundedModelUse
NameCardRef: NC-BOUNDED-MODEL-USE-STRUCTURE
LocalSenseBasisRelationRefs: LocalSenseBasisRelation.BoundedModelUseStructure.FPFCore.2026-07-25
LocalSenseBasisRelation.BoundedModelUseStructure.FPFCore.2026-07-25:
localSenseCellRef: SenseCell(FPFCoreReferenceScheme, BoundedModelUseStructure-core)
basisEpistemeRef: A.1.1
LocalSenseBasisRelationDescription.BoundedModelUseStructure.FPFCore.2026-07-25:
entityOfConcernRef: LocalSenseBasisRelation.BoundedModelUseStructure.FPFCore.2026-07-25
entityOfConcernKindRef: LocalSenseBasisRelation
viewpointRef: FPFCoreReaderViewpoint
claimGraph:
supportedSenseClaim: BoundedModelUseStructure names the exact A.1.1/A.22 dependent structure specialization, with bounded context retained only as its Plain retrieval name
admittedUseClaim: Core-facing designation and citation of that governed specialization
nonAdmittedUseClaim: the name or row creates no structure, holon, context bearer, direct relation occurrence, crossing occurrence, view, representation, or publication event
referenceScheme: FPFCoreReferenceScheme
editionId: 2026-07-25
This row records BoundedModelUseStructure for public reuse; availability of its selected edition requires the separate E.24.PUB publication relations. A.22 retains CrossContextRelationStructure as a provisional local designator and governs when a positive structure member may be claimed. Any later naming settlement or public row must be established for its exact governed value under F.18 and the row gate.
F.17:12.4e - Three bounded-model-use direct relation-kind rows
These rows record the three A.1.1 relation-kind names used by E.24.UK. Each row makes one naming decision recoverable. A.1.1 separately defines the obtaining and reidentification tests for relation occurrences, and E.24.PUB governs availability of a selected row edition.
UTSRowId: UTS.ModelApplicabilityRelation.FPFCore.2026-07-25
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: R1.2-BoundedModelUse-Naming
Block: Architecture and model use
GovernedValueRef: ModelApplicabilityRelation
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.1.1
UnifiedTechName: ModelApplicabilityRelation
UnifiedPlainName: this model applies to this holon within this claim scope
NameCardRef: NC-MODEL-APPLICABILITY-RELATION
SenseCellRefs: SenseCell.ModelApplicabilityRelation.FPFCore.2026-07-25
BridgeRefs: none; this row makes no semantic-correspondence or substitution claim
RowRationale: the governed value is the A.1.1 relation-kind token; its admitted instances are exactly the obtaining U.Relation occurrences that satisfy the A.1.1 applicability predicate and identity rule, and the selected names expose that relation while keeping A.2.6 scope membership, the derived interval, assertions, and the selected structure separate
AdmissibleUse: Core-facing designation of the A.1.1 relation kind, including A.2.6 claim-scope coordination and the E.24.UK bounded-model-use membership test
BlockedUse: no applicability occurrence from a name, model mention, shared label, scope row, assertion, interval, publication, or structure membership
RowEditionId: 2026-07-25
CurrentnessCondition: reopen when A.1.1 changes the participant kinds, predicate, scope alignment, model-scheme interpretation, temporal identity, NameCard, or named Core use
SenseCell.ModelApplicabilityRelation.FPFCore.2026-07-25:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: ModelApplicabilityRelation-core
LocalExpression: ModelApplicabilityRelation
LocalSenseClaim: the direct relation kind over one model episteme, one exact holon, and one participating claim scope; one exact relation occurrence obtains only when the A.1.1 applicability predicate is true and all other governing conditions hold
senseFamily: ModelApplicability
NameCardRef: NC-MODEL-APPLICABILITY-RELATION
LocalSenseBasisRelationRefs: LocalSenseBasisRelation.ModelApplicabilityRelation.FPFCore.2026-07-25
LocalSenseBasisRelation.ModelApplicabilityRelation.FPFCore.2026-07-25:
localSenseCellRef: SenseCell(FPFCoreReferenceScheme, ModelApplicabilityRelation-core)
basisEpistemeRef: A.1.1
LocalSenseBasisRelationDescription.ModelApplicabilityRelation.FPFCore.2026-07-25:
entityOfConcernRef: LocalSenseBasisRelation.ModelApplicabilityRelation.FPFCore.2026-07-25
entityOfConcernKindRef: LocalSenseBasisRelation
basisPublicationUnitRef: A.1.1:4.2 ModelApplicabilityRelation
viewpointRef: FPFCoreReaderViewpoint
claimGraph:
supportedSenseClaim: ModelApplicabilityRelation names the exact A.1.1 relation kind rather than a scope-membership predicate, claim, record, or interval
admittedUseClaim: Core-facing designation and citation of that governed relation kind
nonAdmittedUseClaim: the name or row makes no applicability occurrence obtain and grants no selected-structure membership
referenceScheme: FPFCoreReferenceScheme
editionId: 2026-07-25
UTSRowId: UTS.ModelUseRelation.FPFCore.2026-07-25
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: R1.2-BoundedModelUse-Naming
Block: Architecture and model use
GovernedValueRef: ModelUseRelation
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.1.1
UnifiedTechName: ModelUseRelation
UnifiedPlainName: this assignment's holder uses this model during this work concerning this holon
NameCardRef: NC-MODEL-USE-RELATION
SenseCellRefs: SenseCell.ModelUseRelation.FPFCore.2026-07-25
BridgeRefs: none; this row makes no semantic-correspondence or substitution claim
RowRationale: the governed value is the A.1.1 relation-kind token; its admitted instances are exactly the obtaining U.Relation occurrences that satisfy the A.1.1 actual-use predicate and identity rule, and the selected names expose that relation while keeping applicability, system-role assignment, performed Work, Method application, claims, and records separate
AdmissibleUse: Core-facing designation of the A.1.1 relation kind and its use in the E.24.UK bounded-model-use membership test
BlockedUse: no use occurrence from availability, access, mention, assignment alone, Work alone, method application, assertion, publication, or structure membership
RowEditionId: 2026-07-25
CurrentnessCondition: reopen when A.1.1 changes the participant kinds, the F.6 attribution condition for a row that expressly consumes it, actual-use predicate, actor derivation, maximal-continuous-use identity, NameCard, or named Core use
SenseCell.ModelUseRelation.FPFCore.2026-07-25:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: ModelUseRelation-core
LocalExpression: ModelUseRelation
LocalSenseClaim: the direct relation kind over one exact system-role-assignment occurrence, model episteme, performed Work occurrence, and use-locus holon; one exact relation occurrence obtains only when the A.1.1 actual-use predicate is true and all other governing conditions hold
senseFamily: ModelUse
NameCardRef: NC-MODEL-USE-RELATION
LocalSenseBasisRelationRefs: LocalSenseBasisRelation.ModelUseRelation.FPFCore.2026-07-25
LocalSenseBasisRelation.ModelUseRelation.FPFCore.2026-07-25:
localSenseCellRef: SenseCell(FPFCoreReferenceScheme, ModelUseRelation-core)
basisEpistemeRef: A.1.1
LocalSenseBasisRelationDescription.ModelUseRelation.FPFCore.2026-07-25:
entityOfConcernRef: LocalSenseBasisRelation.ModelUseRelation.FPFCore.2026-07-25
entityOfConcernKindRef: LocalSenseBasisRelation
basisPublicationUnitRef: A.1.1:4.2 ModelUseRelation
viewpointRef: FPFCoreReaderViewpoint
claimGraph:
supportedSenseClaim: ModelUseRelation names the exact A.1.1 actual-use relation kind rather than applicability, availability, Work, assignment, method application, claim, or record
admittedUseClaim: Core-facing designation and citation of that governed relation kind
nonAdmittedUseClaim: the name or row makes no model-use occurrence obtain and grants no selected-structure membership
referenceScheme: FPFCoreReferenceScheme
editionId: 2026-07-25
UTSRowId: UTS.ModelExpressionCoherenceRelation.FPFCore.2026-07-25
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: R1.2-BoundedModelUse-Naming
Block: Architecture and model use
GovernedValueRef: ModelExpressionCoherenceRelation
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.1.1
UnifiedTechName: ModelExpressionCoherenceRelation
UnifiedPlainName: this model content and this expression content satisfy this declared coherence criterion under this comparison scheme
NameCardRef: NC-MODEL-EXPRESSION-COHERENCE-RELATION
SenseCellRefs: SenseCell.ModelExpressionCoherenceRelation.FPFCore.2026-07-25
BridgeRefs: none; this designation makes no semantic-correspondence claim, and any Bridge needed for a particular coherence occurrence is a separately obtaining prerequisite named by that occurrence's predicate declaration
RowRationale: the governed value is the A.1.1 relation-kind token; its admitted instances are exactly the obtaining U.Relation occurrences that satisfy the A.1.1 coherence predicate and participant-determined identity rule, and the selected names expose fixed-content semantic coherence while keeping the local predicate value, maintenance, transformation, evaluation, result, evidence, and assertion separate
AdmissibleUse: Core-facing designation of the A.1.1 relation kind and its use in the E.24.UK bounded-model-use membership test
BlockedUse: no coherence occurrence from a label, predicate label, equal spelling, maintenance or evaluation Work, changed carrier, result episteme, evidence, assertion, publication, or structure membership
RowEditionId: 2026-07-25
CurrentnessCondition: reopen when A.1.1 changes the participant kinds, five-part predicate-value rule, interpretation branch, permitted loss, participant-determined identity, NameCard, or named Core use
SenseCell.ModelExpressionCoherenceRelation.FPFCore.2026-07-25:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: ModelExpressionCoherenceRelation-core
LocalExpression: ModelExpressionCoherenceRelation
LocalSenseClaim: the participant-determined direct relation kind over one model episteme, expression episteme, admitted five-part predicate value, and comparison scheme when an admissible interpretation branch exists and that predicate is true
senseFamily: ModelExpressionCoherence
NameCardRef: NC-MODEL-EXPRESSION-COHERENCE-RELATION
LocalSenseBasisRelationRefs: LocalSenseBasisRelation.ModelExpressionCoherenceRelation.FPFCore.2026-07-25
LocalSenseBasisRelation.ModelExpressionCoherenceRelation.FPFCore.2026-07-25:
localSenseCellRef: SenseCell(FPFCoreReferenceScheme, ModelExpressionCoherenceRelation-core)
basisEpistemeRef: A.1.1
LocalSenseBasisRelationDescription.ModelExpressionCoherenceRelation.FPFCore.2026-07-25:
entityOfConcernRef: LocalSenseBasisRelation.ModelExpressionCoherenceRelation.FPFCore.2026-07-25
entityOfConcernKindRef: LocalSenseBasisRelation
basisPublicationUnitRef: A.1.1:4.2 ModelExpressionCoherenceRelation
viewpointRef: FPFCoreReaderViewpoint
claimGraph:
supportedSenseClaim: ModelExpressionCoherenceRelation names the exact A.1.1 relation kind rather than its predicate value, maintenance, transformation, evaluation, result, evidence, or assertion
admittedUseClaim: Core-facing designation and citation of that governed relation kind
nonAdmittedUseClaim: the name or row makes no coherence occurrence obtain, makes no predicate-value name available, and grants no selected-structure membership
referenceScheme: FPFCoreReferenceScheme
editionId: 2026-07-25
Do not create a public F.17 row for ModelExpressionCoherencePredicate: that label remains local to A.1.1 and names the five-part criterion ValueKind rather than any of the three relation kinds.
F.17:12.4f - Viewpoint, view, and conformance-relation public rows
Use three separate rows for the different receiver needs below. E.24.UK admits U.Viewpoint and U.View as same-individual dependent kinds under U.Episteme; E.17.0 defines their positive membership predicates and EpistemeViewpointConformanceRelation.
Stable Core citation and typed-reference use justify the rows. Retain the existing Tech designations under F.14 rather than creating a synonym family; establish membership, relation obtaining and publication through their separate governing rules.
The two existing dependent-kind designations use the following F.18 naming-settlement epistemes. They remain distinct from the E.24.UK admission results, the governed kinds, their members, every reference or designator, and the F.17 rows that cite them.
NameCard:
NameCardId: NameCard.U.Viewpoint.FPFPublic.2026-10-30
GovernedValueRef: U.Viewpoint
GovernedValueKindRef: U.Kind
SubjectPatternLocator: E.17.0
ReferenceScheme: FPFCoreReferenceScheme
ClaimContent: NameCard.U.Viewpoint.FPFPublic.2026-10-30.ClaimGraph — complete naming-settlement graph constituted by the claims designated below
LocalSenseCellRef: SenseCell.U.Viewpoint.FPFCore.2026-10-30
LocalSenseBasisRelationRef: LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-10-30
TechLabel: U.Viewpoint
PlainLabel: viewpoint
CandidateSet: U.Viewpoint; ViewpointEpisteme; ViewpointConvention; ViewpointRecord; ViewpointStructure
CandidateCoverage: dependent-kind, episteme, convention, record, and structure readings tested
RejectedCandidates: ViewpointEpisteme hides the stable public kind name; ViewpointConvention can denote fixed claim content rather than P; ViewpointRecord adds a wrapper; ViewpointStructure names S rather than P; none is an alias
SelectionRationale: retain the admitted Core Tech name and ordinary Plain retrieval word while the exact local-sense claim keeps P, S, references, and designators distinct
DeclaredUse: Core-facing designation of the E.17.0 same-individual dependent kind and typed reference resolution to exact P
NonAdmissibleUse: no P, S, kind membership, selection, Work, conformance, view membership, or publication follows from the card or labels
BridgeRefs: none; this settlement makes no cross-local correspondence claim
PublicRowStatus: current
UnifiedTermRowRef: UTS.U.Viewpoint.FPFCore.2026-08-02
LineageEntries: ViewpointId remains only a designator of exact P; viewpointRef remains U.ViewpointRef and resolution grants no membership
RefreshCondition: reopen when E.17.0 changes P's same-individual membership predicate, E.24.UK admission, exact reference typing, FPFCoreReferenceScheme, reader meaning, or public use
NameCard:
NameCardId: NameCard.U.View.FPFPublic.2026-08-02
GovernedValueRef: U.View
GovernedValueKindRef: U.Kind
SubjectPatternLocator: E.17.0
ReferenceScheme: FPFCoreReferenceScheme
ClaimContent: NameCard.U.View.FPFPublic.2026-08-02.ClaimGraph — complete naming-settlement graph constituted by the claims designated below
LocalSenseCellRef: SenseCell.U.View.FPFCore.2026-08-02
LocalSenseBasisRelationRef: LocalSenseBasisRelation.U.View.FPFCore.2026-08-02
TechLabel: U.View
PlainLabel: episteme conforming to an exact viewpoint
CandidateSet: U.View; ViewEpisteme; ConformingEpisteme; ViewArtifact; PublishedView
CandidateCoverage: dependent-kind, episteme, conformance, artifact, and publication readings tested
RejectedCandidates: ViewEpisteme can look like a second individual; ConformingEpisteme drops the exact viewpoint relation; ViewArtifact collapses episteme with form or carrier; PublishedView makes availability look constitutive; none is an alias
SelectionRationale: retain the admitted Core Tech name while the Plain label exposes that the same E gains membership only through exact E/P conformance
DeclaredUse: Core-facing designation of the E.17.0 same-individual dependent kind and typed reference to an already conforming episteme
NonAdmissibleUse: no membership from direct authoring, construction, query execution, transformation, selection, rendering, bundle, form, carrier, or publication
BridgeRefs: none; this settlement makes no cross-local correspondence claim
PublicRowStatus: current
UnifiedTermRowRef: UTS.U.View.FPFCore.2026-08-02
LineageEntries: viewRef resolves exact E only after membership is independently current; view, diagram, face, form, and carrier readings remain separated
RefreshCondition: reopen when E.17.0 changes E/P conformance, same-individual membership, E.24.UK admission, FPFCoreReferenceScheme, reader meaning, or public use
F.17:12.4f.1 - U.Viewpoint
UTSRowId: UTS.U.Viewpoint.FPFCore.2026-08-02
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: R1.2-MultiView-Naming
Block: Multi-view describing
GovernedValueRef: U.Viewpoint
GovernedValueKindRef: U.Kind
SubjectPatternLocator: E.17.0
UnifiedTechName: U.Viewpoint
UnifiedPlainName: viewpoint
NameCardRef: NameCard.U.Viewpoint.FPFPublic.2026-10-30
SenseCellRefs: SenseCell.U.Viewpoint.FPFCore.2026-10-30
BridgeRefs: none; this row makes no semantic-correspondence or substitution claim
RowRationale: the governed value is the E.17.0/E.24.UK same-individual dependent kind. Each admitted member is an independently identified C.2.1 episteme P whose fixed ClaimGraph and effective ReferenceScheme satisfy the complete E.17.0 predicate. Its EntityOfConcern is the independently admitted target kind in the ordinary branch, or independently selected viewpoint-convention Structure S_viewpoint when that organization itself must be maintained. Admission result E24UK-AR-UVIEWPOINT-RG-01 remains a separate decision projection.
AdmissibleUse: Core-facing designation of the dependent kind and exact typing of a reference whose resolution yields an already admitted viewpoint episteme P
BlockedUse: no viewpoint membership, episteme identity, Structure selection, method, Work, conformance, View membership, authority, or publication from the row, name, ViewpointId, viewpointRef, NameCard, bundle position, selected S, form, or carrier
RowEditionId: 2026-10-30
CurrentnessCondition: reopen when E.17.0 changes P's C.2.1 discriminators, target-kind or conditional S EntityOfConcern, fixed target/concern/admitted-kind/conformance claims, effective ReferenceScheme, same-individual predicate, E.24.UK admission, NameCard, or typed-reference use
Notes: retain the exact field viewpointRef : U.ViewpointRef; under the effective scheme its resolution yields P, while ViewpointId only designates P and neither operation grants membership
SenseCell.U.Viewpoint.FPFCore.2026-10-30:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: U.Viewpoint-core-2026-10-30
LocalExpression: U.Viewpoint
LocalSenseClaim: the same-individual dependent kind of exact C.2.1 epistemes P whose exact EntityOfConcern is the independently admitted target kind, or independently selected viewpoint-convention Structure S_viewpoint when that organization itself must be maintained, and whose fixed claims identify the selected subject and state the exact target-kind criterion, stakeholder or audience referents when current, concerns, admitted episteme kinds, coverage, semantic-form, completeness, consistency, omission and conformance rules without circular View premises, and the describing-use frame and fixed applicability qualifiers
senseFamily: MultiViewRecognition
NameCardRef: NameCard.U.Viewpoint.FPFPublic.2026-10-30
LocalSenseBasisRelationRefs: LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-10-30
LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-10-30:
localSenseCellRef: SenseCell(FPFCoreReferenceScheme, U.Viewpoint-core-2026-10-30)
basisEpistemeRef: E.17.0
LocalSenseBasisRelationDescription.U.Viewpoint.FPFCore.2026-10-30:
entityOfConcernRef: LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-10-30
entityOfConcernKindRef: LocalSenseBasisRelation
basisPublicationUnitRef: E.17.0:4.2,4.6.1-4.6.4
viewpointRef: FPFCoreReaderViewpoint
claimGraph:
supportedSenseClaim: U.Viewpoint names the kind whose members are the same epistemes P identified under C.2.1 when the target-kind or conditional S EntityOfConcern and fixed convention claims satisfy E.17.0
admittedUseClaim: Core-facing designation, exact U.ViewpointRef typing, and retrieval of the direct membership rule
nonAdmittedUseClaim: the basis relation, cell, NameCard, row, identifier, reference, Structure, bundle, or publication grants no membership
referenceScheme: FPFCoreReferenceScheme
editionId: 2026-10-30
F.17:12.4f.2 - U.View
UTSRowId: UTS.U.View.FPFCore.2026-08-02
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: R1.2-MultiView-Naming
Block: Multi-view describing
GovernedValueRef: U.View
GovernedValueKindRef: U.Kind
SubjectPatternLocator: E.17.0
UnifiedTechName: U.View
UnifiedPlainName: episteme conforming to an exact viewpoint
NameCardRef: NameCard.U.View.FPFPublic.2026-08-02
SenseCellRefs: SenseCell.U.View.FPFCore.2026-08-02
BridgeRefs: none; this row makes no semantic-correspondence or substitution claim
RowRationale: the governed value is the E.17.0/E.24.UK same-individual dependent-kind token, not candidate episteme E, viewpoint P, conformance occurrence, reference, form, or carrier; an admitted member is the same exact C.2.1 episteme E only when EpistemeViewpointConformanceRelation(E,P) obtains for at least one exact admitted P; one unchanged E may conform to several viewpoint editions through distinct pair-determined occurrences while remaining one episteme; admission result E24UK-AR-UVIEW-RG-01 remains a separate decision projection
AdmissibleUse: Core-facing designation of the dependent kind and exact typing of U.ViewRef values that resolve already conforming epistemes
BlockedUse: no View membership, episteme identity, conformance occurrence, adequacy, authority, or publication from the row, name, viewRef, NameCard, direct authoring, A.6.3 construction, query execution, transformation, evaluation, selection, bundling, rendering, audience, form, carrier, or publication
RowEditionId: 2026-10-30
CurrentnessCondition: reopen when E.17.0 changes candidate-episteme identity, the exact conformance predicate or pair-determined occurrence rule, same-individual membership, E.24.UK admission, NameCard, FPFCoreReferenceScheme, or typed-reference use
Notes: construction history and publication availability remain separately governed; neither creates membership, and no second View individual wraps E
SenseCell.U.View.FPFCore.2026-08-02:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: U.View-core
LocalExpression: U.View
LocalSenseClaim: the same-individual dependent kind of exact C.2.1 epistemes E for which at least one direct EpistemeViewpointConformanceRelation(E,P) occurrence obtains to an exact admitted viewpoint episteme P; E remains the same individual and construction, selection, use, representation, and publication remain non-constitutive
senseFamily: MultiViewRecognition
NameCardRef: NameCard.U.View.FPFPublic.2026-08-02
LocalSenseBasisRelationRefs: LocalSenseBasisRelation.U.View.FPFCore.2026-08-02
LocalSenseBasisRelation.U.View.FPFCore.2026-08-02:
localSenseCellRef: SenseCell(FPFCoreReferenceScheme, U.View-core)
basisEpistemeRef: E.17.0
LocalSenseBasisRelationDescription.U.View.FPFCore.2026-08-02:
entityOfConcernRef: LocalSenseBasisRelation.U.View.FPFCore.2026-08-02
entityOfConcernKindRef: LocalSenseBasisRelation
basisPublicationUnitRef: E.17.0:4.4-4.5
viewpointRef: FPFCoreReaderViewpoint
claimGraph:
supportedSenseClaim: U.View names the kind whose members are the same epistemes E when exact E/P conformance obtains; membership introduces no generated or published wrapper
admittedUseClaim: Core-facing designation, exact U.ViewRef typing, and retrieval of the direct membership rule
nonAdmittedUseClaim: the basis relation, cell, NameCard, row, reference, construction, evaluation, form, carrier, or publication grants no membership
referenceScheme: FPFCoreReferenceScheme
editionId: 2026-10-30
F.17:12.4f.3 - EpistemeViewpointConformanceRelation
UTSRowId: UTS.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: R1.2-MultiView-Naming
Block: Multi-view describing
GovernedValueRef: EpistemeViewpointConformanceRelation
GovernedValueKindRef: U.Kind
SubjectPatternLocator: E.17.0
UnifiedTechName: EpistemeViewpointConformanceRelation
UnifiedPlainName: the episteme conforms to this exact viewpoint
NameCardRef: NameCard.EpistemeViewpointConformanceRelation.FPFPublic
SenseCellRefs: SenseCell.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02
BridgeRefs: none; this row makes no semantic-correspondence or substitution claim
RowRationale: the governed value is E.17.0's direct relation-kind token, not its RelationSignature, either participant, a reference, occurrence, assertion, evaluation result, NameCard, or row; each positive occurrence has exactly candidate episteme E and admitted viewpoint episteme P as participants and is pair-determined by <E,P>; it obtains only when E's C.2.1 EntityOfConcern satisfies P's exact target-kind criterion, E has an independently admitted episteme kind allowed by P without circular U.View use, and E's fixed content under its effective scheme satisfies P's fixed concern-coverage, semantic-form, completeness, consistency, omission, and loss rules
AdmissibleUse: Core-facing designation of the direct relation kind, exact RelationSignature lookup, and readable E/P conformance claims under E.17.0
BlockedUse: no conformance occurrence, U.View membership, adequacy, truth, authority, or publication from the row, name, NameCard, signature, SlotSpecs, viewpointRef, ViewpointId, participant fillers, assertion, evidence, evaluation Work, result, construction, query, rendering, form, carrier, or publication
RowEditionId: 2026-08-02
CurrentnessCondition: reopen when E.17.0 changes either participant kind, the target/admitted-kind/content predicate, pair-determined positive occurrence identity, RelationSignature, complete NameCard, FPFCoreReferenceScheme, or named Core use
Notes: `EpistemeViewpointConformanceRelationSignature` is the E.17.0 declaration episteme whose exact EntityOfConcern is `EpistemeViewpointConformanceRelation`; A.6.0 independently gives that same individual `U.Signature` membership and relation-facing `RelationSignature` use, with `CandidateEpistemeSlot : U.EpistemeRef` and `ViewpointEpistemeSlot : U.ViewpointRef`; retain the exact consumer field `viewpointRef : U.ViewpointRef`, whose resolution yields P but proves no conformance
SenseCell.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: EpistemeViewpointConformanceRelation-core
LocalExpression: EpistemeViewpointConformanceRelation
LocalSenseClaim: the direct two-participant relation kind whose exact positive occurrence is pair-determined by one independently identified candidate episteme E and one independently admitted viewpoint episteme P and whose E.17.0 predicate tests E's exact EntityOfConcern kind, independently admitted episteme kind, fixed claim content, effective scheme, and satisfaction of P's fixed coverage, semantic-form, completeness, consistency, omission, and loss rules
senseFamily: MultiViewConformance
NameCardRef: NameCard.EpistemeViewpointConformanceRelation.FPFPublic
LocalSenseBasisRelationRefs: LocalSenseBasisRelation.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02
LocalSenseBasisRelation.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02:
localSenseCellRef: SenseCell(FPFCoreReferenceScheme, EpistemeViewpointConformanceRelation-core)
basisEpistemeRef: E.17.0
LocalSenseBasisRelationDescription.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02:
entityOfConcernRef: LocalSenseBasisRelation.EpistemeViewpointConformanceRelation.FPFCore.2026-08-02
entityOfConcernKindRef: LocalSenseBasisRelation
basisPublicationUnitRef: E.17.0:4.4-4.4.1
viewpointRef: FPFCoreReaderViewpoint
claimGraph:
supportedSenseClaim: EpistemeViewpointConformanceRelation names the exact E.17.0 direct kind rather than its signature, participant references, assertion, evaluation, result, or dependent View membership
admittedUseClaim: Core-facing designation, exact signature lookup, and readable reference to the direct relation kind
nonAdmittedUseClaim: the basis relation, cell, NameCard, row, signature, references, evaluation, construction, or publication makes no occurrence obtain and grants no U.View membership
referenceScheme: FPFCoreReferenceScheme
editionId: 2026-08-02
Each row retains its C.2.1 episteme identity and refers separately to the governed value, naming decision and local sense. The displayed fields preserve the distinct designators, references and relation occurrences. When readers need access to a selected row edition, recover the E.24.PUB expression, bearing and publication occurrences outside the row; displaying this block alone does not establish them.
F.17:12.4g - Make a settled row available only through a separate publication operation
Do not perform an E.24.PUB publication operation on a placeholder. First require the governed value, its lexical classification, the reference scheme’s selected name and permitted scope, and the intended reader use to pass F.18 and the ordinary F.17 row gate. If any input is unresolved, keep it as naming work rather than representing it as a current row.
When availability is current, state how the selected row edition is available to its audience for the bounded use through an expression and carrier. E.24.PUB governs that claim at its required granularity; name reusable-form conformance only when it matters.
A NameCard, scheme-sense cell, basis relation, row reference, or E.24.PUB occurrence substitutes for none of those decisions. Keep predicate definition, actual use, basis analysis, naming settlement, row admission, and downstream availability separate.
F.17:12.4h - Role-Precision Core Rows
These eight rows expose the F.18 designation pairs for Core citation. Each names one value defined or constrained by its subject pattern and uses one FPFCoreReferenceScheme sense cell. Its currentness depends on that value and subject-pattern rule, the E.10 token classification and allowed-use rule it consumes, its exact NameCard, sense cell and cited use.
UTSRowId: UTS.U.SystemRoleAssignment.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: U.SystemRoleAssignment
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.2.1
UnifiedTechName: U.SystemRoleAssignment
UnifiedPlainName: assignment to a system role
NameCardRef: NC-U-SYSTEM-ROLE-ASSIGNMENT
SenseCellRefs: SenseCell.U.SystemRoleAssignment.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the direct assignment family whose species relate an independently admitted system to one exact local system-role kind
AdmissibleUse: Core-facing citation of the family and exact directly declared species
BlockedUse: no kind, record, field, occurrence, authority, responsibility, or Work follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when A.2.1, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for U.SystemRoleAssignment, or the cited use changes
UTSRowId: UTS.KindUseAdaptationDeclaration.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: KindUseAdaptationDeclaration
GovernedValueKindRef: U.Kind
SubjectPatternLocator: C.3.4
UnifiedTechName: KindUseAdaptationDeclaration
UnifiedPlainName: declaration of a local use of a kind
NameCardRef: NC-KIND-USE-ADAPTATION-DECLARATION
SenseCellRefs: SenseCell.KindUseAdaptationDeclaration.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the C.3.4 declaration-episteme family; each member pins one exact base kind and signature edition, one receiving use, its constraints or vocabulary bindings, definedness, and intended guard use
AdmissibleUse: Core-facing citation of the C.3.4 declaration family
BlockedUse: no kind, assignment, scope, profile, system role, guard decision, or judgment follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when C.3.4, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for KindUseAdaptationDeclaration, or the cited use changes
UTSRowId: UTS.KindUseAdaptationCorrespondenceDeclaration.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: KindUseAdaptationCorrespondenceDeclaration
GovernedValueKindRef: U.Kind
SubjectPatternLocator: C.3.4
UnifiedTechName: KindUseAdaptationCorrespondenceDeclaration
UnifiedPlainName: declaration of how two local ways of using kinds correspond and what is lost
NameCardRef: NC-KIND-USE-ADAPTATION-CORRESPONDENCE-DECLARATION
SenseCellRefs: SenseCell.KindUseAdaptationCorrespondenceDeclaration.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the C.3.4 correspondence-declaration family; each member states deterministic correspondence and loss between two exact adaptation declarations
AdmissibleUse: Core-facing citation of the C.3.4 correspondence-declaration family
BlockedUse: no F.9 Bridge, executable adapter, mapping Method, representation correspondence, assignment, or target truth follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when C.3.4, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for KindUseAdaptationCorrespondenceDeclaration, or the cited use changes
UTSRowId: UTS.KindUseAdaptationJudgment.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: KindUseAdaptationJudgment
GovernedValueKindRef: U.Kind
SubjectPatternLocator: C.3.4
UnifiedTechName: KindUseAdaptationJudgment
UnifiedPlainName: judgment of whether a candidate fits a local use of a kind
NameCardRef: NC-KIND-USE-ADAPTATION-JUDGMENT
SenseCellRefs: SenseCell.KindUseAdaptationJudgment.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the C.3.4 judgment family; each member is the true, false, or unknown result for one candidate under pinned base-kind, signature, declaration-edition, and slice inputs
AdmissibleUse: Core-facing citation of the C.3.4 judgment family
BlockedUse: no declaration, candidate, guard disposition, evidence result, or kind membership follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when C.3.4, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for KindUseAdaptationJudgment, or the cited use changes
Notes: J_kindUse remains declaration-local notation and receives no row
UTSRowId: UTS.SystemRoleKindDescription.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: SystemRoleKindDescription
GovernedValueKindRef: U.Kind
SubjectPatternLocator: F.4
UnifiedTechName: SystemRoleKindDescription
UnifiedPlainName: description of a system-role kind
NameCardRef: NC-SYSTEM-ROLE-KIND-DESCRIPTION
SenseCellRefs: SenseCell.SystemRoleKindDescription.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the F.4 description-episteme construction; each member has one exact local system-role kind as its EntityOfConcern
AdmissibleUse: Core-facing citation of the F.4 description-episteme construction
BlockedUse: no described kind, assignment, NameCard, row, publication form, or carrier follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when F.4, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for SystemRoleKindDescription, or the cited use changes
UTSRowId: UTS.SystemRoleAssignmentStateRelation.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: SystemRoleAssignmentStateRelation
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.2.5
UnifiedTechName: SystemRoleAssignmentStateRelation
UnifiedPlainName: this assignment to a system role satisfies this state condition
NameCardRef: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-RELATION
SenseCellRefs: SenseCell.SystemRoleAssignmentStateRelation.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the A.2.5 direct relation kind; each obtaining occurrence relates one exact U.SystemRoleAssignment occurrence and one by-value SystemRoleAssignmentStatePredicate
AdmissibleUse: Core-facing citation of the A.2.5 direct relation kind
BlockedUse: no state assertion, displayed status, predicate value, assignment, or obtaining occurrence follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when A.2.5, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for SystemRoleAssignmentStateRelation, or the cited use changes
UTSRowId: UTS.SystemRoleAssignmentStatePredicate.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: SystemRoleAssignmentStatePredicate
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.2.5
UnifiedTechName: SystemRoleAssignmentStatePredicate
UnifiedPlainName: state condition for an assignment to a system role
NameCardRef: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-PREDICATE
SenseCellRefs: SenseCell.SystemRoleAssignmentStatePredicate.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the predicate-value family whose members state truth conditions over exact system-role assignments
AdmissibleUse: Core-facing citation of the A.2.5 predicate-value family
BlockedUse: no relation occurrence, assertion, displayed result, state label, or assignment follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when A.2.5, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for SystemRoleAssignmentStatePredicate, or the cited use changes
UTSRowId: UTS.SystemRoleKindRelationStructure.FPFCore.2026-08-09
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: RoleOntologyAndWordingPrecision.2026-08-09
Block: System-role assignments and kind-use precision
GovernedValueRef: SystemRoleKindRelationStructure
GovernedValueKindRef: U.Kind
SubjectPatternLocator: A.2.7
UnifiedTechName: SystemRoleKindRelationStructure
UnifiedPlainName: structure of relations among system-role kinds
NameCardRef: NC-SYSTEM-ROLE-KIND-RELATION-STRUCTURE
SenseCellRefs: SenseCell.SystemRoleKindRelationStructure.FPFCore.2026-08-09
BridgeRefs: none
RowRationale: both designations name the relation-defined kind specified by A.2.7; each member is a selected U.Structure, not the kind itself
AdmissibleUse: Core-facing designation of that A.2.7 kind; one selected member must instead be identified by its exact kind constituents, selected obtaining relation occurrences, applied constraints, and named selection-use frame
BlockedUse: no new root kind, selected structure instance, assignment configuration, taxonomy episteme, graph, table, or system collection follows from this row
RowEditionId: 2026-08-09
CurrentnessCondition: reopen when A.2.7, the exact NameCard, FPFCoreReferenceScheme or sense cell, E.10:7.5b classification or allowed-use rule for SystemRoleKindRelationStructure, or the cited use changes
The rows use these exact scheme-based sense cells; the cells name no additional value and require no Bridge merely because both Tech and Plain designations exist.
SenseCell.U.SystemRoleAssignment.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: U.SystemRoleAssignment-core
LocalExpression: U.SystemRoleAssignment
LocalSenseClaim: the family of assignments in which each occurrence belongs to a declared species, relates an admitted System to one local system-role kind, and includes only the other participants required by that species
NameCardRef: NC-U-SYSTEM-ROLE-ASSIGNMENT
SenseCell.KindUseAdaptationDeclaration.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: KindUseAdaptationDeclaration-core
LocalExpression: KindUseAdaptationDeclaration
LocalSenseClaim: a C.2.1 declaration episteme that pins the base kind and signature edition, receiving use, constraints or vocabulary bindings, definedness, and intended guard use
NameCardRef: NC-KIND-USE-ADAPTATION-DECLARATION
SenseCell.KindUseAdaptationCorrespondenceDeclaration.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: KindUseAdaptationCorrespondenceDeclaration-core
LocalExpression: KindUseAdaptationCorrespondenceDeclaration
LocalSenseClaim: a C.2.1 declaration episteme stating deterministic correspondence and loss between two exact KindUseAdaptationDeclaration values; it creates no Bridge, execution, representation correspondence, or target truth
NameCardRef: NC-KIND-USE-ADAPTATION-CORRESPONDENCE-DECLARATION
SenseCell.KindUseAdaptationJudgment.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: KindUseAdaptationJudgment-core
LocalExpression: KindUseAdaptationJudgment
LocalSenseClaim: the true, false, or unknown result for one candidate under a pinned base kind, signature edition, adaptation-declaration edition, and slice; it is not the declaration, guard disposition, or evidence
NameCardRef: NC-KIND-USE-ADAPTATION-JUDGMENT
SenseCell.SystemRoleKindDescription.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: SystemRoleKindDescription-core
LocalExpression: SystemRoleKindDescription
LocalSenseClaim: an F.4 description episteme whose exact EntityOfConcern is one local system-role kind
NameCardRef: NC-SYSTEM-ROLE-KIND-DESCRIPTION
SenseCell.SystemRoleAssignmentStateRelation.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: SystemRoleAssignmentStateRelation-core
LocalExpression: SystemRoleAssignmentStateRelation
LocalSenseClaim: the direct relation kind whose obtaining occurrences relate one exact U.SystemRoleAssignment occurrence to one by-value SystemRoleAssignmentStatePredicate
NameCardRef: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-RELATION
SenseCell.SystemRoleAssignmentStatePredicate.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: SystemRoleAssignmentStatePredicate-core
LocalExpression: SystemRoleAssignmentStatePredicate
LocalSenseClaim: the predicate-value family whose members state truth conditions over exact system-role assignments; it is not an assertion, displayed result, or obtaining relation
NameCardRef: NC-SYSTEM-ROLE-ASSIGNMENT-STATE-PREDICATE
SenseCell.SystemRoleKindRelationStructure.FPFCore.2026-08-09:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: SystemRoleKindRelationStructure-core
LocalExpression: SystemRoleKindRelationStructure
LocalSenseClaim: the A.2.7 relation-defined kind of selected structures; each member is a U.Structure with exact system-role-kind constituents, selected obtaining relation occurrences, applied constraints, and one named selection-use frame; this cell names the kind, not one member, assignment configuration, taxonomy episteme, or system collection
NameCardRef: NC-SYSTEM-ROLE-KIND-RELATION-STRUCTURE
F.17:12.4i - Architectural Reference term row
This row makes the F.18:4.2e settlement reusable for the architectural-reference form already governed by E.4, E.11.PFP and E.11.DSG. The governed value is the functional publication-unit form, not a newly minted root kind.
A single row is useful because the same function is cited across these rules and applied at framework, Suite and Library levels. The row identifies that function without identifying all its instances as one publication.
UTSRowId: UTS.ArchitecturalReference.FPFCore.2026-10-12
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: ArchitecturalReferenceNaming.2026-10-12
Block: Public account of a method language
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
UnifiedTechName: ArchitecturalReference
UnifiedPlainName: architectural reference
NameCardRef: NC-ARCHITECTURAL-REFERENCE
SenseCellRefs: SenseCell.ArchitecturalReference.FPFCore.2026-10-12
BridgeRefs: none
RowRationale: both designations name the public account of a named method language's architecture, connections, reasons and shared explanation; embedded and separate carriage are alternatives for the same function, and useful question-led entries return to the full Methods without limiting the whole account to short answers
AdmissibleUse: Core-facing designation of this functional form and full public titles of the form <name of the explained whole> Architectural Reference; a shorter mention is sufficient when the whole is unambiguous
BlockedUse: the row establishes no disciplinary composition, composite Method, independent product series, edition admission, publication occurrence, availability, maintenance or source authority; it neither supplies an unwritten Method nor turns an account into another framework or teaching Guide
Notes: DPFSuiteReference and its earlier sense cell designate the narrower cross-DPF answer-publication sense, not this broader governed value; no EpistemeEditionRelation or F.9 Bridge is asserted from shared wording, section placement or carrier
RowEditionId: 2026-10-12
CurrentnessCondition: reopen when E.4, E.11.PFP or E.11.DSG changes the function, public content, assembly-level or product boundary, or title rule; when the exact NameCard, FPFCoreReferenceScheme, sense cell or selected use changes; or when readers repeatedly recover a different function
SenseCell.ArchitecturalReference.FPFCore.2026-10-12:
ReferenceScheme: FPFCoreReferenceScheme
LocalSenseId: ArchitecturalReference-core
LocalExpression: ArchitecturalReference
LocalSenseClaim: the E.4/E.11.PFP/E.11.DSG functional form of a public account explaining a named method language's architecture, connections, rationale and shared conditions, embedded or separately carried at its actual assembly level, with useful entries and returns to full constituent explanations; naming the form establishes no disciplinary parthood, composite Method, independent product series, publication, availability or maintenance
NameCardRef: NC-ARCHITECTURAL-REFERENCE
For example, FPF Library Architectural Reference and Engineering Suite Architectural Reference identify different explained wholes. An embedded Method Engineering Principle Framework Architectural Reference performs the same function for that framework. Whether the account is independently managed depends on its use and change boundary. Its title alone does not decide this. The row makes the designation recoverable, while E.24.PUB separately governs any publication of this row or a particular architectural reference.
F.17:12.6 - Model-comparison direction and level rows
Use these three rows to cite model refinement, its converse and the levels established by comparing models. B.5.MR gives the tests for the two model relations. The level row gives both directional readings of one order used in project documents and teaching.
In the shared ReferenceScheme a model’s completions satisfy its assertions. The inquiry and its interpretation determine the answer read from each completion, including probability claims when relevant. C refines A when at least one completion of C exists and every completion of C satisfies A under that interpretation. A is then an abstraction of C. Strictness requires an answer that A admits and C excludes. Within a chain established by this test, models with the same answers share a level for that inquiry. Models on different branches can give the same answer while imposing incompatible constraints.
For each row, UnificationThreadId is ModelComparisonDirections, GovernedValueKindRef is U.Kind and ReferenceScheme has the value given above. The stable row designators are retained. RowEditionId for this edition is 2026-11-18. Each sense cell gives its expression and local sense under the shared scheme.
UTSRowId: UTS.ModelRefinement.2026-11-16
GovernedValueRef: B.5.MR:4.2 refinement relation kind
SubjectPatternLocator: B.5.MR:4.1–4.2
UnifiedTechName: model refinement
NameCardRef: NC-MODEL-REFINEMENT
SenseCellRefs: SenseCell.ModelRefinement.2026-11-18
RowRationale: retain the specification-theory designation while making feasibility, interpretation and the converse recoverable
AdmissibleUse: cite C's feasible preservation of A for the named inquiry, including equality; use more concrete only with strictness
BlockedUse: the name alone establishes neither higher empirical accuracy nor a strict difference
CurrentnessCondition: reopen on changed predicate, interpretation, NameCard, cell or repeated confusion between refinement and accuracy
SenseCell.ModelRefinement.2026-11-18:
LocalExpression: model refinement
LocalSenseClaim: C refines A for inquiry Q under interpretation I exactly when at least one completion of C exists and every completion of C satisfies A under I; strictness additionally excludes an answer of A distinguishable for Q
UTSRowId: UTS.ModelAbstraction.2026-11-16
GovernedValueRef: B.5.MR:4.2 abstraction relation kind
SubjectPatternLocator: B.5.MR:4.2; B.5.MR:4.2.2
UnifiedTechName: model abstraction
NameCardRef: NC-MODEL-ABSTRACTION
SenseCellRefs: SenseCell.ModelAbstraction.2026-11-18
RowRationale: give the converse comparison a durable name while keeping model construction separate
AdmissibleUse: cite A as an abstraction of C under the same inquiry and interpretation by establishing that C refines A
BlockedUse: the name supplies no unique inverse construction and does not validate a wider empirical claim
CurrentnessCondition: reopen on changed predicate, interpretation, NameCard, cell or confusion between the relation and omitted visible detail
SenseCell.ModelAbstraction.2026-11-18:
LocalExpression: model abstraction
LocalSenseClaim: A is an abstraction of C for inquiry Q under interpretation I exactly when C refines A for Q under I. Calling A more abstract than C requires strictness for Q.
UTSRowId: UTS.ModelAbstractionLevel.2026-11-16
GovernedValueRef: B.5.MR:4.3 inquiry-relative level of model abstraction
SubjectPatternLocator: B.5.MR:4.2–4.3
UnifiedTechName: level of model abstraction
NameCardRef: NC-MODEL-ABSTRACTION-LEVEL
SenseCellRefs: SenseCell.ModelAbstractionLevel.2026-11-18, SenseCell.ModelRefinementLevel.2026-11-18
RowRationale: name the ordered levels in both directions so the reader can identify which models are compared and what follows from the comparison
AdmissibleUse: read L0 towards L4 as levels of model abstraction and L4 towards L0 as levels of model refinement in an established application chain. Use intermediate levels where the comparison warrants them.
BlockedUse: a level name alone establishes neither preservation nor a strict difference for the inquiry
CurrentnessCondition: reopen on changed comparison, NameCard, cell or repeated use as a global rank
SenseCell.ModelAbstractionLevel.2026-11-18:
LocalExpression: level of model abstraction
LocalSenseClaim: level in an established refinement chain read towards a model that allows an answer the other model excludes for Q under I. Successive models with the same answers share a level for Q.
SenseCell.ModelRefinementLevel.2026-11-18:
LocalExpression: level of model refinement
LocalSenseClaim: the same order read towards a model that excludes a previously admissible answer for Q under I. Successive models with the same answers share a level for Q.
The rows cite no F.9 Bridge: they make no correspondence claim between different local meanings. A concrete comparison still needs its models, inquiry, interpretation and B.5.MR test; citing a row supplies the selected name and its meaning.
F.17:12.5 - Bias-Annotation
F.17 blocks table-bias: a row does not make the named object real, global, reusable, equivalent, or authoritative. It also blocks label-bias: the public name is a designation for a governed value, relation, slot, or local concept, not a substitute for the rules that define or constrain it, the scheme-based local-sense coordinate, Bridge, admissible-use statement, or currentness condition.
F.17:13.5 - Conformance Checklist
| Check | Passing condition |
|---|---|
CC-F17-1 | One exact governed value, its kind, the pattern that defines or constrains it, and the proposed row use were recovered before the row. |
CC-F17-2 | Each current card, cell and row has a receiving need under F.14; an already adequate lighter treatment is reused. |
CC-F17-3 | Row episteme, NameCard, designation expressions, governed value, reference, exact SenseCell, basis relation, and any F.9 Bridge remain distinct. |
CC-F17-4 | Every cell resolves to an effective by-value ReferenceScheme, exact expression, and local-sense claim; no generic context field or selected structure substitutes for them. |
CC-F17-5 | Every actual LocalSenseBasisRelation has exactly the cell and basis episteme as participants; descriptions, source units, publication occurrences, forms, and carriers stay separate. |
CC-F17-6 | Any F.9 Bridge cited in the row obtains between its exact endpoint cells; the separate use claim and A.10/B.3 reliance are visible only when that row use is current. |
CC-F17-7 | Admissible use, any grounded blocked-use claim, row edition id, currentness condition, and any exact C.2.1 edition relation are recoverable without treating designators as identity. |
CC-F17-8 | Check a claimed availability under E.24.PUB at its stated granularity, independently of the row and any rendering or upload Work. For a fixed expression and carrier recover their exact publication relations. When both form and carrier are fixed, the same expression must conform to the form and be borne by that carrier. For a broader claim check the permitted alternatives and any fixed constraints. |
CC-F17-9 | Multi-view naming uses three separate rows: U.Viewpoint names a dependent kind. An episteme P itself belongs to that kind when it satisfies E.17.0’s fixed-content viewpoint predicate. Normally P concerns the target kind. Select the viewpoint-convention structure S only when that organization itself must be maintained. U.View names another dependent kind. The episteme E itself belongs to it only when conformance holds between that exact E and at least one admitted viewpoint episteme P. EpistemeViewpointConformanceRelation names the two-participant pair-determined direct kind. References, designators, NameCards, RelationSignature, occurrences, construction, and publication grant none of those results. |
F.17:13 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Why it fails | Repair |
|---|---|---|
| Global glossary row | Removes the exact governed value, scheme, and local-sense claim. | Recover the exact value and one scheme-based cell; keep local wording local when that suffices. |
| One row for system-role kind and status | Fuses a work-facing system-role kind with a state-family value. | Split the rows and use the pattern that defines or constrains each value. |
| Evidence-role bucket | Turns evidence use, source use, assurance, and Work into one pseudo-kind. | Recover each claim under A.10, B.3, E.10.D2, or the pattern that defines or tests the source or Work claim. |
| Automatic card-cell-row chain | Treats the presence of one naming object as need for the next. | Apply F.14 separately at each gate and stop at the lightest sufficient object. |
| Merged viewpoint/view/conformance row | A dependent kind, another dependent kind, and their direct relation are treated as one naming result. | Keep separate U.Viewpoint, U.View, and EpistemeViewpointConformanceRelation rows and use E.17.0 for every membership or obtaining claim. |
| Spelling or suffix identity | Lets a familiar label, stable id, or ...@Context form create or merge values. | Resolve the value under the pattern that defines or constrains it and treat only tokens fixed there as lineage. |
| Borrowed locality label as Tech name | Imports one tradition’s commitments into the row and hides the effective interpretation basis. | Recover the governed value and scheme-based cell; select the designation under F.18 and cite an actual F.9 Bridge only when its separate predicate and use conditions hold. |
| Basis by source title | Replaces the exact cell and actual basis relation with a file or citation. | Recover the cell and two-participant basis relation; keep source-unit and publication facts separate. |
| Row as publication | Treats table presence, rendering, upload, form or carrier alone as availability. | Establish E.24.PUB availability for the selected row edition, audience and bounded use through its expression and carrier; include reusable-form conformance when needed. |
| Block as ontology or completeness proof | Treats navigation as subtype structure or row count as value evidence. | Keep blocks optional and judge the exact row use through reader recovery and blocked-use avoidance. |
| Row without its defining or constraining pattern | Lets F.17 govern the named object. | Point to the pattern that defines or constrains the value or stop the public-row path. |
F.17:14 - Closure conditions
One row is ready for its declared citation use only when:
- the governed value, exact kind, the pattern that defines or constrains it, and the proposed use are explicit;
- each current card, cell and row supplies a receiving need established under F.14;
- the exact F.18 NameCard, selected Tech designation and any Plain designation are current for this public-row gate;
- every
SchemeSenseCellresolves to one by-value ReferenceScheme, local expression, and local-sense claim; - every relied-on local-sense basis is an actual two-participant
LocalSenseBasisRelationand every description/source/publication object remains separate; - any row use that relies on semantic correspondence between different local meanings cites an obtaining F.9 Bridge for the exact endpoints, a separate affirmative use claim and current A.10 reliance for that use or, when a named assurance claim is needed, the corresponding B.3 assurance result;
- the row has one decision, an admitted citation use, any grounded blocked-use claim, an edition designator, and a reopen condition;
- any historical continuation is an exact C.2.1
EpistemeEditionRelationrather than shared id or title; - any claimed availability has E.24.PUB grounds at the granularity asserted; an ordinary availability statement is sufficient when no finer identity or change question is current; and
- every ontology, obtaining, equivalence, authority, system-role-kind, assignment, relation-position, status, evidence, Work, and other subject-use claim uses the pattern that defines, constrains, or tests it.
No other row needs to be filled before this one can close. A sheet’s row count or optional block plan says nothing about whether another naming decision is substantively needed.
F.17:14.1 - Consequences
Benefits. Readers gain a stable route from the selected designation or designations to the naming decision, governed value, defining or constraining rules, local sense, and admitted use without treating the table as ontology or publication proof.
Costs. A tempting row waits until the independently governed value, F.14 disposition, naming settlement, exact cell, and any actual Bridge are current. Publication availability adds its own E.24.PUB objects only when needed.
Failure avoided. F.17 prevents global glossary drift, card-cell-row cascades, label-based sameness, row-shaped ontology, optional-layout completeness claims, and authority or publication smuggled through a table.
F.17:14.2 - Rationale
Terms travel farther than the reasoning that produced them. F.17 carries only the reopening hooks needed for that travel. The pattern that defines or constrains the governed value, together with F.18, F.9, C.2.1, A.10/B.3, and E.24.PUB, supplies the separate rules to which those hooks lead.
F.17:16 - SoTA Decision for One Reader-Facing Term Row
Question and selected answer. At the effort of settling one reusable term, what must a reader recover beyond a familiar label, and what apparatus can be left out? Under E.8:11, use one readable row that returns separately to the named value, naming decision, exact local sense, permitted citation use and any grounded blocked-use claim, and the condition that reopens the row. Create it only when that reader-facing route is needed.
The lightweight serious rival. The OntoLex Community Report, Overview, Purpose, Core, and Semantics permits the core module alone. A fair one-term comparator is a lexical entry with a form, a sense and a reference to the already defined ontology entity, plus only the usage notes this application needs. It does not require a full lexicon, morphology or syntax graph; it is not intended to define the ontology itself.
Adapt its expression/sense/reference separation in 5.1 and 7. Its extensibility also permits notes or a view to expose the same decision content as an F.17 row.
Compare the row with the lightweight lexical entry. Hold the term, target, use conditions, and maintenance obligation fixed. A bare label or bare form/sense/reference chain lets the reader find the expression and target, but leaves the naming choice and reason to revisit it unstated, along with any blocked use that the reader needs to distinguish.
Adding those statements to the lightweight rival closes that gap; a generated readable view of those same statements is an acceptable way to express the F.17 row. A different vocabulary or file format is not, by itself, an improvement or a second naming result.
For an ordinary reader inspecting one term, select the explicit row because the decision and return are visible together. The trade-off is maintaining a truthful reader-facing projection instead of asking that reader to reconstruct it from linked lexical statements. When lexical tooling already produces that projection, keep it and avoid a second editable source.
When morphology, translation, or machine lexicon exchange is the actual use, the core model and only its needed extensions may be the better carrier. No measured speed advantage, blanket cost superiority, or replacement of OntoLex is claimed.
Exact effect and countercases. Steps 1–5 of section 4, together with sections 6 and 14, stop at ordinary wording, a local card, or a cell when no row is needed; steps 7–8 of section 4, together with sections 5.1 and 7, make the row’s returns explicit and keep later publication separate.
The countercase in 12.2 prevents a state label from becoming a system-role kind, 12.4c leaves ordinary mantra wording without rows, 12.4h distinguishes a reusable structure kind from one selected instance, and 12.4i returns the Reference name to its product-form rule without creating a product or lookup Work.
These cases supply the FPF-local reason for the added decision content; the OntoLex report supplies the rival’s lexical modeling capability, not validation of FPF ontology. Reject mandatory full-lexicon modeling, raw label familiarity as sufficient reader recovery, and the inference that a row makes its referent or publication real.
Reopen. Recompare when an equally small lexical entry or other presentation exposes the same decision, relevant use limits, and exact returns with less reader and maintenance effort; when a generated view drifts from its source; or when the current use needs linguistic distinctions or machine exchange omitted by the row. If the added reader projection no longer changes use, retain the simpler expression of the same content.
Currentness rule: when F.2, F.3, F.5, F.7, F.8, F.9, F.10, F.14, F.15, F.18, C.2.1, E.17.0, E.24.UK, E.24.PUB, A.1.1, A.2, A.2.1, A.2.7, A.6.5, A.10, B.3, E.10.D2, or the pattern that defines or constrains the governed value changes the value, kind, membership or obtaining rule, designation, scheme, cell, basis relation, Bridge, bounded-use claim, reliance, status and system-role boundary, edition relation, reference typing, or publication boundary, recheck only the affected rows and worked examples.
F.17:15 - Relations
Builds on: F.2 and F.3 for local-sense discovery probes; C.2.1 for row and NameCard epistemes plus exact EpistemeEditionRelation; F.14 for the anti-explosion gate; F.8 and F.18 for naming disposition and settlement; F.9 for actual cell-to-cell Bridges; F.5 for designation form; and F.7/F.15 for neighboring unification and conformance decisions.
Coordinates with: E.10.LRN for the learning anti-row and split boundary; A.2, A.2.1, A.2.7, A.6.5, A.6.P, A.10, A.15.1, A.19.SPR, B.3, C.2.P, E.10, E.10.D2, E.17.0, E.24.UK, E.24.PUB, F.4, F.6, and F.10, plus every row’s SubjectPatternLocator.
Row-local review after a changed value, membership or obtaining rule, designation, cell, Bridge, reference typing, edition, or availability rechecks the exact defining predicate and any neighboring subject assertion. Use G.11 only when an actual refresh plan, edition orchestration, telemetry, freshness, or decay claim is current. F.17 does not inherit a generic context-holon identity reading from earlier terminology practice.
Constrains: every public, Core-facing, durable, or cross-local term row that cites FPF values, local senses, relation names, slot names, system-role names, status names, or Bridge occurrences.
F.17:17 - Didactic distillation
Recover the governed value and settle only the name needed for the use. If readers need a durable route, make a row that leads back to the naming decision, exact local sense and defining rules. Revisit the row and its dependent uses when those grounds change; establish publication availability separately.