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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 21:55:20 UTC

C.3 - Kinds, Intent and Extent, and Typed Reasoning

Type: Typed reasoning discipline pattern Status: Stable Normativity: Normative unless a section is explicitly informative

C.3:0 - 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: For this plant’s operating report, a cooling pump is a pump circulating coolant through the heat exchanger during the reporting interval. The circuit connections and the interval’s flow reading establish that Pump #14 did so. 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.

C.3:1 - 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.

C.3:2 - 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.

C.3:3 - Forces

ForceTension
Bounded typed use vs public ontology growthA project needs typed claims now, but not every useful kind needs its own durable public U.* name.
Kind vs declarationA kind can continue across compatible declaration editions without becoming identical to the episteme that declares its criterion.
Identity vs localityA changed practice or source warns that the membership distinction may differ, but cannot prove sameness or difference.
Admissibility vs uncertaintyAn ill-typed or out-of-applicability request must not look like an admissible candidate whose relevant facts are unsettled.
Condition vs evidentiary useThe governed condition named by the criterion makes membership hold; an item’s use as evidence alone does not. The criterion may itself concern an episteme, status, or relation.
Extent vs ontologyA set of true members can serve a query without becoming a collection holon, entity-set kind, or direct classification relation.
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.

C.3:4 - Four Objects and a Pre-judgment Check

Keep these four objects separately recoverable:

ObjectMeaningSubject pattern
U.Kind individual and any U.SubkindOf factsOne intensional classification distinction, recovered through its candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule. U.SubkindOf facts form a preorder; mutually obtaining facts state classification equivalence for the declared alignment and do not merge kind identities.C.3, C.3.1, and accepted E.24.UK results for U.Kind and U.SubkindOf
KindSignatureOne U.Signature declaration episteme whose exact EntityOfConcern is the kind and whose claim content declares candidate ValueKind, criterion, applicability, reference scheme, assumptions, dependencies, formality, and any current ExtentRule.C.3.2, A.6.0, and C.2.1
classification judgmentOne evaluation for an admissible exact candidate, 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 candidates whose admissible judgment is true for the fixed signature edition and slice.C.3.2; C.29 when a separate mathematical representation or transfer issue affects the use

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. For an admissible candidate, return unknown when the available grounds leave the criterion unsettled.

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.

C.3:5 - 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. For this catalogue, suppose a stool is a seat designed for one person, with neither back nor arms. To classify a seat, inspect those features. To count stools in the May delivery, identify its units and apply the catalogue criterion to each. A list of two confirmed stools settles the total only if the delivery inventory and classifications account for every possible member. 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.

  1. 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.
  2. Use C.3.1 for subkind and continuity. A U.SubkindOf fact 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.
  3. Use C.3.2 for declaration and admissible judgment. A repeated condition may justify a KindSignature. First check candidate ValueKind and applicability. Only an admissible application returns true, false, or unknown.
  4. 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.
  5. Keep four outcomes distinct. not-applicable means the judgment should not be formed. For an admissible candidate, a satisfied criterion gives true, a known failed criterion gives false, and an unsettled criterion gives unknown. Missing facts elsewhere in a compound criterion leave an independently settled result intact. A guard may decline use without rewriting any of these results.
  6. Materialize an extension only for use. A query, quantification, comparison, or review may need KindExtension(k, slice). It represents admissible candidates judged true; notation, rows, or set membership do not create an ontic collection or classification relation.
  7. Keep scope, formality, Work, and publication separate. Formality characterizes the declaration episteme. Scope belongs to claims or capabilities. U.Work is a kind and W : U.Work is 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.

C.3:6 - Decision Split

Current questionSubject pattern
What kind does this claim quantify over, and what makes it the same kind later?C.3 and C.3.1; use candidate domain, membership distinction, and continuity rule
Does one kind count as a subkind of another for this declared applicability?C.3.1; distinguish criterion entailment, exhaustive closed-domain evaluation, classification equivalence, and kind identity
May this candidate be evaluated under this declaration and slice?C.3.2 admissibility; not-applicable forms no three-valued judgment
Does this admissible candidate satisfy this kind under this declaration edition and slice?C.3.2 returns true, false, or unknown
Does a receiving use need the represented set of true members?C.3.2; C.29 when a separate mathematical representation or transfer issue affects the use
Does the target slice belong to the assertion’s declared claim scope?A.2.6 for its U.ClaimScope; do not attach that scope to the kind
Did the practice, source, team, or other locality change?Compare exact kind definitions. Reuse the same kind when its distinction continues. Use C.3.3 only after two distinct kinds and a proposed correspondence are independently present
Did only the declaration’s effective reference scheme change?C.2.1 for another episteme and the separate edition-continuity test; A.6.0 and C.3.2 for signature qualification; C.3.1 for kind continuity and any renewed subkind test; the scheme is not a kind or relation-occurrence identity key
Did only the context slice change?C.3.2 for another applicability check, judgment input, and possible extension; the slice alone creates no bridge
Is this kind proposed as another durable public FPF U.* kind?E.24.UK, followed by applicable naming patterns
Is a candidate, quality, relation, construction, episteme, status, publication occurrence, or Work being identified?Its direct subject pattern; C.3 consumes that result and does not create it by classification notation

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.

C.3:7 - 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 by its instruction content while PDF and HTML forms circulate.Judge the exact episteme against the local kind criterion.Changing only publication form or carrier leaves this content-based judgment unchanged.
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 candidate and criterion.Schema spelling alone yields neither true nor a public U-kind.
A flow reading is missing for a criterion that requires both operation and adequate flow.If the pump was off, return false. If it was running and the available facts leave its flow undecided, return unknown.A guard can decline either result. Record the classification separately.
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.

C.3:8 - 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.

C.3:9 - Conformance Checklist

CheckRequirement
CC-C3-1U.Kind and U.SubkindOf rely on exact accepted E.24.UK results; another public kind name requires its own admission.
CC-C3-2Kind, KindSignature, admissibility result, admissible three-valued judgment, and optional extension remain distinct; scheme and locality are not stored on the kind.
CC-C3-3Kind identity is tested through candidate domain, membership distinction, intended member/non-member boundary, and continuity rule. A practice/source change is a comparison cue, not proof.
CC-C3-4Candidate and slice applicability is checked before judgment; not-applicable is distinct from admissible unknown.
CC-C3-5The governed condition named by the criterion decides membership. Evidentiary use alone does not constitute an independent condition, while directly criterion-bearing epistemes, statuses, and relations keep their own governors.
CC-C3-6Subkind facts follow C.3.1’s criterion-entailment or exhaustive closed-domain branch and form a preorder; classification equivalence does not merge kind identities.
CC-C3-7Kind scope is absent; declaration and assertion scopes remain on their epistemes, and the slice remains an evaluation input.
CC-C3-8An extension is a representation of admissible true candidates, not U.EntitySet, a world-side collection-belonging claim, a collection holon, or a direct relation occurrence.
CC-C3-9C.3.3 is used only after distinct kinds and a proposed correspondence are independently established; same-kind reuse requires a fresh receiving judgment when the receiving use is candidate-bearing.
CC-C3-10U.Work, exact W : U.Work, and any episteme about W remain distinct.

C.3:10 - 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 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 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.

C.3:11 - 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.

C.3:12 - 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.

C.3:13 - 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.

C.3:14 - 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 detailDirect locusContent carried there
Kind identity, subkind relation, and continuityC.3.1admitted U.Kind and U.SubkindOf, criterion-entailment or exhaustive closed-domain obtaining, preorder and classification equivalence, participant-determined relation identity, and operational before/after continuity.
Declaration, candidate judgment, and extensionC.3.2KindSignature, exact four-key judgment, true/false/unknown, optional KindExtension, and scope/formality/evidence boundaries.
Cross-local kind useC.3.3identity comparison first; same-kind reuse without a bridge; for distinct kinds, an obtaining directional KindBridge, its separate assertion, preservation/loss, and a fresh admissible receiving judgment when the receiving use is candidate-bearing.
Local adaptation without cloning a kindC.3.4A KindUseAdaptationDeclaration for one named local use of an exact base kind, its pinned base-kind judgment and additional candidate-feature constraints, the exact three-valued KindUseAdaptationJudgment, and any separately declared KindUseAdaptationCorrespondenceDeclaration between two exact adaptation declarations.
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.

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.

C.3:15 - 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 and F.18. B.3.5:4.1 provides 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. Use A.7.1 for a general diagnostic return to the subject construction.
  • 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

Referenced in the corpus

210 literal mentions in other sections. Read their context to establish the relation.