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.21:7 - Check the ordinary gate decision

  1. Decision. Name the gate, the action or transition being decided, its scope, and its time window.
  2. Applicable rule. Point to the profile rule and edition that apply to this gate and subject. Recover its required checks, mappings, consequences, scope and window, and any authority the rule itself requires.
  3. Checks. For each check, name its subject, criterion and edition, case, requirement, evaluation state, source result, and mapping rule.
  4. Nothing missing. Keep every required check visible, including notRun, unknown, error, and failure.
  5. Worst result wins. Aggregate only after the rule has mapped every required result. A missing or unrun required result cannot support pass.
  6. Next action. State what pass, degrade, block, or abstain means for this action and when to decide again.
  7. Boundary. Do not turn the decision into work-entry readiness or performed Work, and add no crossing, Bridge, publication, or assurance claim that is absent.

A.21:7.1 - Triggered additions

Current useAddDirect pattern
Launch decisionProspective work-entry claim and only the checks selected by the applicable profileA.15.5, E.18, and the pattern defining each check
Structural crossingChanged-binding and crossing facts; SquareLaw only when its crossing rule appliesE.18
Semantic correspondenceSeparate Bridge and bounded-use claim; optional evidence or publication apparatus only when usedF.9, F.17; E.17 for a source-backed reader face, E.24.PUB for publication occurrence, form, carrier, and availability
PublicationForm, carrier, publication occurrence, and the minimum decision refsE.24.PUB; E.17 when a source-backed reader face is needed
Evidence, safety, regulation, or assuranceExact source result and its evidence or assurance relationA.10, B.3, or the applicable domain pattern
Reuse or replayEquivalence witness when claiming reuse, cache, or stability over an interval; optional decision log for audit, history, or replay§4.10; G.6 when a citable provenance path is needed, G.11 when currentness or refresh is at issue, and E.24.PUB when published