A.19.UNM:8 - Common Anti‑Patterns and How to Avoid Them
-
Hidden normalization inside scoring or selection Avoid this by using
CN_Spec.comparability.modeand applying UNM. -
“NCV ⇒ indicator” shortcut Avoid by treating indicatorization as UINDM policy, not a byproduct of normalization.
-
“We normalized” without declaring invariants Avoid by naming the domain, transformation, preserved invariants and lost distinctions; supply a class or congruence claim only under its additional conditions.
-
Reusing a normalized value after its basis changed Recover the bearer, method and CN-Spec editions, comparison basis, evidence, intended use and scope/window. Recheck the conditions that changed, including any relation required by the new use.
-
Choosing a representative implicitly Avoid by either keeping quotient objects abstract or declaring
NormalizationFix. -
Treating a generic mapping word as a specialized relation claim State the normalization’s operands, rule, invariants and loss. Test any specialized
Mapor F.9 Bridge claim separately under its defining pattern. -
Treating UNM outputs as comparable beyond their declared bearer, basis, scope/window, or reference plane Avoid by keeping comparison local to the recorded premises. Where a conclusion depends on another source-local meaning, bearer kind, or plane, cite the obtaining relation and its loss; otherwise constitute a new normalization result or fail closed.
-
Re-authoring method, basis, or evidence anchors downstream Avoid by citing the editioned method, basis, and evidence anchors as refs; a downstream pattern neither rewrites them nor replaces them with a generic registry.