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 08:26:43 UTC · last check 2026-10-03 08:50:20 UTC

A.10.1:3 - Forces

ForceTension
Unknown receiving uses vs bounded effortReceiving uses cannot all be named before discovery, but a global corpus search is rarely justified.
Source-outward trace vs receiver-side realityBacklinks and lineage find declared uses; receiver inspection finds equivalent or undeclared premises. Neither direction alone is generally adequate.
Automation vs judgmentSearch, lineage, traces, and AI can find candidates; the practitioner tests actual reliance in the receiving content under the direct rule.
Local closure vs hidden gapsIndependent resolved branches should finish, while inaccessible or unindexed surfaces must not become implicit evidence of no impact.
Reuse vs safetyUnaffected prior results should remain usable, but only when the changed claim lies outside their actual dependency.
Common move vs subject authoritySource-to-use discovery is reusable; materiality remains specific to the subject, including any separate evidence, assurance, or release question.
Short account vs recoverabilityThe result should be usable without a universal impact record, yet another practitioner must be able to reproduce the frame, coverage, direct-use test, and stop.