Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:15:10 UTC

A.19.CPM:9 - Consequences

  • Improved usability: CPM gives a single, engineer‑readable place to learn “what admissible comparison means” and what it does not mean.
  • Higher replayability: comparison results remain traceable through the Compare application and its ComparisonResultSlot binding, any consumed obtaining F.9 Bridge with its separate bounded-use claim, and any ReferencePlane relation and policy. Recover dated comparison U.Work and the A.10 evidence-provenance path when the account asserts them or the receiving use consumes them.
  • Reduced semantic drift: teams cannot silently shift from Pareto to lexicographic to “weighted sum” without changing explicit comparator specs and pins.
  • Explicit tradeoffs: set-valued outcomes retain incomparability and uncertainty for downstream reasoning.
  • Cost: downstream consumers (notably selection) must handle sets, abstentions, and partial orders explicitly. This moves complexity from hidden heuristics into explicit policy‑bound mechanisms.