G.7:8 - Common Anti-Patterns and How to Avoid Them

• Bridge‑by‑prose (“they have the same sense”). Avoid: publish BCT rows + BridgeCards + UTS rows; require SenseCell anchoring and row scopes.
• Scope or sense relation used as a kind bridge. Avoid: state the channel in RowScopeId and use its direct governor. A C.3.3 correspondence needs its kind endpoints and separate receiving classification; cite CL^k and any loss policy only when that calibration or reliance account uses them.
• Plane blindness (“concept = world”). Avoid: record plane pins and policy id pins; keep plane effects auditable and separable from CL/CL^k semantics.
• CL smoothing / averaging. Avoid: establish the common scale and calibration question before taking a minimum; retain actual counterexamples and losses, and keep the receiving decision separate.
• Pack‑wide refresh on a local bridge edit. Avoid: register sentinels scoped to PathSliceId and emit typed RSCR triggers with minimal payload pins.
• QD metric drift by unpinned artefacts. Avoid: enable G.7:Ext.QDParityPins only when needed and require edition/policy pins when enabled.