E.20:4.6 - Step 6: Suite integration (if the mechanism is a suite member)
If the introduction changes a suite (MechSuiteDescription or specialization):
- Membership set semantics (WF‑MS‑1).
mechanismsis a set: duplicates are nonconformant and list order carries no semantics. - Ordering is only in protocols. Express any order that matters in
suite_protocols. - Protocol closure (WF‑MS‑2). Apply A.6.7 WF-MS-2: every
ProtocolStepin a suppliedSuiteProtocolresolves to a selected member edition and a declaration-local operation in that edition. Membership alone does not resolve the step. - No hidden tails. Required stages (e.g., normalization/aggregation/Γ‑fold) are explicit protocol steps; do not hide them inside other steps.
- Guard/gate separation. Suites and mechanisms SHALL NOT publish
GateDecision/DecisionLog.AdmissibilityConditionsand tri‑stateGuardDecisionremain governed by the mechanism definition;OperationalGate(profile)acceptance thresholds and pass/fail criteria remain gate/acceptance concerns. - Suite is descriptive only (WF-MS-3/4). A suite states membership, obligations, pins, and suite protocols. It does not restate
U.Mechanismidentity-bearing content. Any publication or telemetry continuation remains outside the suite protocol and requires its own exact publication or flow assertion and predicate.
Kernel stability rule (recommended). When a change would add a required stage to a kernel suite, prefer a suite variant to changing kernel membership. If mutation is unavoidable, pair it with terminology continuity (E.20:4.9) and RSCR triggers (E.20:4.10).