fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 47308–47316

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 14:40:20 UTC

B.5.3:3 - Forces

ForceTension
Domain fluency vs. ontological parsimonyTeams need familiar words, but FPF must not grow a new root kind whenever a local term appears.
Same word vs. different claimThe same expression can make different local claims in different sources or schemes and can point to different FPF values. Spelling alone decides none of them.
Meaning recovery vs. role overuseSome domain uses concern a system-role kind or assignment; many concern another value or relation. Recover the claim before choosing the terminology.
Small result vs. hidden ontologyThe result should be as small as the use permits, yet still expose any real kind, relation, loss, and return condition instead of hiding them behind a synonym.