CC-C32-1 | Kind, KindSignature, pre-judgment admissibility, admissible three-valued judgment, and optional extension remain separately recoverable. |
CC-C32-2 | The signature’s EntityOfConcern is the kind, and its content names candidate ValueKind/domain, criterion, applicability, scheme, assumptions, dependencies, formality, and any extent rule. |
CC-C32-3 | Candidate mismatch or slice outside applicability yields not-applicable and no judgment; only admissible requests return true, false, or unknown. |
CC-C32-4 | The directly governed condition named by the criterion decides satisfaction. Evidentiary use alone does not constitute an independently governed condition; an episteme, relation, status, or publication occurrence may be the condition when its direct pattern says so. |
CC-C32-5 | Missing support or unavailable dependency for an admissible request yields unknown, distinct from known false. |
CC-C32-6 | No world-side collection-belonging claim, U.EntitySet, collection holon, or direct classification occurrence is inferred from judgment or extension. |
CC-C32-7 | A separate classification assertion is a C.2.1 episteme and creates neither candidate nor kind. |
CC-C32-8 | Subkind checks compare admissible judgments and use C.3.1’s criterion-entailment or exhaustive closed-domain branch; samples only support an assertion. |
CC-C32-9 | Locality change triggers kind-definition comparison. Only independently identified distinct kinds with an obtaining correspondence use C.3.3; receiving judgments remain fresh. |
CC-C32-10 | The kind carries no scope; the slice is an evaluation input and declaration/assertion scopes stay on their epistemes. |
CC-C32-11 | Physical, episteme/publication, value, schema, unavailable-support, not-applicable, registration-status, and Work cases respect the same architecture. |
CC-C32-12 | Ordinary use stays readable, and declarations or extensions appear only for named receiving uses. |