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:20:10 UTC

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

Anti-patternFailureRepair
Version fanoutA new edition reopens every downstream result.Compare claims first; follow only actual action-changing dependence.
Carrier preservationThe same world object or familiar file shape is treated as proof that all uses remain valid.Separate source episteme, claim content, publication, carrier, and world-side change.
Search hit equals impactEvery textual hit is classified affected.Inspect the receiving content and exact direct use relation.
Declared graph equals realityEvery reachable node is reopened and undeclared premises are missed.Combine source-outward and receiver-oriented discovery; establish each relation independently.
One convenient repository equals coverage“No use found” hides inaccessible, stale, or excluded surfaces.State the frame, surface-by-surface basis, explicit exclusions, and gaps.
Unresolved means unaffectedA missing premise or inaccessible source receives a silent clean result.Return unresolved or a coverage gap and name the practitioner or System responsible for the next action.
Subject judgment in the common account“Preserved” or “reopened” is issued before engineering, finance, strategy, assurance, permission, or release judgment.Apply the direct subject guidance and pass its independently governed result to its existing consumers. Add a local summary only for a common receiving question.
Completed account fed back into its own resultThe common summary becomes circular evidence for the subject verdict it contains.Keep the acyclic application and direct subject-result-to-consumer route.
Perpetual impact programmeEvery change creates a standing corpus-wide monitoring obligation.Stop at the present bounded question; use G.11 only when a named currentness or refresh need remains.