A.6.7:3 - Forces
-
Strict distinction (level hygiene). “many mechanisms” must not be encoded as “many realizations of one mechanism”. Violating this blurs specialization laws, mechanism-declaration invariants, and audit/crossing responsibilities.
-
Minimal specificity + kind suffix discipline (E.10). The token name should encode only what is essential: it is a description, it is about mechanisms, it is a suite. It must not capture a domain (e.g., CHR) in the Kernel name.
-
Governing spec ref centrality (CN‑Spec and CG‑Spec). Suites must cite governing spec refs as pins, not duplicate their internals, otherwise multiple competing admissibility centers arise.
-
Transport and crossing visibility discipline. A claimed semantic correspondence between different local interpretation bases needs its obtaining F.9 Bridge; a kind correspondence needs its C.3.3 basis; a plane relation retains its own defining rule. Expose the anchors required by each actual relation and receiving use. An independently governed E.18 crossing or A.21 gate retains its required bundle or gate evidence. Assess loss under the receiving-use rule; apply the model-bound penalty conditions in §4.2(2). Suites do not embed CL/Φ/Ψ/Φ_plane tables.
-
Guard vs gate separation. Mechanisms can output tri-state guard outcomes and explanations; gate decisions (including
block