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 14:30:10 UTC

C.31:4.6 - Claim-scoped residual heads

C.31 uses residual heads only as qualitative repair cues. These heads do not create one complexity characteristic.

HeadMeaningRelated claim pattern locator and assertion requirementRiskRepair direction
ComplexityGrowthPressurePressure to add, split, mediate, or stabilize a declared aggregation scope, interface grammar, control relation, evidence scope, work-method scope, abstraction scope, or source-return condition.C.30.ILC, C.31.ASAP when an architecture scale-preference claim is being made, G.5, C.11treating more apparatus as progressname the pressure and the repair direction; use set-return or decision patterns when the corresponding claim is being made
FrustrationResidualPersistent cross-scope residual after local repair.C.30.ILC, C.29-local cross-scope lens claimturning a lens-backed interpretation into proofkeep as residual cue or apply C.29 or C.30.ILC
ConflictResidualSlopeResidual grows or shrinks over declared scale variable, scale window, or coarse-graining scale.C.31.ASAP, C.29, C.27, C.18.1, C.19.1treating two points as universal lawdeclare window, lens-use boundary, and measurement basis or stop at report-only
DeclaredScopeAdditionCostAdded work, evidence, change-policy, latency, observability, accountability, or interface cost from a new declared aggregation or control scope.C.16, C.31, C.30.LCAignoring the cost of added structureidentify cost bearer and apply the measurement pattern if used for comparison
BespokeResidueGrowthOne-off exceptions grow with deployment spread, regulation, or project repetition.C.31.RSA, C.31.ASAP when an architecture scale-preference claim is being madeassuming all bespoke work is badsplit useful exception from repairable residue
InterfaceAlphabetGrowthInterface variants grow faster than reuse, substitutability, or integration payoff.A.6.M, C.31premature standardizationadd platform grammar, split context, or accept bounded variation
SourceReturnCostFrequency or cost of returning from a compressed, indexed, coarse, extracted, or accounting view to source-side structure records.C.29, source-return discipline, A.10over-compressionadd source-return condition or reduce compression
ControlNestingDepthRiskNested control relations create latency, accountability, observability, stability, or assurance cost.C.30.LCA, C.27, B.3, A.3.3LCA-as-proofapply control, temporal, assurance, or dynamics subject patterns when the corresponding claim is being made