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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:30:10 UTC

E.17.0:3 - Forces

ForceTension
Lightweight use vs inspectable assuranceMost uses need one readable conformance judgment; contested use needs exact participants, predicate, occurrence identity, evaluation, and warrant.
Stable kind membership vs changing useAn episteme can remain a view after a reading, project, publication, or selected-use episode ends.
Direct authoring vs derivationSome views are authored directly; others are constructed through a query or projection. Construction history must not define view membership.
Self-contained viewpoint vs reusable convention structureOne P can carry the complete fixed test; separate C/Q/S is useful only when convention components and their organization vary independently and change a named reuse, comparison, or maintenance action.
Several views vs one invented containerMulti-view work needs organization and correspondence, but a package, graph, or shared heading does not establish either.
Readable domain language vs ontological precisionPractitioners need functional view and safety view; load-bearing use still needs exact epistemes and direct relations.
Correspondence vs consistency repairA correspondence can obtain while later evaluation finds an inconsistency or while repair work is still pending.
View vs publicationA view can be unpublished, and one view can be published repeatedly through different forms and carriers.