G.5:6 - Bias-Annotation

Potential biases and failure modes this pattern explicitly guards against:

• Monoculture bias (single Tradition dominance by default). Mitigation: rows retain an explicit eligibility basis and conditional assurance expectations; public registration adds its stronger records; selection is set‑returning under partial orders; method‑specific policies stay explicit pins rather than hard-coded defaults.

• Hidden scalarisation bias. Mitigation: set-return semantics is pinned through G.Core; dominance regimes are explicit and each default cites one declared governing definition.

• “Tool equals method” bias. Mitigation: notation independence and prohibition of tool keywords in core registry and eligibility fields; tool choices are outside the core.

• Cross-sense leakage bias. Mitigation: when expressions have distinct source-local meanings, require exact F.17 endpoint senses, an obtaining F.9 Bridge, a separate C.2.1 bounded-use proposition, and the matching A.10 or B.3 reliance branch; keep loss and CL visible where material. Crossing pins and bundles remain audit or publication references and cannot make an implicit crossing admissible.

• Survivorship bias in refresh. Mitigation: RSCR triggers are typed and id-based; freshness, decay, and telemetry deltas are first‑class causes with canonical ids.