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

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:0 - Use this when

Use A.21 when a named gate must decide whether one bounded action or transition may proceed under an applicable profile rule. Identify every check that the rule requires, including the subject and criterion of each check.

First useful move. Name the action being decided, the profile rule that applies, and every required check result. Map each check result under that rule, then let the worst mapped value win.

Quick worked case. WorkshopEntryGate-4 decides whether CalibrationCycle-17 may start before 16:00. WorkshopEntryProfile-E5 requires two checks: CalibrationCertificate-44 for TorqueWrench-12 is current under CalibrationRule-E3, and WorkshopEnclosure-2 is closed under EnclosureRule-E2. Both checks are evaluated and satisfied, so each maps to pass; the gate returns pass and the cycle may start before 16:00. Recheck if the instrument, certificate edition, enclosure state, profile edition, or time window changes.

If the state of WorkshopEnclosure-2 is unknown, that check remains unknown. WorkshopEntryProfile-E5 maps the uncertainty to block, not to abstain, so the cycle stays on hold until the enclosure is checked. A different policy may accept a bounded uncertainty only through an explicit rule that names the subject, tolerance, consequence, and validity window.

Short boundary. A gate decision is neither work-entry readiness nor performed Work. Use A.15.5 for the ordinary readiness question. If Work later occurs, identify it under A.15.1; do not treat the gate, plan item, or prospective claim as that later Work.

What goes wrong if missed. A green display is mistaken for permission, an unknown required check disappears as a neutral value, two different check subjects are merged by label, or a new path slice is treated as authority to weaken policy.

What this buys. The practitioner can recover what was decided, which rule applied, which facts supported the decision, what action follows, and when the decision must be made again.

Not this pattern when.

  • Use A.20 for one internal-constraint result.
  • Use A.15.5 for full-kit or work-entry readiness without a gate decision.
  • Use E.18 for transformation-flow positions, paths, slices, and structural crossings.
  • Use the pattern that defines the policy, safety rule, regulatory rule, evidence claim, channel condition, or system-role claim for the truth of that check.
  • Use E.17 when the decision needs a source-backed reader face and return to source; use E.24.PUB when its publication occurrence, form, carrier, or availability matters.