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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:45:12 UTC

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

Anti-patternWhy it failsRepair
Copy the source stackPrinted order can be chapter order, explanation order, Method order, Work order, subject grouping, or nothing architectural.Name the subject and recover each relation before retaining a structure.
Fictitious representative WorkProposed Method use acquires false evidence and false actuality.Use an intended-use case, WorkPlan, or other prospective account; state realization and later-test conditions.
One view set for every practiceA convenient template becomes a universal ontology and imports irrelevant work.Always keep the identity-and-relation check; add other structures only when they change the decision.
Synonyms as alternativesSeveral names hide one unchanged organization and create false diversity.State what decision, relation, or unlike-case result differs; merge candidates that differ only by labels.
Local win, invisible burdenThe apparent improvement exports cost, delay, evidence, control, or residual to another structure.Name the receiving scope and compare the moved burden with the claimed gain.
Product comparison everywhereThe Method becomes framework-product design even when the architecture of Methods and their use is the only question.Open the four-option branch only when product identity is current.
Product comparison nowhereA live field or maintenance boundary is hidden inside a favored architecture.Compare the four arrangements and pass the result to the applicable product decision.
Model equals its subjectA view or matrix is treated as a world-side whole or relation.State the described subject, model use, correspondence, and preserved and lost distinctions.
Project choice equals cultural successA deliberate intervention is taken as proof of later recognition, spread, selection, or retention.Keep the project claim and each cultural-change claim separate; use C.36 for the latter.
Notation as the first resultThe account becomes precise but unusable to the practitioner who must act on it.Lead with the short prose synthesis; retain notation only where it catches a real ambiguity or supports a later check.