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 13:00:08 UTC

F.4:3 - Forces

ForceTension
Recognition versus ontologyA description must be easy to read but cannot replace the kind, classification judgment, assignment, capability, Method, or Work occurrence.
Kind continuity versus local reuseThe candidate domain, operative membership distinction, member/non-member boundary, and continuity rule decide whether one kind continues. A practice or source change only tells the reader where to compare definitions; a later use may still need a C.3.3 relation between distinct kinds or an F.9 relation between distinct F.17 local-sense cells.
Compactness versus completenessA useful description is small, but a stronger receiving claim may need state, capability, Method, assignment, evidence, or status checks.
Open-world use versus form burdenSome uses need only a recognition paragraph; stronger uses need explicit neighboring references without pretending every possible relation is current.
Work-facing classification versus episteme useAn admitted system may satisfy a system-role kind and participate in an assignment. An episteme is instead used through evidence, source, publication, requirement, explanation, assurance, or status relations.