fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 110766–111451

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:16:27 UTC · snapshot created 2026-10-03 05:17:06 UTC · last check 2026-10-03 05:20:20 UTC

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.

The UTS row does not declare one universal reviewer kind. It creates two rows. Only when a named use really needs correspondence between their two exact sense cells may it cite an obtaining F.9 Bridge plus 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 or B.3 to state reliance on the use claim; no row or card creates an assignment or 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. Record distinct rows and connect them only through relations that actually obtain in 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. The current sources also do not constitute FPFSeminarTeachingReferenceScheme-2026-07-11 as a second by-value reference scheme. F.17 therefore records no demonstrative-slice row, seminar SenseCell, Bridge, bounded-use claim, or current public-row result from those tokens.

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 actually 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 and exposes the already selected A.1.1/F.18 naming decision for the dependent U.Structure specialization. It does not make A.1.1 Stable, create a structure individual, make any relation obtain, or make the row edition available.

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 makes only BoundedModelUseStructure current for public reuse; that currentness does not make its row edition available without an exact E.24.PUB publication package. A.22’s separate cross-structure NameCard remains local and pending: without an independently governed obtaining crossing and an exact positive membership basis, no public row is admitted or current for that label.

F.17:12.4e - Three bounded-model-use direct relation-kind rows

These rows record the three already governed A.1.1 relation-kind names used by E.24.UK. Each row makes one naming decision recoverable; it does not make that row edition available. A.1.1 defines the obtaining and reidentification tests for each such relation occurrence. The naming objects and the separately governed local-sense basis occurrences make none of the three A.1.1 relations obtain, and they create no assertion, temporal extent, Work, or structure.

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

These three rows satisfy different receiver needs and therefore cannot be merged. E.24.UK has already admitted U.Viewpoint and U.View as same-individual dependent kinds under U.Episteme; E.17.0 defines both positive membership predicates and the direct EpistemeViewpointConformanceRelation. F.14 has been applied again: the existing Tech designations are retained, no synonym family is opened, and the public rows are justified by stable Core citation and exact typed-reference use. The rows admit no kind, make no relation obtain, and assert no E.24.PUB publication occurrence, form, carrier, or authority.

The two existing dependent-kind designations use these progressive-minimum 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-08-02
  GovernedValueRef: U.Viewpoint
  GovernedValueKindRef: U.Kind
  SubjectPatternLocator: E.17.0
  ReferenceScheme: FPFCoreReferenceScheme
  ClaimContent: NameCard.U.Viewpoint.FPFPublic.2026-08-02.ClaimGraph — complete naming-settlement graph constituted by the claims designated below
  LocalSenseCellRef: SenseCell.U.Viewpoint.FPFCore.2026-08-02
  LocalSenseBasisRelationRef: LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-08-02
  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-08-02
SenseCellRefs: SenseCell.U.Viewpoint.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 P, S, a reference, or a designator; an admitted member is the same exact C.2.1 episteme P whose EntityOfConcern is independently selected viewpoint-convention Structure S_viewpoint and whose fixed ClaimGraph under its effective ReferenceScheme satisfies E.17.0's complete positive membership predicate; 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-08-02
CurrentnessCondition: reopen when E.17.0 changes P's C.2.1 discriminators, exact 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-08-02:
  ReferenceScheme: FPFCoreReferenceScheme
  LocalSenseId: U.Viewpoint-core
  LocalExpression: U.Viewpoint
  LocalSenseClaim: the same-individual dependent kind of exact C.2.1 epistemes P whose exact EntityOfConcern is independently selected viewpoint-convention Structure S_viewpoint and whose fixed claims identify S, 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-08-02
  LocalSenseBasisRelationRefs: LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-08-02

LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-08-02:
  localSenseCellRef: SenseCell(FPFCoreReferenceScheme, U.Viewpoint-core)
  basisEpistemeRef: E.17.0

LocalSenseBasisRelationDescription.U.Viewpoint.FPFCore.2026-08-02:
  entityOfConcernRef: LocalSenseBasisRelation.U.Viewpoint.FPFCore.2026-08-02
  entityOfConcernKindRef: LocalSenseBasisRelation
  basisPublicationUnitRef: E.17.0:4.2,4.6.1-4.6.4
  viewpointRef: FPFCoreReaderViewpoint
  claimGraph:
    supportedSenseClaim: U.Viewpoint names the same P identified under C.2.1 only when P's exact 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-08-02
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-08-02
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 same E only when exact E/P conformance obtains; it never names a 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-08-02
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

The three row epistemes, their UTSRowId designators, external references, selected designations, governed values, NameCards, cells, basis relations, admission-result refs, conformance RelationSignature, and every obtaining relation occurrence remain independently recoverable. If availability for an audience later becomes current, exact E.24.PUB expression, bearing, and publication occurrences must be added outside these rows; file inclusion or this displayed block is not publication.

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. Only when an exact audience and bounded availability use are current should E.24.PUB make the selected row edition available through a distinct form and carrier.

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 accepted F.18 designation pairs for Core citation. Each row names one value already defined or constrained by its subject pattern and uses one FPFCoreReferenceScheme sense cell. Its currentness follows that value and subject-pattern rule, the stable E.10 token classification and allowed-use rule it consumes, its exact NameCard, sense cell, and cited use. A dated corpus audit or candidate-conformance result is not a row dependency. The rows create no assignment, declaration, judgment, description, relation occurrence, predicate truth, structure, Bridge, or publication occurrence.

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: an obtaining direct relation between one exact U.SystemRoleAssignment occurrence and 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 - DPF Suite Reference public row

This row projects the current F.18 settlement for the product form already governed by E.11.DSG. The governed kind remains the relation-defined product form, not a newly minted root kind. The row makes the name reusable under FPFCoreReferenceScheme; it is neither the Reference product nor the operation that publishes one.

UTSRowId: UTS.DPFSuiteReference.FPFCore.2026-08-28
ReferenceScheme: FPFCoreReferenceScheme
UnificationThreadId: DPFSuiteReferenceNaming.2026-08-28
Block: DPF Suite public reference product form
GovernedValueRef: E.11.DSG DPF Suite Reference product form
GovernedValueKindRef: U.Kind
SubjectPatternLocator: E.11.DSG
UnifiedTechName: DPFSuiteReference
UnifiedPlainName: DPF Suite Reference
NameCardRef: NC-DPF-SUITE-REFERENCE
SenseCellRefs: SenseCell.DPFSuiteReference.FPFCore.2026-08-28
BridgeRefs: none
RowRationale: both designations name the editioned non-framework product form that starts from a cross-DPF working question, returns a bounded answer or blocker, and points back to the Suite collection, product series, editions, results, states, and sources that change the answer; maintenance is a separate claim
AdmissibleUse: Core-facing designation of the E.11.DSG product form and readable title component for one exact continuing DPF Suite Reference series or admitted edition
BlockedUse: no Suite, product series, edition, admission, Suite inclusion, currentness, availability, source authority, answer, lookup Work, framework status, instructional Guide, or publication occurrence follows from this row
LineageEntries: DPF Suite Guide is the predecessor Plain designation only; DSG remains stable PatternID lineage residue and is not a current public expansion; no DSR or synonym family is admitted
RowEditionId: 2026-08-28
CurrentnessCondition: reopen when the E.11.DSG product function, boundary, or identity rule; the exact NameCard; FPFCoreReferenceScheme or sense cell; the selected public use; or repeated reader classification changes

SenseCell.DPFSuiteReference.FPFCore.2026-08-28:
  ReferenceScheme: FPFCoreReferenceScheme
  LocalSenseId: DPFSuiteReference-core
  LocalExpression: DPFSuiteReference
  LocalSenseClaim: the E.11.DSG relation-defined product form for an editioned non-framework publication that answers bounded cross-DPF questions, returns sources and honest gaps, and leaves Suite constitution, product-series and edition identity, lookup Work, publication, availability, authority, currentness, and any maintenance claim to their direct rules
  NameCardRef: NC-DPF-SUITE-REFERENCE

A product-specific title may qualify the Plain designation, for example Engineering DPF Suite Reference. That use still needs the exact product-series or edition claim; this row supplies only the shared product-form designation.