Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:40:10 UTC

B.5.QD.CF:8 - Common Anti-Patterns and How to Avoid Them

Failure invited by conflict repairBetter move
“This way has always worked, so the result requires it.”Recover what the way supplies and ask whether another operation supplies that contribution.
A solver returns a solution after a hard requirement is removed.State the changed requirement and return to the original need; the witness answers the relaxed problem.
Two names are introduced for one quantity in one condition.Establish the actual distinction or retain the incompatibility, as in :5.1.
The small conflicting set is repaired while another affected requirement is ignored.Reapply the retained requirements; inspect the transition time or lost information that the change can affect.
A consistent description is presented as an implemented repair.State the operation and support still needed to obtain the result.
Every conflict is promised a solution that preserves every demand.Return the supported limit or requirement-change question when no warranted repair exists.