Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:40:18 UTC
C.3.3:10 - Anti‑patterns & Remedies (informative)
Anti‑pattern
Why it’s wrong
Remedy
One interoperability score, or mandatory scope-plus-kind bridges
Blurs independent channels and invents unused relations
Open only the exact Scope, kind, and sense relations consumed by the receiving use; keep their losses and R consequences separate
Claiming preserved ⊑ while inverting order
Makes typed reasoning unsound
Mark as not preserved; add loss note; consider adapter or subkind redesign
Hiding collapses
Overstates coverage
List collapsed subkinds explicitly; plan the justified R penalty for lost granularity
Implicit latest mapping
Non-deterministic and non-auditable
Pin both scheme editions and the mapping-rule edition in the bridge assertion; outside bridge definedness decline that bridge use without changing an independently obtained receiving result.
Using KindBridge to widen G
Conflates kind correspondence with claim-scope translation
Keep Scope edits in USM (ΔG±); KindBridge never widens Scope
Adjusting F/G for poor CL^k
Violates F–G–R & USM separation
Route consequences to R only; consider narrowing Scope or adding adapters