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

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 06:05:20 UTC

A.1:3 - Forces

ForceTension
Universal root vs domain comfortPractitioners know words such as system, model, product, team, document, program, and discipline; FPF needs a cross-domain root that does not import one domain’s assumptions.
Identity vs compositionA thing can be individuated before FPF knows whether it has parts or belongs to a larger whole.
Acting vs claim-bearingSystems can be classified by exact local system-role kinds, perform Work, and participate in separately governed system-role-assignment, Method-enactment, plan-use, publication, citation, comparison, or reliance relations. Changed claim content identifies another episteme under C.2.1.
Open-world modeling vs premature completionA holon slot can be relevant even when not yet filled; omission means “not current or not recovered”, not absence in the world.
Collection usefulness vs collective agencyCollections can have whole-level characteristics without being acting systems.
Architecture usefulness vs math-lens driftGraphs, algebras, matrices, and embeddings can describe structures; they do not become the structure or holon by spelling.