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 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 17:40:10 UTC

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

MisuseFailure visible in the worked casesRepair
Substitute the right number into the wrong commandA count of relative motor increments is treated as an absolute wheel-position target.Recover the interface’s counted participant, unit and initial-state use; construct the input it actually accepts.
Check only the middle calculationThe robot arithmetic is correct while rolling or successful completion remains unsupported for an actual-travel claim.Add the physical and observation contributions consumed by that stronger claim, or return the conditional design.
Treat a sufficient abstraction as complete physical designA gear colouring is taken to establish torque or mechanical compatibility.State the bounded direction consequence and obtain the missing mechanical account when the decision requires it.
Repair the drawing while leaving the arrangement unchangedAn odd-cycle edge is deleted from the contact graph but the gears remain meshed.Change the actual contact or revise the contact rule with its physical basis, then reconstruct the graph consequence.
Count reservations as occupantsThree cards outside the free pool are reported as three visitors inside during handover.Retain Reserved and Awaiting-return states, or report the resulting occupancy bound.
Preserve local rules while duplicating a shared resourceEach entrance has its own three-card stock and both are used for one room.Use one total stock or a partition of it; transfer existing free cards when balancing entrances.
Traverse every contribution before using a sufficient resultA proof already excludes a design, yet simulation and implementation continue as compulsory stages.Return the proved physical obstruction under its assumptions and choose a revised design question.
Ask a contributor for an unexplained answerThe receiver gets a count, proof or program whose needed meaning cannot be recovered.Request the particular interpretation, decisive argument or operating condition required by the next use.