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

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

Anti-patternSymptomRepair
DependencyGraph as ontologyThe graph is treated as the thing being built.Name the dependency structure and exact relations first.
External supplier as partA supplier or infrastructure system is drawn inside the product.Use the exact boundary-crossing, supply, commitment, evidence, publication-use, source-use, or other direct relation; use parthood only for admitted parts. Use A.6.C only when the source’s contract wording itself must be unpacked.
Mapping as parthoodA model, dashboard, or digital twin is a node inside the asset.Use the exact representation, publication, architecture-description, or evidence relation.
Order as componentA subsequent step is represented as a component of an earlier step.Use the pattern that defines the order, method, description, or Work-occurrence claim.
Acyclicity as adequacyThe graph has no cycles, so the model is accepted.Check whether the selected relation is grounded and whether graph checks answer the current concern.