| Mechanism semantics in A.6.1, effects-handler practice, and refinement-style declaration discipline require an explicit operation, law, admission, and applicability locus. | U.Mechanism identity is <content, EntityOfConcernRef, effectiveReferenceScheme>; direct subject and range fields, operation algebra, laws, admission conditions, Applicability, and an optional dependency manifest are identity-bearing content. Each reused operation carries declaration-local argument and result declarations; an operation index may be derived from operation designators, while A.6.5 SlotSpecs remain RelationSignature content and realization, bridge, evaluation, evidence-use, and publication relations remain neighboring. | When a mechanism is introduced or changed, make the A.6.1 declaration target resolvable before suites, plans, or wiring cite it; state each operation member in its exact operation declaration and handle every neighboring claim under its direct pattern. | Treating suite vocabulary, wiring prose, a card layout, or a MIP manifest as mechanism semantics. |
| SoTA method evolution is carried by SoTA synthesis packs, shipping boundaries, and refresh wiring rather than silent kernel mutation. | Use G.2, G.10, and G.11 for method-evolution apparatus: SoTA packs, release/shipping boundary, and refresh wiring. If the SoTA change alters mechanism meaning, the mechanism-governing definition changes. Current-source examples are usable only through named pack refs, such as SLSA v1.2 for provenance and attestation discipline, RO-Crate 1.2 for research-package publication discipline, QDax JMLR 2024 for QD-library practice, or a named current domain survey or source when that domain claim is present. | Tie a mechanism-changing SoTA update to the SoTA pack or source ref named by value and the refresh or shipping locus, then edit the mechanism-subject pattern if semantics changed. | Rephrasing a fashionable method update as kernel semantics or hiding it in wiring. |
| Open-ended and set-valued method evolution may return candidate sets, archives, or selector outputs. | C.18, C.19, and G.5 preserve set-return and selection boundaries; MIP must not force one approved mechanism too early. | Keep candidate mechanisms, selected sets, abstain/reject states, and archive semantics in their receiving loci until a mechanism-governing definition is actually selected for introduction. | Collapsing open-ended exploration or selector output into one prematurely approved mechanism. |
| Mechanism-related refresh uses explicit pins and trigger kinds rather than restating method semantics. | G.11-style refresh uses edition pins, policy pins, PathSliceId, and RSCR trigger kinds; refresh wiring enables comparable reruns but does not redefine the method. | When a mechanism change affects refresh, name the pins and RSCR trigger kinds and keep method semantics in the mechanism or SoTA-pack locus. | Letting refresh wiring become a second method definition. |
| Stable identifiers and modular vocabularies preserve reference continuity. | Names, aliases, lexicons, and stable identifiers preserve citeability; they do not establish mechanism law, admissibility, evidence, or gate fit. Mechanism meaning and admissibility belong in definitions, signature, law, and admissibility patterns, suite boundaries, SoTA packs, and wiring modules according to their exact use named by value. | Use alias docking and lexicon updates to preserve references, then return mechanism meaning to the definition that supplies it. | Treating ontology or vocabulary modularity as sufficient mechanism introduction. |