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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:15:10 UTC

G.8:2 - Problem

  1. Selector needs a stable input artefact. G.5 cannot consume “maturity narratives” and scattered SoS‑LOG snippets without re‑authoring semantics or inventing implicit defaults.
  2. Thresholds leak into LOG. Numeric gates are often embedded directly into rule text or ladder rungs, blurring the boundary between LOG decisions (C.23) and Acceptance thresholds (G.4).
  3. Auditability is brittle. Decisions (pass/degrade/abstain) lack stable, citable links to evidence paths (G.6) and crossing pins (Bridge/CL/Φ policy ids as required for the stated use), so later re‑checks and RSCR become ad‑hoc.
  4. Telemetry contaminates decision semantics. QD/OEE/illumination signals are frequently treated as dominance inputs without explicit policy pins; edition drift then silently changes outcomes.
  5. Refresh is under‑specified. Bundle evolution (rules, ladders, pins, policies, editions) must be RSCR‑addressable via typed trigger kinds, not by free‑text “reasons”.