Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:50:20 UTC

E.20:2 - Problem

Without an explicit authoring protocol, introducing a mechanism or mechanism family can cause five problems:

  1. Governing-definition ambiguity causes partial changes: a suite enumerates a new MechanismDefinitionRef, but that designator has no resolvable A.6.1 U.Mechanism episteme or resolves only to a card-shaped placeholder without mechanism identity and content.
  2. Boundary erosion occurs: suite descriptions start to define mechanism semantics; method wiring starts to redefine kernel meaning; publication/telemetry becomes a hidden tail.
  3. Plan/enactment confusion appears: planned slot fillings start to carry launch values, witnesses, or gate decisions.
  4. Terminology drift breaks citations: renames happen silently; tokens fragment across registers; downstream references become unstable.
  5. Review becomes non‑local: reviewers must piece together each introduction across several patterns, making training, review, and refresh unreliable.