A.19.CPM:6 - Bias-Annotation — informative
CPM makes comparator choices and failure behavior inspectable. This can expose hidden thresholds, tie-breakers or unknown coercion; the declaration alone does not establish that an application avoided them.
Typical bias risks and mitigations:
- Comparator choice encodes value judgments. Weights, priority orders, thresholds, and “tie‑break” conventions can encode organizational bias. Declare these choices in the selected
ComparatorSpecor policy, using existing prose or code when it makes their meaning and edition recoverable. - Systematic missingness. If evidence is systematically missing for certain contexts or groups, naive “unknown → worse” is a bias amplifier. CPM’s tri‑state guard avoids coercion; but teams must still define policy‑bound failure behavior and be explicit when abstention is acceptable.
- Cross-scheme comparisons can embed structural unfairness. A comparison that relies on a semantic relation between two F.17
SchemeSenseCellvalues cites the obtaining F.9Bridgeand its separate bounded-use claim; together they expose the tested correspondence or difference and tolerated loss. A plane-only crossing cites the ReferencePlane relation and policy. Neither branch replaces comparison scope, predicate, comparator, or time. - Overconfidence via scalarization. Collapsing partial orders into scalars often overstates certainty and hides tradeoffs. CPM makes set-valued outcomes available to a decision maker who needs to take those tradeoffs into account.