A.19.SelectorMechanism:12 - Relations
-
Builds on
A.6.1and its conformance checklist for mechanism identity, declaration content, applicability, and specialisation-chain discipline.A.19.CHRfor suite membership, suite protocol closure, SlotKind lexicon, and threshold and default discipline.G.0forCG‑Specadmissibility and evidence declarations.A.19for theCharacteristicSpacePredicatebasis when one governs selection.A.19.CPMfor every binaryCompareapplication in the finite basis, its pair, realized eligibility value, and own set-valued output binding.A.2.6forU.ClaimScopeidentity andU.ContextSlicemembership.A.19.CNforCN-Spec, whose declared comparison and candidate-use conditions supply an explicit input.C.22forTaskSignatureas a policy-reference artifact when used.A.6.1 §4.2for operation-local argument/result meanings and their SlotIndex projection; the local extension rule preserves inherited meanings.A.15.2for the edition/policy baseline on P2W paths;A.15.3plusA.19.CHR:4.7.2for typed filling of independently declared positions.C.27.TAfor the explicit selection-evaluation point or interval.A.2.4,A.10, andG.11for evidence-use scope, provenance, and currentness, separately from selection scope and output.
-
Used by
A.19.CHRas theselectstage in CHR pipelines.G.5as the primary conformance and specialization context for selector-based method dispatch andPortfolioModepolicies.E.18when this declaration is used by transformation-flow nodes. A.15.3 governs planned refs only for independently declared receiving positions; operation bindings and any dated selection Work retain their rules.
-
Coordinates with
CPMand other admissible comparison stages as producers of the result bindings whose justified-token union fills the Selector’sComparisonResultSlotargument.ULSAMand other admissible aggregation stages that must remain explicit rather than hidden inside selection.E.20for governing-pattern discipline;F.18when a reusable name or alias needs to be chosen. An F.9 semantic Bridge requires its own predicate, not merely a source term.