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:40:10 UTC

A.15.8:3 - Forces

ForceTension
Useful whole versus justified wholeA coupled arrangement can be a useful unit of analysis without being one admitted U.System, performer, Agent, or capability holder.
Actual versus prospectiveActual Work permits obtaining performer and support claims; a present WorkPlan permits only current claims about plan content and a proposed configuration.
Compact result versus exact ownershipA reader needs one short result, while System identity, Work, capability, representation, evidence, architecture, and choice remain independently governed.
Perfect-run success versus recoverabilitySuccess in one live configuration does not establish recovery after interruption, handoff, staleness, or degraded support.
Transferable skeleton versus domain mechanismMany domains share the configuration-and-probe move, but their checkpoints, cues, thresholds, safety conditions, and recovery mechanisms differ.
Recognition versus assuranceOne credible failure can open the pattern; consequential use may require much stronger evidence, authority, and stop rules.
State availability versus state correctnessA carrier may be present while its value is stale, inconsistent, uninterpretable, inaccessible, or unsafe to use.