A.2.6:9 - Lexical Discipline (Part E compliance)

L‑USM‑1 (names). Use Claim scope (G) for epistemes, Work scope for capabilities, and Publication scope for publication views or forms. Use Scope for the common extensional scope value. Avoid naming any characteristic as “applicability,” “envelope,” “generality,” “capability envelope,” or “validity”.

L‑USM‑2 (Work and Run). Prefer Work and Run vocabulary from A.15 for system execution contexts. Do not introduce “operation” or “operating” as characteristic names; use Work scope.

L‑USM‑3 (Validation). “Validation/Validate” remain reserved for LA in assurance lanes (Part B). Do not name a scope object “validity”.

L-USM-4 (Domain). “Domain” is a recognition cue, not a guard input. Name the exact U.ContextSlice selectors needed by the membership predicate.

L-USM-5 (First mention). On first use in a pattern or working instruction, write “Claim scope (G)” so the F-G-R meaning is recoverable.