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 12:05:13 UTC

C.2.P:3 - Forces

ForceTension
Precision vs readabilityFPF-governed wording needs kinds named by value, but a sentence overloaded with every possible kind becomes unreadable.
Preservation vs cleanupAccepted source text or accepted governing text must not be paraphrased away, but source-companion statement cannot be mistaken for pattern authority.
Local repair vs new ontologyMany phrases only need local A.6.P and F.18 recovery; a few reveal a real missing FPF kind or relation.
FPF-side vs project-side workThe same word can describe FPF pattern authorship or a user’s project publication, record, work, or action.
Guidance vs auditThe pattern must tell authors what to do, while check rows only verify that the rewrite was carried out.