FPF Reference

    Kinds, Intent and Extent, and Typed Reasoning

    C.3 · Cluster C.I - Core CALs / LOGs / CHRs · Stable · Typed reasoning discipline pattern · Normative unless a section is explicitly informative · Part C - Kernel Extension Specifications

    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: Typed reasoning discipline pattern Status: Stable Normativity: Normative unless a section is explicitly informative

    Use this pattern when a claim needs a context-local kind, a subkind order, a judgment about whether one exact candidate satisfies one local kind, or an optional representation of the candidates that satisfy it in one exact context slice.

    Keywords

    • bounded-context local kind
    • intent-bearing KindSignature
    • effective ReferenceScheme
    • three-valued candidate judgment
    • optional slice-indexed extension
    • SubkindOf
    • KindBridge.

    Relations

    C.3builds onHolon Ontic Foundation (U.Holon and Admitted Holon Kinds)
    C.3builds onUnified Scope Mechanism (USM): Context Slices & Scopes
    C.3builds onU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    C.3coordinates withU.Kind and U.SubkindOf Core
    C.3coordinates withKind Intent, Membership Judgment, and Extension
    C.3coordinates withKindBridge & CL^k — Cross-context Mapping of Kinds
    C.3coordinates withU-kind Admission and Ontic Settlement
    C.3coordinates withAlignment and Bridge across Contexts
    C.3builds onU.Signature - Reusable Law-Governed Declaration Episteme
    C.3coordinates withKindAT — Intentional Abstraction Facet for Kinds (K0…K3)
    C.3coordinates withTyped Guard Macros for Kinds + USM (Annex)
    C.3coordinates withMathematical Lens Use
    C.3coordinates withUniversal Core Principle
    C.3coordinates withOntological Parsimony
    C.3coordinates withMint-or-Reuse Decision
    C.3coordinates withLocal-First Unification Naming Protocol
    C.3coordinates withConstraint-Governed Unfolding Structure
    C.3coordinates withKinds, Intent and Extent, and Typed Reasoning
    C.3coordinates withConsequence-Guided Ontological Problem Solving
    C.3coordinates withAdvanced Mereology: Components, Portions, Aspects & Phases
    C.3coordinates withUnified Scope Mechanism (USM): Context Slices & Scopes
    C.3coordinates withU.Ontic and Ontic Introduction Discipline
    C.3outline childU.Kind and U.SubkindOf Core
    C.3outline childKind Intent, Membership Judgment, and Extension
    C.3outline childKindBridge & CL^k — Cross-context Mapping of Kinds
    C.3outline childRoleMask — Contextual Adaptation of Kinds (without cloning)
    C.3outline childKindAT — Intentional Abstraction Facet for Kinds (K0…K3)
    C.3outline childTyped Guard Macros for Kinds + USM (Annex)
    C.3explicit referenceUnified Scope Mechanism (USM): Context Slices & Scopes
    C.3explicit referenceMathematical Lens Use
    C.3explicit referenceU.Kind and U.SubkindOf Core
    C.3explicit referenceKind Intent, Membership Judgment, and Extension
    C.3explicit referenceU.Signature - Reusable Law-Governed Declaration Episteme
    C.3explicit referenceU.Episteme: Constitution, Empirical Grounding, and Edition Relations
    C.3explicit referenceKindBridge & CL^k — Cross-context Mapping of Kinds
    C.3explicit referenceAlignment and Bridge across Contexts
    C.3explicit referenceWorking-Model Relations & Grounding (CT2R-LOG)
    C.3explicit referenceConstraint-Governed Unfolding Structure
    C.3explicit referenceU-kind Admission and Ontic Settlement
    C.3explicit referenceKindAT — Intentional Abstraction Facet for Kinds (K0…K3)
    C.3explicit referenceTyped Guard Macros for Kinds + USM (Annex)
    C.3explicit referenceUniversal Core Principle
    C.3explicit referenceOntological Parsimony
    C.3explicit referenceMint-or-Reuse Decision
    C.3explicit referenceLocal-First Unification Naming Protocol
    C.3explicit referenceConsequence-Guided Ontological Problem Solving
    C.3explicit referenceAdvanced Mereology: Components, Portions, Aspects & Phases
    C.3explicit referenceU.Ontic and Ontic Introduction Discipline

    Content

    Use This When

    Use this pattern when a claim needs a context-local kind, a subkind order, a judgment about whether one exact candidate satisfies one local kind, or an optional representation of the candidates that satisfy it in one exact context slice.

    What goes wrong if missed. A source type, local category, programming class, schema label, mathematical set, or public U.* name starts doing several jobs at once. The kind is confused with its declaration, evidence is treated as membership, an unavailable fact becomes false, a current extension becomes ontology, or claim scope is stored on the kind.

    What this buys. Typed reasoning stays usable without premature ontology growth. A practitioner can recover the local kind, the declaration used to classify, one three-valued judgment, and any optional extension representation while leaving direct world-side features, evidence, scope, work, and durable U-kind admission with their own governors.

    Primary EntityOfConcern. One typed-reasoning question: the exact context-local U.Kind, any U.SubkindOf order needed by the claim, and the C.3.2 classification question the use actually asks. The exact KindSignature edition used for that question carries the effective U.ReferenceScheme in its claim content; the scheme is not stored on the kind.

    First useful move. Write the ordinary conclusion first. For example: Pump #14 counts as a cooling pump in this plant slice because it satisfies the declared cooling-pump criterion. Add a reusable declaration, explicit judgment details, evidence reference, or extension representation only when a named receiving use needs it.

    Not this pattern when. Use E.24.UK when the question is durable public FPF U-kind admission. Use the direct subject pattern when the question is whether a physical quality, relation, construction, work occurrence, or other world-side feature obtains. Use A.2.6 for claim, work, or publication scope and C.29 for a claim-bearing mathematical representation.

    Problem Frame

    Across source ontologies, reference schemes, and project slices, "type" can mean ontology class, programming type, schema shape, category, source label, local kind, or public FPF U-kind. C.3 provides the smaller typed-reasoning architecture. A context-local U.Kind can be used now without being promoted to a durable public kind; its declared intent, candidate judgment, current extension representation, and the scope of any assertion remain separate objects.

    Start with locality, not coordinates. If a typed claim crosses from one U.BoundedContext to another, check the source and target local kinds through C.3.3 even when both contexts cite the same reference-scheme edition or observationally equivalent slices: different authority, membership law, or institutional meaning can still change what counts. A C.3.3 KindBridge relates the exact source and target local kinds. When the crossing also changes local vocabulary or interpretation, an F.9 Bridge relates the corresponding SenseCells; it does not map or change a U.ReferenceScheme as a whole. Within one context, a changed effective reference scheme identifies another KindSignature episteme edition, after which C.3.1 decides kind continuity. A U.ContextSlice only selects the classification and KindExtension evaluation; changing the slice alone creates neither a new semantic locality nor a bridge.

    Problem

    A project often needs classification before it needs ontology governance. If the kind, its definition, the classified candidate, a record about the candidate, and a displayed set of current members are treated as one object, several false conclusions follow: a label classifies by itself, evidence creates the feature it reports, missing evidence proves non-membership, a table becomes an entity set, or a plan row becomes actual work. C.3 keeps each conclusion at its direct owner.

    Forces

    ForceTension
    Local typed reasoning vs public ontology growthA project needs typed claims now, but not every useful local kind deserves a durable FPF U.* name.
    Kind vs declarationA kind must remain usable across compatible declaration editions without becoming identical to the episteme that declares its criterion.
    Truth vs supportDirect candidate features make classification true or false; evidence can support an assertion about those features but cannot create them.
    False vs unknownA known failed criterion differs from missing evidence, unavailable dependency, or out-of-domain input.
    Extent vs ontologyA set of true members can be useful for a query without becoming a collection holon, entity-set kind, or direct relation occurrence.
    Scope vs kindA claim can have narrow scope without creating a narrower kind or storing scope on the kind.
    Formal discipline vs ordinary useRepeated typed use may need a declaration; one readable case should not require a card or extension table.

    Four Objects and Their Owners

    Keep these four objects separately recoverable:

    ObjectMeaningDirect owner
    context-local U.Kind and U.SubkindOf orderThe kind value used by the typed-reasoning claim and its local partial order.C.3 and C.3.1
    KindSignatureOne U.Signature declaration episteme whose exact EntityOfConcern is the local kind and whose claim content declares the candidate ValueKind, criterion, slice conditions, reference scheme, assumptions, dependencies, formality, and any current ExtentRule. It is neither the kind nor another root U-kind.C.3.2, A.6.0, and C.2.1
    classification judgmentOne evaluation for an exact candidate, local kind, signature edition, and context slice with result true, false, or unknown. It is not a direct relation occurrence by default.C.3.2
    KindExtension(k, slice)An optional set-valued representation of the declared candidates whose judgment is true for the fixed signature edition and slice.C.3.2, with C.29 when the representation changes a claim-bearing use

    Scope is not a fifth part of the kind. A KindSignature episteme may carry its own U.ClaimScope, and a separate classification assertion carries the scope of that assertion. The U.ContextSlice is an explicit input to the judgment.

    Solution

    Use the lightest object that answers the current typed-reasoning question.

    1. Recover the local kind. Name its bounded context and the local identity basis by which later claims can refer to the same kind. Do not store the current use, claim scope, or effective U.ReferenceScheme on the kind. A local U.Kind is not automatically a durable FPF U-kind.
    2. Use C.3.1 for order and continuity. U.SubkindOf is a partial order over local kinds. C.3.1 also decides whether the same local kind continues when a declaration edition changes.
    3. Use C.3.2 for declaration and judgment. A repeated criterion may justify a KindSignature whose claim content pins the effective U.ReferenceScheme; one application judges an exact candidate against one exact edition in one exact slice.
    4. Let direct features decide. Direct qualities, relations, constructive grounding, or other governed candidate features make the criterion hold or fail. Measurements, observations, schemas, sources, and evidence support claims about those features; they do not constitute membership.
    5. Keep three results. A satisfied criterion gives true; a known failed criterion gives false; missing evidence, an unavailable declared dependency, or an out-of-domain candidate gives unknown. A guard may decline use on unknown without changing that judgment to false.
    6. Materialize an extension only for use. A query, quantification, comparison, or review may need KindExtension(k, slice). The representation contains the true candidates for the fixed signature edition and slice; notation, rows, or set membership do not create an ontic collection or classification relation.
    7. Keep scope, formality, and work separate. Formality characterizes the declaration episteme. Scope belongs to claims or capabilities. U.Work is the admitted U-kind; W : U.Work is one independently grounded, world-side, dated 4D work occurrence; a plan, log, card, field bundle, or database row about W is a separate episteme. No kind symbol or record occupies an individual-occurrence position.

    Typed reasoning composes with F-G-R and USM in this order: recover typed compatibility and the exact judgment; separately check claim-scope coverage; then apply evidence, assurance, freshness, and bridge consequences when the receiving use requires them.

    Decision Split

    Current questionGoverning pattern
    What local kind does this claim quantify over?C.3 and C.3.1
    Is one local kind a subkind of another, or does the same kind continue across a declaration change?C.3.1
    Does this exact candidate satisfy this local kind under this declaration edition and context slice?C.3.2
    Does a receiving use need the represented set of true members?C.3.2; C.29 when the representation itself changes a claim-bearing use
    Does the assertion hold in a target slice?A.2.6 for its U.ClaimScope; do not attach that scope to the kind
    Does a typed claim cross into another bounded context?C.3.3 for the KindBridge between the exact local kinds; add F.9 only when the local senses also need alignment
    Did only the effective reference scheme change within one bounded context?C.3.2 for another KindSignature edition and C.3.1 for the same-kind continuity decision; the scheme change alone is not a context bridge
    Did only the context slice change?C.3.2 for another judgment input and possible KindExtension; the slice change alone is not a context bridge
    Is the local kind being proposed as a durable public FPF U.* kind?E.24.UK, followed by the applicable naming patterns
    Is a candidate, quality, relation, construction, or work occurrence being identified?The direct subject pattern; C.3 consumes the governed result and does not create it

    When typed reasoning is part of a structural construction-to-representation passage from a constructive representation or working model to a target kind or logical representation, cite StructuralCT2RTypingGroundingUnfoldingStructureBlock from B.3.5. C.3 contributes only the local kind, judgment, subkind, and bridge loci inside that B.3.5-governed local A.22.CGUS specialization. It does not create separate unfolding-structure authority and does not make a constructive trace, working-model relation, proof, evidence relation, or classification true by label. For a general diagnostic return from an inadequate working account to the exact subject construction, use A.7.1; classification remains one possible locus rather than a general ontology-return method.

    The unfolding is admitted only when the block names the starting representation, target kind or logical representation, current bridge when one is used, preserved structure, lost or collapsed structure, CL or CL^k, admissible reuse, blocked substitution, and the proof or evidence governing pattern when that stronger claim is current.

    Archetypal Grounding

    SituationC.3 typed-reasoning moveBoundary
    Pump #14 is evaluated as a cooling pump.Use one local kind, one declared criterion, one exact plant slice, and one true/false/unknown judgment.The pump and its cooling, flow, and measured-state facts remain under direct physical and measurement governors.
    A maintenance episteme is classified while PDF and HTML forms circulate.Judge the exact episteme against the local kind criterion.Publication form and carrier do not decide membership.
    A temperature value is classified into an interval.Keep the value under its unit and measurement interpretation and judge the value directly.Do not fabricate a value-shaped entity merely to classify it.
    A schema labels a row Customer.Treat the label as a cue to recover the actual candidate and criterion.Schema spelling alone yields neither true nor a public U-kind.
    A measurement required by a criterion is unavailable.Return unknown; let a safety guard decline the use separately.Do not coerce missing information to false.
    A log row is labelled inspection work.First identify any exact dated W : U.Work under A.15.1; only then can W be a candidate for a local kind.The row, plan, or label is not W, and U.Work never occupies W's individual position.

    Bias-Annotation

    C.3 counters lexical bias, document bias, and ontology-growth bias. A familiar type word or schema label does not supply the declared criterion. A record or evidence item does not create the candidate feature. A displayed set does not create a collection holon. The mitigation is the four-object split, direct-feature judgment, three-valued result, and progressive elaboration from one readable sentence.

    Conformance Checklist

    CheckRequirement
    CC-C3-1The local U.Kind and any U.SubkindOf order remain distinct from durable FPF U-kind admission.
    CC-C3-2Kind, KindSignature, classification judgment, and optional KindExtension are separately recoverable; the effective reference scheme is claim content of the exact signature edition, not a property stored on the kind.
    CC-C3-3The judgment names an exact candidate, kind, signature edition, context slice, and one of true, false, or unknown.
    CC-C3-4Direct governed candidate features decide classification; evidence or representation does not create membership.
    CC-C3-5Missing evidence, unavailable dependency, and out-of-domain input yield unknown, not false.
    CC-C3-6Kind scope is absent; declaration and assertion scopes remain on their own epistemes, and U.ContextSlice remains an evaluation input.
    CC-C3-7An extension is a representation of true candidates, not U.EntitySet, A.14 MemberOf, a collection holon, or a direct relation occurrence.
    CC-C3-8Public U.* admission uses E.24.UK; cross-context kind use uses C.3.3.
    CC-C3-9U.Work, an exact W : U.Work, and any episteme about W remain distinct.
    CC-C3-10Bounded-context locality is the outer cross-context trigger: a shared scheme or equivalent slices do not remove it, while a scheme-edition or slice change inside one context does not create it.

    Common Anti-Patterns and How to Avoid Them

    • Treating a programming type, schema class, source ontology class, regulatory category, or ordinary noun as a durable public FPF U-kind.
    • Treating a KindSignature as the kind, or attaching its formality and claim scope to the kind.
    • Using A.14 MemberOf or minting a classification relation merely to state one judgment.
    • Treating evidence availability, a schema row, or a publication form as the fact that makes classification true.
    • Returning false when the criterion cannot be evaluated.
    • Treating KindExtension or mathematical set notation as ontology.
    • Repairing a subkind counterexample by silently changing an extension table.
    • Treating a plan or work record as a dated work occurrence.

    Consequences

    Benefits. C.3 supports local typed claims, subkind reasoning, classification, and queryable extensions without premature ontology growth or evidence-created membership.

    Costs. Repeated uses must pin a declaration edition and context slice, and receiving uses must distinguish false from unknown.

    Risks avoided. False sameness, implicit time, scope-on-kind, record ontology, accidental relation minting, kind/individual substitution, and mathematical-set overread are blocked at the first use.

    Rationale

    The kind, its declaration, one classification judgment, and a representation of current true members answer different engineering questions and change for different reasons. Keeping them separate lets a kind continue across compatible declaration revisions, lets candidate state change an extension without changing the kind, and lets evidence or a guard change reliance without rewriting the world-side classification.

    SoTA-Echoing

    Model theory, type systems, ontology engineering, and schema practice distinguish intensional declarations, candidate evaluation, extensions, and assertion scope. C.3 adapts that separation to FPF's object discipline: declaration epistemes follow A.6.0 and C.2.1, context slices and claim scope follow A.2.6, mathematical representations follow C.29, and durable kind admission follows E.24.UK.

    Detail Map

    C.3 is the head pattern for typed reasoning. It leaves each detailed mechanism at its direct neighboring pattern while preserving a discoverable route to that mechanism.

    Needed detailGoverning locusContent carried there
    Local kind order and continuityC.3.1U.Kind, U.SubkindOf, partial-order law, judgment monotonicity, and continuity across signature editions.
    Declaration, candidate judgment, and extensionC.3.2KindSignature, exact four-key judgment, true/false/unknown, optional KindExtension, and scope/formality/evidence boundaries.
    Cross-context kind useC.3.3The direct KindBridge relation between exact source and target local kinds, its separate bridge-assertion episteme, declared preservation and loss, and target-context reevaluation under the exact target KindSignature edition.
    Local adaptation without cloning a kindC.3.4A RoleMask declaration episteme, its pinned base-kind judgment and additional candidate-feature constraints, the exact three-valued masked judgment, and any separately declared cross-context adapter.
    Abstraction facetC.3.5KindAT as an editorial planning facet on one exact local kind, with no effect on the kind, declaration, judgment, extension, bridge assessment, guard, or F–G–R.
    Typed guards and applied examplesC.3.ADeclaration-level kind compatibility and exact candidate-use judgments kept separate across regulatory, assurance, ESG, and Method–Work uses, including the independently grounded actual W : U.Work boundary.

    Do not treat this compact head pattern as the whole C.3 discipline when a case needs declaration, classification, extension, bridge, mask, abstraction, or applied-guard detail. Use the neighboring C.3 pattern that governs the live detail.

    Relations

    • Builds on: A.2.6 context-slice and scope discipline, A.6.0 reusable declaration discipline, C.2.1 episteme identity, F-G-R, and direct subject patterns for candidate features.
    • Coordinates with: C.3.1 through C.3.5, C.3.A, C.29, E.24.UK, A.8, A.11, F.8, F.18, and generic A.22.CGUS when typed reasoning is one locus in an admitted unfolding structure; coordinates with StructuralCT2RTypingGroundingUnfoldingStructureBlock only when C.3 supplies local-kind, judgment, subkind, and bridge loci inside a structural construction-to-typed/logical projection, with any cross-context bridge remaining a bridge within that projection rather than an alternative trigger; coordinates with A.7.1 for a general diagnostic return.
    • Does not replace: direct candidate-feature ontology, A.14 collection membership, A.2.6 scope, C.29 representation use, ontic settlement in E.24, U-kind admission in E.24.UK, or naming in Part F.

    C.3:End

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