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

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:35:10 UTC

C.2.P:9.1 - Operating consequence

For each repair:

  1. start from the sentence’s function and practical consequence, not from a word list;
  2. preserve any E.10 cue or routing result and recover only the one still-hidden episteme, publication, carrier, source-to-use, or use-disposition distinction;
  3. use the direct pattern as soon as it is known;
  4. choose direct repair before a compact row, and a compact row before a full check;
  5. keep the final sentence readable to a cold practitioner and state what action or non-use remains;
  6. reopen only when a material field or use changes.

Do not perform global lexical replacement. Do not treat every FPF pattern edit as a full epistemic-restoration case. Do not retain a compatibility field whose only function is to remember a previous internal schema.