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:45:04 UTC

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

Anti-patternWhy it failsRepair
Generic support bucketHides whether support means basedness, evidence use, assurance, work enablement, navigation, source description, or ordinary helpApply the support wording selection test; state the direct relation or keep ordinary help instead of minting a support-headed relation or record
Umbrella “anchored/attached/grounded” with no direct relationHides relation kind and predicateName the participants, use the relation-specific verb, and apply its direct predicate
Perspective flip without recoverable participantsDirection and typing become ambiguousKeep the same participants and direction in both active and passive wording; add formal endpoint names only when reused
Work or carrier treated as evidence relationCollapses producing Work, result episteme, carrier, provenance, evidence use, and relianceState the exact A.2.4 evidence-use relation; open A.10 only for the replayable provenance or reliance path
Implicit “current/latest”Violates explicit time disciplineDeclare Γ_time explicitly and use witness timespans for freshness where needed
Decision use without its actual basisA relied-on assertion cannot be checkedCite the exact evidence-use, provenance, currentness, or assurance relations required by that decision; do not add a generic witness field or new document
Semantic meaning expressed as basednessConfuses source-local meaning with another relationRecover the source-local claim under F.0.1 and add an F.17 cell or basis relation only when needed
Relation-kind change presented as an editA semantic shift masquerades as continuityState the new direct relation and use the applicable continuity rule when that history matters
Using *Slot to name an endpoint/valueConfuses SlotKind with ValueKind/RefKind; breaks substitution and toolingKeep *Slot for positions; use base/dependent for values and *Ref for stored references
Optional record field treated as a carrier or free-text kindLets a record label stand in for the direct relationMake the field identify the already admitted relation vocabulary entry; keep the assertion, carrier, and relation occurrence separate