G.9:7 — Anti‑patterns and remedies

• AP‑1 Hidden edition drift. Remedy: require edition pins in ParityPinSet; treat changes as RSCR‑relevant via canonical trigger kinds.
• AP‑2 Baseline set is informal prose. Remedy: require BaselineBindingRef and EvidenceTrace pins.
• AP‑3 Comparator semantics are “whatever the code did”. Remedy: ComparatorSpecRef.edition (and any normalization/comparability refs) must be cited and pinned.
• AP‑4 Cross-sense or reference-plane reuse without its obtaining relation and visible pins. Remedy: recover the exact F.17 cells and cite the obtaining F.9 relation when local meanings differ; cite the exact reference-plane crossing basis and visibility records when planes differ (delegated to G.Core).
• AP‑5 Parity report becomes a hidden scoring sheet. Remedy: preserve CSLC-admissible outcome shape and keep telemetry as telemetry unless explicitly policy‑promoted by the governing policy pattern.
• AP‑6 “Metric” as a primitive in Tech. Remedy: name the exact CharacteristicRef, ScaleRef, UnitRef when applicable, DHCMethodRef, MethodRef, and U.Measure or result episteme; add DistanceDefRef only when used. “Metric” may appear only in Plain with a pointer to those canonical objects.
• AP‑7 Hidden DHC replay drift. Remedy: carry every active field of the C.21 replay basis and refuse parity reuse when a required field is unresolved or differs across the compared readings. Register refresh tests only for a named receiver that consumes those changes.