FPF Reference

    Ontic Candidate Detection and First-Use Disposition

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

    About this pattern

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

    How to use this pattern

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

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

    Use this pattern when a recurring word, card, table, schema, diagram, record, draft pattern row, or field bundle looks like a new FPF subject and the author must decide what to do next.

    Relations

    E.24.CDbuilds onU.Ontic and Ontic Introduction Discipline
    E.24.CDbuilds onU-kind Admission and Ontic Settlement
    E.24.CDbuilds onU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    E.24.CDbuilds onKinds, Intent and Extent, and Typed Reasoning
    E.24.CDbuilds onU.Kind and U.SubkindOf Core
    E.24.CDbuilds onKind Intent, Membership Judgment, and Extension
    E.24.CDbuilds onOntic Description and Publication Discipline
    E.24.CDbuilds onMathematical Lens Use
    E.24.CDbuilds onDeclarative Representation Precision Restoration
    E.24.CDbuilds onRelation-Declaration Slot Discipline - SlotKind, ValueKind, RefKind, and participant-designation discipline
    E.24.CDbuilds onRelation, Signature, Interface, Role, and Slot Precision Restoration
    E.24.CDbuilds onFunction and Functional Precision Restoration (RPR-FUNCTION)
    E.24.CDbuilds onRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims
    E.24.CDbuilds onUnified Lexical Rules for FPF
    E.24.CDbuilds onWording-Use Ontological Precision Restoration Architecture
    E.24.CDbuilds onLocal-First Unification Naming Protocol
    E.24.CDcoordinates withNeeded Relation Claim Derivation and Relation-Kind Admission
    E.24.CDcoordinates withU.MultiViewDescribing - Viewpoints, Views & Correspondences
    E.24.CDcoordinates withHolon Ontic Foundation (U.Holon and Admitted Holon Kinds)
    E.24.CDcoordinates withHolon Aggregation and Part-Whole Construction
    E.24.CDcoordinates withMeta-Holon Transition — Whole Reidentification
    E.24.CDcoordinates withAdvanced Mereology: Components, Portions, Aspects & Phases
    E.24.CDcoordinates withConstructional Mereology (Compose‑CAL)
    E.24.CDcoordinates withU.Transformation: Bounded Change Under Conditions
    E.24.CDcoordinates withU.Work: Dated Performed Work Occurrence
    E.24.CDcoordinates withCausalUse-CAL: Causal-Use Questions, Causality-Ladder Rungs, Identification and Realizability
    E.24.CDcoordinates withU.Signature - Reusable Law-Governed Declaration Episteme
    E.24.CDcoordinates withProblematic-For Relation
    E.24.CDcoordinates withProblemCard
    E.24.CDcoordinates withP2W Problem-to-Work Carry-Through
    E.24.CDcoordinates withQuality Improvement Loop Method
    E.24.CDcoordinates withCharacteristicSpace & Dynamics Hook (A.CHR‑SPACE)
    E.24.CDcoordinates withEvaluation CharacteristicSpace Construction
    E.24.CDcoordinates withU.Ontic and Ontic Introduction Discipline
    E.24.CDcoordinates withU-kind Admission and Ontic Settlement
    E.24.CDcoordinates withMathematical Lens Use
    E.24.CDused byU.Ontic and Ontic Introduction Discipline
    E.24.CDoutline parentU.Ontic and Ontic Introduction Discipline
    E.24.CDoutline next siblingOntic Description and Publication Discipline
    E.24.CDexplicit referenceKinds, Intent and Extent, and Typed Reasoning
    E.24.CDexplicit referenceU.Kind and U.SubkindOf Core
    E.24.CDexplicit referenceKind Intent, Membership Judgment, and Extension
    E.24.CDexplicit referenceU.MultiViewDescribing - Viewpoints, Views & Correspondences
    E.24.CDexplicit referenceOntic Description and Publication Discipline
    E.24.CDexplicit referenceMathematical Lens Use
    E.24.CDexplicit referenceUnified Lexical Rules for FPF
    E.24.CDexplicit referenceWording-Use Ontological Precision Restoration Architecture
    E.24.CDexplicit referenceU.Ontic and Ontic Introduction Discipline
    E.24.CDexplicit referenceU-kind Admission and Ontic Settlement
    E.24.CDexplicit referenceU.Transformation: Bounded Change Under Conditions
    E.24.CDexplicit referenceU.Work: Dated Performed Work Occurrence
    E.24.CDexplicit referenceHolon Aggregation and Part-Whole Construction
    E.24.CDexplicit referenceAdvanced Mereology: Components, Portions, Aspects & Phases
    E.24.CDexplicit referenceConstructional Mereology (Compose‑CAL)
    E.24.CDexplicit referenceMeta-Holon Transition — Whole Reidentification
    E.24.CDexplicit referenceRelation, Signature, Interface, Role, and Slot Precision Restoration
    E.24.CDexplicit referenceFunction and Functional Precision Restoration (RPR-FUNCTION)
    E.24.CDexplicit referenceRelational Precision Restoration — Recovering Direct Relations from Under-Specified Claims
    E.24.CDexplicit referenceU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    E.24.CDexplicit referenceLocal-First Unification Naming Protocol
    E.24.CDexplicit referenceP2W Problem-to-Work Carry-Through
    E.24.CDexplicit referenceQuality Improvement Loop Method
    E.24.CDexplicit referenceCharacteristicSpace & Dynamics Hook (A.CHR‑SPACE)
    E.24.CDexplicit referenceEvaluation CharacteristicSpace Construction
    E.24.CDexplicit referenceDeclarative Representation Precision Restoration
    E.24.CDexplicit referenceProblemCard
    E.24.CDexplicit referenceProblematic-For Relation
    E.24.CDexplicit referenceRelation-Declaration Slot Discipline - SlotKind, ValueKind, RefKind, and participant-designation discipline
    E.24.CDexplicit referenceNeeded Relation Claim Derivation and Relation-Kind Admission
    E.24.CDexplicit referenceHolon Ontic Foundation (U.Holon and Admitted Holon Kinds)
    E.24.CDexplicit referenceCausalUse-CAL: Causal-Use Questions, Causality-Ladder Rungs, Identification and Realizability
    E.24.CDexplicit referenceU.Signature - Reusable Law-Governed Declaration Episteme

    Content

    Use This When

    Use this pattern when a recurring word, card, table, schema, diagram, record, draft pattern row, or field bundle looks like a new FPF subject and the author must decide what to do next.

    Typical moments:

    • one word such as "process", "source", "quality", "architecture", "problem", "view", "role", "function", "mechanism", or "method" points to several FPF objects or claims at once;
    • several patterns repeat a similar declaration, participant list, or relation rule;
    • a project data structure looks concept-shaped, although it may be only a claim-bearing episteme, publication form, representation, or local record;
    • a draft ToC row names a family that no current pattern yet governs;
    • a proposed U.* kind feels useful, but it may duplicate a current kind or direct relation.

    Primary EntityOfConcern. When the author records this choice in a C.2.1 episteme, its EntityOfConcern is the subject already identified under a direct pattern. If that subject cannot yet be identified, use the source episteme or expression entity whose inquiry remains open. The visible form and the note recording the disposition are not substitutes.

    First useful move. Write one plain sentence: “For this work or decision, we need to know or do <action> about <subject>.” Then ignore the wrapper long enough to recover the subject, the needed claim, and the current pattern that governs it. Apply the first truthful disposition in section 4.

    What goes wrong if missed. FPF grows shadow ontology. A table becomes a kind; a field label is mistaken for a relation-participant meaning; a filled field is treated as an actual relation participant merely because it occupies a column; a card becomes the subject; or a convenient word creates a second ontology over values and relations that already have governing patterns.

    What this buys. The author identifies one usable governing pattern without filling a candidate record or maintaining a registry. A genuine durable ontic must still pass E.24's full identity and relation test; simpler cases stop with their direct governing pattern, local classification, description or publication handling, wording repair, or a precise unresolved question.

    Not this pattern when.

    • If one existing governing pattern already states the needed claim, use it directly.
    • If a local kind, criterion, candidate judgment, or extension is already the question, use C.3, C.3.1, and C.3.2.
    • If the current question is a description episteme, use C.2.1 for its identity and the subject-specific description pattern when one applies. For view membership, publication form or occurrence, representation, or carrier, use E.17.0, E.24.PUB, or C.29.
    • If the subject and governing claim are clear and only the wording hides them, use E.10, E.10.ARCH, or the applicable precision-restoration pattern.
    • If a durable ontic has already been selected, use E.24; if a durable public U.* kind is separately at issue, use E.24.UK.
    • If the work is comparing architecture alternatives, construct the evaluation through A.19.ECS.

    Problem Frame

    An apparent ontology candidate usually arrives inside something visible: a label, form, record, diagram, source passage, or repeated field list. That visible thing may point to a real durable subject, but it may instead carry claims about several already governed objects, publish or represent them, classify them for one context, or merely use an imprecise word.

    E.24.CD governs this first-use choice before E.24 opens. It neither admits a durable ontic nor creates a candidate object of its own.

    Problem

    Without an explicit first-use disposition:

    1. Publication forms become false subjects. A card, table, or schema receives ontology authority because it is visible.
    2. Local classification hardens into public ontology. A criterion useful in one context is treated as a durable FPF kind.
    3. Direct governing patterns are bypassed. Existing methods, work, relations, epistemes, structures, sources, and results are duplicated under a new head.
    4. Wording repair becomes ontology creation. A broad word is replaced with a new broad word while the actual subject and predicate remain hidden.
    5. Candidate work becomes a registry ritual. Authors fill fields or scores for possible ontics instead of deciding the current case.

    Forces

    ForceTension
    Early recognition vs premature ontologyA recurring concern should be noticed, but recurrence alone must not mint a durable subject or U.* kind.
    Visible form vs governed subjectA form can reveal the problem while remaining an episteme, publication form, representation, carrier, or local record.
    Direct reuse vs shared coordinationExisting patterns should carry their own claims; E.24 opens only when dependent patterns need one stable subject identity and minimal relation set.
    First-use affordability vs adequate discriminationThe author needs a quick choice, but the choice must still separate direct use, local classification, publication, wording, and durable admission.
    Traceability vs registry growthA disputed choice may need one explanatory sentence; it does not need a standing candidate catalogue.

    Solution

    Start from the work that is blocked, not from the shape of the source material.

    Ask these four questions in order:

    1. What must the next person do or decide? Name the comparison, classification, publication, repair, decision, or other practical use.
    2. What is that use about? Name the subject, claim, or source expression without treating its card, row, filename, diagram, or field bundle as the answer.
    3. Which current pattern already governs the needed claim? Name the predicate or judgment that would let the work proceed.
    4. If that pattern does not close the case, what is actually missing? State one applicable pattern or one precise unresolved stop below.

    Apply the first truthful disposition

    Plain situation, incident, current configuration, operating <system>, and emergency are recognition cues, not kind names. Recover only the subjects, claims, and relations that the receiving work actually needs.

    Current needNext useStop that follows
    One current subject pattern already states the needed claim or action.Apply that direct governing pattern. If the missing piece is a relation-bearing claim that no current direct predicate closes, apply A.6.RCD before proposing a relation kind.Do not create an ontic, kind, candidate note, or disposition record. A local compound claim or predicate-definition episteme is neither a relation kind nor an occurrence; only a separately justified kind candidate proceeds through E.24 and E.24.UK.
    One exact ClaimGraph forms one claim-bearing whole about one truthful exact EntityOfConcern under one effective ReferenceScheme.Use C.2.1 to identify that episteme. Other independently governed objects may be designated inside its claims without becoming extra EntityOfConcern fields or ontic slots.If one truthful EntityOfConcern or one identity-bearing ClaimGraph cannot be recovered, keep the epistemes separate. State a collection, publication, representation, or other use relation only when its own predicate obtains; common use or co-publication does not identify one episteme.
    Wording such as situation, incident, current configuration, operating <system>, or emergency groups several cues.Recover the exact systems or holons, characteristic or state claims, actual part relations, and only the temporal or causal relations needed by the current use. Add actual U.Transformation or U.Work only when independently grounded under A.3.4 or A.15.1. Use a possible-state episteme when possibility is the subject, and a separate C.2.1 description episteme only when claim-bearing orientation is current.Their conjunction is neither U.Situation nor U.IncidentSituation. An episteme's EntityOfConcern and any grounding holon in a separately current EpistemeEmpiricalGroundingRelation neither identify the world-side subject nor become mandatory fields. Stop decomposition once the action-facing distinction needed by the receiving use is recovered.
    A proposed subject exists only as an arbitrary fusion, co-presence, connected set, or chosen boundary.Reject the bundle without forcing it through a construction record. If a constructed object survives as the current subject, apply B.1, A.14, and C.13, and apply B.2 only when whole reidentification is current; recover its exact construction inputs, whole-forming relations, and identity rule.Fusion, co-presence, connectedness, and a selected boundary alone form no durable whole. The no-mint result does not block a genuinely irreducible subject later shown to have its own identity and obtaining laws.
    Repeated typed reasoning needs a local criterion, candidate judgment, or true-candidate set for one context slice.Use C.3, C.3.1, and C.3.2.The local kind, KindSignature, judgment, and optional extension stay distinct; no public U.* kind or classification-relation occurrence follows.
    A card, record, table, diagram, file, or schema carries claims, is used as a description, conforms to a viewpoint, expresses an edition, represents something, or bears a form.Use C.2.1 to identify an episteme only when its constitution test passes. If it describes a method, structure, relation occurrence, or another subject, apply that subject's description pattern. Use E.17.0 for actual view membership, E.24.PUB for publication, and C.29 for representation and correspondence. Several patterns can apply because they govern different objects or relations.Visible shape does not identify the described subject or make any neighboring relation obtain.
    A path, table, dashboard, schema, or other declarative form seems to authorize, dispatch, prove, prescribe, or perform something by its shape.Use C.2.P.DR to name the visible expression, recover the direct object or relation, state its representation or correspondence use—or none—and block the unsupported action claim.A declarative form does not itself authorize or dispatch work, perform an action, or grant authority.
    Words such as relation, slot, field, interface, role, function, or endpoint still leave the object or claim unclear.Use A.6.RSIR, A.6.F, or A.6.P according to the ambiguity, then stop at the identified direct governing pattern.An engineering word does not create a subject kind, relation kind, participant, or declaration.
    The subject and governing claim are already clear, but a word or phrase compresses them.Repair the bounded wording through E.10, E.10.ARCH, or the applicable precision-restoration pattern.A clearer name does not create a new subject, relation, or kind.
    An already governed value needs a stable reusable name rather than a repaired sentence.Use F.18 after recovering the value, its kind and direct governing pattern, its effective reference scheme, and the local sense to be named. For relation-facing wording, settle any missing direct relation through A.6.RCD first.A label or NameCard neither admits the value or a public kind nor makes a relation obtain.
    Several named dependent patterns genuinely need one reusable subject identity and the same minimal set of direct relation rules.Open E.24 and apply its existing-governor, identity, relation, dependent-use, and non-duplication checks.E.24.CD establishes only that E.24 is the applicable next pattern. E.24 decides whether a durable ontic is admitted.
    The subject, needed claim, or governing pattern cannot yet be recovered.Keep the inquiry attached to the source expression or blocked work and name what is missing.Do not hide non-settlement inside a candidate record, score, provisional U.* name, or “future ontology” list.

    When a durable public U.* kind is also proposed, E.24.UK returns its separate admission result. If the ontic and kind are both new, use the atomic co-decision already defined by E.24 and E.24.UK; neither result proves the other.

    Recover objects hidden by a visible form

    For a project card, row, schema, or diagram, inspect only what the current work consumes:

    1. Which filled statements are claims, and what is each claim about?
    2. Which entities or non-entity values are independently identified under their direct patterns?
    3. Which direct predicates are asserted, what are their actual participants, and which independently established facts satisfy their obtaining conditions?
    4. Is the visible arrangement a publication form, a C.29 representation, a carrier, or merely a local layout?
    5. Does the work need local classification of a candidate, or only a claim about an already governed feature?
    6. What stronger reading must be blocked—for example, record existence creates performed work, a row creates membership, or a field name admits a kind?

    A field label is not a SlotSpec. A.6.5 governs the declaration: a reusable SlotSpec appears only inside a RelationSignature for an already recovered direct relation and only when a named later use needs that declaration. A row value is not an actual relation participant merely because it occupies a column.

    Apply E.24 only when several patterns need the same subject rules

    Applying E.24 is warranted only when all of these are recoverable:

    • one primary governed subject kind;
    • its direct identity, constitution, or recognition rule;
    • two or more named dependent patterns whose work depends on the same subject identity or relation rule;
    • the smallest set of independently governed direct relations those uses must keep coherent;
    • how a changed participant or direct-relation fact would change what those uses may claim, compare, rely on, repair, or stop;
    • confirmation that every already governed value keeps its own kind, identity, direct relations, and governing pattern;
    • the practical difference that this reusable coordination makes;
    • why direct-pattern use, a bounded episteme, local typed projection, publication handling, and wording repair do not close the case; and
    • the nearest case that must remain outside the proposed ontic.

    These facts tell the author to open E.24; they do not admit an ontic. Repeated words, several source forms, copied fields, or a useful schema can prompt inspection, but none substitutes for those facts.

    State one result and stop

    Most cases need only one sentence:

    For <work or decision>, apply <governing pattern> to <exact subject or claim> because <decisive fact>; <blocked stronger reading> does not follow.

    When no pattern can yet apply truthfully, say:

    For <work or decision>, leave <exact subject or claim question> unresolved because <missing subject, predicate, or governing pattern>; <blocked stronger reading> does not follow.

    Use a longer explanation only when another author must understand a disputed disposition. Do not create an OnticCandidateCluster, candidate registry, scorecard, or mandatory disposition form. Once the applicable pattern or unresolved stop is stated, continue there; reopen E.24.CD only if the recovered subject or practical use changes.

    Archetypal Grounding

    A candidate that genuinely opens E.24

    Before C.2.1, “description”, “view”, “claim set”, and “publication” repeatedly pointed to a claim-bearing object used across many patterns. The practical need was stable claim identity across description, evaluation, reference, and publication work. Existing patterns could not supply that shared identity and relation set independently.

    That case opens E.24. E.24 then decides the durable ontic; C.2.1 governs the resulting U.Episteme; E.17.0, E.24.PUB, F.18, and C.29 keep viewpoint conformance, publication, naming, and representation separate. Cards and files do not become the episteme.

    Local cooling-pump classification

    A maintenance team repeatedly asks whether Pump #14 counts as a cooling pump in plant slice S-14. Pump #14 and its flow, heat-transfer, and operating-state features already have direct governors. The needed outputs are a reusable local criterion and a candidate judgment, not a durable ontology unit.

    Apply C.3.2. A KindSignature may declare the criterion for repeated use; the judgment can be true, false, or unknown; a current extension is materialized only for a named set-consuming use. A measurement supports a claim about Pump #14's features but does not create its membership.

    Problem card

    A ProblemCard@Context under C.22.2 is a problem-side episteme. It may carry a signal, hypothesis, forecast, scenario, anticipated-condition claim, affected-entity reference, evidence cue, constraint, proposed direction, assignment cue, source reference, or gate cue without creating an actual Problem.

    An actual Problem is one obtaining ProblematicForRelation under C.22.PFR. A card may assert that exact predicate, but it may designate a current Problem occurrence only after C.22.PFR independently establishes the actual-condition relation, criterion-applicability relation, adverse truth, and occurrence identity. Signals, hypotheses, forecasts, scenarios, anticipated conditions, and reviewable formulations remain under C.22.2 or their exact forecast, scenario, temporal, or causal governor.

    For a repair decision, keep the affected entity, evidence-use relation, role assignment or other responsibility relation, source-use relation, and gate or decision claim under their direct governing patterns. Apply E.18.1, E.23, and the exact work, search, evaluation, or continuation pattern when repeated problematization or later action is current. Neither the card nor its acceptance or publication creates or ends an actual Problem. Open E.24 only if a different reusable subject-identity or relation gap remains after these direct claims are recovered; do not rediscover the actual Problem as a new ontic.

    Record-shaped false candidate

    A project schema contains:

    ChangeItem:
  status:
  owner:
  method:
  mechanism:
  evidence:
  result:
  target:
  source:

    Treat the schema as source material, not as an ontology. A proposal episteme, method, mechanism declaration, work plan, intended-work claim, performed-work occurrence, holder system, state claim, evidence item, result, affected referent, and source remain different objects. Recover only those that the meeting actually uses:

    Field cueObject and relation to recover
    ownerIdentify an admitted holder U.System, then state the exact U.RoleAssignment, responsibility, commitment, or authority relation only if its predicate obtains. The field neither assigns the holder nor grants authority.
    statusName the exact bearer and the governed state or status value, claim, gate disposition, decision result, or other current relation. Field presence implies no readiness, validity, gate passage, work authorization, or release.
    method and mechanismKeep an admitted U.Method and any qualifying U.MethodDescription distinct from the A.6.1 U.Mechanism declaration episteme and its declared operation family. If the field concerns one use, identify the exact operation application and only its declaration-local argument or result bindings that obtain. If it concerns realization, identify the realizing entity and the obtaining mechanism-realization relation. Apply [A.6.1](/generated/patterns/A.6.1) when the row does not yet distinguish these readings. Shared wording identifies none of them.
    plan, intended work, and actual workKeep a U.WorkPlan or intended-work claim under [A.15.2](/generated/patterns/A.15.2). Add a U.Work under [A.15.1](/generated/patterns/A.15.1) only for an independently grounded performed occurrence, whether ongoing with an open end or completed. A proposal, row, trace, or completion label does not make work occur.
    evidenceFirst identify what the field points to; do not rename it to fit a pattern. Keep its direct kind: an episteme or evidence record, a carrier, the work that produced or interpreted evidence, a currentness relation, or a provenance relation. If it is an episteme and the meeting asks only about its bounded evidence-use or status-use for the claim, use [A.2.4](/generated/patterns/A.2.4) first. Use [A.10](/generated/patterns/A.10) when the evidence path must be retraceable; include only the record, carrier, work, currentness relation, and provenance relation needed for this claim. Use [B.3](/generated/patterns/B.3) only when a separate assurance claim is current. The field proves neither the claim nor the row's status.
    resultIdentify the result entity, value, or result episteme independently, then state the exact production, measurement, evaluation, decision, delivery, acceptance, or other result relation actually claimed. A result label creates no generic result object or relation.
    targetIdentify the affected referent and state an exact work-to-referent, change, effect, or other subject relation only when current. The field does not make the referent a work participant or changed entity.
    sourceIdentify the source episteme or expression and the exact source-use relation. Source presence is not evidence, authority, or currentness by itself.

    Not every row has every listed object, not every filled field is claim-bearing, and co-presence in one row does not constitute a larger subject. The filled row is one C.2.1 episteme only when one exact ClaimGraph forms a claim-bearing whole about one truthful exact EntityOfConcern under one effective ReferenceScheme. Otherwise keep the epistemes separate and state only the exact collection, publication, representation, or meeting-use relation that actually obtains.

    The column arrangement is a publication form only when selected to express an identified episteme for the meeting. The form is not a U.ChangeItem, and its columns are not ontic slots. If the project later needs a local kind of records for a query, [C.3.2](/generated/patterns/C.3.2) may classify those records as records. If several FPF patterns later demonstrate a different shared durable subject with its own identity and minimal relation set, that evidence can reopen [E.24](/generated/patterns/E.24); the schema's shape cannot.

    Current configuration around a holon

    A maintenance review asks about “the current configuration around Pump #14.” Identify Pump #14 under its system governor, then recover only the characteristic or state claims, actual part relations, temporal phase, and other direct relations that the maintenance decision uses. If the work compares a possible configuration, identify the possible-state episteme and its direct state or configuration claims rather than asserting current actuality.

    A separate C.2.1 description episteme may provide claim-bearing orientation. Its exact EntityOfConcern and any grounding holon in a separately current EpistemeEmpiricalGroundingRelation neither identify Pump #14 nor turn the surrounding claims into one world-side object. The holon and those current relations answer the question; their conjunction is not U.Situation.

    Operating pump with connected parts

    Pump #14 is operating while a sensor, valve, and controller are connected. Operating first cues a governed state claim; it does not establish U.Work or U.Transformation. Connectedness does not establish parthood. Identify the pump and connected entities, state the exact connection relations, and use A.14 only for part relations whose predicates actually obtain.

    Add a dated maintenance or control-work occurrence under A.15.1 only when its performer, assignment, method enactment, temporal extent, and other required facts are independently grounded. Add an actual bounded change under A.3.4 only when its changed referent, boundary, conditions, and change facts obtain. No bundle of system, state, connection, work, and change becomes a situation entity.

    Multi-party emergency

    An emergency report mentions a leaking vessel, an overheated subsystem, a suppression system, and response teams. Recover each participating system, each independently grounded actual change, and each dated response-work occurrence separately. State temporal relations through their temporal governors and a causal relation through C.28 only when that causal-use claim is current and supported.

    Use a C.2.1 emergency-description episteme only when the receiving work needs claim-bearing orientation across those objects. The emergency word, the record, and the co-presence of several systems and works identify neither U.IncidentSituation nor another bundled whole. Stop decomposition once the response decision has the exact subjects and relations it needs.

    Mathematical inconsistency under a declared formal substrate

    Two specification epistemes state constraints that cannot both hold under one declared FormalSubstrate and applicability. Identify the exact claims or epistemes, name that formal substrate, and state the exact inconsistency or consequence relation under its direct formal governor. Use C.29 only when the formalism is also being used as a mathematical lens for another declared use.

    The formal relation may guide a later decision or repair-work occurrence, but it establishes no project-world event, work, transformation, causal relation, adverse episode, actual Problem, or situation entity. Formal consequence is not causation. Inconsistent descriptions do not make their world-side subjects inconsistent without a separately governed bridge claim. If the exact relation or substrate cannot be named, leave the formal claim unresolved rather than letting the word inconsistency stand for it.

    Architecture diagram

    An architecture diagram may carry claims about selected structures of one holon. If the diagram is selected as one claim-bearing whole, C.2.1 identifies that episteme. The same episteme has U.View membership only when E.17.0 conformance obtains; its publication form and carrier use E.24.PUB; selected graphical elements use C.29 only with explicit correspondence to independently recovered objects.

    The diagram does not become the architecture, structure, or ontic by being visible. If the current work is simply to correct one architectural claim, apply the architecture and structure patterns directly.

    Broad source word

    A source says that a method “supports” production. If the author can recover a specific required-effect, method-use, work-enactment, capability, evidence-use, or other direct claim, apply its governing pattern. If the source word still compresses several claims, use E.10 and E.10.ARCH to retain it only with its bounded meaning or in quote-only or reduced use.

    Do not open E.24 merely because support recurs, and do not invent SupportRelation as the candidate.

    Score table and characteristic space

    A score table can serve as the publication form of an evaluation-result episteme over a U.CharacteristicSpace, or it may be only a local report. Use A.19 when the characteristic space itself must be identified and A.19.ECS when the work is constructing the evaluation characteristics for a contested comparison. Use C.29 when readers calculate, compare, infer, navigate, or inspect through the table's mathematical structure and those available operations matter.

    The table does not admit U.CharacteristicSpace by appearance and does not require another candidate ontology beside the current A.19 governing pattern.

    Bias-Annotation

    Lenses tested: Onto, Arch, Epist, Prag, Did.

    This pattern intentionally biases toward early recovery of the real subject and the blocked work. It resists:

    • publication-form bias: treating a card, schema, table, or record as the subject matter;
    • wording bias: treating a repeated word as a kind or relation decision;
    • registry bias: collecting possible ontics instead of disposing the current case;
    • scoring bias: rating a candidate before its subject, identity rule, direct relations, and practical use are known;
    • semio-bias: discussing forms and labels while the governed subject and claim disappear.

    The mitigation is concrete: name the work, subject, needed claim, pattern that states it, applicable disposition, and blocked stronger reading. Open E.24 only when several named patterns need the same subject identity or relation rules.

    Conformance Checklist

    CheckRequirement
    CC-E24CD-1The first-use disposition starts with a recognizable work or decision and the subject or claim that blocks it.
    CC-E24CD-2A visible card, row, schema, diagram, filename, or field bundle is not treated as the subject merely by form.
    CC-E24CD-3Independently governed objects and direct predicates are recovered before a new ontic or kind is proposed.
    CC-E24CD-4A current direct governing pattern is applied when it already closes the needed claim. A relation-bearing claim that no current predicate closes goes through A.6.RCD; a local compound claim or predicate-definition episteme is not thereby a relation kind or occurrence.
    CC-E24CD-5One C.2.1 episteme requires one exact ClaimGraph, one truthful exact EntityOfConcern, and one effective ReferenceScheme. Otherwise epistemes remain separate, and co-use or co-publication supplies no shared identity.
    CC-E24CD-6Local classification uses C.3.2's kind, signature, judgment, and optional extension distinction and does not imply a public U.* kind or direct classification relation.
    CC-E24CD-7Episteme, view membership, publication form, representation, carrier, and publication occurrence remain separate and use their governing patterns only when current.
    CC-E24CD-8Applying E.24 requires one primary subject kind, identity rule, dependent uses, minimal direct-relation set, practical gain, rejected simpler applications, and nearest non-use.
    CC-E24CD-9Any public U-kind question is handled by E.24.UK as a separate admission result; E.24.CD admits neither ontic nor kind.
    CC-E24CD-10No candidate cluster, registry, scorecard, or mandatory disposition form is created.
    CC-E24CD-11The result names the exact pattern applied to the exact subject or claim, or a precise unresolved stop, and blocks the strongest tempting overread.
    CC-E24CD-12A record-shaped false candidate keeps holder, status bearer and value, method, mechanism, plan, work, evidence item and use, result and relation, target and subject relation, and source and source-use relation distinct; absent fields and row shape establish none of them.
    CC-E24CD-13Ambiguous relation, slot, interface, role, function, and endpoint wording uses the matching precision-restoration pattern instead of becoming ontology.
    CC-E24CD-14Declarative-form agency is blocked through C.2.P.DR, and reusable naming starts in F.18 only after the governed value and any needed relation settlement are available.
    CC-E24CD-15Wording such as situation, incident, current configuration, operating <system>, or emergency recovers only the exact systems, claims, work, change, and temporal or causal relations needed by the current use; their conjunction creates neither U.Situation nor U.IncidentSituation.
    CC-E24CD-16Arbitrary fusion, co-presence, connectedness, or a chosen boundary creates no whole. Only a surviving constructed-object candidate is tested for exact inputs, whole-forming relations, and identity under B.1, A.14, C.13, and B.2 when reidentification is current.
    CC-E24CD-17Mathematical inconsistency names exact claims or epistemes, the declared formal substrate, and the direct inconsistency or consequence relation; it establishes no world event, causation, Work, Transformation, Problem, or situation.
    CC-E24CD-18A ProblemCard, signal, forecast, scenario, formulation, actual Problem, and later problematization or work remain under C.22.2, C.22.PFR, and their exact continuation governors rather than one card-derived ontic.

    Common Anti-Patterns and How to Avoid Them

    Anti-patternSymptomRepair
    Card-to-kind jumpA useful card is promoted into a U.* kind because it has repeated fields.Recover its claims, subject, form, and carrier; use C.2.1 or E.24.PUB as triggered.
    Structural U-kind jumpA heading, title, filename, or ToC row keeps U.* because the spelling is convenient.Recover the subject and use E.24.UK for the admission question; naming follows the result.
    Column-to-participant jumpA field label is treated as a relation-participant meaning, or a filled field as an actual participant; either is called a SlotSpec because of column position.Recover the direct predicate, its relation-participant meanings, and its actual participants first. Keep the field as a representation element or participant designation; under A.6.5, declare a SlotSpec only inside a needed RelationSignature for that already recovered relation.
    One-word candidateA broad word is renamed and treated as settled.Recover the subject and predicate; use E.10 and E.10.ARCH when only wording remains.
    Local-kind inflationA useful project criterion is promoted to durable public ontology.Use C.3.2 and keep the local kind, declaration, judgment, and extension distinct.
    Registry trapThe author keeps a list of possible ontics without deciding the blocked case.State the work, apply one truthful governing pattern or name one precise unresolved stop, and stop.
    Scoring before identityA score form is filled before the subject and direct relation gap are known.Recover the subject, identity rule, dependent uses, and missing coordination; use A.19.ECS only for an actual comparison.
    Repetition-as-admissionSeveral forms or patterns share a label, so an ontic is inferred.Require the E.24 entry facts: one subject identity and minimal relation set reused by named dependent patterns.
    Negative-catalogue repairThe text lists only what the candidate is not.State the positive subject, claim, governor, next action, and one blocked stronger reading.

    Consequences

    Positive consequences:

    • authors reach a governing pattern from a recognizable work situation;
    • durable ontics are proposed from an identity and reuse gap rather than from form or vocabulary;
    • local classification, claim coordination, publication, representation, and wording remain cheaper dispositions;
    • cards, records, tables, and schemas remain useful source material and detection cues without becoming ontology by appearance;
    • no candidate registry or score ritual is added to routine authoring.

    Costs:

    • the author must recover the subject and needed claim before choosing a governing pattern or unresolved stop;
    • some attractive names are lowered to local kinds, source wording, epistemes, publication forms, or representations;
    • a genuine durable candidate still requires the full E.24 decision and, when current, a separate E.24.UK admission result.

    Rationale

    Ontic candidates rarely arrive as pure ontology. They appear through the forms people use: project tables, cards, schemas, diagrams, source packets, draft rows, examples, and repeated words. Those forms reveal working concerns, but they do not decide what exists, what relation obtains, or what FPF kind is needed.

    The pattern therefore asks for one first-use disposition instead of a candidate record. Keep direct claims in their direct patterns; use C.2.1 only when one exact ClaimGraph, one truthful EntityOfConcern, and one effective ReferenceScheme constitute an episteme; and use C.3.2 for local classification. Keep publication in E.24.PUB and representation in C.29. Use C.2.P.DR to block action inferred from declarative form; resolve ambiguous wording through A.6.RSIR, A.6.F, A.6.P, or E.10; and name only an already governed value through F.18. Open E.24 only when named dependent patterns need one stable subject identity and minimal relation set that those simpler applications cannot preserve.

    This order keeps the first move affordable and falsifiable. Another author can see which fact selected the applicable pattern or unresolved stop and which stronger reading was blocked. A list of candidate fields or scores would make the form look authoritative and invite optimization of the record instead of settlement of the subject.

    SoTA-Echoing

    Source familyCurrent lesson for E.24.CDFPF decision
    Shimizu and Hitzler 2024, and Eells, Dave, Hitzler, and Shimizu 2024.Current modular-ontology and micropattern work favors ontology units that are understandable, extensible, aligned, reusable, and small enough to assemble.Inspect repeated subject identity and direct-relation rules across named dependent uses; do not treat word frequency, common nouns, or record fields as admission evidence.
    Norouzi, Hertling, Waitelonis, and Sack 2025.Current process-ontology ODP extraction work shows that process-like and workflow-like forms can expose implicit design patterns that domain experts need to examine.Recover the objects and predicates hidden by process, record, card, and field-list forms and check them against their governing patterns; do not reopen transformation-flow decisions or import imperative motion metaphors.
    Nayyeri et al. 2025, and Oyewale and Soru 2026.Current data-model-to-ontology and enterprise-KG work shows that schemas, documentation, relations, provenance, and validation can reveal ontology candidates while also encouraging schema-shaped overreads.Treat project databases, tables, schemas, and enterprise data models as source material and detection cues for selecting the applicable governing pattern, not as ontology decisions; require bounded scope, agreement with each current governing pattern, and expert validation.
    CYC microtheory line.Lineage-only caution: context-bounded knowledge modules are a useful analogy for contradiction locality and scope-bounded ontology fragments.Do not cite CYC as current decisive support for FPF ontic design and do not import CYC architecture as FPF law.
    OWL, SKOS, RDF, and triple-store practice.Infrastructure and expression lineage: these lines carry ontology descriptions, vocabulary links, queries, and serialization forms.Use them as expression and publication caution only; they do not substitute for U.Ontic, do not show that labels are ontology, and do not answer FPF ontic modularization by themselves.

    Smallest source-currentness reopen trigger: reopen this SoTA slice when a newer ontology-engineering or data-model-to-ontology source changes the selected criteria for reusable subject identity, minimal relation sets, bounded scope, validation, or source-form overread; do not reopen it merely because a new vocabulary, serialization, or KG tool appears.

    Relations

    • Builds on: E.24 for durable ontic settlement; E.24.UK for separate public U-kind admission; C.2.1 for exact episteme constitution; C.3, C.3.1, and C.3.2 for local typed projection; E.24.PUB for publication; C.29 and C.2.P.DR for representation and declarative-form overread; A.6.5 for SlotSpec declaration and participant-designation discipline; A.6.RSIR, A.6.F, A.6.P, E.10, and E.10.ARCH for bounded ambiguity repair; and F.18 for naming after the governed value is settled.
    • Coordinates with: A.6.RCD when the missing piece is a relation-bearing claim that no current direct predicate closes. A local compound claim or predicate-definition episteme is neither a relation kind nor an occurrence; only a separately justified kind candidate proceeds through E.24 and E.24.UK. It also coordinates with E.17.0 for actual view membership; A.1, B.1, B.2, A.14, and C.13 for a surviving constructed-whole question; A.3.4, A.15.1, the temporal patterns, and C.28 for actual change, work, temporal, and causal claims; A.6.0 and C.29 for formal-substrate and mathematical-lens use; C.22.PFR, C.22.2, E.18.1, and E.23 for actual Problem, problem-side formulation, and later problematization; A.19 for U.CharacteristicSpace; and A.19.ECS for evaluation-characteristic construction.
    • Used by: DRRs and authoring work that must decide whether a recurring construct uses an existing governing pattern, remains one or several bounded epistemes, becomes a local typed projection, applies description or publication handling, receives wording repair, opens E.24, or remains unresolved.

    E.24.CD:End

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