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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:45:12 UTC

A.6.RCD:3 - Forces

ForceTension to resolve
Exact semantics vs readable useAuthors MUST make each conforming derivation replayable without making every practitioner read formal notation.
Local affordability vs repeated reuseOne local claim should stay cheap; repeated semantics should not be copied inconsistently.
Expressive claims vs small ontologyFPF should permit compound truths without minting one kind per compound predicate.
Reuse vs hidden dependenciesReusable definitions need visible base-relation and substrate editions.
Truth conditions vs occurrence semanticsA predicate can be satisfied without supplying a way to reidentify relation occurrences.
Formal power vs substrate authorityConstructor names are available only where the selected substrate gives them semantics.
Mathematical representation vs ontologyA formula, path, graph, or query can represent a rule without making that rule obtain in the world.