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 22:20:20 UTC

C.3.1 - Kind Identity and Subkind Relations (U.Kind and U.SubkindOf)

Type: Kind identity, subkind relation, and continuity pattern Status: Stable Normativity: Normative unless a section is explicitly informative

C.3.1:0 - Use This When

Use this pattern when work must recover one reusable kind, decide whether one kind is a subkind of another, or decide whether the same kind continues across a changed KindSignature edition.

What goes wrong if missed. A source or practice label becomes an identity key, U.SubkindOf carries dependency or construction, a finite sample is mistaken for a universal order, mutually classifying kinds are silently merged, or a changed declaration is treated as automatically new or automatically harmless.

What this buys. The user gets an operational kind-continuity test, a replayable subkind test, and a preorder of subkind facts distinct from declaration identity, current extension, evidence, bridging, and public naming.

Primary EntityOfConcern. One U.Kind individual recovered through its candidate domain, operative membership condition, intended member/non-member distinction, and continuity rule; or one proposed U.SubkindOf relation between kind participants within declared applicability.

First useful move. Write the two criteria so the reader can test inclusion. If this plant defines a cooling pump as a pump that circulates coolant through a heat exchanger, anything meeting that criterion already meets the pump criterion. Establish that both uses of “pump” have the same meaning. Introduce an occurrence identifier or a formal equivalence grouping only when the receiving use needs it.

Not this pattern when. Use C.3.2 for a declaration, admissibility result, candidate classification, or extension; C.3.3 only for a claimed correspondence between independently identified distinct kinds; and E.24.UK when admitting another durable public kind rather than using an already admitted U.Kind individual.

C.3.1:1 - Problem Frame

A practice/source boundary is provenance and a comparison cue. It affects the continuity decision only when comparison exposes a difference in the candidate domain or membership distinction.

U.SubkindOf is a same-individual dependent kind under U.Relation. Its participants are a narrower kind and broader kind. An effective reference scheme and aligned KindSignature editions make the criteria interpretable and qualify applicability; they are not relation participants or occurrence-identity discriminators. Candidate state, context slice, declaration edition, kind identity, and one obtaining subkind relation can therefore change for different reasons.

C.3.1:2 - Problem

The sentence cooling pump is a pump is useful only when the membership conditions justify it. A current extension table can hide a bad proposal, and different intensional kinds can happen to classify the same candidates. Conversely, a unit rewrite, source move, or clearer declaration need not create another kind. The core needs an obtaining test for the relation and a before/after test for kind continuity without treating a signature, sample, locality, or extension as the kind.

C.3.1:3 - Forces

ForceTension
Small typed reasoning vs ontology growthProjects need reusable kinds without a new public U.* name for each distinction.
Preorder vs kind identityMutual subkind facts may hold for different intensional kinds; classification equivalence must not collapse their identities.
Criterion entailment vs observed supportExact rule entailment or exhaustive evaluation of a closed domain can establish the obtaining condition; a non-exhaustive sample only supports an assertion.
Stable kind vs changing declarationA kind may continue across a compatible change, while a changed membership distinction must not inherit identity silently.
Applicability vs uncertaintyA non-applicable classification request is not an unknown judgment and cannot establish or refute a subkind fact.
Locality vs correspondenceA changed practice or source prompts comparison but does not establish another kind or a bridge.

C.3.1:4 - Core Objects

ObjectMeaningBoundary
U.KindThe admitted meta-kind whose individuals are reusable intensional classification distinctions. One individual is recovered through its candidate domain, operative membership condition, intended member/non-member distinction, and continuity rule.A KindSignature, label, source boundary, reference scheme, current extension, or receiving use is not the kind.
U.SubkindOfThe admitted direct relation kind whose occurrences relate narrower and broader U.Kind participants within declared applicability. Its obtaining facts form a preorder.It is not a predicate expression, assertion episteme, dependency, part-whole relation, construction, system-role assignment, or admission relation.
SubkindOfObtains(k1, k2)The relation-obtaining condition. It holds either because the exact membership criterion for k1 entails the criterion for k2 under an aligned interpretation and applicability, or because an exhaustive evaluation over a declared common finite domain establishes that every member of k1 there is also a member of k2 (§4.1).The first branch is criterion-based. The second is explicitly domain-bounded. Non-exhaustive observations support a separate assertion but do not make the relation obtain.
R_sub : U.SubkindOfOne obtaining relation occurrence between narrower kind k1 and broader kind k2.Use a designator only when a receiver needs it. The ordered kind participants determine occurrence identity; schemes, signatures, evidence, assertions, and publications do not.
subkind assertion epistemeA C.2.1 episteme that affirms, denies, or leaves unresolved the obtaining condition and cites its interpretation, applicability, branch, and support.The assertion does not make the relation obtain; a negative or unresolved assertion designates no obtaining occurrence.
classification equivalence for an alignmentMutual obtaining U.SubkindOf facts between two kinds within the same declared applicability.It says that the two membership distinctions classify alike there. It does not identify the kinds. A consumer that needs a partial order may order these equivalence groups.
KindSignature editionThe C.3.2 declaration episteme used to interpret and evaluate one kind.It is neither the kind nor the subkind relation.

C.3.1:4.1 - Direct U.SubkindOf Relation Boundary

A readable sentence such as CoolingPumpKind is a subkind of PumpKind for this declared plant use states that the direct relation obtains. It needs no occurrence identifier when no receiver distinguishes or refers to the occurrence.

The criterion-entailment branch compares the two membership conditions under an aligned interpretation and applicability. For the finite-domain branch, identify the complete domain to which both declarations apply and account for each candidate using the pinned editions. Every narrower member must also satisfy the broader criterion. An unresolved classification that could conceal a counterexample leaves inclusion unestablished. If the declarations apply together only on part of the proposed domain, state that smaller domain on the conclusion.

A candidate that satisfies the narrower criterion and fails the broader one refutes inclusion on the stated domain. Missing observations can leave the finite-domain test open even when the membership rules themselves suffice to prove entailment.

When a receiver needs one occurrence, R_sub is participant-determined by the ordered pair of kind identities. The effective scheme, aligned signatures, and applicability qualify how obtaining is tested and asserted.

A scheme-edition change therefore prompts an alignment and renewed test; it does not create another relation occurrence. If the same participants still satisfy the condition, the same relation continues to obtain. If they no longer do, the prior obtaining claim is no longer current; another assertion may record that change without inventing a scheme-keyed occurrence.

C.3.1:5 - Solution

  1. Recover each kind before comparing it. For each kind, state the candidate domain, membership condition, intended member/non-member contrast, and continuity rule. Use practice/source provenance to locate the declaration, not to decide identity.
  2. Check admissibility first. Compare only candidates admissible under both aligned declarations and the stated applicability. not-applicable forms no C.3.2 judgment.
  3. Select one obtaining branch. Use exact criterion entailment when the membership rules can be compared directly. Use exhaustive evaluation only for a deliberately closed finite domain. State which branch and where it applies.
  4. Keep observations in their proper role. A non-exhaustive sample, test run, or extension can support the subkind assertion and expose a counterexample. It cannot close an open-domain obtaining claim.
  5. Keep a preorder over obtaining facts. Reflexivity and transitivity apply. Mutual facts between distinct kinds record classification equivalence for that alignment; they do not imply kind identity. Use the equivalence groups only when a receiver needs a partial order.
  6. Separate relation, predicate, and assertion. Use the readable relation sentence first. Add R_sub, a C.2.1 assertion, evidence, or publication only when a named receiver consumes that object.
  7. Diagnose counterexamples at the rule. Repair a false relation proposal, incompatible declaration alignment, or missing distinct-kind bridge. Do not edit an extension row to make the order appear true.
  8. Decide kind continuity independently. Apply the before/after test in section 6 whenever criterion, candidate domain, assumptions, dependencies, effective scheme, or locality changes. Another KindSignature edition neither proves nor denies kind continuity.
  9. Keep scope and Work outside the kind. A kind carries no claim scope. A W : U.Work remains a dated work occurrence under its direct pattern; keep it distinct from a plan, log, label, classification record, or episteme about W.

C.3.1:6 - Continuity Decision

Compare the old and proposed declarations in this order:

QuestionContinuity consequence
What candidate domain and operative membership condition did the old kind use?Write at least one intended member and one relevant non-member or boundary case that exposes the discriminator.
What criterion, domain, assumption, dependency, or interpretation changed?Separate a wording, unit, source, or scheme change from a changed membership law.
Under an explicit alignment, do the old and new conditions classify the boundary probes alike for the receiving typed use, and does the operative discriminator keep the same meaning?If yes, the same kind may continue; cite the actual declaration edition in each judgment. If no, identify another kind.
Did only the practice, source, team, or publication locality change?Run the same comparison. Locality alone supplies no result and no KindBridge.
Are two distinct kinds now being related?State an obtaining U.SubkindOf fact when its criterion or closed-domain branch passes. Use C.3.3 only for a separately justified directional correspondence.

Preserving change. CoolingPumpSignature-3 replaces litres-per-second with an exactly aligned SI expression, preserves the pump candidate domain, cooling-performance discriminator, intended member and non-member probes, and maintenance use. The same CoolingPumpKind continues; new judgments cite edition 3.

Identity-breaking change. A proposed edition replaces physical cooling performance with the presence of schema label CoolingPump. A physical pump without the row changes from member to non-member and a labelled non-performing row can appear to qualify. The operative distinction and candidate domain changed; identify another kind rather than continuing CoolingPumpKind.

Locality change. Journal and grant teams may reuse one ReviewerSystemRole when candidate Systems, required contribution, and acceptance condition remain aligned. If grant review requires a different contribution or admits a materially different candidate boundary, identify another kind. The two labels decide neither case.

C.3.1:7 - Archetypal Grounding

SituationC.3.1 moveBoundary
CoolingPumpKind is below PumpKind.Use criterion entailment: the cooling-pump condition already requires the governed pump condition. State the readable relation and its applicability.Do not infer a public U.CoolingPump, and do not use current extension rows as the truth-maker.
A closed cabinet inventory contains five cabinets. Four satisfy both criteria. For the fifth, the narrower judgement is unknown and the broader is false.Inclusion on this inventory is still open. If the fifth satisfies the narrower criterion it is a counterexample. Establish its narrower classification or use a valid criterion-entailment argument.An unresolved narrower judgement in a cabinet already known to meet the broader criterion could not conceal that counterexample. Even a settled result for the five cabinets covers only this lot.
The shift qualification register and the union register identify the same people on a complete current roster.Check both criteria for every person in that roster to establish inclusion in both directions there.Qualification depends on the shift credential and union membership on enrollment. A later enrollment can change the agreement while both kinds retain their criteria.
A signature adds an aligned unit conversion.Apply section 6, keep the kind, identify the new signature edition, and retain edition-specific judgments.Do not rewrite earlier judgments as if the new edition had been used.
A signature changes from physical cooling performance to a schema label.The boundary probes expose a changed candidate domain and discriminator; identify another kind.Do not hide the mismatch by editing the extension.
Pump #14 changes state in a later plant slice.Re-evaluate the admissible candidate and allow the extension to change.Candidate-state change alone does not create a kind, signature, or relation occurrence.
InspectionWorkKind is used locally.Classify only an independently identified W : U.Work.U.Work, a plan, or a log row cannot occupy W’s candidate position.
WorkPlan depends on Work.Use the governing work or E.24.UK relation.Do not encode dependency as U.SubkindOf.
SafetyCriticalFunctionKind is proposed as a subkind of FunctionKind.First recover both function senses under A.6.F, then use exact criterion entailment or the deliberately closed-domain branch.The word function, a risk label, or current examples establish neither the kinds nor the subkind fact; another public U.* name requires E.24.UK.
A project proposes public U.CoolingPump.Take the recovered kind to E.24.UK, then apply naming patterns if admitted.Local typed use and U.SubkindOf do not admit or publish another durable kind.

C.3.1:8 - Bias-Annotation

C.3.1 counters hierarchy, sample-as-law, assertion-as-world, locality, and table-repair bias. A stronger-looking edge is not automatically an obtaining relation; a sample does not close an open domain; mutual classification does not identify two intensional kinds; a changed source does not split one; and an extension remains an output representation rather than the place to repair the rule.

C.3.1:9 - Conformance Checklist

CheckRequirement
CC-C31-1Each U.Kind individual has a recoverable candidate domain, operative membership condition, intended member/non-member boundary, and continuity rule. Practice/source provenance is a comparison cue, not an automatic identity discriminator.
CC-C31-2U.SubkindOf has ordered kind participants, declared applicability, one valid obtaining branch, and participant-determined occurrence identity.
CC-C31-2aPredicate content, C.2.1 assertion, evidence item, representation edge, scheme and signature editions, and optional occurrence designator remain distinct; none makes the relation obtain by form.
CC-C31-2bObtaining facts form a preorder. Mutual facts between distinct kinds record classification equivalence for the alignment; a partial order is formed only over equivalence groups when needed.
CC-C31-3Criterion entailment compares exact membership rules under aligned interpretation, or exhaustive evaluation covers a deliberately closed finite domain. Non-exhaustive observations support only the assertion.
CC-C31-4Only candidates admissible under both declarations enter the comparison. unknown neither establishes nor refutes a universal proposal; not-applicable forms no judgment.
CC-C31-5Reference schemes and declaration editions qualify interpretation, applicability, and assertions but do not identify the relation occurrence. An aligned edition change triggers reevaluation of the same participant-determined relation.
CC-C31-6Kind continuity uses before/after candidate-domain, membership-discriminator, member/non-member probes, and receiving-use tests; old judgments retain their cited edition.
CC-C31-7A locality change prompts the continuity test; C.3.3 is used only after two distinct kinds and a correspondence proposal exist.
CC-C31-8Scope is absent from the kind, and U.Work, one W : U.Work, and any episteme about W remain distinct.

C.3.1:10 - Common Anti-Patterns and How to Avoid Them

  • Encoding dependency, part-whole, slot filling, construction, system-role assignment, or admission as U.SubkindOf, or treating a predicate expression, assertion, diagram edge, or table row as the obtaining relation occurrence.
  • Treating a source hierarchy or public-looking spelling as durable FPF ontology.
  • Treating KindSignature as the kind or its formality as a property of the kind.
  • Assuming every signature edit makes a new kind, or that no signature edit can make one.
  • Comparing extensions across incompatible editions and repairing a counterexample by changing rows.
  • Storing claim scope on a kind.
  • Treating a work label or record as an individual work occurrence.

C.3.1:11 - Consequences

Benefits. Local typed compatibility remains small while its consequences for candidate judgments are testable.

Costs. A declaration change that matters to later classification needs an explicit edition and a separate continuity decision.

C.3.1:12 - Rationale

Kind identity, direct U.SubkindOf obtaining, assertion identity, declaration identity, candidate state, and current extension answer different questions and change under different conditions. Their separation lets a kind survive a compatible declaration revision while preventing an assertion or revised criterion from creating an order fact, silently rewriting prior classifications, or hiding a non-obtaining subkind proposal. Keeping the core small also prevents construction, admission, naming, scope, slot discipline, or dependency from being introduced into one hierarchy relation.

C.3.1:13 - SoTA-Echoing

For a subkind question restricted to a deliberately closed finite domain, the exhaustive branch in C.3.1:4.1 can suffice: check every candidate’s admissibility and evaluate those admissible under both declarations, resolving every case that could conceal a narrower member falling outside the broader kind. Requiring criterion entailment beyond that domain would demand a stronger result than this use needs. A non-exhaustive sample leaves unexamined candidates and cannot supply this warrant. Keep the domain and aligned interpretation on the conclusion; recheck it when either changes. An open-domain claim still needs criterion entailment.

C.3.1:14 - Relations

  • Specializes: A.6.REL for U.SubkindOf: ordered kind participants, criterion-entailment or exhaustive closed-domain obtaining, applicability, lightweight occurrence use, and participant-determined identity; schemes and declaration editions qualify interpretation and assertion rather than occurrence identity.
  • Builds on: C.3, A.6.0 declaration identity, C.2.1 episteme and assertion identity, A.2.6/USM context-slice and scope discipline, F-G-R, and C.2.3 formality.
  • Coordinates with: C.3.2 judgments and extensions, C.3.3 correspondence between independently identified distinct kinds, A.2 when one local kind is a system-role kind, A.6.5 declaration-slot uses that consume an already obtaining subkind relation, C.29 representations, E.24.UK durable U-kind admission, and A.8, A.11, F.8, and F.5 when public kind governance is current.
  • Other governing patterns: Use C.2.1 for subkind-assertion epistemes, whether affirmative, negative, or unresolved; candidate features, classification assertions, kind declarations, context bridges, and public naming decisions retain their own governing patterns.

C.3.1:End

Referenced in the corpus

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