Kinds, Intent and Extent, and Typed Reasoning
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 reusable kind, a subkind comparison, a judgment about whether one exact candidate satisfies one kind, or an optional representation of the candidates that satisfy it in one exact context slice. A kind may be used locally without receiving its own public U.* name; “local” describes the bounded use, not an identity component.
Keywords
- admitted U.Kind individual
- membership distinction
- KindSignature
- admissibility
- true/false/unknown judgment
- optional extension
- SubkindOf preorder
- distinct-kind KindBridge.
Relations
B.3.5:4.1Content
Use This When
Use this pattern when a claim needs a reusable kind, a subkind comparison, a judgment about whether one exact candidate satisfies one kind, or an optional representation of the candidates that satisfy it in one exact context slice. A kind may be used locally without receiving its own public U.* name; “local” describes the bounded use, not an identity component.
What goes wrong if missed. A source type, practice label, programming class, schema label, mathematical set, or public U.* name starts doing several jobs at once. A source boundary splits one unchanged kind; several kinds inside one source collapse; the kind is confused with its declaration; evidence is treated as membership; a non-applicable request becomes unknown; or a current extension becomes ontology.
What this buys. A practitioner can classify an admissible candidate under a known kind without confusing the kind, its declaration and the judgment. A represented set of current members remains available when a query needs it; the conditions being classified retain their own rules.
Primary EntityOfConcern. One typed-reasoning question: the exact U.Kind individual, its intended candidate domain and membership distinction, any U.SubkindOf comparison needed by the claim, and the C.3.2 candidate question the use asks. The exact KindSignature edition makes its effective designation and interpretation rules recoverable; the scheme and practice/source provenance are 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 condition. Add a reusable declaration, admissibility detail, explicit judgment, support reference, or extension representation only when a named receiving use needs it.
Not this pattern when. Use E.24.UK when the question is admission of another durable public FPF U-kind. Use the direct subject pattern when the question is whether a physical quality, relation, registration, certification, publication occurrence, Work, or other governed condition obtains. Use A.2.6 for claim, work, or publication scope and C.29 when a separate mathematical representation or transfer question remains.
Problem Frame
U.Kind is the admitted meta-kind whose individuals are reusable intensional classification distinctions. One kind individual is recovered by its declared candidate domain, the membership condition that distinguishes intended members from non-members, and the continuity rule for a material declaration change. A KindSignature states that content for repeated use but is not the kind itself. A current extension can change while the kind continues, and two different intensional kinds can happen to classify the same current candidates.
A practice, source, team, or locality tells a reviewer where meaning may have changed. It does not decide kind identity. When a typed use moves, compare the exact membership distinctions. Reuse the same kind when the candidate domain and operative distinction continue. If they differ, identify two kinds; only then can C.3.3 ask whether an exact directional KindBridge obtains.
When local wording or interpretation also differs, F.9 may relate the corresponding F.17 cells, but it neither creates the kinds nor maps a reference scheme as a whole.
A change to the declaration's effective reference scheme identifies another episteme under C.2.1. Judge its U.Signature membership under A.6.0 and its KindSignature qualification under C.3.2 separately; call it another edition only when the C.2.1 EpistemeEditionRelation obtains. C.3.1 separately decides kind continuity. A changed U.ContextSlice alone creates neither a kind nor a bridge.
Problem
A project often needs classification before it needs another public ontology name. 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, a label classifies by itself, evidence availability is mistaken for criterion satisfaction, missing information proves non-membership, a table becomes an entity set, or a plan row becomes actual Work. If locality is made an identity key, the same kind also fragments across teams and sources. C.3 keeps each conclusion at its direct pattern.
Forces
Four Objects and a Pre-judgment Check
Keep these four objects separately recoverable:
Before the judgment, C.3.2 returns admissible or not-applicable. Candidate mismatch with the declared ValueKind, or a slice outside declared applicability, is not-applicable and no three-valued judgment is formed. Missing support or an unavailable dependency for an admissible candidate instead yields unknown.
The kind does not carry scope. 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 evaluation input.
Solution
Use the lightest object that answers the current typed-reasoning question.
First identify what the sentence lets the recipient do. “Repair this stool” designates an item. “Which seats count as stools in this catalogue?” calls for a membership criterion. “Count the stools in the May delivery” also requires identification of the delivery and the units present. A furniture specification can concern a design used for many units. A product family groups models on a stated basis. A membership claim about a kind, identification of an individual and inclusion in such a family require their own grounds. A catalogue row or plural noun can help locate the question. Neither supplies those grounds by itself. F.19:4.3.1 explains how to retain the distinction in working prose.
- Recover the kind. Name the candidate domain and the operative membership distinction: what an intended member must satisfy and what separates a relevant non-member. Record the continuity rule used when that distinction changes. Keep practice/source provenance as a cue to compare definitions, not as an automatic identity key. Do not store the current use, ClaimScope, context slice, or reference scheme on the kind.
- Use C.3.1 for subkind and continuity. A
U.SubkindOffact obtains through exact criterion entailment under an aligned interpretation or through exhaustive evaluation over a deliberately closed finite domain. The facts form a preorder. Opposite facts between distinct kinds may express classification equivalence for that applicability; a consumer may order the resulting equivalence groups without identifying the kinds. - Use C.3.2 for declaration and admissible judgment. A repeated condition may justify a
KindSignature. First check candidateValueKindand applicability. Only an admissible application returnstrue,false, orunknown. - Let the governed criterion condition decide. A direct quality, relation, construction, episteme, registration, certification, publication occurrence, legal status, or other governed condition makes the criterion hold when the criterion names it. An observation, record, or source used merely as evidence does not constitute an independently governed condition. Use each condition's direct pattern.
- Keep four outcomes distinct.
not-applicablemeans the judgment should not be formed. For an admissible candidate, a satisfied criterion givestrue, a known failed criterion givesfalse, and missing support or an unavailable required dependency givesunknown. A guard may decline use without rewriting any of these results. - Materialize an extension only for use. A query, quantification, comparison, or review may need
KindExtension(k, slice). It represents admissible candidates judgedtrue; notation, rows, or set membership do not create an ontic collection or classification relation. - Keep scope, formality, Work, and publication separate. Formality characterizes the declaration episteme. Scope belongs to claims or capabilities.
U.Workis a kind andW : U.Workis one independently grounded dated work occurrence. Plans, logs, cards, field bundles, carriers, and rows remain their own objects.
Typed reasoning composes with F-G-R and USM in this order: recover kind compatibility; check claim-scope coverage; when the receiving use is candidate-bearing, check classification admissibility and, when admissible, the exact judgment; then apply support, assurance, freshness, and any justified bridge consequence required by the receiver.
Decision Split
When a constructive trace or working model and a target kind or logical representation must be inspected together, explain their correspondence.
The account identifies the source and typed or logical target, what the passage preserves or loses, and the supported reuse with its substitution limits. Name an F.9 Bridge or C.3.3 kind correspondence when the use claims or consumes one. Supply CL or CL^k when the consumed assurance or calibration account requires it. Evidence and proof retain their own subject patterns; a changed slice or notation alone supplies no Bridge.
B.3.5:4.1 provides an optional block for recording that account. C.3 supplies the kind, admissibility, judgment, subkind and kind-correspondence content needed. Use A.22 when the receiving question needs a selected structure, and A.22.CGUS for a remaining question about potential continuations and their conditions; test any required formal qualification under that pattern. For general diagnostic recovery of a subject construction from an inadequate account, use A.7.1.
Archetypal Grounding
Bias-Annotation
C.3 counters lexical, locality, document, and ontology-growth bias. A familiar word, source label, or practice boundary supplies neither kind identity nor membership. A record used as evidence does not create an independently governed condition, while an episteme, status, or relation directly named by the criterion keeps its own governor. The kind/declaration/admissibility/judgment/extension split and the readable first move keep the remedy usable.
Conformance Checklist
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
KindSignatureas the kind, or attaching its formality and claim scope to the kind. - Using a world-side belongs-to predicate or minting a classification relation merely to state one judgment.
- Treating evidence availability, a schema row, or a publication form as sufficient for classification when the criterion requires a different governed condition.
- Returning
falsewhen the criterion cannot be evaluated. - Treating
KindExtensionor 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. Reliance-bearing uses must recover the kind distinction, pin the declaration and slice, check admissibility, and keep not-applicable, false, and unknown distinct.
Rationale
The kind, its declaration, pre-judgment admissibility, one classification judgment when admissible, 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 changing what makes the criterion hold.
SoTA-Echoing
For one supported classification, the ordinary conclusion in C.3:0 can be sufficient. Creating a reusable declaration and an extension for every such answer adds products that the receiver may not consume. Keep the criterion, admissibility and needed support recoverable in the lighter answer. Add the corresponding declaration or extension when repeated interpretation or a set-consuming question needs it.
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.
When a case needs detail on declaration, classification, extension, Bridge, kind-use adaptation, abstraction, or applied guards, use the neighboring C.3 pattern that defines or constrains that detail.
Relations
- Builds on:
A.2.6context-slice and scope discipline,A.6.0reusable declaration discipline,C.2.1episteme identity, F-G-R, and direct subject patterns for candidate features. - Coordinates with:
C.3.1throughC.3.5,C.3.A,C.29,E.24.UK,A.8,A.11,F.8andF.18.B.3.5:4.1provides an optional record when constructional and typed or logical content must be inspected together; use A.22 for a needed structure selection and A.22.CGUS for a remaining continuation question or required qualification. UseA.7.1for a general diagnostic return to the subject construction. - Does not replace: direct candidate-feature ontology, A.14 collection membership,
A.2.6scope,C.29representation use, ontic settlement inE.24, U-kind admission inE.24.UK, or naming in Part F.
C.3:End
Last Updated: 2026-10-12 — this section last modified in upstream FPF commit 6c31cd80 (github.com/ailev/FPF)