E.24:4.3a - Authoritative Typed Object Map
Open only rows whose selection question is true for the chosen branch. Later sections point here instead of repeating the inventory.
| 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, admitted kind, participant meaning, 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 edition to an audience current? | under E.24.PUB/E.17, distinguish the publication occurrence, selected edition, audience and use, form that expresses it, and carrier that bears the form |
| 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 declared modeling or reasoning use need an explicit correspondence? | C.29 representation, its elements, effective representation scheme, and explicit correspondence to an independently identified object; representation does not change that object’s identity |
| 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 guards. 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:
The detailed replay below is opened 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 actually 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-01`, selecting `EpistemeOntic` under E.24.
e24FamilySettlement:
decisionMode: ontic-only.
existingUKindAdmissionResultRef: `E24UK-AR-UEPISTEME-RG-01`.
onticSettlementResultRef: `E24-OS-EPISTEME-ONTIC-01`.
atomicCoDecisionRef: none; no new public U-kind is proposed in this replay.
onticRootIfSelected: `EpistemeOntic`, one explicitly designated ontology-unit individual of kind `U.Ontic`. E.24 reidentifies it from the primary governed subject kind `U.Episteme` and the identity-bearing direct relation kind `EpistemeConstitutionRelation`, including that relation's predicate, participant meanings, and admitted actual-participant kinds. It is neither the `U.Episteme` kind nor any PumpStation37 episteme.
identityBearingDirectRelationIfSelected: `EpistemeConstitutionRelation`, governed by C.2.1. Its participant meanings are constitutive claim content, exact EntityOfConcern, and effective reference scheme; its admitted actual-participant kinds are `U.ClaimGraph`, `U.Entity`, and `U.ReferenceScheme`. It obtains when the scheme makes the claim graph interpretable and evaluable as claims about the exact entity and the three participants form one claim-bearing whole; the participant triple identifies the occurrence. The PumpStation37 consuming witness is the distinct occurrence among `MaintenanceClaims_v7`, `PumpStation37`, and `StationMaintenanceReferenceScheme_2026`; that project occurrence neither is nor identifies `EpistemeOntic`.
reusableDeclarationsIfNeeded: `EpistemeConstitutionRelationSignature` with the three SlotSpecs declared in `C.2.1`, only where another pattern needs reusable participant typing.
minimalGovernedRelationSet:
instanceLayer: `EpistemeConstitutionRelation` among actual claim graph, EntityOfConcern, and reference scheme is identity-bearing; `EpistemeEmpiricalGroundingRelation`, `EpistemeEditionRelation`, `EpistemeViewpointConformanceRelation`, and `EpistemePublicationRelation` retain the actual participants and predicates supplied by C.2.1, E.17.0, and E.24.PUB when their named use is current. A.6.3 construction and A.10 evidence use remain separate and join only 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 representation remains under C.29 and corresponds to independently recovered objects.
publicationOccurrenceIfNeeded: if the specification edition is made available to the maintenance team for scheduled repair work, name that selected edition, audience, bounded use, and publication occurrence.
publicationFormIfNeeded: name the form that expresses the selected edition for that use.
presentationCarrierIfNeeded: name the identified paper sheet, file, display, or other `U.PresentationCarrier` that bears the form.
dependentPatterns: `E.17.0` relies on the same C.2.1 episteme identity plus exact viewpoint conformance when the specification is admitted as a `U.View`; `A.6.3` relies on the independently identified source and receiving epistemes only when viewing construction is current. Neither pattern copies the constitution rule.
blockedLocalOverread: grounding holon, viewpoint, view, evidence, edition work, publication occurrence, form, carrier, and representation are not extra participants of `EpistemeConstitutionRelation`.
The full replay form is heavier:
Every candidate gets a truthful branch result, 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. A durable branch is load-bearing because its threshold already requires reuse by multiple current patterns.
The following fuller code block is an optional publication form for 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 participant meanings and kinds, predicate, occurrence identity, direct governor, and the named use it enables.
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:
AdmittedActualParticipantKinds:
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:
No candidate inherits a U.* decision from E.24. Give every candidate a truthful one-screen branch result; 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.