E.24:5 - Archetypal Grounding

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

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

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

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. The point of this archetype is not that all such subjects are one kind. The E.24 decision instead settles the status of the cross-pattern subject before patterns rely on it.

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

A source-driven use closes only after the exact expression remains linked to what was carried forward. For example, a source expression workflow may have source-use status quote-only while its ontology disposition is direct subject-assertion use of one recovered U.MethodDescription under the A.3.2 rule content and one selected TransformationFlowStructure under the E.18 rule content. 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 exact 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 exact Pump #37 will be serviced that week. The decision’s EntityOfConcern remains Line7WorkflowInquiry_v1; its BoundedEpistemeResult points to Pump37WorkflowScheduling_v1, whose own EntityOfConcern is exact Pump #37 under C.2.1. 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, typed-connectivity-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.

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

For another broad head such as system, relation, or architecture, 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.