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 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:50:08 UTC

E.4.PFIP:3 - Forces

ForceTension
Accepted change vs predecessor continuityThe candidate must realize new decisions without treating all other predecessor content as disposable.
Complete traversal vs affordable useEvery predecessor content or selected structure required for the declared use needs an outcome, but ordinary retained content should not create a large positive ledger.
Several forms vs truthful comparisonThe same edition may have several forms, yet shared use or shared carriers do not make those forms one eligible comparison pair.
Text convenience vs structural meaningLine and span diffs are cheap for comparable text; diagrams, cards, and retrieval forms need their own content or selected-structure inventories.
Form evolution vs content dispositionA form can be retired, split, or merged without authorizing the retirement of what it expressed.
Reuse vs local specificityFPF, DPF, and LPF publications share the integration problem, while an applicable FPF pattern still defines or constrains what matters for each form and use.
Strong assurance vs bounded resultThe comparison can expose loss and support later reliance; later admission, publication, release, or assurance decisions use their own methods.