| GateDecision leakage | Select emits GateDecision or writes a decision log | Keep gate decisions in their governing patterns. SelectEligibility remains the mechanism predicate; dated selection work records the realized eligibility value and direct replay basis. |
| Forced single winner | Select always returns exactly one candidate even under incomparability | Return a declared selected set by default; if single winner is required, make it explicit in CriteriaSlot and ensure the induced order is admissible and declared |
| Hidden tie-breakers | “If incomparable, pick lower cost” without declaring that as policy | Move tie-breakers into explicit criteria or into declared comparator policies; never embed inside the kernel |
| Scalarization by convenience | Replace set-valued comparison with a scalar “summary score” treated as decisive | Keep summaries report-only unless explicitly declared as admissible comparator outputs |
| Unknown coerced to pass | Missing evidence treated as acceptable | Use tri-state SelectEligibility; unknown maps to degrade or abstain |
| Selection does comparison | Selection stage recomputes scoring or comparison internally | Keep comparisons upstream; SelectorMechanism binds exact CPM applications and consumes only their justified-token union in ComparisonResultSlot |
| One binary comparison treated as a batch | One Compare(left,right) application is said to cover three or more candidates, or a token union loses its producing applications | Bind a finite basis of exact binary CPM applications, derive required pair coverage from the selection conditions, and trace every consumed token to a member output |
| Selected set as replay record | Candidate universe, comparison ref, criteria, scope, evidence, or currentness are placed inside SelectionSlot | Keep SelectionSlot to selected candidates; bind use arguments on the actual application and use direct evidence, provenance, and currentness relations |
| Boundary drift | Selection reuses a token union after comparison-basis membership, coverage, member pair or eligibility, predicate, scope, selected slices, plane, or window changed | Treat it as another selection application and perform the required binary comparisons again when their governed basis changed |
| Publish inside selection | Selection emits a publication or telemetry relation as part of mechanism semantics | Keep publication and telemetry under their governing patterns; dated work and direct relations retain replay |