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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:16:27 UTC · snapshot created 2026-10-03 05:17:06 UTC · last check 2026-10-03 05:25:10 UTC

E.22:3 - Forces

ForceTension
Cheap readiness vs ambitious improvementA floor evaluation should be short; exceptional improvement needs richer proposals.
Explicit purpose vs reviewer discoveryThe request names the purpose, while the reviewer can still report important unasked questions.
Evaluation vs follow-up actionA useful evaluation may suggest a follow-up, but the suggestion remains a hypothesis until the pattern that defines or constrains the claim, relation, or boundary is applied.
Multi-coordinate gain vs Goodhart riskRaising one visible value can damage usability, affordability, locality, source preservation, or corpus ecology; use E.13 when the visible value or metric is being treated as the intended value itself.
Proposal portfolio vs selected resultSeveral candidate improvements may be useful without becoming a selected set, pool policy, front insertion, parity, or refresh result.