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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 22:54:38 UTC

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.