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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:45:20 UTC

A.2.4:3 - Forces

ForceTension this pattern resolves
Episteme identity versus episteme useThe same episteme can be used for several claims while retaining its identity.
Compact evidence statement versus full evidence graphUsers need a small evidence-use statement first; A.10 remains the pattern for full evidence-provenance graph detail.
Formal proof versus empirical evidenceA proof can be stable inside one theory version; empirical evidence usually needs relevance windows, freshness, and provenance constraints.
Status display versus status assertionA visible badge, cell, or label can cue status but does not by itself create permission, gate passage, assurance, or work evidence.
Local acceptance versus cross-local reuseEvidence and status use are bounded by their source scheme, ClaimScope, window, and intended use; reuse recovers the changed values and any required F.9, source-currentness, publication-use, reliance, or assurance-use relation.
Causal evidence classes versus ordinary evidence relationCausal-use evidence classes need C.28; A.2.4 keeps the evidence-use relation from being misread as a system-role kind or assignment.