fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 35012–35038

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:10:10 UTC

A.19.UNM:0 - At a glance — didactic, informative

Intent. Provide a single, explicit normalization mechanism for coordinate values in a U.CharacteristicSpace, so that comparability and downstream characterization steps can be stated as “normalize-then-compare” (governance), rather than as hidden arithmetic inside scoring/selection.

Where it sits.

  • CN-frame governance card: CN_Spec.normalization + CN_Spec.comparability.mode route whether comparison is coordinatewise or normalization-based.
  • CHR suite role: stage normalize (first-stage, when enabled by the suite protocol / comparability routing).

Key outputs.

  • NCV (NormalizedCharacteristicValue) values for coordinates.
  • When requested for a function n:D→N, the equality-of-output relation x ≡_UNM y iff n(x)=n(y) on its actual domain D. Its classes form a set quotient; preserving further operations or answers needs the additional tests below.
  • An inverse only on the stated image of an invertible transformation; an operational quotient only for compatible operations and recoverable queries; a NormalizationFixSpec only when a representative of an established class is needed.

Two IDs (do not conflate).

  • UNM_id? selects the UNM mechanism instance used by this CN‑frame (a U.Mechanism instance of type UNM; routing/governance level).
  • NormalizationMethodInstanceId selects the normalization method instance applied to specific coordinate(s), with its validity window and evidence pins (method/application level).

Minimum declaration set (didactic).

  • In CN_Spec.comparability: set mode, and (when UNM participates in acceptance/comparison) set minimal_evidence.
  • In CN_Spec.normalization: declare UNM_id?, methods, instances, method_descriptions, invariants, and (if representatives are required) fix.
  • In Audit: cite the chosen NormalizationMethodInstanceId, NormalizationMethodDescriptionRef.edition, characteristic-space and CN-Spec editions, bearer, scope/window, reference or comparison basis, invariants, evidence, and intended comparison. Cite a Bridge, kind relation, or plane relation only when the result or receiving use actually relies on it.

Non-goals.

  • Not indicator selection (that is UINDM).
  • Not scoring, aggregation, comparison, selection (USCM / ULSAM / CPM / SelectorMechanism).
  • Not a data governance system: UNM is a concept-level mechanism with an explicit governing pattern and auditability.