C.3.2:0 - Use This When
Use this pattern when repeated typed reasoning needs one explicit kind criterion, when one exact entity or non-entity value must first be checked as applicable and then judged against that criterion in one context slice, or when a named use needs a representation of the candidates currently judged true.
What goes wrong if missed. A kind is confused with its declaration, a practice label splits one kind, a measurement or schema label creates membership, an out-of-domain request becomes unknown, missing information becomes false, a set becomes ontology, or a guard decision rewrites the classification.
What this buys. A practitioner can state an ordinary result, pin the declaration and slice when reliance requires it, distinguish not-applicable from true, false, and unknown, and materialize an extension only for a receiving query or review. A manager can separately change declaration formality, assurance for a relied-on assertion, or claim scope without treating them as one maturity ladder.
Primary EntityOfConcern. One classification use: exact candidate, kind, KindSignature edition, context slice, pre-judgment admissibility, and—only when admissible—the judgment value.
First useful move. Write the readable result first: Pump #14 counts as a cooling pump in this plant slice because it satisfies the declared cooling-pump condition. Before evaluating, confirm that a pump candidate and this slice are within the declaration’s candidate domain and applicability. Cite support only when the receiving use relies on it; create a reusable signature or extension only for repeated or set-consuming use.
Not this pattern when. Use the direct subject pattern to establish the candidate and the exact quality, relation, episteme, status, publication occurrence, or other condition named by the criterion; A.14 for membership in a collection; C.3.3 for a claimed correspondence between distinct kinds; C.29 for a claim-bearing mathematical representation; and E.24.UK for admission of another durable public kind.