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 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:30:16 UTC

C.30.STRAT:3 - Forces

ForceTension
Source-language usability vs ontologyPractitioners need compact local words; a technical claim needs the actual object or relation, its participants or bearer, its scope, and its allowed use.
Pattern placement vs applicable ruleC.30 placement does not decide the applicable rule: the recovered claim may belong to control, modules, flow, scale, publication, state, evidence, work, or decision.
Thin repair vs shadow registryOne shared cue table is useful; copied local trigger lists are not.
Known meaning vs detourWhen the current object or relation is already clear, use its pattern directly.
Precision vs actionA type-correct result is still a failure if the reader cannot see what to do next.