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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:20:09 UTC

F.0.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternSymptomRepair
Global termA load-bearing word has no recoverable source reading.Name the exact source and passage and state the local meaning.
String-match identityThe same label in two sources is treated as one meaning.Recover both meanings and inspect the actual F.9 relation.
Edition blurA source is cited without the edition that fixes the reading.Identify the edition and reopen only affected uses when it changes.
Domain equals source“Control” or another shelf label is treated as one vocabulary.Identify the actual source or practice and its claim.
Time-stance confusionA design description and a performed occurrence are treated as the same thing.State the source-local distinction and any supported relation.
Mixed local-sense claimA lexical gloss absorbs behaviour, permissions, measurement, or proof rules.Keep the meaning statement local, then use the defining or testing rule for each non-lexical claim.
Relation by similarityA score, paraphrase, or common row is treated as an obtaining relation.Use it only to guide inspection; state the exact relation if supported.
Heavy first answerA cell, record, reliance account, and assurance package are required before one word can be understood.Return the plain source-backed statement first and add stronger objects only for named uses.
Historical relabellingAn old Context Card is renamed into a current cell without recovering its values.Keep it historical and recover only the values needed by the current reliance.