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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:15:11 UTC

A.2.5:9 - Common Failure Modes and Repairs

FailureObservable symptomRepair
Assignment-as-readinessA Work claim proceeds because a holder is assigned.Name the state predicate and establish the corresponding relation for the Work window.
State-label transportTwo domains use Ready as if it were one predicate.Compare full predicate identities; use an explicit bridge only when cross-context preservation is claimed.
Evidence-as-stateA certificate or dashboard display is entered as the state.Keep the world-side relation separate and target its assertion with an evidence-use relation.
Evidence-gap-as-falseA missing current report closes a state episode.Record unresolved reliance; close the occurrence only when a truth-condition clause is demonstrated not to hold.
Capability-as-admissionTool exposure or measured ability admits a concrete action.Keep capability in A.2.2 and evaluate current state and action-specific conditions separately.
Method-order driftTransition arrows are used as the procedure.Name the Work, transformation, decision, or event occurrences that change predicate truth and put order in the Method description.
Product-state explosionA multi-assignment Work claim enumerates every combination of labels.Use separate state occurrences and only the conjunction needed by the current claim; create no compound system-role kind or assignment by form.