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 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 16:40:20 UTC

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

Anti-patternSymptomRepair
One-book domainOne influential source is treated as the whole answer despite a known rival or transfer limit.State the question and add each source whose inspected claims change it. For a SoTA claim, the one source must itself critically compare the serious alternatives.
Currentness launderingA registry entry, official status, maintained label, citation count, or recent date promotes a source into the best-known line.Record identity and currentness separately. Select rank only from the answer-changing comparison, or return the unresolved source gap.
Source-role collapseA lineage anchor, popular default, failure case, and best-known-line candidate are all reported as equivalent support.Classify each retained source by its answer-changing role; official/popular-comparator, lineage-only, and identity/currentness-only roles do not supply SoTA rank.
Reading-list cutMany sources are retained without distinct roles.Keep only answer-changing roles and record deliberate exclusions.
Edition blurA source is named without the edition that fixes the relied claim.Identify the edition and reopen only affected claims when it changes.
Domain-family inferenceA shelf label is treated as evidence of meaning, relation, or relevance.Use the label only to find sources; inspect their claims.
Relation by stealthSelection prose says two sources are “basically the same.”Keep them distinct and open an F.9 question if an actual relation is needed.
Designed-versus-performed collapseA design description is treated as a performed occurrence.State the source role and the time distinction it contributes.
Search score as gateRank, distance, threshold, or model answer admits or excludes a source.Use the reading to prioritize inspection; decide from the source’s contribution.
Variant becomes the questionA broader query drops a condition, and the returned passage answers that broader question instead.Preserve the original concern and restore its conditions during candidate inspection.
Locator becomes sourceA title or excerpt is treated as inspection of the unavailable original.Return what was actually inspected, its address and missing context; retain the original as an inaccessible lead.
No hit becomes absenceOne phrase or limited index finds nothing, so the whole repertoire is declared empty.State the route’s reach, repair a consequential blind spot if feasible, or return the scoped gap.
Exhaustive pretenseA small cut is reported as complete literature coverage or saturation.State its question-relative limits and use the domain review method when needed.
Compact-note inflationThe one-screen representation grows into a second source analysis.Keep the ClaimGraph concise and place detailed analysis with the receiving work.
Context container revivalSources or meanings are treated as members of a universal Context object.Identify the exact sources. When a source-role decision depends on a disputed expression, recover its plain local meaning through F.0.1 before selection; create an F.17 cell only for a later durable need.