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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:05:20 UTC

C.23:2 - Problem

Unstructured “readiness” stories and undisciplined evidence lead to:

  • (i) Illicit scalarisation across mixed scale types,
  • (ii) Prose‑only gating that a dispatcher cannot execute,
  • (iii) reuse after the family, evidence profile, claim scope, qualification window, or comparison basis changed, or reliance on an unstated source-local, kind, or plane relation, and
  • (iv) Immature families leaking into production. We need a notation‑independent LOG layer whose executable rules use TaskSignature (S2) + EvidenceProfiles to return admit / degrade / abstain, routing CL penalties selected under R4 to R_eff only (never mutating F/G).