| Chartless number | “Latency = 120” | No unit/vantage → untestable | Fill cs_basis + chart |
| Normalization smuggling | Quiet “per‑unit” normalisation mid‑stream | Trend reversal | Declare UNM normalization references (NormalizationMethodId / NormalizationMethodInstanceId) + named invariants (see A.19.UNM) |
| Bridge-by-name | Reusing equal labels under different schemes | False comparability | Test the needed F.9 predicate; cite a Bridge only when it obtains, then ground the separate receiving-use claim and reliance. An unsupported required correspondence blocks that use. |
| Free-hand averaging | An arithmetic mean is used without a model for the intended risk result | The number can answer the wrong question | Use A.9 to select a justified law, bound or separate-input result; declare a Γ_fold only for the selected fold |
| CN‑frame sprawl | Overlapping definitions obscure which comparison basis to use | Avoidable reconstruction and maintenance | Reuse a sufficient basis and retain differences that change the use. A registry supports maintained editions; use E.9 when a consequential decision needs a DRR. |
| Self-certification hidden by assignments | A holder authors the basis and later certifies it under a new role | A required independent check still examines that holder’s own basis | Apply §4.2 to participation in the edition; separate authority and examination, and keep uncertified use explicit when certification is not required |