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 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:30:16 UTC

B.3.3:5 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailure in useRepair
Tested but referring to different thingsRequirements and architecture use “Sensor” for different participants; the test concerns only one.Resolve that correspondence and re-examine affected claims; more test links do not fix it.
Perfect blueprint, unsupported operationA proof assumes conditions that the actual system has not been shown to meet.Obtain or use the needed empirical and assumption evidence for the actual claim, or narrow the conclusion.
Maturity by receiptA fresh smoke test and a term mapping receive a positive performance label.Judge the support for the requested performance, not the receipt count or type combination.
Proof as an admission tollSufficient empirical support is rejected because an unrelated formal proof is absent.Apply the receiving claim’s evidence rules; retain formal proof obligations where their contribution is necessary.