E.10:7.5a - Lexical prerequisites for a durable token

Mentioning LEX.TokenClass, LEX.Reserved-Names, or LEX.AllowedScopes does not create the values needed to admit a durable token. Before a NameCard can become current, the selected FPFCoreReferenceScheme must resolve four things: (1) the U.NameToken; (2) its current TokenClass classification assertion; (3) the current reserved-name or other authoritative collision-set value and the collision result; and (4) the current allowed-scope policy and a passing use-scope assertion. A prose example, full-text absence, heading, registry-shaped table, or intended policy supplies none of them by implication.

Worked near-miss. Suppose SelectedRuleContentSubgraphDesignation, derivedUsingRuleContent, and evaluatedAgainstRuleContent are proposed as KernelToken candidates. They can pass the tri-domain and object-of-talk tests through assembly-rule content selected in manufacturing derivation, protocol content used in healthcare derivation while evidence separately warrants case facts, and deployment-policy content selected for cloud release evaluation while service-provision Work and operational support remain separate. Even if their spellings do not collide in the inspected corpus, corpus absence is not a reserved-name or allowed-scope result. Do not publish their F.18 NameCards or F.17 rows until all four prerequisites resolve; a placeholder card or row closes none of them.

Using these names as candidate designators in declaration content changes no predicate semantics and does not admit them as public names, enumerations, Characteristics, CharacteristicSpace values, relation kinds, or U-kinds.