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

C.3.2:3 - Forces

ForceTension
Readable use vs reusable declarationOne case should stay ordinary, while repeated classification needs a stable criterion and assumptions.
Admissibility vs uncertaintyCandidate or slice mismatch means no judgment; missing knowledge for an admissible request means unknown.
Criterion condition vs evidentiary useThe direct condition named by the criterion can be physical, relational, epistemic, institutional, or publication-dependent; use as evidence alone creates none of them.
False vs unknownKnown criterion failure differs from unavailable support or dependency.
Intent vs extensionA declaration can stay fixed while candidate state or selected slice changes the true-candidate set.
Set use vs ontologyA query may need a set without creating a collection holon, direct relation occurrence, or U.EntitySet.
Scope vs evaluation inputClaims may be scoped; the kind is not. The context slice is an explicit input.