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.3:7 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Library as theoryA repository or reading list is treated as one episteme.Recover one exact candidate and test A.1 plus the C.2.1 constitution relation; if either test fails, withhold episteme-result recognition. Keep any independently established collection claim without inferring that it is sufficient for the current use; report unknown when a required test cannot be evaluated.
PDF as epistemeA PDF carrier or its publication form is used as the theory itself.Use publication patterns for the PDF and keep B.2’s resultHolonRef for the independently constituted episteme.
Doctrine receives agency“The standard enforces…” or “the theory decides…”For a literal claim of dated enforcement or decision Work, recover its actual performer through A.13 and admit the Work independently under A.15.1; add F.6 only when the use consumes precise assignment-bound attribution. Otherwise use F.19 to retain ordinary guidance wording when its capable user and action are recoverable.
Morphism as MHTA view, translation, coarsening, or retargeting is called a new episteme whole.Use A.6.2, A.6.3, A.6.4, or A.6.3.CSC unless B.2 whole reidentification is current.
Synthesis as high trustA new theory inherits trust because its sources were reliable.Rebuild assurance for the result episteme through A.10, B.3, B.3.5, C.2.1, and source-use patterns.