| Extensibility and kernel stability | Authors need to add mechanisms while keeping kernel reference points minimal and citeable. |
| One governing definition vs cross-locus reach | Each mechanism meaning, suite change, WorkPlan planned-baseline change, wiring module, or token migration needs one governing definition while a mechanism introduction often spans suites, plans, wiring, and lexicon. |
| Didactic usability vs inspectability | Humans need clear recognition text and examples, while declarations, obligations, and pins must remain checkable at their governing loci. |
| SoTA evolution and semantic integrity | Methods evolve quickly. Mechanism meaning SHALL NOT change silently through a wiring update. |
| Local naming freedom and global reference continuity | Contexts need local labels. References must remain stable across editions and refactors. |