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 14:25:10 UTC

C.29.3:8 - Common Anti-Patterns and How to Avoid Them

MisuseWhy it fails hereRepair
Send an unrepresentable answerA signed field wraps or rejects a value that is valid in the calculation.Change the encoding or realization, or restrict the admitted input.
Split a command without recovering compositionTwo absolute targets do not add like relative increments.Explain the state and rule connecting the completed commands.
Read the carrier by its familiar scaleThe circuit’s physical average uses a different decoding from its inputs.Derive and use the receiving scale.
Infer exact occupancy from unavailable cardsSome assigned cards are outside during reservation or return.Use the four-state account or retain the upper bound.
Treat one successful run as every required runAn untested endpoint or interleaving can change the result.Supply the argument or evidence that covers the declared use.
Require a new trial for an adequate conditional designThe trial may leave the design decision unchanged.Finish with the sufficient conditional consequence; obtain further information when its use warrants it.