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

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

Anti-patternFailureRepair
Context holonNearby systems, Work, and epistemes become parts of one extra whole.Keep their direct identities; select only the decision-relevant relation organization as U.Structure.
Subsystem shortcutLocation or team ownership identifies the bounded context.Recover all four A.22 discriminators. One subsystem can support several model-use structures.
One-relation or missing-frame shortcutApplicability or actual use alone is expected to carry coherence, constraints, or the selection decision.Stop at the direct relation until all three relation families, applied constraints, and one exact frame are current.
Description or publication substitutionA map, code repository, schema file, view, or publication is treated as the model-use organization or an occurrence.Classify the exact content, carrier, system, structure, and publication claims under their subject patterns.
Locality inflationA term, rule, unit, evidence use, or status use gets a context or structure proxy.Apply the A.1.1:4.4 triage and keep the direct governed value or relation.
Crossing by labelMapped, Conformist, or shared wording is treated as an obtaining structure crossing.Preserve the proposal and apply WF-A1.1-CROSS; stop until the direct crossing governor exists.