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

• Anti‑pattern: Embedding thresholds inside SoS‑LOG rules or ladder rungs. Avoid: thresholds live in G.4 Acceptance; bundle only cites clause ids.

• Anti‑pattern: Treating illumination/QD telemetry as a hidden scalar score that changes dominance. Avoid: keep telemetry report‑only unless explicitly promoted by a governing-pattern policy pin.

• Anti‑pattern: Publishing a bundle that “implies” cross‑context reuse without its required relation/use/reliance pins, or omits CL/Φ pins required by the actual calibration or named assurance use. Avoid: if reuse is asserted, publish the crossing pins required by G.8:Ext.BridgeReuseWiring for that use; otherwise downstream must abstain from reuse.

• Anti‑pattern: Re‑defining PortfolioMode/DominanceRegime defaults in the bundle text. Avoid: cite each default’s governing definition through G.Core.DefaultGoverningDefinitionIndex.

• Anti‑pattern: Recording RSCR “reasons” as prose labels only. Avoid: emit canonical RSCRTriggerKindId values per G.Core.