Preflight Resource Probe¶
Pre-use readiness checklist — instantiates Use-Time Referent Validation
Sweeps every referent a high-stakes operation depends on in one go/no-go check just before the point of no return, so a single missing dependency blocks the whole action rather than surfacing mid-flight.
Some operations cannot be half-done. Before one starts, Preflight Resource Probe enumerates every referent the action leans on — the files, permissions, downstream services, inputs, and physical resources — and confirms in a single consolidated sweep that each is present, ready, the intended thing, and authorized. Its defining move is the batch and the timing: rather than discovering a dead dependency partway through an irreversible action, it forces one explicit go/no-go moment as close as possible to the point of no return, where any single unconfirmed item halts the whole operation before it begins. It does not watch continuously and it does not re-check per dereference; it takes one deliberate readiness snapshot, on purpose, right before you commit.
Example¶
An operating team is about to make the first incision. Before the scalpel touches skin, everyone stops for a time-out[n1]: the surgeon, anesthetist, and nurse confirm out loud that this is the right patient, the surgical site is the one marked, consent is on file for exactly this procedure, the correct imaging is on the screen, the right implant is in the room, antibiotics were given in the window, and the instrument count is complete. Each of these is a referent the operation depends on — and each was "true" at some earlier point (in the pre-op notes, the booking, the consent signed last week). The time-out re-confirms, at the last reversible moment, that each still resolves to the intended, current thing.
The value shows up on the miss. A consent form is for a left knee; the marked site is the right. Any one item failing collapses the whole go decision — the incision does not happen, and the mismatch is resolved before it becomes irreversible. That is the mechanism's entire purpose: catch the one assumed-fine dependency while stopping still costs nothing.
How it works¶
- Enumerate the full dependency set. List every referent the action requires, not just the ones expected to be problematic — the checklist's coverage is its whole value.
- Run one consolidated check at the last safe moment. Position the sweep as close to the point of no return as possible so the snapshot has the least time to go stale.
- Require explicit affirmation, not silence. Each item is actively confirmed (present, correct, identified, authorized); an unspoken assumption does not count as a pass.
- Treat any single failure as a hard stop. The probe is a conjunction — one unconfirmed referent blocks the entire operation, rather than being worked around in flight.
Tuning parameters¶
- Scope — how many dependencies make the list. Broader coverage catches more, but a bloated checklist invites rote ticking; prune to the items that can actually be missing.
- Proximity to use — how close to the irreversible step the sweep runs. Closer means a fresher snapshot but less time to react; further back buys recovery time at the cost of staleness.
- Affirmation mode — silent tick-box versus read-and-respond aloud. Spoken cross-confirmation resists autopilot but costs time and social friction.
- Risk-weighting — which items are mandatory hard-stops versus advisory. Weight by
volatility_and_risk_profile: volatile, high-consequence referents get a hard gate; stable ones can be advisory. - Stop-strength — whether a failed item is an absolute block or an override-with-signoff. Overridable gates flex under pressure but erode the "any failure stops everything" guarantee.
When it helps, and when it misleads¶
It is strongest exactly where a single missing referent is catastrophic and the action cannot be partially undone: launches, cutovers, surgeries, irreversible deletes. It surfaces the dependency everyone assumed was fine, and it does so while stopping is still free.
Its failure modes are staleness and ritualization. Because it is a one-shot snapshot, anything that changes between the probe and the actual use slips through — the longer that window, the less the check is worth, which is why it pairs with a use-time guard when the gap is non-trivial. And a checklist run too often against too many always-green items degrades into box-ticking, where items are affirmed without being examined — a slow slide into treating the deviation as normal.[n2] The classic misuse is running the probe as an after-the-fact compliance record rather than a genuine pre-commit gate. The disciplines that keep it honest: keep the list short and failable, keep it close to the point of use, require real affirmation, and hand the check-use gap to a mechanism built to close it.
How it implements the components¶
action_referent_dependency— the checklist is the enumerated dependency set: every referent the action relies on, made explicit as a row to confirm.identity_and_sameness_test— each item is confirmed to resolve to the intended thing (right patient, right site, right implant), not merely to something present.volatility_and_risk_profile— the risk-weighting step decides which referents are mandatory hard-stops versus advisory, based on how volatile and how consequential each is.
It does not evaluate a live validity predicate at each dereference — that's Just-in-Time Existence Check; it does not close the check-to-use gap under concurrency — that's Transactional Precondition Guard; and it does not define the recovery route on a miss — that's Safe Missing-Referent Fallback.
Related¶
- Instantiates: Use-Time Referent Validation — Preflight Resource Probe supplies the one-shot, batch readiness gate just before an irreversible action.
- Sibling mechanisms: Just-in-Time Existence Check · Transactional Precondition Guard · Atomic Check-and-Use Operation · Capability or Authorization Revalidation · Compare-and-Swap or Version Guard · Lease, Lock, or Reservation Token · Revocation or Tombstone Check · Safe Missing-Referent Fallback · Stale Reference Monitor
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Preflight Resource Probe operates as a repeatable ordered procedure or handoff sequence that coordinates action because it sweeps every referent a high-stakes operation depends on in one go/no-go check just before the point of no return, so a single missing dependency blocks the whole action rather than surfacing mid-flight.
Independent corroboration: The frozen evidence defines Preflight Resource Probe as 'Sweeps every referent a high-stakes operation depends on in one go/no-go check just before the point of no return, so a single missing dependency blocks the whole action rather than surfacing mid-flight', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Sweeping all required referents immediately before commitment follows aviation preflight and mission-readiness practice.
Related originating lineages:
- Computer Science & Software Engineering — Atomically validating all runtime dependencies before an irreversible operation is a software and systems-engineering practice.
- Engineering & Design — Systems engineering materially contributes dependency closure and binary readiness criteria.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of aviation aeronautics. World Health Organization: Surgical Safety Checklist Tools and Resources directly documents the defining practice or theory described in the selected origin rationale. Other domains are retained only where the blind reviews identify material co-development or translation; broad application is recorded separately as domain_reach=multi_domain, while origin_mode=convergent describes the relationship among origin lineages.
Attribution caveat: The boundary with computer science is substantive because that tradition materially developed or translated part of the mechanism; the cited provenance places the defining form in aviation aeronautics.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
Notes¶
The probe validates a snapshot; it does not hold anything in place. If a confirmed referent can be revoked, consumed, or moved in the interval before use, the snapshot's guarantee decays with the length of that interval — so on high-contention resources it belongs upstream of an atomic or transactional guard, not in place of one.
[n1] The pre-incision "time-out" is a step of the WHO Surgical Safety Checklist, a real, widely-adopted protocol in which the operating team pauses to confirm patient, site, and procedure before beginning. It is the canonical real-world instance of a batch preflight sweep on an irreversible action. ↩
[n2] Normalization of deviance — Diane Vaughan's term for how a group gradually comes to accept a deviation from safe practice as normal because it has not yet caused harm. It is the mechanism by which a live checklist decays into rote affirmation. ↩