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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:30:15 UTC

E.18:3 - Problem

  1. Mathematical lens != selected structure. A catalog of morphism-scoped, transformation-scoped, mechanism-scoped, work-scoped, or refresh-scoped patterns does not, by itself, explain how the whole selected structure is built, constrained, and audited.
  2. Flow proliferation. Multiple “reference flows” can be declared; practitioners need one structure discipline that keeps their flow relations typed and comparable without privileging any single flow.
  3. Unsafe publication. Faces re-list inputs and outputs, hide scalarization, omit edition and plane pins, or present a Bridge Card, CL value, UTS row, or policy id as if it made a GateCrossing or gate decision current.
  4. Cycles without norms. Selection↔Planning loops run without an explicit budget (Γ_time), an exact stale-measurement finding and any separately identified refresh plan it triggers, or slice-scoped refresh; a pre-run gate decision is mistaken for actual launch bindings, or a FinalizeLaunchValues record is written before an exact Work occurrence and its independently obtaining bindings exist.