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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:05:10 UTC

B.2.4:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Capability by declarationA leader names a new capability, but the exact capability facts remain component-level or unknown.Use A.2.2 for the capability facts, C.16 for their measured characteristics, and A.10 for support; use B.2 only if the existing-whole explanation fails.
Function as partA function block is treated as a physical or organizational part.Use A.6.F for function-like wording, E.18 for transformation-flow structure and C.30.TFS-REL for its bounded architecture use, A.6.M for module wording, and C.30, A.22, or C.30.ASV for the current architecture, selected structure, or structural-view claim.
Method chain as wholeA sequence of methods is called a new holon.Recover the exact method relation and any current work occurrence; use B.2 only when a result holon is current.
Diagram as flow structureA diagram or graph is treated as the transformation-flow structure itself.Use the applicable description, publication, mathematical-lens, or selected-structure pattern; use B.2.4 only after the selected structure is recovered and a whole-reidentification question remains.
Metric jump as wholeA KPI improves and MHT is declared.Use C.16, A.10, and existing-whole explanation first.