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:20:10 UTC

B.1.5:3 - Forces

ForceTension
Method reuse vs source concretenessTeams need a reusable way of doing, while sources often show only one description, run, or plan.
Order fidelity vs compact modelingImportant sequences and joins must remain explicit without turning every diagram edge into ontology.
Order vs simultaneous contributionA real first–then condition must survive, while Methods that contribute together must not be invented as stages merely because they are described in sequence.
Whole-method identity vs relation usefulnessSome method-side relations are useful without asserting one composite method whole.
Interface exposure vs encapsulationA composite method must state which interactions callers may rely on and which remain internal.
Assurance vs executionAssurance needs joins, adapters, cutsets, and failure conditions; dated enactment, result, and evidence-use claims stay with their subject patterns.