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 10:15:17 UTC

C.31.RSA:3 - Forces

ForceTension
Reuse visibility vs false proofReusable loci should be visible, but a share is not proof of quality, assurance, or architecture adequacy.
Accounting convenience vs heterogeneous structureTemplates, interface grammars, work methods, and evidence packages do not automatically share one unit.
Residue repair vs useful exceptionSome bespoke residue should be refactored; some should remain a bounded exception.
Compression vs source returnAccounting can summarize structure, but downstream action may require return to source-side records.
Local triage vs cross-case comparisonA local report-only share can guide repair; comparison needs declared scale, unit interpretation, admissible comparability relation, and comparator admission named by value.
Reuse value vs reuse costMore reusable structure can increase interface cost, evidence decay, or loss of needed variation.