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 09:45:10 UTC

A.15.2:7c - Consequences

BenefitTrade-off and mitigation
Plans become inspectable without being confused with performed work.More explicit claims; mitigate by using compact PlanItem content for ordinary coordination.
Variance becomes meaningful because planned baseline and performed work stay separate.Requires discipline around baselines; keep the exact plan episteme and baseline visible, and name an edition relation only when its predicate actually obtains.
Cross-team and cross-context coordination becomes safer.Requires the two reference schemes, exact SchemeSenseCell correspondence, separate use claim, and reliance result; apply checklist item 7 before reusing a planned value, target, or verdict.
P2W carry-through can prepare work without pretending work already happened.Use A.15.1, A.15.3, A.15.4, A.15.5, A.10, B.3, A.20, or A.21 only when the source actually makes the corresponding performed-work, planned-filling, appearance-based reliance, readiness, evidence, assurance, internal constraint, or gate claim.