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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:55:20 UTC

A.19.CN:1 - Context

A.19 established a substrate‑neutral picture:

  • a CN‑frame = a selected CharacteristicSpace (CS) + chart (coordinate patch and value basis, with Units where applicable) + a referenced Normalization mechanism (UNM) for one named bearer, comparison basis, scope/window, and intended use. A.19.UNM defines directed normalization, its preservation/loss basis and any separately justified ≡_UNM class use;
  • operators (subspace, product, pullback/pushforward) and comparability (coordinatewise vs normalization‑based (normalize‑then‑compare));
  • RSG touch‑points: role readiness (RSG states) are certified against CS via checklists over observable characteristics;
  • entity/relational mixtures across CN‑frames via minimal schemas and bridges.

Terminology guard. CN‑frame is the lens (I); CN‑Spec is the specification (S) that fixes the bearer, characteristic and scale editions, chart, comparison basis, scope/window, normalization references, comparability rule, aggregation choice, and intended use; CN‑Description is the didactic surface (D) with worked examples and anti-patterns. Mechanism-level term cards such as NormalizationMethod, NormalizationMethodInstance, NCV, ≡_UNM, and IndicatorChoicePolicy remain defined by the corresponding A.19.<MechId> patterns and are only cited here.

Normalization names. Use A.19.UNM’s method and instance identifiers to identify the selected normalization. Ordinary mathematical “mapping” describes its function; it does not assert a specialized FPF Map kind or an F.9 Bridge. Resolve a legacy identifier through F.18 alias docking when needed.

A.19.CN makes this operational and auditable.