E.10:7.5 - Compatibility with USM (how tokens and scopes meet)
To check a mint, rename or use of a token, identify its class and the conditions of this particular LexicalAct, including the register and publication setting required by the policy. AllowedScopes(c) supplies the policy for token class c.
For one use, test whether its U.ContextSlice belongs to a scope admitted by that policy under A.2.6. To authorize use throughout a proposed scope, show that the policy covers every proposed slice. For a policy that explicitly requires registration of the exact scope, also check the corresponding registry entry. An unresolved test supplies no permission to use the token.
The LEX registry defines AllowedScopes(c) (for example, KernelToken use in normative kernel constraints is admitted; Plain-register use outside a glossary is restricted; a locally scoped use under another scheme requires its own valid designation rule and does not gain a Bridge by alias alone).
Audit. Violations are flagged as SCR‑LEX‑Sxx (see acceptance tests below).