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

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.UNM:3 - Forces

ForceTension
Evolvability vs UsabilityStable mechanism surface ↔ method families evolve; single place to read ↔ modular wiring.
Semantic precision vs Cognitive loadFormal invariants/quotients ↔ a mechanism description that engineers can act on.
Governing-pattern discipline vs Cross-cutting realityUNM touches CN, CG, transport, and plane claims ↔ avoid “shadow specs” and duplicate centers of gravity.
Trustworthiness vs Overreach“Normalization is legitimate” must be evidence-backed ↔ UNM must not pretend to define measurement meaning itself.
Locality vs ReuseA normalized value is valid for a declared bearer, basis, scope, window, and use ↔ a later use may need a separately supported relation or a new normalization.
Fail-closed safety vs ConvenienceUnknown/insufficient evidence must not coerce ↔ teams want “a number anyway”.