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:55:20 UTC

B.1.5.RS:8 - Common Anti-Patterns and How to Avoid Them

FailureRepair
One matching output stands in for preserved behavior.Recover the timing, interaction or property actually used by the whole and test that contribution.
Compatibility in one whole is exported to every user.Separate receiving uses and restrict the conclusion accordingly.
Every implementation detail must remain unchanged.Preserve what the declared use relies on; permit changes outside that dependence.
An adapter is omitted from the candidate’s cost or failure analysis.Include the adapter in the candidate arrangement and follow the combined behavior.
A successful trial becomes an unconditional guarantee.State its supported scope and establish stronger claims only when required.