Library / Method Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:35:14 UTC

ME.19:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“The pressure came first, so it caused the Method change.”State a link claim, rivals, diagnostic observations, and the C.28 result required by the receiving use.
“The timeline is the explanation.”Treat it as an index and test explicit links and rivals.
“Process tracing proves the causal effect.”Use it for within-case diagnosis; apply C.28 for the named causal use and lower the verdict when identification, a bound, or estimation required for that use is missing.
“Unsupported means the history is useless.”Retain descriptive sequence and a separately named non-causal hypothesis within their use boundaries.
“The history tells us what to implement.”Send bounded results to a separate authorized architecture decision.