E.10:7.2 - KernelToken — Minimal Generality (MG‑K)

MG-K1 (Tri-domain witness). A DRR note or Glossary note provides at least three heterogeneous arenas where the invariants hold, for example manufacturing, healthcare, and cloud operations. Otherwise reject or narrow the KernelToken candidate and recover each word or qualifier under the object and rule that define it. Use a ContextToken only after the exact local source, practice, scheme, meaning, and receiving use are recovered. Use an A.19 CharacteristicSpace only when one named U.Characteristic, one declared CSLC scale, and the exact receiving use make that construction current; an assignment-state relation remains under A.2.5. MG-K2 (No parochial nouns). Kernel names contain no domain nouns such as Ticket, Microservice, Patient, or Developer. Domain-looking wording is a recovery trigger, not a destination: it may denote a C.3 local kind, exact system-role kind, system-role assignment, system or architecture object, episteme or record kind, declared Characteristic and scale, source wording, ordinary qualifier, recovered local-use ContextToken, or another value whose kind and use are already defined. Bare role has no default Tech reading. SystemRole appears only inside a concrete local kind designation admitted through C.3 and A.2; lexical shape alone creates neither that kind nor an assignment. MG-K3 (No vacuity). Avoid vacuous heads such as Thing, Event, Process, or Resource. Use existing U-kind heads such as U.Holon, U.Work, and U.Method. MG-K4 (Intent after recovery). U-kind names and labels for an exact local system-role kind or its F.4 SystemRoleKindDescription encode recovered semantic intent rather than notation, implementation, or local-realizer accidents. Algorithm, hardware-form, and recipe-flavor wording is a recovery trigger, not one ontological family: name one U.Method, qualifying U.MethodDescription, qualified holder-ability claim under A.2.2, U.Mechanism, system or architecture object, A.19 CharacteristicSpace, A.2.5 SystemRoleAssignmentStateRelation, C.29 representation, formal substrate, source wording, or another value only when the predicate for that value is satisfied. Do not use Capability, CharacteristicSpace, assignment-state relation, or mechanism as disposal bins for unlike cases. MG‑K5 (Notation independence, SHOULD). The EntityOfConcern-side kind criterion is separable from any one notation or toolchain. MG-K6 (Refactoring safety). If a name fails MG, record a DRR and apply F.13 Lexical Continuity and Deprecation rather than mutating it silently.