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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:15:10 UTC

IMPROVEMENT — Define better before repeating change

  • Situation: A team wants to improve something but has not agreed what better means or how the changed version will be checked.
  • Question: Which evaluation question, characteristics, scales, changes, and comparison make improvement reviewable?
  • First useful result or blocker: One evaluation question, current assessment, bounded change, before-after comparison, or exact missing use, evidence, scale, or trade-off.
  • Mantra: Name the entity, current state, and use that better must serve. Frame the question before choosing metrics; select characteristics, scales, and protected trade-offs; assess the current state; compare candidate changes; make only the supported change; evaluate it on the same basis; continue, stop, or change direction from that result.
  • Start with: E.22, A.19.ECS, C.16, and E.23 as their questions become current.
  • Stop or return: Stop at the first missing prerequisite or useful comparison. Reopen when the entity, use, evidence, or scale changes.