E.24:4.3 - Check 3: Direct Relation and Declaration Test
An ontic-introduction decision identifies each direct relation needed by the selected use before it introduces reusable SlotSpecs in a separate RelationSignature episteme. It singles out one identity-bearing relation only when the subject pattern does.
Choose the branch with three observable thresholds before opening the ontology object map:
- Direct use closes the case when one readable claim under current subject patterns gives the named receiving use what it needs. Point to that claim and stop; do not add a coordination episteme or ontic.
- A bounded local episteme is needed when one named receiving use must read several already governed claims together, but no other current pattern relies on their package as reusable ontology. Identify that one episteme under C.2.1 and keep every governed object under its direct pattern.
- A durable ontic is needed only when multiple current patterns must reuse the same independently identified ontology unit and would otherwise duplicate or disagree about its identity or constitution and minimal relation set.
If none of the three thresholds can yet be demonstrated, record an unresolved stop. Source provenance remains the separate source-use status under E.24:4.0 and can accompany any of the three resolved branches.
Use this short card to keep the effort of first use low. State the recognizable situation, the use that must close, and the exact subject; run the three thresholds; then fill ontologyDispositionResult last. Work and decision are examples of receiving use, alongside comparison, preservation, teaching, publication, and reference use.
Treat a filled card as the decision episteme only when its claim content, fixed pre-judgment decisionEntityOfConcern, and effective ReferenceScheme are recoverable under C.2.1. The branch payload is a result about that candidate, not the candidate’s replacement. If the result later changes, identify the changed ClaimGraph as another decision episteme and state any edition continuity separately.
A working phrase, topic cluster, draft heading, or list is not that subject. If no candidate entity, proposal episteme, or source construct is independently recoverable, the card remains an inquiry prompt.
OnticIntroductionFirstUse:
currentSituation: one recognizable sentence naming the current claim or source expression.
receivingUse: the exact comparison, preservation, teaching, publication, reference, work, decision, or other use that must close.
decisionEntityOfConcern: one independently identified pre-judgment candidate entity, proposal episteme, or source-construct entity; it stays fixed across the branch result.
decisionEntityOfConcernGovernor: the direct rule that identifies that candidate before judgment.
branchThresholdResult:
directUseCloses: yes or no; the one readable claim and current pattern that close the receiving use.
boundedCoordinationNeeded: yes or no; the several governed claims that must be read together for this use, plus confirmation that no current pattern relies on their package as ontology.
durableReuseNeeded: yes or no; the multiple current patterns that must reuse one ontology unit and the identity, constitution, or relation-set disagreement that would otherwise recur.
ontologyDispositionResult:
disposition: fill last from those thresholds: subject-pattern-use | bounded-local-episteme | durable-ontic | unresolved-stop.
directUseResult?: exact closing assertion and direct pattern locators.
boundedEpistemeResult?: exact bounded episteme, its declared use, and stop.
durableOnticResult?: exact ontic-settlement result, selected ontic, and subject-pattern locator.
unresolvedResult?: exact unresolved reason and the missing evidence or rule.
sourceUseStatusIfCurrent?: quote-only | reduced use | selected stronger source use; omit when no source-use claim is current and keep exact provenance when it is.
blockedLocalOverread?: only an independently grounded plausible overread whose correction changes the receiving use, under F.19:4.
Every candidate receives one truthful branch result. Ordinary direct, bounded, and unresolved cases stop at this card: direct use needs only its current closing assertion, and bounded use adds only the C.2.1 coordination required by that use. Omit source, publication, view, representation, Work, U-kind, and other neighboring-object fields when no such claim is current; absence is enough and needs no blank or not current value.
E.24:4.3a - Authoritative Typed Object Map
Open only the rows whose selection question is true for the chosen branch. Later sections refer back to this map.
| Object class | Selection question | Record by value and subject pattern |
|---|---|---|
| World-side participant | Does an obtaining predicate require this actual object in one participant meaning? | actual object and its independent identity rule, participant meaning, any kind condition required by the predicate, and the direct relation pattern; a SlotSpec or designation is not the participant |
| Relation occurrence | Is the current claim that one direct predicate obtains among actual participants? | relation kind, participants, obtaining condition, occurrence identity, and direct governor; use this row for the one readable claim that closes direct use |
| Reusable declaration | Does another use need the same participant typing without asserting an occurrence? | RelationSignature episteme and only the reused SlotSpec = <SlotKind, ValueKind, refMode> declarations under A.6.5 |
| Claim-bearing episteme | Does the receiving use need an assertion, description, decision, or several governed claims read together? | C.2.1 identity, exact EntityOfConcern, ClaimGraph, effective ReferenceScheme, declared use, and stop; a bounded episteme governs no new ontology |
| Durable ontology unit | Must multiple current patterns reuse one independently identified unit or otherwise duplicate or disagree about identity, constitution, or the minimal relation set? | ontology-unit individual, primary subject kind, identity or constitution rule, minimal relation set and governors, governing ontic pattern, E.24.UK result when current, and dependent reliance |
| Publication object | Is availability of one selected episteme to an audience current? | under E.24.PUB/E.17, distinguish E, audience and use declarations, exact expression X, carrier C and the obtaining publication occurrence; reusable form F and its conformance apply when selected; keep broader availability at its actual quantified granularity |
| View | Does one identified episteme conform to an exact viewpoint for the receiving use? | E.17.0 conformance for the same episteme as U.View; A.6.3 construction only when that history is current; viewpoint use does not change episteme identity |
| Representation | Does a modeling or reasoning use need a correspondence? | recover the representation, its elements, operative conventions and correspondence to the independently identified subject; A.6.3.RT and A.6.3.RT.OE govern expression construction, with C.29 additionally governing a mathematical lens and inference |
| Source expression | Does source wording or provenance change what use is authorized? | exact expression, source episteme, current source publication occurrence when relevant, carried content, source-use status, admissible use, and smallest stronger-use condition |
| Dependent-pattern reliance | Does another current pattern consume this accepted result? | that pattern and the exact ontic identity, direct relation rule, or reusable declaration it relies on; do not copy the rule |
Before opening the full OnticIntroductionDecision form, run two checks.
First, state the subject’s identity, constitution, or recognition rule and the smallest relation set the named dependent use needs. For every included direct relation, write one readable sentence naming its participants and predicate; mark it identity-bearing only when its subject pattern does. Only then declare SlotKind, ValueKind, and refMode under A.6.5 for a relation whose typed reuse is current; when refMode is a RefKind, name that declared RefKind.
Second, treat bare role as an E.10.ROLE trigger and ask only whether the current ontic decision has confused a world-side participant, a local system-role kind and its A.2/C.3.2 classification, an exact A.2.1 assignment occurrence, or a declaration-local participant meaning in an A.6.5 reusable declaration. Keep the participant under its direct subject pattern and use F.6 only when Work attribution is current. E.24 does not reconstruct any assignment signature or occurrence rule, and bare role supplies no common head for these objects.
When an encountered card, table, schema, diagram, or record is current, apply the selection question in E.24:4.3a to each proposed use. Visible shape and field co-occurrence identify no episteme, publication object, representation, relation kind, or obtaining occurrence. Only an identified U.System performs description, rendering, or publication work.
Introducing an ontic organizes kinds, direct relation rules, declarations, and named dependent-pattern reliance in FPF. It does not create or individuate any project-side relation occurrence. For each such occurrence, apply the direct predicate and domain identity rule under A.6.REL. A designator may designate the already reidentified occurrence; a governed reference may resolve to it; an assertion or description episteme may carry a claim and designation about it. A publication occurrence instead makes one selected episteme edition available and neither designates nor creates the world-side occurrence.
Worked durable-branch replay:
Use this replay only after the first-use thresholds select a durable ontic. Its pre-judgment subject is EpistemeOnticProposal_v1, identified under C.2.1 by EpistemeOnticProposalClaims_v1 about source construct E24-Episteme-Ontic-Candidate-v1 under FPF-Ontic-Proposal-Scheme-2026; it exists before and is not identical to the selected EpistemeOntic.
The replay applies the object map to a pump-maintenance specification. C.2.1 selects an identity-bearing constitution relation for the Episteme ontic; the named project triple is one witness. Other ontics use their own identity rule and need not imitate this relation shape.
OnticIntroductionDecisionReplay:
primaryGovernedSubjectKind: `U.Episteme`.
receivingUse: FPF authors compare and maintain dependent episteme patterns against one shared identity and relation set; maintenance engineers then apply those rules to the PumpStation37 specification while its grounding, views, evidence, editions, and publications change.
decisionEpistemeIdentity:
claimGraph: `PumpMaintenanceOnticDecisionClaims_v1`.
entityOfConcern: `EpistemeOnticProposal_v1`; this fixed proposal episteme is not the selected ontic.
effectiveReferenceScheme: `FPF-Ontic-Decision-Scheme-2026`.
ontologyDispositionResult:
disposition: durable-ontic.
durableOnticResult: `E24-OS-EPISTEME-ONTIC-02`, selecting `EpistemeOntic` under E.24.
e24FamilySettlement:
decisionMode: ontic-only.
existingUKindAdmissionResultRef: `E24UK-AR-UEPISTEME-RG-01`.
onticSettlementResultRef: `E24-OS-EPISTEME-ONTIC-02`.
atomicCoDecisionRef: none; no new public U-kind is proposed in this replay.
onticRootIfSelected: `EpistemeOntic`, one designated ontology-unit individual of kind `U.Ontic`. Its identity includes the primary subject kind `U.Episteme`, the exact C.2.1 constitution rule and the minimal relation set below, including each relation's participant meanings, obtaining predicate and occurrence-identity rule. `EpistemeConstitutionRelation` is the selected identity-bearing direct relation. The ontology unit, the kind and each PumpStation37 episteme have their respective identities.
identityBearingDirectRelationIfSelected: `EpistemeConstitutionRelation`, governed by C.2.1. Its participants are the complete semantic claim content, one independently identified EntityOfConcern, and the effective designation and interpretation rules. C.2.1:4.1.1 recovers and compares the two epistemic constituents; the subject pattern identifies the entity. The relation obtains when the scheme makes that content interpretable and evaluable as claims about the entity and the three participants form one claim-bearing whole; their triple identifies the occurrence. The PumpStation37 witness uses the exact content `MaintenanceClaims_v7`, entity `PumpStation37`, and effective rules `StationMaintenanceReferenceScheme_2026`. Those labels require the corresponding content, entity identity, and rules; they are not a classification test for all claim contents or schemes. That project occurrence neither is nor identifies `EpistemeOntic`.
reusableDeclarationsIfNeeded: C.2.1:4.2.1 supplies the constitution declaration for reusable EntityOfConcern designation with `EntityOfConcernSlot`, `U.Entity` and `U.EntityRef`; :4.3 and :4.5 supply grounding and edition declarations. For typed replacement of constituents, :4.1.2 supplies `NonemptyClaimContent` and `EpistemeInterpretationScheme`, with complete A.6.5 SlotSpecs supplied by the receiving declaration. Those bounded ranges establish neither general `U.ClaimGraph` nor `U.ReferenceScheme` admission. E.24.PUB supplies exact publication and supporting declarations when that typed interface is needed.
minimalGovernedRelationSet:
instanceLayer: `EpistemeConstitutionRelation` relates actual claim content G, EntityOfConcern T and effective interpretation R and is identity-bearing; `EpistemeEmpiricalGroundingRelation` connects designated empirical claims with mappings involving the grounding holon; `EpistemeEditionRelation` supplies source-based continuity between distinct epistemes; `EpistemeViewpointConformanceRelation` supplies exact E/P conformance; `EpistemePublicationRelation` supplies exact E/A/U/X/C availability through expression and bearing. C.2.1, E.17.0 and E.24.PUB govern those predicates and identities. E.24.PUB also supplies conditional form conformance, form-mediated claims and broader availability. A.6.3 construction and A.10 evidence use join under their own current governors.
ontologyDeclarationLayer: this decision episteme says that `EpistemeOntic` coordinates the `U.Episteme` identity rule and those exact relation rules and declarations for the named dependent patterns. It asserts no world-side relation whose participants are `EpistemeOntic`, `U.Episteme`, a relation kind, a signature, or a pattern.
claimBearingEpistemesIfNeeded: the independently identified `EpistemeOnticProposal_v1` remains the decision's EntityOfConcern. The PumpStation37 episteme and its constitution occurrence are separate consuming witnesses; a separate assertion about that occurrence is added only when that claim is current.
viewIfNeeded: exact maintenance episteme E is the same individual as a `U.View` only when E.17.0 conformance to exact maintenance viewpoint P obtains; any source episteme and A.6.3 construction remain separate.
representationIfNeeded: a wiring diagram has identified elements, interpretation and correspondence to independently recovered objects; use A.6.3.RT/A.6.3.RT.OE for expression construction and C.29 when mathematical inference or transfer is required.
publicationOccurrenceIfNeeded: if the specification is available to the maintenance team for scheduled repair work, identify E, audience declaration A, bounded-use declaration U, particular expression X and carrier C under E.24.PUB. The five participants and maximal continuous interval identify the exact publication; a broader availability claim retains its permitted alternative expressions and carriers.
publicationFormIfNeeded: name reusable form F and establish `PublicationFormConformanceRelation(X,F)` when the use depends on its rules. For form-mediated availability, the same X must express the required E content, conform to F and be recoverable from C.
presentationCarrierIfNeeded: independently identify the actual physical or digital entity C as a `U.Entity`, state its file-object, snapshot-value or copy-token identity as appropriate, and establish `PublicationExpressionBearingRelation(C,X)` through its relevant state or realization.
dependentPatterns: C.2.1 grounding and edition uses rely on the shared episteme identity and their own exact relations; `E.17.0` relies on that identity for E/P conformance; `E.24.PUB` relies on it to identify E, A and U while expression and carrier continuity follow their own predicates. `A.6.3` relies on independently identified source and receiving epistemes when viewing construction is current. Each use returns to its direct rule.
blockedLocalOverread: grounding holon, viewpoint, view, evidence, edition work, publication occurrence, form, carrier, and representation are not extra participants of `EpistemeConstitutionRelation`.
Record a branch result for each candidate, but ordinary direct, bounded, and unresolved cases stop at the one-screen card. Open the full form only when dependent patterns will rely on a proposed durable ontic, the current claim changes admissible use, or a receiving use needs a replayable reason why bounded C.2.1 coordination was insufficient. The durable branch meets the first condition: multiple current patterns must rely on it.
You can use the following form to publish one claim-bearing ontic-introduction decision episteme. When a guard above opens it, include only rows activated by the selected branch and receiving use. Omit every inactive neighboring-object or assurance row; the labels are prompts, not fields that must be filled, and they are not world-side participants, SlotSpecs, or components of the selected ontic.
OnticIntroductionDecision:
OntologyDispositionResult:
Disposition: fill last from the existing-governor, identity, connectivity-or-constitution, dependent-use, and non-duplication evidence; durable-ontic | bounded-local-episteme | subject-pattern-use | unresolved-stop.
DirectUseResultIfSelected: exact closing assertion and direct pattern locators; detailed governed object below.
BoundedEpistemeResultIfSelected: exact bounded-episteme reference, declared use, and stop; identity details below.
DurableOnticResultIfSelected: exact OnticSettlementResult, selected ontic, and ontic subject-pattern locator; settlement details below.
UnresolvedResultIfSelected: exact unresolved reason and missing evidence or rule.
SourceUseStatusIfCurrent: quote-only | reduced use | selected stronger source use; omit when source use is not current.
WorkingSubjectExpressionIfCurrent: wording that opened a source-driven inquiry; never used as an EntityOfConcern without independent identification.
SourceExpressionUseIfCurrent:
ExactSourceExpression:
SourceEpistemeIfRecoverable:
SourcePublicationOccurrenceIfCurrent:
RecoveredEntitiesRelationsAndClaims:
CurrentAdmissibleUse:
StrongerUseCondition:
WordingUseRestorationCoordinatesIfE10ARCHOpenedTheCase:
SemanticAreaBaseConcept:
SemanticArea:
SemanticAreaSenseFamily:
OntologicalNeighborhood:
DecisionEpistemeIdentity:
ClaimGraph:
EntityOfConcern: one independently identified pre-judgment candidate entity, proposal episteme, or source-construct entity; never a result selected by the branch.
EntityOfConcernIdentityGovernor:
EffectiveReferenceScheme:
DirectGovernedObjectIfSelected:
BoundedLocalEpistemeIfSelected:
EpistemeIdentity:
EntityOfConcern:
ClaimGraph:
EffectiveReferenceScheme:
DeclaredBoundedUseAndStop:
SelectedOnticNameIfAny:
PrimaryGovernedSubjectKind:
ReceivingUse: exact comparison, preservation, teaching, publication, reference, work, decision, or other use and how absent coordination changes it.
SelectedOnticIfDurableDisposition:
StableIdentityCriterion:
IdentityOrConstitutionRule:
DirectGoverningPattern:
E24FamilySettlement:
DecisionMode: ontic-only | U-kind-only | atomic ontic-plus-U-kind.
SharedCandidateInputsRef: exact CandidateInputs block governed by E.24:4.0a.
ExistingAcceptedOnticOrUKindResultRefsIfReused:
AtomicCoDecisionRefIfBothNew?:
OnticSettlementResultRefIfAny?:
UKindAdmissionResultRefIfAny?:
UKindOutputIfCurrent:
SharedDecisionRef: exact `E24FamilySettlementDecision` governed only by E.24:4.0a; do not fill another E.24.UK decision form.
DecisionMode: U-kind-only | atomic ontic-plus-U-kind.
ExistingAcceptedOnticSettlementRefIfReused?: cite only an accepted ontic settlement actually consumed by the shared decision. For U-kind-only with no additional durable ontic needed, retain the shared direct-use or bounded-local-episteme result in OntologyDispositionResult above and omit this reference; no new OnticSettlementResult is required.
UKindAdmissionResultRef: exact `UKindAdmissionResult` output.
AdmissionDisposition: exactly one value from E.24.UK's closed set: root | same-individual-dependent | identity-dependent | reuse | local-kind | reject.
BranchSpecificResultRefIfRequired: the exact membership, dependence, reused-kind, local-declaration, or recovered-object result required by that disposition.
LocalGainCostAndDuplicateOntologyRisk: the decision-changing rationale; not another disposition or decision form.
MinimalGovernedRelationSet:
InstanceLayer: for every included direct relation, its actual participants and independent identity rules, participant meanings, required kind conditions, predicate, occurrence identity, direct governor, and named receiving use.
OntologyDeclarationLayer: the exact decision claims that include each kind, relation rule, declaration, or pattern and state each dependent reliance; an actual declaration-side relation is named only when independently governed.
IdentityBearingDirectRelationIfSelected:
DirectRelationKind:
DirectGoverningPattern:
ParticipantMeanings:
ParticipantIdentificationRules:
KindConditionsRequiredByPredicate:
ObtainingCondition:
OccurrenceIdentityRule:
RelationSignatureIfNeeded:
SlotSpecs:
DependentKindsIfAny:
NeighboringGovernedEntitiesOutsideSelectedRelationSet:
ClaimBearingEpistemesIfNeeded:
ViewsIfNeeded:
RepresentationsIfNeeded:
PublicationUsesIfNeeded:
PublicationOccurrence:
SelectedEpistemeEdition:
DeclaredAudienceAndBoundedUse:
PublicationForm:
PresentationCarrier:
GoverningPatterns:
OnticGoverningPatternIfSelected:
SubjectKindIdentityAndRelationPatterns:
NeighboringDirectRelationPatterns:
DirectUsePatternsBeforeNewOntic:
ExistingGoverningPatternsReused:
DependentPatternReliance: for each named dependent pattern, the exact ontic identity, direct relation rule, or RelationSignature declaration relied on.
RelationLabelsThatAreNotNewKinds:
NonUseBoundary:
An ontic-settlement result does not by itself admit a public U.* kind; that requires the shared decision’s separate UKindAdmissionResult. Record a one-screen branch result for every candidate; complete the full form only when one of its three guards is true, and then only by the rows that guard, branch, and receiving use activate.
When typed reuse needs a declaration of one selected direct relation, its RelationSignature uses A.6.5 and the E.24 decision defines no second slot discipline; the direct relation retains its exact predicate and defining ClaimGraph. A SlotKind names one participant meaning only inside the selected RelationSignature, and its ValueKind constrains the admitted kind of the actual participant corresponding to that SlotSpec. Neither the SlotKind label nor its wording decides that kind; an exact participant-kind assertion does.