#U.Ontic and Ontic Introduction Discipline

E.24 · Stable · Part E FPF authoring discipline pattern · Normative unless a section is explicitly informative · Part E - The FPF Constitution and Authoring Guides

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Part E FPF authoring discipline pattern Status: Stable Normativity: Normative unless a section is explicitly informative

Use this pattern when FPF work appears to need a durable ontic: a connected action-facing ontology unit whose stable identity and admissible uses depend on keeping several direct relation kinds, their relation-participant meanings and admitted actual-participant kinds, reusable declarations, and neighboring governing patterns coherent.

#Relations

#Content

#Use This When

Use this pattern when FPF work appears to need a durable ontic: a connected action-facing ontology unit whose stable identity and admissible uses depend on keeping several direct relation kinds, their relation-participant meanings and admitted actual-participant kinds, reusable declarations, and neighboring governing patterns coherent.

On first reading, expect two outputs rather than guessing a branch. First characterize the current candidate or source claim and run the existing-governor, identity, relation-or-constitution, dependent-use, and non-duplication tests below. Only then record the ontology disposition: introduce a durable ontic, coordinate already governed claims in a bounded local episteme, rely directly on current governing patterns, or stop unresolved. Record the source-use status independently: not current, quote-only, reduced use, or a selected stronger source use with its exact provenance. Source-use status can accompany any resolved ontology disposition; it is not a fourth ontology branch. Use source-only as a stop only when no governed payload has been selected.

A durable ontic is a reusable ontology unit whose governing pattern states its identity rule and minimal governed relation set for dependent FPF use. A bounded local episteme is a claim-bearing U.Episteme that coordinates already governed entities and relations for one named use. Direct governing-pattern use relies on those existing patterns without adding another ontology unit. An unresolved stop retains the inquiry without pretending that one of those three payload dispositions has been selected.

Typical, non-exhaustive working situations include:

• a bounded local episteme starts being cited as though it were a new ontology unit;
• a source expression or project-side expression keeps pointing to several FPF values at once;
• a draft ToC row names a calculus or object family, but no current pattern carries its governing meaning;
• a subject pattern begins to carry local slot-relation doctrine that other patterns also need;
• a proposed subject needs one stable identity, constitution, or recognition rule plus the smallest set of governed relations that dependent use must keep coherent.

Primary EntityOfConcern. The pattern governs U.Ontic, the durable action-facing ontology unit. Each particular ontic-introduction decision episteme still needs one exact EntityOfConcern selected by its ontology disposition: the selected ontic, the exact object handled by direct governing patterns, one independently governed object that every bounded-episteme claim concerns, or—at an unresolved stop—the exact source episteme or expression entity whose inquiry remains open. The source-use status does not change that EntityOfConcern. The decision episteme describes and justifies the choices; it is not part of U.Ontic, and an unresolved phrase or topic list cannot be its EntityOfConcern.

Primary working reader. The first reader is an FPF pattern author or reviewer deciding whether several nearby patterns are describing one ontic, several existing governed values, or only a compressed source expression. The downstream reader is the practitioner who needs the resulting subject pattern to say what can be done, claimed, relied on, repaired, compared, or stopped.

Working concern and viewpoint. From the FPF-authoring viewpoint, preserve the subject's governing relations without duplicating kinds or promoting a claim-bearing episteme for one named use into durable ontology.

First useful move. State the working expression or current claim, recover its exact EntityOfConcern and named receiving use, and record source provenance when current. Then run Checks 1–4: reuse existing governors, test exact identity, recover the needed direct relations or constitution, and test dependent reuse without duplicate ontology. Fill the ontology disposition only from those results. If neither a governed payload nor an exact source episteme or expression entity is identifiable, keep only inquiry material and do not fabricate a decision episteme.

What goes wrong if missed. FPF grows shadow ontology. The same project concern becomes a method in one place, a mechanism in another, a record in a third, and a local checklist in a fourth. Later uses then repair visible symptoms instead of settling the underlying kind, slot, and governing-pattern question.

What this buys. A durable ontic gets an explicit identity plus named direct relation kinds, participant meanings, obtaining conditions, and occurrence-identity rules. RelationSignature and SlotSpec declarations are added only where dependent uses need reusable participant typing. Otherwise, state the coordination in a bounded local episteme whose ClaimGraph cites the direct entities, relations, and governing patterns already carrying the work.

Main gains:

• it prevents duplicate ontology by recovering the direct entities and relations first, then reusing their governing patterns;
• it replaces negative catalogues with positive relation discipline: state the direct relation kind, relation-participant meanings, admitted actual-participant kinds, obtaining condition, and occurrence-identity rule; add RelationSignature and SlotSpec declarations only when a receiving use needs reusable typing;
• it gives dependent patterns one stable durable ontic and one governing pattern to cite without copying direct relation rules or reusable SlotSpecs;
• it keeps each current world-side participant, relation occurrence, reusable declaration, claim-bearing episteme, publication object, view or representation, and source expression under its direct owner; E.24:4.3a is the single typed object map;
• it makes wording follow the one mapped object selected by the current claim instead of repeating the surrounding inventory.

Not this pattern when.

• If one existing governing pattern already carries the claim, use that pattern directly.
• If the issue is only one wording-use repair row, use E.10 and E.10.ARCH.
• If the issue is only a new or revised mechanism meaning, use E.20.
• If the issue is only durable naming, use F.18.
• If the issue is only a pattern publication-form or section-order matter, use E.8.

#Problem Frame

Some FPF governed objects are small enough to define through one direct relation pattern. Others become candidates for a durable ontic when several direct relations and governing patterns need persistent coordination across dependent use. U.Episteme is the central example: correct reuse depends on keeping its identity, components, direct relations, dependent same-individual episteme kinds, descriptions, and publication-side relations coherent without treating a card field, RelationSignature, or C.29 representation as the episteme itself.

The same failure recurs elsewhere. A project label such as algorithm, process, model, architecture, service, quality, time, rhythm, change, or source can point to several FPF objects. Choosing a better word does not recover those objects. Introducing one umbrella kind fuses entities and relations that already have direct governing patterns. E.24 governs the decision whether a durable ontology unit is needed and the declaration of the direct relations that make it useful.

#Problem

Without this discipline:

1. Local epistemes become pseudo-ontics. A repeated claim-bearing episteme or reusable publication form starts to be cited as a new ontology unit even though its claims or layout only refer to existing governed values.
2. Draft ToC rows become false authorities. A planned ToC row is cited as if it already supplied current governing text.
3. Pattern placement is mistaken for ontology. A numbering or placement label becomes the proposed ontic even though no primary governed subject kind, exact identity or constitution rule, minimal governed relation set, or governing pattern is named.
4. Reusable SlotSpecs are copied without a direct relation. Several patterns list similar SlotSpecs, but no direct pattern states the relation kind, participant meanings, obtaining condition, or occurrence identity.
5. Existing typed values are duplicated. A new head repeats U.Method, U.Mechanism, U.WorkPlan, U.Work, evidence, gate, source, or result relations under a new name.

#Forces

#Solution

E.24 governs U.Ontic as the FPF kind for a connected action-facing ontology unit. Before dependent patterns rely on that unit, the accepted ontic-introduction decision states its primary governed subject kind, exact identity, constitution, or recognition rule, the smallest independently governed relation set needed by dependent use, any identity-bearing direct relation actually selected by the subject's direct owner, any reusable RelationSignature declarations, governing patterns, named dependent-pattern reliance, and non-use boundary.

Connected is an admission condition here, not a metaphor. The decision names the smallest set of independently governed relations that makes the subject usable across the named dependent patterns and states why each relation belongs. When the subject's direct owner selects one identity-bearing direct relation, say so; otherwise do not invent a head relation. Action-facing means that the decision names a receiving use whose outcome changes when that coordination is absent—for example comparison, preservation, teaching, publication, reference, work, or decision use. Topic adjacency and a shared label satisfy neither condition.

Keep two layers explicit:

1. Instance layer. For each included direct relation kind, name the actual participant meanings and admitted actual-participant kinds supplied by its direct owner. An obtaining occurrence relates those actual participants; it does not relate their kinds, the relation kind, a pattern, a RelationSignature, or the ontology unit.
2. Ontology and declaration layer. The ontic-introduction decision episteme states which subject kind, identity rule, relation kinds, declaration epistemes, governing patterns, and dependent-pattern reliance claims belong in this ontology unit. Those are typed claims in the decision episteme unless an independently governed declaration-dependency, governance, inclusion, or reliance relation is actually current. Do not call them world-side direct relations merely because the ontology unit coordinates them.

The ontology unit is connected when every included relation kind has its instance-layer participants and direct governor, every included declaration is tied to the relation use it declares, and every dependent pattern names the exact identity rule, direct relation rule, or declaration it relies on. The decision marks any identity-bearing edge explicitly. This typed account establishes ontology-level coordination; it fabricates no relation occurrence among kinds, declarations, patterns, or the ontic.

Named dependent-pattern reliance states each dependent pattern and the identified ontic identity, direct relation rule, or RelationSignature declaration on which it relies. A dependent pattern name without that reliance basis is insufficient.

Reidentify one U.Ontic by its primary governed subject kind, the exact identity, constitution, or recognition rule supplied by the subject's direct owner, and the minimal governed relation set selected for dependent use. Include an identity-bearing direct relation only when that owner selects one. Only a change to the subject kind, identity rule, or relation set consumed by a named dependent pattern can reopen ontic identity; a change in how the subject is described, published, viewed, represented, or named does not. Use the typed object map in E.24:4.3a for those neighboring objects.

Keep the subject under decision separate from every means of stating, presenting, or inspecting it. Open a neighboring row in E.24:4.3a only when that object's identity or direct relation changes the current choice or receiving use. A decision or description remains a C.2.1 episteme; availability, viewpoint conformance, and mathematical correspondence do not alter the subject's identity.

Keep the direct verbs with their owners: a designator designates, a governed reference resolves, an episteme carries claims, a publication occurrence makes one edition available, a publication form expresses it for that use, and a carrier bears the form. The typed map supplies the governing pattern and stop for each current object; visible co-occurrence on a card supplies none of them.

When a durable ontic is selected, its branch of the ontic-introduction decision states at least:

• the primary governed subject kind and the named receiving use—such as comparison, preservation, teaching, publication, reference, work, or decision use—for which coherent identity and relation rules matter;
• the exact identity, constitution, or recognition rule supplied by the subject's direct governing pattern;
• the smallest set of independently governed direct relations needed by named dependent use, with the practical use each relation enables;
• one identity-bearing direct relation only when the subject's direct owner selects it and states its participants, predicate, and occurrence identity;
• any RelationSignature epistemes used to declare reusable SlotSpecs for relation-participant meanings actually reused;
• the current FPF patterns that govern the subject kind, identity rule, and selected direct relations;
• the pattern that governs the durable ontic;
• the named dependent-pattern reliance: each dependent pattern and the identified ontic identity, direct relation rule, or RelationSignature declaration on which it relies without copying that rule or declaration.

A project entity does not fill an ontic. It keeps its own kind and may participate in the ontic's direct relation or in a neighboring direct relation. A SlotSpec belongs to a RelationSignature declaration. An assertion or description episteme may designate the world-side participants by value or reference and claim that the direct predicate obtains. The participant, SlotSpec, designation, assertion, and relation occurrence remain different objects.

FPF ontology is therefore not one flat class list and not a collection of filled records. A durable ontic is one connected ontology unit over a small group of direct kinds and relations, linked at the ontology layer by the typed claims in its decision episteme. At the instance layer, only actual participants enter obtaining direct-relation occurrences. The same project entity may participate in relations governed by several ontics without changing its kind or becoming part of a second ontology.

E.24 carries the accepted decision to use U.Ontic because one ontology unit needs stable identity and one pattern governing the relation rules reused by dependent patterns. Without it, those patterns duplicate or disagree about that shared basis. Every other current object remains under the owner named in E.24:4.3a.

The cost is kernel growth and metamodel risk. Repetition, a reusable layout, or ontology-shaped wording does not make any object a U.Ontic. Admit one only when the decision supplies stable identity, the minimal relation set actually reused across patterns, existing-governor checks, and a non-use boundary.

U-kind admission is a neighboring E.24-family question, not the main body of E.24. Both hosts use the one E24FamilySettlementDecision schema in E.24:4.0a:

• a durable ontic is a connected action-facing ontology unit;
• durable U.* kindhood is admitted only through an accepted UKindAdmissionResult under that shared schema;
• an ontic may coordinate already admitted kinds, and a new kind may reuse an already accepted ontic settlement;
• when the same case needs both a new ontic and a new public U-kind, one atomic co-decision returns a separate OnticSettlementResult and UKindAdmissionResult; neither is evidence for the other inside that decision;
• every non-ontic object keeps the kind, relation, and owner selected by the typed object map.

Use E.24.UK only when a candidate claims durable U-kind force. E.24 consumes its exact accepted result when that result changes the ontic settlement; naming or placement alone supplies neither output.

#Constructive Foundation And Math-Lens Boundary

If a reader asks where an FPF ontic gets constructive grounding, follow the identity or grounding rule named by its direct owner. E.24 records that rule and only the relations needed by dependent use; it does not turn declarations, descriptions, publication objects, views, or representations into grounding participants. Their owners remain in E.24:4.3a.

For structural identity claims, the constructive chain is E.14 -> B.3.5 -> C.13: Working-Model relation first, declared validationMode, tv:groundedBy, and a reconstructible Γ_m.sum, Γ_m.set, or Γ_m.slice trace. The Γ_m trace is the reconstructible grounding object cited through tv:groundedBy under B.3.5. If a graph, tuple, or another mathematical expression represents that trace, the expression is a separate C.29 representation. Neither the trace nor its representation becomes the public relation vocabulary, and this structural grounding apparatus is not required for non-structural ontics.

For a non-structural ontic, use the identity, grounding, or recognition rule named by its direct subject pattern. Open E.24.UK only for U-kind admission, C.2.1 only for an episteme's identity, E.24.PUB only for current availability, and the other rows of E.24:4.3a only when their selection question is true.

A.14, B.2, and A.15.1 carry BORO- and CCO-compatible identity and occurrence discipline. They support the constructive foundation; they do not create a separate durable-kind ontology.

Before a dependent pattern relies on the ontic, classify each current object with E.24:4.3a. The selection question—not a shared label or visual container—decides whether the object is a world-side participant, relation occurrence, reusable declaration, claim-bearing episteme, publication object, view or representation, source expression, or durable ontology unit.

An encountered card illustrates the rule. Its claims, reusable layout, diagram elements, and carrier are separately governed only when their own identity and direct relation are established; the word card identifies none of them and does not make the collection an ontic.

When several current governing patterns already address the same project concern, select an ontic only if one exact identity rule and minimal relation set must be reused across them. Keep every otherwise current object in its E.24:4.3a row; shared topic or proximity cannot fuse their kinds. At the ontology layer, state reliance on relation rules without inventing an occurrence whose participants are the kind, pattern, or ontic.

Build the decision evidence in this order; do not select a disposition first and then backfill reasons:

1. Current case and exact subject. State the working expression or source claim, one exact EntityOfConcern with its direct identity governor, and the named receiving use. Record source-use status and provenance here when current; they do not settle the ontology disposition.
2. Existing-governor reuse and non-duplication. Name the current direct patterns checked by value. State which current claim they already close, or the exact coordination they fail to supply. Reject a new umbrella when it would merely rename those governed objects or copy their rules.
3. Identity, constitution, or recognition. State the exact rule supplied by the subject's direct governing pattern and what would reidentify the subject across the receiving use. Do not replace several required facts with an invented universal relation.
4. Typed connectivity and dependent use. Use E.24:4.3a to classify only the objects that the receiving use consumes. Name each needed direct relation and governor, any identity-bearing relation selected by its owner, each declaration actually reused, and each dependent pattern's exact reliance basis. Omit every neighboring map row whose selection question is false.
5. Disposition and boundary—fill last. From steps 1–4, record direct governing-pattern use, bounded local episteme, durable ontic, or unresolved stop. For a durable ontic, name the ontology-unit individual and its governing pattern; for a bounded episteme, identify it under C.2.1 and state its non-governing use; for direct use, point to the exact closing patterns; for an unresolved stop, state the missing evidence. End with the nearest tempting overread that remains disallowed.

A relation-participant meaning belongs in one selected direct relation only when that relation's predicate depends on an actual participant having that meaning and the direct pattern states the admitted kind of that participant. When typed reuse is needed, a compatible RelationSignature declares that admitted kind as the SlotSpec's ValueKind. Another entity remains under its own direct relation when that relation already expresses the needed use. Reuse pressure can justify a RelationSignature; it cannot turn a neighboring relation, record field, or mathematical operand into a participant or SlotKind of another relation.

Optional-in-use status belongs to a declaration or description. It does not mean that a world-side relation occurrence has an unfilled participant. A missing designation leaves the assertion incomplete or the participant unknown to the current user. It does not show that the participant is absent, and it does not make the direct predicate obtain or cease.

Not every ontic needs every map row. Open one only when its selection question changes the named receiving use; otherwise omit it and keep the object under its direct owner.

Keep annotation proportional. E.24 calls for recovery only where wording can change ontic identity, a direct relation, participant meaning, a reusable SlotSpec declaration, a description claim, admissible use, or the reliance basis of a dependent pattern. If readable domain prose already preserves those objects, do not replace it with declaration syntax merely to show that an ontic exists.

This differs from pure ontology engineering because FPF patterns are action-facing: they help an engineer-manager decide what can be done, claimed, relied on, repaired, compared, or stopped in a problem situation. The accepted ontic-introduction decision supplies the object discipline that makes those actions intelligible. It states which objects and relations the subject pattern's Solution may use, while that subject pattern still carries the practical move, boundary, evidence, and consequence.

Precision restoration uses the same discipline without turning it into lexical style. First recover the source-side entities, direct relations, assertions, descriptions, and governing patterns compressed by the wording. Then repair toward a current FPF ontic only when one accepted ontic-introduction decision states how those objects are coordinated. If no such ontic exists, use the direct governing patterns, state only the needed claims in a bounded local episteme under C.2.1, or open an E.24 ontic-introduction decision.

When a source expression opens the ontic-introduction question, preserve its source-to-use path independently of the ontology disposition. Name the exact expression and its source episteme; name the source publication occurrence when availability through that occurrence matters; recover the entities, relations, and claims actually carried forward; and set the source-use status to quote-only, reduced use, or one selected stronger use with the smallest condition that licenses it. Keep that trace beside a durable-ontic, bounded-episteme, or direct-use disposition whenever both are current. If no governed payload has been selected, mark the ontology disposition unresolved and retain source-only inquiry material rather than treating provenance as an ontology answer. When a stronger-use condition occurs, reopen the source expression through C.2.P or the direct source-use pattern instead of treating the repaired noun as a substitute for the source relation.

When an E.10.ARCH wording-use restoration row opened the case, retain its four coordinates inside that source-to-use trace: semanticAreaBaseConcept is the source cue, semanticArea is the selected Part-F row or bounded row-set, semanticAreaSenseFamily prevents theme-level overgeneralization, and ontologicalNeighborhood is the applicability neighborhood used to recover the subject kind, relations, and governing patterns. These are coordinates of the wording repair under E.8 and E.10.ARCH. They are not components or identity criteria of U.Ontic; a subject discovered directly through engineering work does not need them.

E.24 governs introduction of U.Ontic and describes that decision discipline. Under self-application, the ontology unit, its identity rule, every selected direct relation, each RelationSignature, claim-bearing episteme, publication occurrence, publication form, presentation carrier, view, and representation remain distinct; E.24 does not license every local ontology-shaped bundle as a U.* kind.

#Shared E.24-Family Settlement and Atomic Co-decision

E.24 and E.24.UK use this one schema without weakening or restating it differently. MinimalGovernedRelationSet means the smallest independently governed direct-relation rules needed by named dependent use. It does not require one universal head relation. IdentityBearingDirectRelationIfSelected is filled only when the subject's direct owner selects such a relation; otherwise it is explicitly none.

E24FamilySettlementDecision:
  DecisionEpistemeIdentity:
    ClaimGraph:
    EntityOfConcern: one exact ontic, local kind, proposal episteme, source-construct entity, or exact inquiry entity selected before judgment.
    EffectiveReferenceScheme:
  CandidateInputs:
    ReceivingUseAndVisibleResult:
    PrimaryGovernedSubjectKind:
    SubjectIdentityConstitutionOrRecognitionRule:
    ProposedDurableUKindIfAny:
      GovernedIndividuals:
      DurableMembershipRuleAndReferenceScheme:
      IntendedExtentAndNonMemberBoundary:
      RootInclusionImplicationIfSameIndividualDependent?:
      ExactDependenceRelationAndDiscriminatorsIfIdentityDependent?:
    ExistingGovernorAndNonDuplicationResult:
    MinimalGovernedRelationSet:
      DirectRelationKind:
      ParticipantMeaningsAndAdmittedActualParticipantKinds:
      ObtainingAndOccurrenceIdentityRule:
      DirectGovernor:
      DependentUseEnabled:
    IdentityBearingDirectRelationIfSelected: exact direct relation entry | none.
    ReusableDeclarationsActuallyConsumed:
    NamedDependentPatternReliance:
    NonUseBoundary:
    ReopenCondition:
  Outputs:
    OnticSettlementResult?:
      OnticSettlementResultRef:
      SelectedOnticRefOrBootstrapSchemaRef:
      PrimaryGovernedSubjectKind:
      SubjectIdentityRule:
      MinimalGovernedRelationSet:
      NamedDependentPatternReliance:
      NonUseAndReopenBoundary:
    UKindAdmissionResult?:
      UKindAdmissionResultRef:
      AdmissionDisposition: root | same-individual-dependent | identity-dependent | reuse | local-kind | reject.
      DirectGoverningPatternRef:
      DurableMembershipAndExtentResultIfPositive?:
      BranchSpecificResultRef:
      NonUseAndReopenBoundary:
  DecisionMode: ontic-only | U-kind-only | atomic ontic-plus-U-kind.

In ontic-only, cite the already accepted U-kind result consumed by the ontic and omit a new UKindAdmissionResult. In U-kind-only, cite the already accepted ontic settlement and omit a new OnticSettlementResult. Use atomic ontic-plus-U-kind only when neither needed output already exists. The two outputs are evaluated from the same candidate inputs, remain provisional while either branch is unresolved, and become accepted together only when both branches pass. One output must never cite the other as an already accepted premise from the same decision. If one branch fails, retain the independently valid existing objects and record the exact reuse, local-kind, reject, or unresolved result; do not manufacture the missing output to save the other.

The bootstrap co-decision is E24-CO-UONTIC-BOOT-01. Its EntityOfConcern is the exact source-construct entity defined by E.24:4 for the kind U.Ontic; it does not presuppose an admitted U.Ontic or a pre-existing ontic instance. From that common input it returns two distinct accepted outputs: E24-OS-UONTIC-BOOT-01, which accepts this shared settlement schema as the direct rule for identifying future ontology-unit individuals, and E24UK-AR-UONTIC-BOOT-01, which admits the root kind U.Ontic. The schema, pattern, decision episteme, and kind are not thereby instances of U.Ontic; each concrete ontology-unit individual still needs an ordinary OnticSettlementResult. No relation-about-relation or relation from the kind to itself is invented for the bootstrap.

E.24 is compatible with modular ontology and ontology-design-pattern practice: modular ontology libraries and ontology design patterns show why reusable small ontology structures matter, and recent process-modeling work reports loss of reuse when process patterns remain implicit. E.24 is narrower and more FPF-specific: it governs the decision whether FPF should introduce a durable action-facing ontic, rather than importing an external microtheory or treating every reusable repair table as ontology.

If the three resolved ontology dispositions need reusable comparison, apply [A.19.ECS](/generated/patterns/A.19.ECS) to construct the evaluation CharacteristicSpace: retain the current governing-pattern relations, add one bounded local episteme whose claims cite them for a declared use, or add a durable ontic and its governing pattern. E.24 supplies those candidate dispositions and the ontic constraints applicable to each; [A.19.ECS](/generated/patterns/A.19.ECS) owns characteristic selection and evaluation. Source-use status remains an independent provenance choice and is not a fourth candidate. A comparison result does not establish ontic identity.

Within this split, E.24 carries the distinction among the ontic, the claim-bearing decision episteme, reusable declarations, and publication-side objects, plus the ontic-introduction decision needed before dependent patterns rely on a durable ontic. Publication-section rules, adequacy scales, wording-use restoration rules, and evaluation of the resulting FPF pattern-set structures are handled by the neighboring patterns named above.

Use the current split this way:

• use [E.24](/generated/patterns/E.24) for U.Ontic identity, the primary governed subject kind, exact identity or constitution rule, minimal governed relation set, governing patterns, named dependent-pattern reliance, and non-use boundary;
• use [E.24.CD](/generated/patterns/E.24.CD) when the current problem is detecting and characterizing an apparent subject before deciding whether it should enter an E.24 ontic-introduction decision at all; [E.24.CD](/generated/patterns/E.24.CD) supplies detection and characterization only and selects no E.24 disposition. Local use frame is not an E.24 disposition: recover whether the payload needs direct governing-pattern use, a bounded local episteme under C.2.1, a durable ontic, or an unresolved stop; record any source-use status separately.
• use [E.24.PUB](/generated/patterns/E.24.PUB) when the current problem is the distinction among the ontic, an ontic-description episteme, the publication occurrence that makes one selected edition available, the publication form that expresses it for that use, and the U.PresentationCarrier that bears the form; use [E.17.0](/generated/patterns/E.17.0) for U.View membership, A.6.3 for optional viewing construction, and [C.29](/generated/patterns/C.29) for a representation;
• use [A.19.ECS](/generated/patterns/A.19.ECS) only when the contested question is how to construct an evaluation CharacteristicSpace for comparing the resulting FPF pattern-set structures after retaining the governing-pattern relations, adding one bounded local episteme whose claims cite them for a declared use, or adding a durable ontic and its governing pattern.

This split keeps E.24 ontic-first. Questions about candidate detection, publication discipline, and contested evaluation remain under their neighboring governing patterns rather than becoming sections that turn E.24 into a general discovery, documentation, or scoring pattern.

Introduce or rely on a durable FPF ontic only after the ontic-introduction decision satisfies four checks.

#Check 1: Existing Governing Pattern Check

Name the current claim under decision and ask whether an existing pattern already carries it.

Use direct governing patterns first. If the case is method semantics, use A.3.1; if it is method description, use A.3.2; if it is mechanism meaning, use A.6.1 and E.20; if it is work planning or dated work, use A.15.2 or A.15.1. For evidence, gate, source, assurance, decision, release, publication, or another case, name the current claim and its current direct governing pattern by exact pattern ID before selecting direct governing-pattern use. If no current governor can be recovered by value, that disposition is unavailable; return to the other E.24 dispositions rather than treating the topic word as authority.

Do not introduce a durable ontic only because several patterns are near each other or because one source word appears often.

For a candidate relation kind, recover the exact participants and test the current direct relations through their direct governing patterns. If one direct relation closes the named receiving claim, use that settlement and stop. If none closes it, A.6.RCD may derive the needed claim and return a local-claim, predicate-definition, derived-kind-candidate, or primitive-kind-candidate disposition. A local compound claim or reusable predicate-definition episteme is not a relation kind. A derived-kind candidate proceeds only with a proposed direct subject settlement of its base dependencies, obtaining, applicability, and occurrence identity; a primitive candidate proceeds only with a candidate standalone direct pattern that supplies its own obtaining and occurrence identity. E.24 consumes the direct settlement or A.6.RCD result and does not repeat the derivation method.

#Check 2: Stable Identity Test

A candidate qualifies as a durable ontic only when it has stable identity beyond one local wording issue, source expression, or bounded local episteme used for first explanation.

Ask:

1. What exact independently identified object is the decision episteme about, and what pattern governs that object's identity?
2. If the later disposition is durable ontic, which identified ontology-unit individual becomes the decision episteme's EntityOfConcern?
3. What changes the identity of that ontic?
4. What does not change ontic identity, even if an ontic-description episteme, publication form, notation, view, or presentation carrier changes?
5. Which direct world-side relations and grounding conditions are required for identity?
6. Which dependent patterns may rely on that identity? If those questions cannot be answered, keep any needed coordination in a bounded local episteme under C.2.1 or use the direct governing patterns without another coordination episteme.

Test the invariant against the subject before filling a relation field:

#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's direct owner does.

One-screen first-use card:

Choose the branch with three observable thresholds before opening the ontology object map:

• Direct use closes the case when one readable claim under current governing 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 from F05 and can accompany any of the three resolved branches.

The following card is the cheap first-use summary. State the recognizable situation, the use that must close, and the exact subject; run the three thresholds; then fill ontologyDisposition 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, exact decisionEntityOfConcern, and effective ReferenceScheme are recoverable under C.2.1. A working phrase, topic cluster, draft heading, or list is not that exact subject. If neither a governed object nor an exact source episteme or expression entity is 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 object and its direct identity governor; never the unresolved wording itself.
  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.
  ontologyDisposition: fill last from those results: direct governing-pattern use | bounded local episteme under C.2.1 | durable ontic | unresolved stop.
  sourceUseStatus: not current | quote-only | reduced use | selected stronger source use; keep exact provenance when current.
  acceptedResultPointer: exact closing patterns | identified bounded episteme | identified durable ontic and its governing pattern | missing evidence for the unresolved stop.
  blockedLocalOverread: the nearest tempting object, kind, relation, or authority that this result does not create or license.

#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.

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 direct owner 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, keep work-facing U.Role and U.RoleAssignment under A.2, A.2.1, and A.15; a declaration-local SlotKind is not a role value.

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. It 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.
  ontologyDisposition: durable ontic.
  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.
  sourceUseStatus: not current; this replay is opened by the current FPF episteme architecture rather than a source expression.
  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: this decision is identified under C.2.1 by `PumpMaintenanceOnticDecisionClaims_v1` as its ClaimGraph, exact `EpistemeOntic` as its EntityOfConcern, and `FPF-Ontic-Decision-Scheme-2026` as its effective ReferenceScheme. 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:

For ordinary first use, stop at the one-screen card unless dependent patterns will rely on the proposed ontic, the current claim changes admissible use, or a receiving use needs a replayable reason why a bounded local episteme under C.2.1 was not enough.

The following fuller code block is an optional publication form for one claim-bearing ontic-introduction decision episteme. Its labels prompt decision claims; they are not world-side participants, SlotSpecs, or components of the selected ontic.

OnticIntroductionDecision:
  OntologyDisposition: fill last from the existing-governor, identity, connectivity-or-constitution, dependent-use, and non-duplication evidence; durable ontic | bounded local episteme under C.2.1 | direct governing-pattern use | unresolved stop.
  SourceUseStatus: not current | quote-only | reduced use | selected stronger source use.
  WorkingSubjectExpression: wording that opened the inquiry; never used as an EntityOfConcern without independent identification.
  SourceExpressionUseIfCurrent:
    ExactSourceExpression:
    SourceEpistemeIfRecoverable:
    SourcePublicationOccurrenceIfCurrent:
    RecoveredEntitiesRelationsAndClaims:
    CurrentAdmissibleUse:
    StrongerUseCondition:
    WordingUseRestorationCoordinatesIfE10ARCHOpenedTheCase:
      SemanticAreaBaseConcept:
      SemanticArea:
      SemanticAreaSenseFamily:
      OntologicalNeighborhood:
  DecisionEntityOfConcern:
    ExactObject:
    DirectIdentityGovernor:
    BranchSelectionReason:
  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?:
  UKindDecisionIfCurrent:
    E24UKDecisionRef: exact E.24.UK `UKindAdmissionDecision` episteme.
    E24SettlementRef: exact `OnticSettlementResult` from the shared schema; never the other output of the same still-open co-decision.
    AdmissionDisposition: exactly one value from E.24.UK's closed set: root | same-individual-dependent | identity-dependent | reuse | local-kind | reject.
    BranchDetailRefIfRequired: the exact branch-specific reference or references required by E.24.UK for that disposition.
    LocalGainCostAndDuplicateOntologyRisk: the decision-changing local rationale; not another disposition field.
  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:

For every other candidate, complete the decision form by value; no candidate inherits the U.* decision from E.24.

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 itself remains governed by its direct pattern. 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; the participant's direct governing pattern does.

#Check 4: Governing-Pattern and Dependent-Use Test

State:

• the pattern governing the selected durable ontic;
• the direct pattern governing each relation in the minimal set, and which relation is identity-bearing when the subject's owner selects one;
• each dependent pattern and the identified ontic identity, direct relation rule, or RelationSignature declaration on which it relies;
• each draft ToC row, planned pattern label, or absent governing-pattern section that remains non-governing.

Naming, publication placement, and evaluation remain neighboring authoring work under F.18, E.8, E.9.DA, and E.21. The ontic-introduction decision may point to those next moves, but none establishes ontic identity or replaces the governing pattern.

If the decision selects a durable ontic, write the pattern that governs it before dependent patterns rely on it. If the decision selects only a bounded local episteme, identify that episteme under C.2.1 and state its non-governing bounded use and claims by value. If no pattern governing the proposed durable ontic is written, do not cite that candidate as governing current FPF use.

#Bounded Local Episteme Decision

Use a bounded local episteme when one application family needs a readable coordination of entities and direct relations that are already governed elsewhere, but no new durable ontology unit is justified.

A bounded local episteme is a U.Episteme identified under C.2.1, not a new U-kind. Select one independently identified EntityOfConcern before writing claims. It may be a world-side entity or individuated occurrence under a direct owner, an admitted collection-as-whole or selected U.Structure, or an identified source, expression, or pattern-set architecture object. The selection test is the same: every claim must concern that one object. If several unrelated subjects remain and no admitted whole or selected structure unifies them, split the claims. A phrase or list cannot stand in for the missing subject.

For that bounded use:

• name the application concern, exact EntityOfConcern, and direct pattern that identifies it;
• state why every carried claim concerns that one object;
• identify each other governed entity and direct relation designated by those claims;
• cite the pattern governing each direct relation rather than restating its participant or identity rules;
• state the tempting ontic overread that the episteme does not license;
• stop before dependent patterns treat this one episteme as a durable ontology unit.

Positive example. Pump37MaintenanceCoordination_v1 has exact Pump #37 as its EntityOfConcern. Its ClaimGraph may designate the current maintenance plan, dated work, enacted method, and direct relations because every claim explains how this exact pump is maintained for the named scheduling decision. Pump #37's A.1 identity is independent of the coordinating episteme.

Blocked example. The expression workflow points variously to a method, work plan, dated work, and transformation-flow structure, but no one identified entity, admitted collection-as-whole, or selected structure yet unifies those claims. Do not make the word or the four-item list an EntityOfConcern. Keep the source inquiry material and split any already valid direct claims until one exact subject is recovered.

Precision restoration may use a bounded episteme when one receiving use needs several mapped claims read together. The episteme coordinates those claims for that use; every referenced object and relation still uses the direct owner named in E.24:4.3a.

#Archetypal Grounding

Use these slices as archetypes for the ontic-introduction decision. They are not a recommended progression. Each slice shows the exact governed payload, its ontology disposition, any independent source-use status, and the tempting overread that is blocked.

#Episteme Ontology Unit as Durable Ontic

The ontology-unit individual EpistemeOntic passes because multiple patterns reuse C.2.1 episteme identity and its exact direct relation rules without copying them. E.24.UK retains U.Episteme as the root kind, C.2.1 identifies each particular episteme, and neither is EpistemeOntic. The PumpStation37 specification is a consuming witness. Descriptions, availability, views, and representations use their rows in E.24:4.3a and do not change that identity.

#Multi-Pattern Subject Matter as an Ontic-Candidate Archetype

A project phrase such as "algorithm", "process", "solver", "workflow", "system", "quality", "time", "source", or "architecture" can point to one recognizable subject that is spread across several FPF values and patterns. The point of this archetype is not that all such subjects are one kind. The E.24 decision instead settles the status of the cross-pattern subject before patterns rely on it.

In this archetype, "process" and "workflow" begin as source expressions. Recover the one current object through E.24:4.3a, select the ontology disposition from that object's receiving use, and retain source-use status independently. The boundary fixture below supplies the concrete direct, bounded, durable-threshold, and unresolved cases; the label never becomes their common kind.

A source-driven use closes only after the exact expression remains linked to what was carried forward. For example, a source expression workflow may have source-use status quote-only while its ontology disposition is direct governing-pattern use of one recovered U.MethodDescription under A.3.2 and one selected TransformationFlowStructure under E.18. The source expression neither becomes their common kind nor disappears from the provenance of that use. If a later claim needs the source's stronger ordering, execution, or evidence meaning, reopen the named source episteme and apply the exact direct governing pattern for that stronger claim.

#One Workflow Expression Across the Boundary

Use one fixture to see what changes the answer. The exact expression Line 7 pump-service workflow comes from source episteme Line7MaintenanceManual_v4; when availability matters, Line7ManualRelease_2026-04 is its source publication occurrence. Keep its source-use status quote-only in every case below. The recovered objects are already governed: Pump37ServiceMethodDescription_v2 under A.3.2, Pump37WeeklyMaintenancePlan_2026Q3 under A.15.2, dated Work occurrence Pump37ServiceWork_2026-07-18 under A.15.1, and selected Pump37MaintenanceFlowStructure under E.18. The expression and provenance do not choose the ontology disposition; the receiving use and recovered subject do.

1. Direct-use result. A manual editor needs to check the one claim that Pump37ServiceMethodDescription_v2 describes the service method used in the manual. The exact EntityOfConcern is that identified method-description episteme, and A.3.2 closes the readable claim. Select direct governing-pattern use. Do not add a coordination episteme or a workflow ontic.
2. Bounded-episteme result. A weekly scheduling review needs the method description, current work plan, dated Work occurrence, and selected flow structure read together because each claim explains how exact Pump #37 will be serviced that week. Exact Pump #37 is the EntityOfConcern of Pump37WorkflowScheduling_v1, identified under C.2.1. No current pattern consumes that claim package as ontology. Select bounded local episteme; leave every designated object under its direct governor.
3. Durable-ontic threshold—not met by the current fixture. A durable result would require multiple current patterns to consume one same independently identified ontology unit and otherwise duplicate or disagree about its identity or constitution and minimal relation set. Before selecting that branch, a direct subject owner would have to identify a candidate such as MaintenanceWorkflowOntic_v1, supply its stable identity or constitution rule, and show exactly how the current A.3.2, A.15.2, A.15.1, and E.18 consumers rely on that one unit rather than merely mentioning their distinct governed objects. Until that stronger owner and cross-pattern reliance exist, the source expression and recurring four-object list do not identify a durable ontic.
4. Unresolved stop. The same manual may ask only to “align the workflow” while leaving open whether the concern is the method description, plan, dated Work, flow structure, Pump #37, or an admitted whole or selected structure. The exact source expression entity remains the EntityOfConcern of the unresolved decision episteme, but no exact governed payload has been recovered. Record unresolved stop, keep the quote and provenance, and split any direct claims that are already valid; do not turn the phrase or list into a subject.

This boundary case replaces the predecessor's filled transformation-slot assignment. It changes no direct owner's ontology and shows the nearest fact that moves the result: one closing claim; several claims for one use; shared cross-pattern ontology reliance with stable identity; or no exact governed subject.

The E.24 move is:

1. name the working expression and recover the exact governed object under concern; if none is identifiable, retain inquiry material and stop before claiming a decision episteme;
2. list the direct entities and relations that currently carry the subject; for every reused declaration, separately list its RelationSignature and SlotSpecs;
3. run the existing-governor, exact-identity, typed-connectivity-or-constitution, dependent-use, and non-duplication tests, then select one ontology disposition for the recovered payload—direct governing-pattern use, bounded local episteme under C.2.1, durable ontic, or unresolved stop—and record source-use status separately;
4. if a durable ontic is selected, write or cite the pattern governing that ontic before dependent patterns rely on it.

Do not repeat the surrounding method/work/change inventory here. The current claim selects one object class in E.24:4.3a; the workflow fixture names method description, plan, Work, and structure only because each changes that case. Their co-occurrence is an applicability signal, not a durable-ontic result.

For another broad head such as system, relation, or architecture, open its direct subject owner first and apply the same thresholds; the head alone admits no ontic.

Dependent subject patterns may keep a thin cue: when one recognizable concern spans several direct entities and relations, name the relation currently being asserted and use its governing pattern. That cue does not license treating a local set of references as a durable ontic before the E.24 decision, assigning one entity to two kinds without direct admission, or treating a SlotKind label as alternate ontology.

#Draft ToC Row or Planned Pattern Label as False Authority

A draft ToC row or older source label may name a calculus, family, or object before current FPF has a governing pattern for it. Such a label can guide investigation, but it cannot govern current use.

Example: older source wording may name a method calculus before current pattern text carries it. If no current pattern text carries it, it is not a governing pattern for current FPF use. Use the patterns that govern the direct entities and relations: A.3.1 for method semantics, A.3.2 for method description, A.15.2 for work planning, A.15.1 for dated work, and B.1.5 for method composition when ordering is current. A separate method calculus can govern other patterns only after it has its own E.24-style ontic decision, stable identity, named direct relation kinds with obtaining and occurrence-identity rules, and dependent-pattern declaration.

The same test applies to any draft ToC row or planned pattern label. If no current pattern carries the label's governing meaning, do not cite it as ontology. Either cite current governing patterns, keep the label as investigation context, or open an E.24 ontic-introduction decision.

#Broad Terms That Hide Several Governed Objects

A broad head such as system, architecture, or change is a working expression, not current ontology. Recover one exact subject and direct owner, run the three branch thresholds, and classify only current neighboring objects through E.24:4.3a. If the subject or receiving use is still missing, use the current direct patterns and stop before ontic admission.

#Bias-Annotation

Lenses tested: Gov, Arch, Onto and Epist, Prag, Did. Scope: the authoring decision about one candidate ontology unit. It selects durable U.Ontic, direct governing-pattern use, bounded local U.Episteme, or unresolved stop as the ontology disposition; it separately records source wording as not current, quote-only, reduced use, or selected stronger source use. The scope does not include the subject matter governed by the resulting pattern.

This pattern intentionally biases toward explicit identity, direct relation rules, reusable declarations where needed, and governing-pattern reuse. It resists five recurring distortions:

• shadow-kind bias: repeated use of one bounded local episteme is mistaken for evidence that a new durable ontic exists;
• placement bias: a pattern nest or draft ToC row is mistaken for the governed subject kind or governing text;
• name bias: a cleaner term hides unresolved kinds, slots, and relations;
• semio-bias: discussion of description epistemes, publication occurrences, forms, carriers, or review evidence displaces the ontic or subject matter being introduced;
• process-bias: development-state, publication-state, evaluation-state, or process evidence status is copied into ontic or subject-matter content.

The mitigation is the same in each case: recover the primary governed subject kind, exact identity or constitution rule, minimal governed relation set, any identity-bearing direct relation actually selected, any required RelationSignature, and governing-pattern reuse before naming, placement, dependent-pattern reliance, or publication form starts governing the decision.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

• FPF can introduce rich ontology units without treating every bounded local episteme as a new durable ontic.
• Draft ToC rows and planned pattern labels stop acting like current governing patterns.
• Dependent patterns can rely on the ontic-governing pattern and its named direct-relation patterns instead of reconstructing those rules locally.
• Selecting a durable ontic has an ongoing maintenance consequence: a change to the primary governed subject kind, identity rule, or any relation needed by named dependent use reopens the ontic-introduction decision and may affect those patterns. The bounded-local-episteme and direct-use dispositions avoid that cost when no durable coordination is needed; retaining a source expression for quotation or reduced use changes provenance handling, not that ontology cost.

#Rationale

FPF needs a pattern for ontic introduction because many important ontology units require one exact identity rule and several direct relation patterns to remain coherent. The repair is not to make one record-shaped episteme or universal head relation stand in for every nearby object. It is to give the ontic stable identity, state the smallest independently governed relation set needed by dependent use, single out an identity-bearing relation only when the subject's direct owner does, and add RelationSignature declarations only where dependent uses need them.

U.Episteme is the main stress case. C.2.1 identifies one episteme through claim content, exact EntityOfConcern, and effective reference scheme, while separate direct relations govern grounding and edition continuity. A RelationSignature declares reusable participant typing only when another use needs it. If a card is current, classify its actual use through E.24:4.3a; neither its layout nor its publication makes the episteme's claims true.

Role assignment is the second stress case. U.Role remains a work-facing role value, and generic U.RoleAssignment is a direct relation occurrence with exactly four participants: an admitted U.System holder, one U.Role value, the identified role-taxonomy episteme, and the effective U.ReferenceScheme. A.2.1 states obtaining and occurrence identity; its RelationSignature declares four SlotSpecs corresponding to those four relation-participant meanings for repeated assertion and reference use. AssignmentInterval belongs to an assertion or occurrence description. A selected BoundedModelUseStructure belongs to the receiving assertion or use unless a separately governed narrower relation kind makes it a required participant and states the stronger predicate.

This preserves ontology compactness without inventing a new kind for every participation name. Use U.Role only for a work-facing role value assigned to an admitted U.System. For another relation-participant meaning, the direct relation pattern states that meaning and the admitted actual-participant kind; a reusable RelationSignature may declare the corresponding SlotKind without changing the actual participant's kind. Without E.24, FPF ontology development oscillates between two bad moves. One move invents a new umbrella name and leaves the mixed ontology intact. The other refuses the new name but still leaves several patterns carrying duplicated local slot doctrine. E.24 gives a bounded ontology decision: use an existing governing pattern, introduce a durable ontic, state only the needed claims in a bounded local episteme under C.2.1, or stop unresolved. A separate source-use status preserves or strengthens the source relation without replacing that ontology decision.

The pattern is deliberately about the introduction decision. It does not define every ontic and does not become a registry of system, episteme, method, mechanism, architecture, source, quality, temporal, dynamics, or change objects. Each accepted subject matter still needs its own governing pattern; a bounded local episteme may carry claims for one declared use but does not govern the ontology.

#SoTA-Echoing

E.24 does not claim to replace ontology engineering, OWL-style formal ontology, or UFO-style foundational ontology. Its governing reason is the current FPF need for action-facing ontology compactness, plus a narrow SoTA echo:

For the working reader, these rows discipline named parts of the method. The SKOS and OWL baseline bounds taxonomy-only use in E.24:4.1 and E.24:5.4; modular ontology patterns support the reusable ontic and governing-pattern move in E.24:4.3 and E.24:4.4; interoperability work supports the stable-identity and currentness tests; process-representation work disciplines the workflow case in E.24:5.2; and gUFO stress-tests the role-assignment separation in the checklist and rationale.

This SoTA echo justifies a bounded conclusion: FPF ontology can remain more compact than a taxonomy-only design when one governed subject needs stable identity, several coordinated direct relations, reusable declarations, and dependent patterns. It does not make every modular ontology pattern an FPF ontic. External source content changes an ontic-introduction decision only when an accepted source-use decision selects it for the subject under concern; current FPF use still depends on the resulting governing pattern.

Use external sources when one ontic or subject matter itself depends on a source tradition. Put that source decision in the DRR and in the governing pattern for that subject matter. Do not make E.24 carry a borrowed external theory of every durable ontic.

#Currentness and Lowering Logic

Treat E.24 as current for ontic-introduction decisions while the governing patterns for relation-occurrence identity, reusable relation declarations, episteme identity, U-kind admission, wording-use restoration, and durable naming preserve the boundaries used here. Reopen one subject's ontic-introduction decision when one of these changes governs that subject:

• a new accepted FPF pattern changes direct relation identity, SlotSpec discipline, EntityOfConcern discipline, U-kind admission, or durable-name discipline;
• a bounded local episteme begins to be cited as if it governed a durable ontic;
• a planned pattern label acquires current governing pattern text and changes the ontic-introduction decision;
• dependent patterns start copying direct-relation rules or RelationSignature declarations instead of relying on their governing patterns;
• external source work governs the introduction method itself rather than one selected ontic or subject matter.

Do not let an unresolved ontology disposition govern dependent use. Return to E.24:4.1 until the payload is selected for direct governing-pattern use, a bounded local episteme, or a durable ontic, or is explicitly stopped unresolved. Record source-use status independently: quote-only, reduced use, or stronger source use does not settle the payload's kind, identity, relation set, dependent-pattern reliance, or non-use boundary.

#Relations

• Builds on: A.6.REL for direct relation occurrence identity, each direct relation pattern for relation-participant meanings, obtaining, applicability, and occurrence identity, and A.6.RCD for a residual needed claim or a derived-or-primitive candidate with its proposed direct subject settlement; A.6.0 and A.6.5 govern reusable RelationSignature and SlotSpec declarations, and C.2.1 governs decision, assertion, predicate-definition, and description epistemes.
• Coordinates with: E.8 for pattern publication placement, E.10 and E.10.ARCH for wording-use restoration, and F.18 for durable naming after ontology is settled.
• Coordinates with: E.24.CD for candidate detection before the ontic-introduction decision, E.24.UK for the UKindAdmissionResult output of the one shared E24FamilySettlementDecision, and E.24.PUB for ontic-description and publication distinctions. When both a new ontic and a new public U-kind are needed, E.24 and E.24.UK consume the same atomic decision inputs and neither treats the other's output as prior evidence.
• Coordinates with: E.17.0 for U.View membership, A.6.3 for optional viewing construction, C.29 for mathematical representation, and the E.14 -> B.3.5 -> C.13 chain for structural constructive grounding. Each ontic-introduction decision names any additional subject-specific governing patterns instead of treating this relation list as a registry.
• Coordinates with: A.19.ECS for contested comparison of candidate dispositions, E.9 and E.9.DA for recording and evaluating the authoring decision, and E.21 for evaluating the resulting pattern. Those evaluation results do not become part of the selected ontic.
• Used by: FPF authors when repeated relation and declaration material may need one durable ontic rather than direct governing-pattern use or claims coordinated only inside a bounded local episteme.

#E.24:End

Last Updated: 2026-08-04 — upstream FPF commit 7ba40a95 (github.com/ailev/FPF)