Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:55:20 UTC

E.24 - U.Ontic and Ontic Introduction Discipline

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

E.24:0 - 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 participant identities and meanings, any required kind conditions, reusable declarations, and neighboring subject patterns coherent.

Characterize the current candidate or source claim and run the existing-rule-content, identity, relation-or-constitution, dependent-use, and non-duplication tests below. Only then record the ontology disposition: introduce a durable ontic, coordinate already defined claims in a bounded local episteme, rely directly on current exact subject assertions and their ClaimGraph sources, or stop unresolved.

A current source-use record states quote-only, reduced use, or a selected stronger source use with its exact provenance; omit it when source use is not current. Source use can accompany any resolved ontology disposition as a separate provenance decision. Use source-only as a stop only when no exact payload assertion has been selected.

A durable ontic is a reusable ontology unit whose exact defining or constraining ClaimGraph states its identity rule and minimal relation set for dependent FPF use.

A bounded local episteme is a claim-bearing U.Episteme that coordinates already identified entities, exact relations, and subject assertions for one named use. Direct rule-content use relies on those existing assertions and ClaimGraph sources without adding another ontology unit. An unresolved stop retains the inquiry without selecting one of those three payload dispositions.

Typical examples 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 defining or constraining ClaimGraph states its meaning;
  • one pattern description begins to repeat local slot-relation doctrine that other uses 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 defines or constrains U.Ontic, the durable action-facing ontology unit. Each ontic-introduction decision episteme has one independently identified EntityOfConcern before judgment: a candidate entity, proposal episteme, or source-construct entity that carries the inquiry before any disposition is known. That object remains the EntityOfConcern for direct, bounded, durable, and unresolved results.

The selected direct-use object, bounded local episteme, durable ontic, or unresolved reason is the branch payload recorded in the result, not a replacement for the decision’s subject. Source-use status does not change the subject.

If a revised result changes the ClaimGraph, C.2.1 identifies another decision episteme; any edition continuity is stated separately rather than hidden by swapping the EntityOfConcern. An unresolved phrase or topic list is not itself an EntityOfConcern unless the exact source expression or source construct has been independently identified.

Primary working reader. The first reader is an FPF pattern author or reviewer deciding whether several nearby pattern descriptions concern one ontic, several already identified values, or only a compressed source expression. The downstream reader is the practitioner who needs the resulting subject assertions and practical guidance to decide what can be done, claimed, relied on, repaired, compared, or stopped.

If a separate U.MethodDescription claim matters, apply A.3.1 and A.3.2 to identify its Method and show that the episteme substantively describes how that Method is done; the E.24 locator alone establishes neither.

Working concern and viewpoint. From the FPF-authoring viewpoint, preserve the subject’s exact relations, assertions, and defining or constraining ClaimGraph sources 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, identify one exact pre-judgment candidate entity, proposal episteme, or source-construct entity and its direct identity governor, and use that object as the decision episteme’s EntityOfConcern. Name the receiving use and record source provenance when current.

Then run Checks 1–4: reuse existing exact predicates and ClaimGraph sources, test exact identity, recover the needed direct relations or constitution, and test dependent reuse without duplicate ontology. Fill the typed disposition result from those tests alone. Its direct, bounded, durable, or unresolved payload never replaces the decision subject. If no exact candidate or source construct can be identified, keep 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 subject-pattern question.

What this buys. A durable ontic has a stated identity and 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.

When those rules already close the receiving use, apply them directly. Add a bounded local episteme only when that use needs several already governed claims read together; its ClaimGraph cites their subject assertions and rule-content locators.

Not this pattern when.

  • If one existing defining or constraining ClaimGraph already states the claim kind, write the exact subject assertion and use the pattern id only as its locator.
  • If the issue is only wording, use F.19; open E.10 or E.10.ARCH only for FPF meaning that remains unresolved.
  • 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.

E.24:1 - Problem Frame

Some FPF objects are small enough to define through one direct relation ClaimGraph. Others become candidates for a durable ontic when several direct relations and rule-content loci 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 defining or constraining ClaimGraph sources. The decision method described here tests whether a durable ontology unit is needed and which direct relations make it useful.

E.24:2 - 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 subject 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.

E.24:3 - Forces

ForceTension
Ontic stability vs bounded local explanationA durable FPF ontic needs stable identity plus named direct relation kinds and their exact defining or constraining ClaimGraph sources; a bounded local episteme keeps its C.2.1 identity and needs only the claims and references required for one use family.
Reuse vs overgrowthDependent patterns may need one stable direct relation and a reusable declaration; premature U.* growth creates another ontology.
Ontology rule content vs pattern placementThe primary subject kind, exact identity or constitution rule, minimal relation set, exact subject assertions, and their defining or constraining ClaimGraph sources determine the ontic-introduction decision; a pattern nest is only publication and specialization placement under E.8.
Draft citeability vs current rule contentDraft ToC rows can guide investigation, and an accepted DRR can carry the authoring decision, but current exact rule content for FPF use resides in the defining or constraining ClaimGraph; a pattern id only locates it.
Naming vs ontologyF.18 can improve a name, but naming cannot decide identity, direct relations, declarations, species, or the reliance basis of dependent patterns.

E.24:4 - Solution

The ClaimGraph at E.24 defines U.Ontic as the FPF kind for a connected action-facing ontology unit.

Before dependent uses rely on that unit, the accepted ontic-introduction decision states its primary subject kind, exact identity, constitution, or recognition rule, the smallest exact relation set needed by dependent use, any identity-bearing direct relation selected by an exact identity assertion, any reusable RelationSignature declarations, rule-content locators, named dependent-use reliance, and non-use boundary.

Connected is an admission condition. The decision names the smallest set of independently defined relations that makes the subject usable across the named dependent uses and states why each relation belongs. When an exact identity assertion selects one identity-bearing direct relation, say so; otherwise do not invent a head relation.

Action-facing means that the decision names a dependent 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.

A kind’s independently justified membership rule also supplies no additional ontology unit by itself. When direct rules already close the named uses, record that no additional durable ontic is needed and select direct subject-pattern use, or bounded coordination when several claims must be read together. An empty relation set is not positive evidence of connected coordination, and adding a nearby relation merely to fill the set does not establish a contribution.

Keep two layers explicit:

  1. Instance layer. For each included direct relation kind, state how its actual participants are identified under their subject rules, how they contribute to the obtaining predicate, and which kind conditions that predicate requires. The defining ClaimGraph supplies those conditions and the occurrence-identity rule. An obtaining occurrence relates the actual participants satisfying that predicate. Kinds or declaration epistemes can themselves participate when the direct rule admits them; citing them in the decision establishes no such occurrence.
  2. Ontology and declaration layer. The ontic-introduction decision episteme states which subject kind, identity rule, relation kinds, declaration epistemes, rule-content locators, and dependent-use reliance claims belong in this ontology unit. These are typed claims in the decision episteme. A corresponding world-side declaration-dependency, inclusion, or reliance relation obtains only when its participants satisfy an independently defined predicate. Coordinating the objects in the ontology unit does not establish that occurrence.

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

Precise coordination does not require a new public kind for every participant. It does require a rule that recovers which object participates, what counts as the same or a different participant, and how it contributes to the relation.

Apply an existing kind criterion wherever the predicate depends on that classification. When a receiver additionally needs typed membership or substitution, A.6.5 requires independently established ValueKinds and complete SlotSpecs; an exact-value example cannot establish the whole range.

A missing identity or obtaining basis blocks the affected relation claim. A missing required range blocks its typed use while leaving separately warranted exact-value uses available. An ontic supplies neither missing basis by being declared.

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

Reidentify one U.Ontic by its primary subject kind, the exact identity, constitution, or recognition rule supplied by its defining ClaimGraph, and the minimal relation set selected for dependent use. Include an identity-bearing direct relation only when an exact identity assertion selects one.

Only a change to the subject kind, identity rule, or relation set used by a named dependent use 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.

Compare the included relation kinds by their participant meanings, obtaining predicates and occurrence-identity rules. Unchanged printed names do not preserve a relation whose governing meaning changed. Publishing an existing rule in another expression differs from changing that rule.

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 direct verbs with their exact subjects and predicates: a designator designates, a reference resolves, an episteme contains claim content, a publication occurrence makes one edition available, a particular expression conveys its required claims for that use, a reusable form constrains that expression, and a carrier bears the expression. The typed map supplies the exact assertion, defining or constraining ClaimGraph, pattern locator, 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 defining ClaimGraph;
  • the smallest set of independently defined direct relations needed by named dependent use, with the practical use each relation enables;
  • one identity-bearing direct relation only when an exact identity assertion selects it and its defining ClaimGraph states participants, predicate, and occurrence identity;
  • any RelationSignature epistemes used to declare reusable SlotSpecs for relation-participant meanings reused;
  • the current FPF patterns that define or constrain the subject kind, identity rule, and selected direct relations;
  • the pattern that defines or constrains 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.

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 reused across dependent uses, existing-rule-content checks, and a non-use boundary.

Use E.24.UK for U-kind admission. Both patterns use the 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; a new kind may reuse an already accepted ontic settlement or be admitted without an additional durable ontic when direct rules suffice for its named uses;
  • 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, exact subject assertion, and defining or constraining ClaimGraph 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.

E.24:4.0 - Constructive Foundation And Math-Lens Boundary

If a reader asks where an FPF ontic gets constructive grounding, follow its exact identity or grounding assertion and defining or constraining ClaimGraph. E.24 records a locator for 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 exact predicates, assertions, and rule-content locators remain in E.24:4.3a.

For structural identity, recover the subject’s direct identity rule and the construction or whole-forming facts it requires.

Use C.13 when the receiving use needs an inspectable construction account. When B.3.5 coverage is elected or a named requirement calls for that profile, apply the E.14/B.3.5 Working-Model requirements with the branch-specific validationMode and tv:groundedBy support, including the appropriate reconstructible Γ_m.sum, Γ_m.set or Γ_m.slice trace where that branch requires it.

Each constructor retains its own subject and conditions. A graph, tuple or other mathematical expression of that trace is a separate C.29 representation. The account, profile and representation do not replace the direct identity or construction facts.

For a non-structural ontic, use the exact identity, grounding, or recognition assertion and defining ClaimGraph located by its direct subject-pattern reference. 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 pattern descriptions already contain rule content for the same project concern, select an ontic only if one exact identity rule and minimal relation set must be reused across their dependent uses. 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 exact relation rules without inventing an occurrence whose participants are the kind, pattern, or ontic.

Gather the evidence in this order. Select the disposition after the first four steps:

  1. Current case and stable decision subject. State the working expression or source claim, one independently identified pre-judgment candidate entity, proposal episteme, or source-construct entity with its direct identity governor, and the named receiving use. Use that fixed object as the decision episteme’s EntityOfConcern. 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 pattern and what would reidentify the subject across the receiving use. Do not replace several required facts with an invented universal relation.
  4. Identity, relations, and dependent use. Use E.24:4.3a to classify only the objects that the dependent use consumes. Name each needed direct relation, its exact predicate and definition source, any relation that the subject’s identity rule selects as identity-bearing, the rule for identifying an occurrence of that relation, each declaration reused, and each dependent assertion’s exact reliance basis. Omit every neighboring map row whose selection question is false.
  5. Disposition, branch result, and boundary—fill last. Keep the decision EntityOfConcern from step 1. From steps 1–4, record exactly one branch payload: the closing assertions and direct patterns; the bounded episteme, its declared use, and stop; the selected ontology-unit individual and subject pattern; or the unresolved reason and missing evidence. Add an explanatory overread only when it passes F.19:4’s full independent-ground, plausible-reader, contribution, and smallest-clear-correction test.

A relation-participant meaning belongs in one selected direct relation only when its predicate depends on an actual participant making that contribution. The defining ClaimGraph must state how the participant is identified independently of a declaration field and state any classification condition the predicate uses. When typed reuse is needed, a compatible RelationSignature additionally declares an independently governed participant 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 subject pattern.

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.

FPF patterns may define or constrain a kind or predicate, state an admission test, frame a judgement, or give practical guidance. That does not make every pattern episteme a U.MethodDescription or every subject a U.Method. An engineer-manager uses the applicable claims and guidance to decide what can be done, claimed, relied on, repaired, compared, or stopped.

If the current claim says that an E.24 episteme describes an ontic-introduction Method, apply A.3.1 and A.3.2 to identify that Method and show that the episteme substantively describes how it is done. The accepted ontic-introduction decision supplies the object discipline for those practical choices.

Precision restoration uses the same discipline without turning it into lexical style. First recover the source-side entities, direct relations, assertions, descriptions, and defining or constraining ClaimGraph sources 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, state the exact subject assertions, cite their pattern-description locators, keep 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 subject 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.

The defining ClaimGraph located at E.24 states the admission conditions for U.Ontic, and E.24 gives practical guidance for the decision. The ontology unit, its identity rule, selected direct relations, declarations, claim-bearing epistemes, publication occurrences and forms, carriers, views, and representations remain distinct. Self-use does not establish a U.MethodDescription; apply A.3.1 and A.3.2 only when a separate Method and MethodDescription claim matters.

E.24:4.0a - Shared E.24-Family Settlement and Atomic Co-decision

E.24 and E.24.UK use one settlement schema without changing its requirements. MinimalGovernedRelationSet means the smallest independently defined direct-relation rules needed by named dependent use. It does not require one universal head relation. IdentityBearingDirectRelationIfSelected is filled only when an exact identity assertion under its defining ClaimGraph selects such a relation; otherwise it is explicitly none.

E24FamilySettlementDecision:
  DecisionEpistemeIdentity:
    ClaimGraph:
    EntityOfConcern: one independently identified pre-judgment candidate entity, proposal episteme, or source-construct entity; unchanged by the disposition.
    EntityOfConcernIdentityGovernor:
    EffectiveReferenceScheme:
  CandidateInputs:
    ReceivingUseAndVisibleResult:
    PrimaryGovernedSubjectKind:
    SubjectIdentityConstitutionOrRecognitionRule:
    CandidatePublicSpellingIfAny?: naming pressure only; it establishes neither the governed object nor admission.
    ProposedDurableUKindIfAny:
      GovernedIndividuals:
      DurableMembershipRuleAndReferenceScheme:
      IntendedExtentAndNonMemberBoundary:
      RootInclusionImplicationIfSameIndividualDependent?:
      ExactDependenceRelationAndDiscriminatorsIfIdentityDependent?:
    ExistingGovernorAndNonDuplicationResult:
    MinimalGovernedRelationSet:
      DirectRelationKind:
      ParticipantMeaningsAndIdentificationRules:
      KindConditionsRequiredByPredicate:
      ObtainingAndOccurrenceIdentityRule:
      DirectGovernor:
      DependentUseEnabled:
    IdentityBearingDirectRelationIfSelected: exact direct relation entry | none.
    ReusableDeclarationsActuallyConsumed:
    NamedDependentPatternReliance:
    NonUseBoundary:
    ReopenCondition:
  Outputs:
    OntologyDispositionResult?:
      Disposition: subject-pattern-use | bounded-local-episteme | durable-ontic | unresolved-stop.
      DirectUseResult?:
        ExactClosingAssertionRefs:
        DirectPatternLocators:
      BoundedEpistemeResult?:
        BoundedEpistemeRef:
        DeclaredUseAndStop:
      DurableOnticResult?:
        OnticSettlementResultRef:
        SelectedOnticRef:
        OnticSubjectPatternLocator:
      UnresolvedResult?:
        UnresolvedReason:
        MissingEvidenceOrRuleRefs:
    OnticSettlementResult?: # only for a selected durable ontic, or the explicit bootstrap case
      OnticSettlementResultRef:
      SelectedOnticRefOrBootstrapSchemaRef:
      PrimaryGovernedSubjectKind:
      SubjectIdentityRule:
      MinimalGovernedRelationSet:
      NamedDependentPatternReliance:
      NonUseAndReopenBoundary:
    UKindAdmissionResult?:
      UKindAdmissionResultRef:
      AdmissionDisposition: root | same-individual-dependent | identity-dependent | reuse | local-kind | reject.
      SubjectPatternLocator:
      DurableMembershipAndExtentResultIfPositive?:
      BranchSpecificResultRef: exact membership/inclusion/dependence result required by the admission branch; an ontic result only when consumed.
      NonUseAndReopenBoundary:
  DecisionMode: ontic-only | U-kind-only | atomic ontic-plus-U-kind.

When the E.24 ontology-disposition question is current, fill exactly one branch field inside OntologyDispositionResult; the decision EntityOfConcern remains fixed and the selected payload stays in that field. A changed result changes the decision’s ClaimGraph and therefore identifies another decision episteme under C.2.1; state any edition continuity explicitly.

In ontic-only, cite the already accepted U-kind result consumed by the ontology-disposition decision and omit a new UKindAdmissionResult. A direct-use or bounded-coordination conclusion returns no new OnticSettlementResult.

In U-kind-only, either cite an accepted ontic settlement needed by the use, or explicitly conclude that no additional durable ontic is needed and record the sufficient direct-use or bounded-local-episteme disposition. The positive admission still requires every E.24.UK membership, extent, witness, need, non-duplication and branch-specific condition. Its result does not require creating a sibling ontic.

Use atomic ontic-plus-U-kind only when both new outputs are independently needed. Evaluate them from common candidate inputs; neither is prior evidence for the other, and they remain provisional together while either required branch is unresolved.

If one branch fails, preserve independently valid existing objects and return the exact gap. If the tests instead establish that no additional ontic is needed, select the explicit U-kind-only branch with its direct-use or bounded-coordination grounds; do not call an empty ontology unit connected or drop a required dependency.

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, use A.19.ECS to construct the evaluation CharacteristicSpace: retain the current subject assertions and relations, add one bounded local episteme for a declared use, or add a durable ontic with its own rule content.

The A.19.ECS locator establishes neither a Method nor a MethodDescription; apply A.3.1 and A.3.2 only if those identities matter. E.24 supplies the candidate dispositions and their ontic constraints, while characteristic selection and evaluation remain separate A.19.ECS assertions.

Source-use status remains an independent provenance choice, not a fourth candidate, and a comparison result does not establish ontic identity.

Within this split, the rule content located at E.24 states the distinction among the ontic, the claim-bearing decision episteme, reusable declarations, and publication-side objects, plus the ontic-introduction decision needed before dependent uses rely on a durable ontic. Publication-section rules, adequacy scales, wording-use restoration rules, and evaluation of the resulting FPF pattern-set structures remain separate exact assertions whose ClaimGraph sources are located through the neighboring patterns named above.

Use the current split this way:

  • use E.24 for U.Ontic identity, the primary governed subject kind, exact identity or constitution rule, minimal governed relation set, subject patterns, named dependent-pattern reliance, and non-use boundary;
  • use 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 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 subject-assertion 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 when the current problem requires distinguishing the ontic, an ontic-description episteme, exact E/A/U/X/C publication, reusable form conformance or independently identified carrier; use E.17.0 for U.View membership, A.6.3 for source-to-receiving construction, A.6.3.RT/A.6.3.RT.OE for expression construction and C.29 for a mathematical lens;
  • use 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 subject-pattern relations, adding one bounded local episteme whose claims cite them for a declared use, or adding a durable ontic and its subject pattern.

Questions about candidate detection, publication discipline, and contested evaluation remain separate exact subject assertions under their own defining or constraining ClaimGraph sources. E.24 governs the ontic-introduction decision.

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

E.24:4.1 - Check 1: Existing Rule-Content Check

Name the current claim under decision and ask whether an existing exact defining or constraining ClaimGraph already states its rule content.

Use existing rule content first. If the case is method semantics, resolve the defining ClaimGraph located at 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 exact current subject assertion and its defining or constraining ClaimGraph, with the pattern id only as locator, before selecting direct rule-content use. If no current rule content can be recovered by value, that disposition is unavailable; use 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 against their exact predicates, assertions, and defining ClaimGraph sources. If one direct relation closes the named dependent-use 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 defining ClaimGraph that supplies its own obtaining and occurrence identity. E.24 uses the direct settlement or A.6.RCD result and does not repeat the derivation method.

E.24:4.2 - 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 candidate entity, proposal episteme, or source-construct entity is independently identifiable before judgment, and what direct rule identifies it as the fixed EntityOfConcern of the decision episteme?
  2. Which exact result payload follows from each available disposition without replacing that fixed EntityOfConcern: closing assertions, a bounded episteme, a selected ontology-unit individual, or an unresolved reason?
  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 durable identity is not established, use an existing assertion or a bounded local episteme under C.2.1 when it meets its threshold in §4.3. Otherwise return the unresolved question about the identified decision subject. If no decision subject can be identified, retain the inquiry material.

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

Governed subjectIdentity, constitution, or recognition ruleRelation-set consequence
Holon or SystemA.1’s exact candidate, constituents, constructive part relations and assembly, reidentification, whole-level characteristic, larger-assembly compatibility, and any kind-specific conditionkeep those facts under their subject patterns; A.1 explicitly forbids compressing them into one universal relation signature
MethodA.3.1’s semantic way-of-doing identity and any independently governed method-holarchy factsname only the direct relations needed by dependent method use; no head relation is presumed
WorkA.15.1’s dated occurrence identity and continuity ruleperformer, enacted method, affected referent, resources, and results stay under their exact direct relations or A.6.1 bindings
TransformationA.3.4’s independently identified actual bounded change at the selected resolutionwork, flow, production, representation, and receiving-use relations remain separate; no core relation is invented
EpistemeC.2.1’s constitution ruleEpistemeConstitutionRelation is identity-bearing because C.2.1 explicitly selects it; empirical grounding, edition, conformance, and publication remain neighboring relations
RelationA.6.REL plus each direct relation pattern’s obtaining and occurrence-identity rulethe ontology unit coordinates common occurrence discipline with those direct rules; no relation-to-relation head occurrence is required

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 classSelection questionRecord by value and subject pattern
World-side participantDoes 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 occurrenceIs 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 declarationDoes 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 epistemeDoes 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 unitMust 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 objectIs 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
ViewDoes 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
RepresentationDoes 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 expressionDoes 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 relianceDoes 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.

E.24:4.4 - Check 4: Exact Rule-Content and Dependent-Use Test

State:

  • the pattern governing the selected durable ontic;
  • the exact defining ClaimGraph for each relation in the minimal set, and which relation is identity-bearing when an exact subject assertion 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 subject-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 subject pattern.

If the decision selects a durable ontic, write the pattern that defines or constrains 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.

E.24:4.4a - Recover broad rule-content, provision, and support wording before admission

Do not admit a generic governance, provision, support, or rule-locus ontic merely because several patterns use those words.

First freeze the exact source occurrence and recover what it says by value: an exact subject assertion, defining or constraining ClaimGraph, direct relation, Work occurrence, Method or MethodDescription, promise or commitment content, source use, publication, evidence, assurance, authority, access, or ordinary-language claim.

The recovered C.2.1 assertion is the preservation object for that occurrence; a shared dispatch table, field name, or word family is not.

A broad candidate fails the durable-ontic test when its proposed members have no common identity or membership rule and no non-duplicative receiving use. In that case E.24 supplies no umbrella object. Keep each narrow recovered meaning under its existing pattern and use E.24.UK for the associated U-kind question with an occurrence-local reject. The rejection’s RejectedCandidateRecoveryRef must resolve the exact preserved assertion. If the occurrence has not yet been recovered, leave its material wording unchanged rather than deleting content under a lexical rule.

This rule blocks generic U.Provision, U.Support, SupportRelation, governance relation kinds or occurrences, and rule-locus description kinds unless a later, independently accepted case supplies exact individuals, identity, membership, non-members, and a receiver that cannot use existing assertions and relations. It does not block genuine service-provision Work, operational support Work, evidence support, source use, publication support, human or institutional authority, or another exact relation whose own predicate obtains.

E.24:4.5 - 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 an exact subject assertion, 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 an ontic overread only when its correction passes the F.19:4 test in E.24:4.0;
  • stop before dependent patterns treat this one episteme as a durable ontology unit.

Positive example. Pump37MaintenanceCoordination_v1 has 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 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 subject pattern named in E.24:4.3a.

E.24:5 - Archetypal Grounding

These examples illustrate different ontic-introduction decisions. Their order does not prescribe a progression. Each slice shows the exact governed payload, its ontology disposition, any independent source-use status, and the tempting overread that is blocked.

E.24:5.1 - Episteme Ontology Unit as Durable Ontic

The ontology-unit individual EpistemeOntic coordinates the shared episteme constitution and the minimal relation rules used across current patterns. E.24.UK retains U.Episteme as the primary kind; C.2.1 identifies each episteme. The ontology unit is identified under :4 by that kind, the exact constitution rule and the included relation meanings. The PumpStation37 specification is one consuming example. Changing the example’s publication or view leaves the ontology unit unchanged; changing a governing relation in its minimal set reopens the ontology unit’s identity.

The coordination is needed because these uses must agree on which episteme they concern. Empirical grounding selects claims of that episteme; edition continuity compares distinct episteme identities; viewpoint conformance tests an identified episteme against an identified viewpoint; publication makes a selected edition available. C.2.1’s constitution rule provides their common subject identity, while each direct pattern retains its own predicate. A content or interpretation change therefore reopens the dependent conclusions that use it, whereas a carrier change alone leaves that identity fixed. Without this shared rule, those patterns could silently evaluate, continue, or publish different knowledge objects under one name.

The coordination uses independently recoverable content and interpretation rules. C.2.1:4.1.2 supplies bounded ranges for their typed substitution; :4.2.1 and A.6.5 govern the receiving declaration. The ontology unit contributes the shared connection among these uses. It grants no missing participant identity, range membership or obtaining relation. A proposed general public U-kind still needs E.24.UK.

E.24:5.2 - 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. A shared phrase does not establish one kind for all these subjects. The E.24 decision 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, workflow may remain quote-only while one receiving question is answered directly by a claim about a recovered U.MethodDescription under A.3.2, and another by a claim about a selected TransformationFlowStructure under E.18. If one use needs both assertions read together, apply the bounded-episteme threshold. 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 state the exact stronger assertion under its defining or constraining ClaimGraph.

E.24:5.2a - 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 fixed EntityOfConcern of each decision card is Line7WorkflowInquiry_v1, an independently identified source-construct entity for this inquiry; it asserts neither a workflow ontic nor any branch payload.

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 evidence 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. A.3.2 closes that readable claim. The decision’s EntityOfConcern remains Line7WorkflowInquiry_v1; its DirectUseResult points to the exact assertion, the identified method-description episteme, and A.3.2. 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 Pump #37 will be serviced that week. The decision’s EntityOfConcern remains Line7WorkflowInquiry_v1; its BoundedEpistemeResult points to Pump37WorkflowScheduling_v1, a bounded episteme under C.2.1 whose EntityOfConcern is Pump #37. A.1 identifies the pump. No current dependent use requires that claim package as ontology. Leave every designated object under its exact predicate, subject assertion, and defining or constraining ClaimGraph.
  3. Durable-ontic threshold—not met by the current fixture. The decision’s EntityOfConcern remains Line7WorkflowInquiry_v1. A positive DurableOnticResult would have to point to an independently identified ontology-unit individual such as MaintenanceWorkflowOntic_v1, its stable identity or constitution rule, and the exact reliance of multiple A.3.2, A.15.2, A.15.1, and E.18 consumers on that one unit. Those facts are absent, so this fixture has no durable result; when this stronger use is the active question, its UnresolvedResult names the missing identity and reliance evidence. 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 decision’s EntityOfConcern remains Line7WorkflowInquiry_v1; its UnresolvedResult records that no exact governed payload has been recovered and names the missing identity evidence. Keep the quote and provenance, and split any direct claims that are already valid; do not turn the phrase or list into a subject.

The fact that changes the result is 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 identify the pre-judgment candidate entity, proposal episteme, or source-construct entity under its direct rule; keep that fixed object as the decision episteme’s EntityOfConcern. If none is identifiable, retain inquiry material; a missing governed payload instead permits an unresolved result about the identified decision subject;
  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-rule-content, exact-identity, relation-or-constitution, dependent-use, and non-duplication tests, then select one ontology disposition for the recovered payload—direct subject-assertion 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 its exact defining or constraining ClaimGraph before dependent uses rely on it.

The workflow fixture needs its method description, plan, Work, and structure because each changes the scheduling use. Select the objects needed by another case through E.24:4.3a; their co-occurrence alone supplies no durable-ontic result.

For another broad head such as system, relation, or architecture, recover its exact subject assertion and defining or constraining ClaimGraph first and apply the same thresholds; the head alone admits no ontic.

Dependent pattern descriptions may keep a thin cue: when one recognizable concern spans several direct entities and relations, name the exact relation assertion and cite the pattern locator for its defining or constraining ClaimGraph. 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.

E.24:5.3 - 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 an exact defining or constraining ClaimGraph for it. Such a label can guide investigation, but it cannot establish current FPF use.

Example: older source wording may name a method calculus before current pattern text contains exact rule content for it. If no current defining or constraining ClaimGraph states it, the label is not current FPF rule content. Use the exact ClaimGraph sources located at 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 constrain other subject assertions 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-use declaration.

The same test applies to any draft ToC row or planned pattern label. If no current defining or constraining ClaimGraph states the label’s meaning, do not cite it as ontology. Either cite current exact subject assertions and their pattern-description locators, keep the label as investigation context, or open an E.24 ontic-introduction decision.

E.24:5.4 - 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 assertion and its defining or constraining ClaimGraph, run the three branch thresholds, and classify only current neighboring objects through E.24:4.3a. If the subject or dependent use is still missing, retain the inquiry and name that missing value before ontic admission.

E.24:5.6 - Bias-Annotation

Scope: the authoring decision about one candidate ontology unit. It selects durable U.Ontic, direct subject-assertion use, bounded local U.Episteme, or unresolved stop as the ontology disposition; when source wording is current, it separately records quote-only, reduced use, or selected stronger source use. The scope does not include the subject matter defined or constrained by the resulting ClaimGraph.

This pattern favors explicit identity, direct relation rules, reusable declarations where needed, and subject-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 selected, any required RelationSignature, and subject-pattern reuse before naming, placement, dependent-pattern reliance, or publication form starts governing the decision.

E.24:6 - Conformance Checklist

Activation rule: every candidate uses the cheap-card checks CC-E24-1, CC-E24-1b, CC-E24-1c, and CC-E24-2. CC-E24-1a activates only when a direct-relation or declaration-layer claim is recorded; CC-E24-3 through CC-E24-5 activate for a durable result; CC-E24-7 activates for bounded coordination. The remaining rows activate only when their named object or claim is current.

A direct result closes from its current assertion and direct pattern. An inactive row is omitted, not filled with blanks or not current.

CheckObservable conformance condition
CC-E24-1The cheap card names the recognizable situation, one exact receiving use, one ontology disposition, any current source use, and one independently identified pre-judgment EntityOfConcern with its identity governor. That subject stays fixed; exactly one typed result points to the closing assertions, bounded episteme, durable ontic, or unresolved reason. Ordinary direct, bounded, and unresolved cases close here unless a stated full-form guard is true. Work and decision are examples of receiving use, not universal prerequisites. A working phrase, topic cluster, heading, or list is never accepted as the EntityOfConcern merely because it opened the inquiry.
CC-E24-1aThe decision keeps two layers explicit. At the instance layer, every included direct relation names actual participant identities and meanings, any kind conditions required by its predicate, and its direct governor. At the ontology/declaration layer, typed decision claims state why each kind, relation rule, declaration, pattern, and dependent reliance belongs; no world-side occurrence among those declaration-level objects is implied. Any identity-bearing relation is marked explicitly.
CC-E24-1bThe author characterizes the current case, runs existing-governor reuse, exact-identity, relation-or-constitution, dependent-use, and non-duplication tests, and fills the ontology disposition last. Its summary placement near the top of a card is not evidence that it was selected first.
CC-E24-1cDirect use is selected when one readable governed claim closes the receiving use; bounded episteme when that use needs several governed claims read together but no pattern consumes their package as ontology; durable ontic only when multiple current patterns must reuse one independently identified ontology unit and would otherwise duplicate or disagree about identity, constitution, or the minimal relation set.
CC-E24-2Existing exact rule content is checked by value before a new ontic is selected. For a relation-kind candidate, the decision cites the exact direct relation pattern passage, which states participant meanings, obtaining, applicability, and occurrence identity, or an A.6.RCD result that returns a derived or primitive candidate with that proposed direct subject settlement. Local claim and predicate-definition results are not admitted as relation kinds.
CC-E24-3When the durable branch is selected, the decision states the proposed ontic’s stable identity criteria and says what does and does not change that identity.
CC-E24-4A durable ontic names the subject’s exact identity, constitution, or recognition rule and its minimal governed relation set. For every included relation it names the direct governor; when one is identity-bearing, it also names participant meanings, independent participant-identification rules, required kind conditions, obtaining condition, and occurrence identity. A typed use additionally requires independently governed participant ranges and complete A.6.5 SlotSpecs; ontic settlement supplies no missing kind admission.
CC-E24-4aA constructive-grounding claim names its direct rule and required subject facts. C.13 supplies an inspectable construction account when needed. For elected or independently required profile coverage, follow the E.14/B.3.5 branch-specific Working-Model, validation-mode and tv:groundedBy conditions, including a Γ_m trace where that branch requires it. Non-structural ontics retain their direct identity, grounding or recognition rule.
CC-E24-4bOntic introduction creates no project-side relation occurrence. A designator designates and a governed reference resolves only after the direct predicate and identity rule reidentify the occurrence; an assertion or description episteme carries the claim and designation. A publication occurrence makes a selected episteme edition available and neither designates nor creates the world-side occurrence.
CC-E24-4cE.24 and E.24.UK use one E24FamilySettlementDecision. Independent positive kind admission may return the explicit direct-use or bounded-coordination conclusion that no additional durable ontic is needed, with no OnticSettlementResult. When both new outputs are independently needed, one atomic decision returns separate result references from common inputs; neither is prior evidence for the other and both remain provisional while a required branch is unresolved. An empty relation set or a nearby relation added for form supplies no coordination contribution.
CC-E24-5When the durable branch is selected, the decision states the primary governed subject kind, stable identity criterion, exact identity or constitution rule, minimal governed relation set and direct governors, the reliance basis of each named dependent pattern, existing-pattern reuse, and non-use boundary by value. E.10.ARCH wording-restoration coordinates are included only when that restoration opened the case, and the E.8 pattern nest remains publication placement; neither becomes a component or identity criterion of the ontic.
CC-E24-5aEvery current object is classified by the selection question and subject pattern in E.24:4.3a. Ontology/declaration-layer inclusion and reliance claims remain typed decision claims unless a separate direct relation is independently governed; none is silently promoted to a world-side occurrence.
CC-E24-5bAn encountered card, table, schema, diagram, file, or record is classified through E.24:4.3a; visible shape and field co-occurrence decide no governed use. Only an identified U.System performs description, rendering, or publication work.
CC-E24-5cMathematical operands, tuple components, nodes, and edges remain C.29 representation elements. A correspondence to a relation object neither identifies the two nor contributes to world-side occurrence identity.
CC-E24-6Draft ToC rows and planned pattern labels remain non-semantic locators. Until an exact defining or constraining ClaimGraph is written, a bounded local episteme contains only its stated claims for its declared use; for every exact entity and direct relation, those claims identify the current ClaimGraph and pattern-description locator.
CC-E24-7A bounded local episteme remains a U.Episteme under C.2.1, not a newly minted U-kind or durable ontic. It has one independently identified EntityOfConcern that every carried claim concerns; if no one subject survives, the claims are split or the inquiry remains unresolved. Other entities and relations stay under their subject patterns.
CC-E24-8The selected name passes F.18; the name does not hide a second ontology or one umbrella for several kinds.
CC-E24-8aDurable U.* names, reusable SlotKind heads, dependent-kind names, publication-form names, public ids, Core-facing heads, and cross-context labels use F.18; F.17 UTS and Name Card material is opened only when that name becomes public, Core-facing, or cross-context, and never replaces A.6.5 SlotSpec discipline.
CC-E24-8bA U.* spelling, type or kind wording, structural heading, title, filename, or ToC row that claims U-kind force is governed by E.24.UK before naming patterns are asked to choose or keep a public term.
CC-E24-9Pattern-quality and DRR-adequacy checks stay in E.21 and E.9.DA; they are not copied as user-facing ontic or subject-matter content.
CC-E24-10Each named dependent pattern is paired with the identified ontic identity, direct relation rule, or RelationSignature declaration on which it relies, and does not duplicate that rule or declaration.
CC-E24-11Bare role is routed through E.10.ROLE. The decision distinguishes a world-side participant under its direct subject pattern, a local system-role kind and its A.2/C.3.2 classification judgment, an exact A.2.1 assignment occurrence, and a declaration-local participant meaning in an A.6.5 reusable declaration. F.6 is opened only for current Work attribution. E.24 copies none of those patterns’ construction or occurrence rules and admits no false common head.
CC-E24-12For every selected direct relation, prose names the relation kind, participant meanings, obtaining rule, and direct governor; reusable declaration prose uses RelationSignature, SlotSpec, SlotKind, ValueKind, refMode, and RefKind. onticSlotRelation is not a universal field, and interface is used only when a governing boundary, module, signature, mechanism, or architecture pattern makes interface meaning current.
CC-E24-13Source-ontology annotation is proportional: decision-changing kind, slot, relation, admissible-use, and subject-pattern differences are recovered, while stable domain prose is not expanded into type labels. When a source expression affects the decision, the exact expression, source episteme, any current source publication occurrence, content carried forward, source-use status, current admissible use, and smallest stronger-use condition remain recoverable beside—not instead of—the ontology disposition.
CC-E24-14When candidate detection, publication-side object distinction, or contested evaluation is current, apply E.24.CD, E.24.PUB, or A.19.ECS respectively; E.24 itself stays centered on the primary governed subject kind, U.Ontic identity, exact identity or constitution rule, minimal governed relation set, subject patterns, named dependent-pattern reliance, and non-use boundary.

E.24:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Shadow-kind by repetitionThe same claim-bearing episteme or reusable publication form appears in several patterns and starts being cited as an ontology object.Apply the E.24 thresholds to the receiving use. A sufficient existing claim needs no new coordination. Introduce a bounded episteme or a durable ontic only when its threshold is met, and retain the inquiry if the evidence is insufficient.
Draft ToC row as authorityA ToC row is cited as if it supplied current governing text.Treat it as an investigation cue only; use current subject patterns until the pattern exists.
Slot list without identityA pattern lists record fields as if they were SlotSpecs but never states what identifies the proposed ontic.For a durable proposal, identify its identity or constitution rule and the smallest direct-relation set required by named dependent use. If that basis is missing, use an existing claim or bounded C.2.1 episteme when its threshold is met. Otherwise identify what is unresolved.
Pattern nest as ontologyA numbering or placement group is treated as the governed subject.Name the primary governed subject kind, exact identity or constitution rule, minimal governed relation set, and their subject patterns; keep the pattern nest as publication and specialization placement under E.8.
New name as solutionThe repair invents a smoother term while the typed values remain mixed.Recover the primary governed subject kind, exact identity or constitution rule, minimal governed relation set, and direct governors first; name only after the ontology is settled.
SlotKind label becomes participant kindA declaration-local SlotKind is reused as the world-side participant’s kind.Keep the participant under its subject pattern and keep the SlotSpec inside the separate RelationSignature declaration.
Interface metaphor for slotsA relation-participant meaning, SlotSpec, assertion-side participant designation, or participant-kind constraint is called an interface without a governing interface pattern.Use the named direct-relation or declaration term unless a boundary, module, signature, mechanism, or architecture pattern makes interface meaning current.
Typed paraphrase overloadA readable subject sentence is rewritten as a full chain of kinds, slots, and source-ontology labels without changing the claim.Keep the subject sentence and annotate only the decision-changing slot or value under decision.

E.24:9 - 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 subject patterns.
  • Dependent patterns can rely on the ontic-subject 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.

E.24:5.7 - 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. One record-shaped episteme or universal head relation cannot stand in for every nearby object. 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 pattern 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.

A bare role cue is a second stress case because it can hide four different objects: a world-side participant, a local system-role kind and its classification judgment, an assignment occurrence, or a reusable declaration’s local participant meaning. E.10.ROLE recovers the intended use; the participant stays under its direct subject pattern, A.2 and C.3.2 govern the local kind and classification, A.2.1 governs the exact assignment species and occurrence, A.6.5 governs the declaration, and F.6 governs any current Work attribution.

E.24 asks only whether the ontic decision has confused those objects or invented a common head. Their participants, predicates, obtaining and occurrence identity remain with the cited patterns.

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

E.24’s rule content and practical guidance concern the introduction decision. They do not define every ontic or become a registry of systems, epistemes, methods, mechanisms, architectures, sources, qualities, times, dynamics, or changes.

If an E.24 episteme qualifies as a U.MethodDescription, A.3.1 and A.3.2 must identify the Method it describes and show substantive guidance for doing it; that gives no other pattern episteme the same membership.

Each accepted subject still needs its own defining or constraining ClaimGraph; a bounded local episteme may contain claims for one declared use but does not define the ontology.

E.24:5.8 - 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:

Source familyCurrent lesson for E.24FPF decision
W3C SKOS Reference, 2009, and W3C OWL 2 Primer, 2012.Reference-baseline use, not a current-best SoTA claim: SKOS remains useful for controlled vocabularies, labels, broader and narrower relations, and concept schemes; OWL remains useful for classes, properties, individuals, axioms, and declarative semantics.Adopt as baseline and adapt: do not present FPF ontology as one taxonomy tree. Use taxonomy relations where they fit, but introduce an ontic only when one exact identity rule and a minimal set of governed relations are needed across dependent use; add reusable declarations only for relations whose typed reuse is current. Current competitive guidance comes from the 2024-2026 modular ontology, interoperability, process-representation, and foundational-ontology rows below.
Modular ontology design patterns, MODL/MOMo, and commonsense ontology micropatterns, including Shimizu and Hitzler 2024 and Eells, Dave, Hitzler, and Shimizu 2024.Current ontology-engineering work emphasizes reusable small ontology structures and pattern libraries, including LLM-assisted ontology engineering where modularity becomes more important, not less.E.24 adapts the modular-pattern lesson: a durable ontic is a reusable FPF ontology unit with a pattern governing its direct relation set and with each dependent pattern paired to its exact reliance basis, not a local checklist copied across patterns.
Qiang 2025, revised 16 June 2026 (v12).Overlapping and conflicting concepts block interoperability; the proposed framework combines design patterns, matching and versioning, and validation across the ontology lifecycle.E.24 prevents shadow ontology and type explosion before matching and versioning becomes a rescue operation. It asks whether a proposed ontology unit becomes a durable ontic, is already governed by existing patterns, stays only as claims in a bounded local episteme, or is not admitted for use.
Norouzi, Hertling, Waitelonis, and Sack 2025 process-representation ODP work.Process ontologies and workflow ontologies often contain implicit design patterns; reuse suffers when those patterns are not explicit and accessible to domain experts.Adopt as a caution for any process-like or temporal subject: a bounded local episteme carries only the claims and references needed for one use; reusable process, method, work, or temporal ontology stays explicit. If such material needs a durable ontic, state its direct relation kinds, participant meanings, obtaining and occurrence-identity rules, and subject patterns.
Almeida, Guizzardi, Sales, and Fonseca 2026 gUFO; UFO and OntoUML role, relator, situation, and high-order type practice.Current foundational-ontology work uses type typology, reification of intrinsic and relational aspects, situations, and high-order types to avoid naive taxonomic flattening.Use as a stress comparator without importing its taxonomy or assignment architecture: route bare role through E.10.ROLE, recover which object is current, and follow A.2/C.3.2, A.2.1, A.6.5, or F.6 for that object’s own rule content.

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 subject-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 supplies a stress comparator for recovering the exact object behind role without importing or repeating its ontology.

These comparisons support the conclusion that 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. The comparisons do not establish that every modular ontology pattern is 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 subject 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 pattern description containing the exact rule content for that subject matter. Do not make E.24 contain a borrowed external theory of every durable ontic.

E.24:5.9 - Currentness and Lowering Logic

Treat E.24 as current for ontic-introduction decisions while the subject 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 subject pattern text and changes the ontic-introduction decision;
  • dependent patterns start copying direct-relation rules or RelationSignature declarations instead of relying on their subject patterns;
  • external source work governs the introduction method itself rather than one selected ontic or subject matter.

Do not let an unresolved ontology disposition constrain dependent use. Use E.24:4.1 until the payload is selected for direct subject-assertion 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-use reliance, or non-use boundary.

E.24:8 - 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, C.13 for a needed inspectable construction account, and E.14/B.3.5 for elected or independently required construction-assurance coverage. Each ontic-introduction decision names any additional subject-specific subject 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 subject pattern use or claims coordinated only inside a bounded local episteme.

E.24:End

Referenced in the corpus

89 literal mentions in other sections. Read their context to establish the relation.