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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:40:10 UTC

E.17.EFP:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it is wrongHow to avoid it
Treating every explanatory prose block as equally faithfulrendering, reconstruction, didactic work, and speculation have different review loadsfirst try the simpler source-linked note; when class ambiguity changes the next action, name only the applicable class, bounded/blocked use, and reopen condition
Letting reader-fit stay implicit when explanation is clearly tailoreda didactic or contrastive rendering can be overinterpreted as general or policy-bearing guidancestate only the audience, interaction, question, use, or overread distinction that changes the present class or boundary; do not publish a five-field block by default
Using an EFP class as a second claim or relation trackchanged claims hide behind reader-friendly proseapply the full identity-and-bounded-sufficiency screen; identify any actual target and obtaining direct relation before classifying its form
Calling a connective source-linked because addedLinkPolicy names ita policy declaration is mistaken for derivation or an obtaining relationrequire exact source premises and effective scheme plus a derivation, or an exact relation claim already in the source plus an independently obtaining occurrence; otherwise constitute a target claim or leave EFP
Treating speculative prose as a source renderinga new causal or counterfactual claim is hidden inside a form labelconstitute the separate B.5.2 hypothesis episteme, then restrict only its publication form’s use
Collapsing MVPK face and publication face/form or interop publication form disciplineexplanation appears to create a new publication familystay on existing MVPK faces and keep named publication face/form or interop publication form and carrier policy explicit
Derivative text as source replacementa changed ClaimGraph is treated as the original source because the text is easier to readidentify same-source form versus exact target episteme and establish that its A.6.3 or other direct relation obtains before EFP classification
Explanation as evidence or assurancea fluent or source-linked explanation is cited as proof, approval, gate passage, release reliance, work authority, or assuranceidentify the exact episteme and any required source-to-target relation before classifying its publication form; open A.10, B.3, A.21, A.15, or another direct record only for the exact operative claim and receiving use that need it