fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 75409–75422

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:35:10 UTC

C.32.ADA:4.3 - Use-specific stop conditions

Declare the use before scoring. Common uses:

Declared useOrdinary stop condition
Internal architecture discussionEvery triggered coordinate is evaluated; 0 absent coordinates block reliance, and values below 3 sufficientlyExpressedForDeclaredUse name the patterns or sources that must be repaired.
Ready for architecture reviewNo triggered coordinate below 3 sufficientlyExpressedForDeclaredUse; candidate basis, trade-off, affected structures, work split, and reopen condition are strong enough for reviewers to inspect by value.
Ready for developer work or implementation commitmentEvery triggered coordinate is at least 4 wellExpressedForDeclaredUse unless a governing project decision explicitly declares a lower diagnostic floor and says the result is not an implementation commitment.
Ready for ADR-like publicationPublication projection, section functions, status, source-return, and supersession are at least 4 wellExpressedForDeclaredUse; if the record will guide developer work, use the developer-work floor too.
Ready for governance enforcementEvery triggered coordinate is at least 4 wellExpressedForDeclaredUse; enforcement status requires a separate current gate, evidence-use, assurance, or governance result.

Use these as ordinary defaults. A project can declare stricter stop conditions. It must not weaken a triggered coordinate by hiding it under an average, and it must not call a diagnostic result ready for developer work or governance enforcement.