| Evolvability vs Usability | A stable operation contract supports evolving method families; readers still need to find the selected method and its conditions. |
| Semantic precision vs Cognitive load | Formal invariants/quotients ↔ a mechanism description that engineers can act on. |
| Shared definitions vs Connected use | UNM uses CN-Spec, CG-Spec and any required relation claims; each retains its own governing definition. |
| Trustworthiness vs Overreach | Evidence must support the normalization used; measurement meaning and calibration retain their own grounds. |
| Locality vs Reuse | A normalized value retains its declared bearer, basis, scope/window and use; a later use may require another relation or normalization. |
| Fail-closed safety vs Convenience | Unknown/insufficient evidence must not coerce ↔ teams want “a number anyway”. |