E.10:8.2 - Inadmissible suffixes and the DevOps, Data Governance and Repository-Workflow Lexical Firewall

M-F (Inadmissible in Kernel tokens). KernelToken names do not use …Function, …Process, …Task, or …Activity. These are ambiguous or vacuous; recover the object through section 6 before naming it: one U.Method, one qualifying U.MethodDescription, one Work occurrence admitted under U.Work, or another accepted recovered value. The source suffix alone selects none.

M-FW (Tool and file markers). Abstract Kernel names do not acquire incidental tool or file suffixes such as …API, …JSON or …YAML. Keep those implementation designations in their local glossary or operational source. A rule governing a named concrete publication form, protocol or grammar may quote its necessary designation or syntax under E.5.1, with the edition/use boundary. Such a quoted subject designation is not thereby a new universal KernelToken. This distinction preserves exact subject rules without importing a data-management ontology.