Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:05:20 UTC

A.19.UNM:7 - Conformance Checklist

  • Normalization identity: cite the selected method and configured instance, its description, invariants and any representative-fixing rule. Resolve legacy identifiers through F.18 when used. An ordinary coordinate mapping does not assert a specialized Map kind or a Bridge; apply the lexical distinction in §4.0.
  • CN routing: uses CN_Spec.comparability.mode and the CN_Spec.normalization surface; does not embed “shadow CN-spec”.
  • Fail-closed: eligibility is tri-state and never coerces unknown to pass.
  • Lawfulness classes declared: method class is one of {ratio:scale, interval:affine, ordinal:monotone, nominal:categorical, tabular:LUT(+uncertainty)} and the instance’s validity window is named.
  • No indicator conflation: does not treat NCV as automatically implying indicator status.
  • Relation and reuse discipline: recover each NCV’s method and CN-Spec editions, bearer, basis, evidence, intended comparison and qualifications. Any relied-on relation and its receiving use satisfy UNM-L5; an assurance penalty has a justified domain model.
  • Result branch: the domain, directed output and preserved/lost distinctions are explicit. An inverse is claimed only on its stated image. A set quotient uses equality of function outputs on that domain; an inherited operation also passes compatibility and partial-availability checks, and a recovered query is constant on each class. A required representative has a declared fix and is not treated as the lost original input.
  • Auditability: the inputs, method and specification editions, evidence, conditions, result or reason for abstaining, and any relied-on relation are recoverable under Audit in §4.1. A separate record is retained when required by the receiving use.
  • Source references: downstream uses cite the method, basis and evidence editions they need, preserving the source definitions.
  • Missing or stale inputs: apply the declared abstain/degrade rule and name the gap. An undefined transformation input has no NCV. Reuse an adequate existing basis or plan a justified acquisition under its own method; normalization alone mandates no new Work.
  • SlotKind discipline: SlotKind tokens reuse the CHR SlotKind lexicon where applicable; UNM‑specific SlotKinds are docked into the suite lexicon before use (no ad‑hoc drift).