A.19.CHR:4.5 - Suite protocols
CHRMechanismSuiteDescription.suite_protocols follows A.6.7: each step resolves to one selected member declaration edition and one operation designator in that declaration. Its guards, laws, arguments and results come from that edition. Stage names below are readable labels, not substitute operation designators.
If suite_protocols is present, it SHALL include at least one protocol that is equivalent to the canonical suite-closed pipeline below (with fold_Γ explicitly optional).
The declaration-local bindings for the canonical stages are:
| Stage label | Governing declaration | Operation designator |
|---|---|---|
| normalize | selected UNM.IntensionRef edition, A.19.UNM §4.1; consume its directed value and preservation/loss basis, adding class use only under its conditions | apply |
| indicatorize | selected UINDM.IntensionRef edition, A.19.UINDM §4.1 | Indicatorize |
| score | selected USCM.IntensionRef edition, A.19.USCM | Score |
| fold_Γ, optional | selected ULSAM.IntensionRef edition, A.19.ULSAM | Fold_Γ |
| compare | selected CPM.IntensionRef edition, A.19.CPM §4.1 | Compare |
| select | selected SelectorMechanism.IntensionRef edition, A.19.SelectorMechanism | Select |
Resolve each cited edition before applying these bindings; a changed designator or contract requires a revised binding. A list of source pins alone selects no operation. If two editions remain eligible, the suite baseline must state the condition that selects one, or stop that dependent step with the unresolved choice.
Show (canonical suite-closed protocol).
normalize (UNM) →
indicatorize (UINDM) →
score (USCM) →
fold_Γ? (ULSAM) →
compare (CPM) →
select (SelectorMechanism)
Tell.
- The
fold_Γstep is optional (explicitly optional, not implicit insidescore/compare/select). suite_protocolsencodes a pipeline/Uses contour between mechanisms; it does not define a specialisation relation (⊑/⊑⁺). A claimed refinement, conservative extension or equivalence uses its ownA.6.1 §4.8content-preservation test, exact predicate and endpoint facts, including the applicable A.6.RCD missing-governor/substrate branch. Project extensions retain their independently declared restrictions; a pipeline order or ⊑/⊑⁺ label establishes no such comparison.- Any publish/telemetry step is outside
suite_protocols(to preserve WF‑MS‑2 closure) and is governed by established publication patterns (G.10 and/or PTM), not as “hidden tails” inside CHR mechanisms.