E.10:8.4 - Morphology tests (apply with § 7 MG-DA)

M‑1 (Kind-side test). The candidate fits one admitted kind or one side in the Strict Distinction lattice (EntityOfConcern ≠ Description episteme ≠ publication carrier; exact local system-role kind ≠ U.SystemRoleAssignment occurrence ≠ Method ≠ Work). If not, rename or split.

M-2 (Classified-kind anchoring). The head noun names the classified FPF kind or exact subject construction: exact local system-role kind, U.SystemRoleAssignment occurrence, Method, Work, Characteristic, Capability, constraint claim, U.Commitment, publication form, service-access relation, service-offer record, exact source or practice boundary, local-use designation, or another direct FPF value. Bare role first uses E.10.ROLE; no free-floating metaphor, bare Service, bare Context, or bare Requirement head passes by lexical shape.

M-3 (Family congruence). Where eligibility clarity is needed, add the exact subject-specific characteristic or SystemRoleAssignmentStateRelation as a separate qualifier for the current value; do not hide either in a system-role-kind name. Do not turn standards, requirements, evidence, or status labels into ...SystemRole names, and do not fake families with bare metaphors such as RowPlane, senseFamily, or ...Lane.

M‑4 (Run and description split). Use Work only for executions. Treat recipe, code, diagram step, procedure, or document form as recognition evidence only: classify a claim-bearing episteme as U.MethodDescription only when its exact EntityOfConcern is one admitted U.Method and its claims pass the A.3.2 substantive-description threshold; keep the method, representation, publication form, plan, and Work occurrence separate.

M-5 (Kernel parochiality). KernelToken names carry no domain nouns. Recover domain markers under the objects and rules that define them. Use ContextToken only after the exact local source, practice, scheme, meaning, and receiving use are recovered; use A.19 CharacteristicSpace only after its named U.Characteristic, declared CSLC scale, and exact receiving use are current; use A.2.5 SystemRoleAssignmentStateRelation only when that direct predicate obtains. Lexical shape establishes none of them.

M‑6 (Vacuity ban). Avoid vacuous heads (Thing, Event, Process, Resource). Use established U-kind heads such as U.Holon, U.Work, and U.Method.

M-7 (Notation independence). The EntityOfConcern-side meaning survives notation and tool swaps.

M-8 (Collision and uniqueness). Before merge, perform full-text and Reserved-Names checks; a token colliding with another FPF meaning is not admitted (cf. MG-DA-T5).