Implementation Intention¶

Version: v1 · 2026-08-24 · History
Prime #: 908
Origin domain: Psychology
Subdomain: cognitive behavioral → Psychology

Core Idea¶

An implementation intention pre-binds, in advance, a specific future cue to a specific action — "when X occurs, I will do Y" — so that at the moment of execution the cue triggers the behavior without re-deliberation. The pattern decouples intention to act from decision to act now by compiling the conditional ahead of time and shipping it to whatever fast, low-attention mechanism runs the trigger. The structural force comes not from the conditional shape itself — any rule is a conditional — but from the pre-binding under absent deliberation condition: the decision is made once, in advance, and at runtime the system only matches and dispatches.^[1]

The load-bearing components are a cue specification naming a future condition with enough precision to be recognized; a bound action paired with that cue ahead of execution time; a registration step that installs the binding in whatever mechanism — memory, rule table, handler — will fire it; and an execution path that does not consult the deliberative process once the cue fires. The pattern is the generic mechanism that ships a decision from a slow, deliberative subsystem to a fast, automatic one, and it applies wherever such a two-tier execution architecture exists.^[1] Robustness depends on three things: cue specificity, binding strength, and the absence of competing triggers that could capture or override the intended dispatch.

How would you explain it like I'm…

When-Then Plan

Before bed you decide once: 'When I wake up, I'll put on my shoes by the door.' Then in the morning you don't have to think — seeing the door reminds you, and you just do it. An implementation intention is deciding ahead of time 'when THIS happens, I'll do THAT,' so later it happens almost by itself.

Decide-Ahead Trigger

An implementation intention is a plan shaped exactly like 'when X happens, I will do Y,' made AHEAD of time so you don't have to decide in the moment. Normally, wanting to do something and actually choosing to do it right now are two separate steps, and the second step is where people freeze or forget. By picking the trigger and the action in advance — 'when the bell rings, I start my homework' — you hand the decision off to the fast, automatic part of you. Then when the trigger shows up, you just match it and go, no arguing with yourself. It works best when the trigger is specific, the link is strong, and nothing else is competing to grab you at that moment.

Pre-Wired If-Then

An implementation intention pre-binds, in advance, a specific future cue to a specific action — 'when X occurs, I will do Y' — so that at the moment of execution the cue triggers the behavior without re-deliberation. It decouples the intention to act from the decision to act NOW by compiling the conditional ahead of time and handing it to whatever fast, low-attention mechanism runs the trigger. The power comes not from the if-then shape itself — any rule is a conditional — but from the pre-binding-under-absent-deliberation condition: the decision is made once, in advance, and at runtime the system only matches and dispatches. The load-bearing parts are a cue specification (a future condition named precisely enough to be recognized), a bound action paired with it ahead of time, a registration step that installs the binding wherever it will fire, and an execution path that doesn't consult deliberation once the cue fires. Robustness depends on three things: cue specificity, binding strength, and the absence of competing triggers that could hijack the dispatch.

An implementation intention pre-binds, in advance, a specific future cue to a specific action — 'when X occurs, I will do Y' — so that at the moment of execution the cue triggers the behavior without re-deliberation. The pattern decouples intention to act from decision to act now by compiling the conditional ahead of time and shipping it to whatever fast, low-attention mechanism runs the trigger. The structural force comes not from the conditional shape itself — any rule is a conditional — but from the pre-binding-under-absent-deliberation condition: the decision is made once, in advance, and at runtime the system only matches and dispatches. The load-bearing components are a cue specification naming a future condition with enough precision to be recognized; a bound action paired with that cue ahead of execution time; a registration step that installs the binding in whatever mechanism — memory, rule table, handler — will fire it; and an execution path that does not consult the deliberative process once the cue fires. The pattern is the generic mechanism that ships a decision from a slow, deliberative subsystem to a fast, automatic one, and it applies wherever such a two-tier execution architecture exists. Robustness depends on three things: cue specificity, binding strength, and the absence of competing triggers that could capture or override the intended dispatch.

Structural Signature¶

the cue specification — the bound response — the ahead-of-time registration step — the deliberation-free runtime dispatch — the two-tier slow-decide/fast-execute split

The pattern is present when each of the following holds:

A cue specification. A future condition is named with enough precision to be recognized when it occurs — a state, an event, a threshold. Specificity of this cue governs the trigger rate.
A bound response. A particular action is paired with the cue, fixed in advance of the moment of execution rather than chosen then.
A registration step. The cue-action binding is installed, ahead of time, into whatever fast mechanism will fire it — a memory trace, a rule table, a handler, a checklist entry.
Deliberation-free dispatch. At runtime the system only matches the cue and dispatches the bound action; the slow deliberative process is not consulted once the cue fires. This pre-binding under absent deliberation is the load-bearing condition that distinguishes the pattern from any ordinary conditional.
A two-tier architecture. The pattern presupposes a slow, high-attention subsystem that decides once and a fast, low-attention subsystem that executes on match; it ships a decision from the former to the latter.
Capture vulnerability. Robustness turns on cue specificity, binding strength, and the absence of competing triggers that could capture the intended dispatch — the three independent points at which the chain can break.

These compose into a compile-ahead-of-time mechanism: deliberation is relocated to a single prior planning act, leaving only cheap recognition and dispatch at the moment of action.

What It Is Not¶

Not a commitment device. A commitment_device binds future choice by making defection costly, addressing temptation; an implementation intention binds future execution by precompiling a cue-action link, addressing forgetting and hesitation. They target different failure modes and often combine.
Not conditioning. conditioning_behavioral installs a cue-response link gradually through associative learning over many trials; an implementation intention installs the link by a single explicit act of declaration, then must survive against habits that were consolidated by repetition.
Not foresight. foresight keeps options open by surveying possible futures; an implementation intention closes options by pre-binding one response to one cue. The two are opposed design pressures, not the same move.
Not a heuristic. A heuristic is a general decision rule applied across many situations to economize on search; an implementation intention is a single specific cue-action binding installed for one anticipated condition, with no generalization claim.
Not automaticity itself. Automaticity is the steady state in which execution is fast and unconscious; an implementation intention is the installation mechanism that bootstraps toward that state without waiting for repeated trials to build it.
Common misclassification. Reading a motivation failure as a binding failure. When the agent recognizes the cue, recalls the action, and deliberately declines it, no amount of sharper cueing helps — the problem has crossed into commitment_device territory.

Broad Use¶

In behavioral and health psychology, the origin, "when I finish lunch, I will take my medication" converts an open-ended goal into an executable conditional, and the effect is robust across domains where intention alone fails to produce behavior.^[2] In software systems event handlers, interrupt vectors, and trigger-action rules register a condition ahead of time that fires automatically when the cue matches.^[3] In military and emergency doctrine standing orders and battle drills precompile action so it executes under cognitive load when deliberation would be too slow.^[4] In aviation and medicine checklists with branching conditionals — "if cabin altitude exceeds the threshold, then masks on" — and pre-briefed contingencies bind responses to named cues before the situation arrives.^[5] In organisational decision-making pre-mortems and tripwires name a threshold and the action it triggers, fixing the response before bias has a chance to bend it. The same structural pattern — cue specification, bound action, execution without re-deliberation — appears in each, only the mechanism that holds the binding changing across substrates.

Clarity¶

The pattern names the difference between holding a goal and having a precompiled rule to execute toward it. A great deal of the intention-behavior gap becomes legible once the wish is separated from the if-then: the gap is not weakness of will but the absence of a registered, cue-triggered binding. In automation design the same distinction separates a workflow that asks the user what to do from one that has already encoded the answer. Naming the pattern also distinguishes it from its neighbours. A commitment device binds future choice by making defection costly, addressing temptation; an implementation intention binds future execution by precompiling the cue-action link, addressing forgetting and hesitation — the two often combine but target different failure modes. Conditioning produces a cue-response link through associative learning over many trials; an implementation intention installs the link by explicit declaration in a single act of planning. And automaticity is the steady state where execution is fast and unconscious; an implementation intention is the installation mechanism that bootstraps toward it without waiting for repetition.

Manages Complexity¶

The pattern pushes branching decisions out of the hot path. Instead of representing every possible state requiring evaluation at runtime, the system pre-binds responses to a sparse set of named cues, so that mental or compute load at execution drops, reliability under stress rises, and the budget at the moment of action can be near-zero. By relocating the deliberation to a single prior planning act and leaving only match-and-dispatch at runtime, the pattern lets a designer reason separately about which conditions are recognized and which response is bound to each, rather than about the full runtime decision space. That separation is exactly what makes a system reliable under load: the expensive reasoning has already happened, and what remains is cheap recognition.

Abstract Reasoning¶

The pattern makes a clean separation between the cue lattice — what conditions are recognized — and the action policy — what response is bound to each. The two can be designed and audited independently, which is itself a structural affordance: a failure can be localised to cue recognition, to binding, or to execution, three distinct repair targets that a unified "the rule didn't work" framing hides. It also supports inference about robustness conditions that port across substrates: specificity of the cue increases trigger rates, conflicting cues create capture failures, rehearsal strengthens the binding, and competing prior habits override weakly bound rules.^[2] These are structural properties of any two-tier register-then-dispatch architecture, not facts about human psychology specifically, and they predict where such a system will fail before it is deployed.

Knowledge Transfer¶

Because the pattern carries structure rather than mere metaphor, the findings and interventions transfer across substrates without re-derivation. From the behavioral literature one inherits a set of properties — specificity of the cue increases trigger rates, conflicting cues create capture failures, rehearsal strengthens the binding, competing prior habits override weakly bound rules — each of which maps directly into rule-based automation, doctrine design, and product nudges. The interventions transfer in the same way: sharpen the cue so it is unambiguously recognizable, rehearse the binding under load so it survives stress, isolate competing triggers so the intended dispatch is not captured, and make the action atomic enough to execute in one step. The structural reason an implementation intention works is identical to the reason an interrupt handler reliably runs while a polling loop with manual dispatch does not:^[6] the cue and the response are pre-bound, so execution does not depend on the agent noticing, weighing, and choosing in the moment — and that explanation ports from a patient's gym habit to a database trigger to a battle drill without alteration. The transfer carries its boundaries as well: a receiving domain must distinguish the pattern from a commitment device (which binds choice against temptation rather than execution against forgetting), from conditioning (which installs the link by repetition rather than declaration), and from foresight (which keeps options open where an implementation intention closes them by pre-binding a single response). A practitioner who has installed cue-triggered actions in one substrate arrives at the next already asking whether the cue is specific enough, whether the binding is strong enough, and whether any competing trigger could capture it.

Examples¶

Formal/abstract¶

Consider an interrupt-driven embedded controller. The cue specification is a hardware condition — say, a rising edge on GPIO pin 7 signaling that a sensor crossed a threshold.^[6] The bound response is the interrupt service routine (ISR) registered for that vector — a fixed, short block of code. The registration step is installing the ISR address into the interrupt vector table at boot, ahead of any event. The deliberation-free runtime dispatch is the processor's hardware dispatch: when the edge fires, the CPU saves context and jumps directly to the ISR without consulting the main program loop — no polling, no if-checking in the hot path.^[6] This instantiates the two-tier slow-decide/fast-execute split exactly: the slow tier is the boot-time configuration that decides which handler serves which vector; the fast tier is the silicon that matches and dispatches in nanoseconds.^[6] The prime's capture vulnerability maps to real failure modes a designer can reason about in advance. Cue specificity failure: an over-broad interrupt condition (level-triggered on a noisy line) fires spuriously, the analog of a vague behavioral cue triggering at the wrong moments. Binding strength failure: an ISR that is too long blocks other interrupts, so the binding fails to execute atomically. Competing triggers: interrupt priority collisions where a higher-priority vector captures the dispatch the designer intended. The intervention set — sharpen the cue (debounce the line), isolate competing triggers (set priority masks), make the action atomic (keep the ISR short, defer work to a task) — is the same checklist the behavioral literature supplies, read off the same structure.

Mapped back: The vector table is the registration step, the ISR the bound response, the hardware edge the cue, and hardware dispatch the deliberation-free runtime — with debouncing, priority masks, and short ISRs the substrate-specific forms of the prime's three robustness moves.

Applied/industry¶

Consider an aviation emergency checklist, such as a rapid-decompression procedure.^[7] The cue specification is a named, recognizable condition: "if cabin altitude exceeds 14,000 feet."^[7] The bound response is a fixed action sequence: "don oxygen masks, establish crew communication, initiate emergency descent."^[7] The registration step is the pre-flight briefing and the crew's prior training and memorization, which install the cue-action binding before the situation arrives. The deliberation-free dispatch is the crucial payoff: under hypoxia and time pressure, the crew does not deliberate about what to do — the cue fires the precompiled response, because deliberation at that moment would be too slow and cognitively impaired. The prime explains precisely why checklists work where good intentions fail: the response is shipped from the slow, high-attention deliberative tier to a fast, trained, low-attention tier ahead of time. The same structure governs organizational tripwires: a board pre-commits "if monthly burn exceeds $X for two consecutive months, we trigger the layoff plan," binding the painful action to a named threshold before motivated reasoning can bend the decision when the moment comes.^[8] And in health behavior — the prime's origin domain — "when I finish lunch, I will take my medication" binds an atomic action to a reliably recurring daily cue, converting an open-ended adherence goal into an executable conditional. Across all three, the diagnosis when it fails is the same: was the cue specific enough to be recognized, was the binding rehearsed enough to survive load, and did a competing trigger capture the dispatch?

Mapped back: The decompression threshold is the cue, the mask-and-descend sequence the bound response, the pre-flight briefing the registration step, and the trained reflex the deliberation-free dispatch — the identical register-then-dispatch structure that drives organizational tripwires and medication-adherence intentions.

Structural Tensions¶

T1 — Pre-binding versus Stale World (temporal). The decision is made once, in advance, and dispatched without re-deliberation at runtime — which means the binding embeds assumptions about a future state that may no longer hold when the cue fires. The prime's whole value is not reconsulting the slow tier; its whole risk is firing a response the deliberative process would now veto. The failure mode is a correctly-triggered but wrongly-applicable action: the standing order executes flawlessly into a situation the planner never anticipated. Diagnostic: ask what staleness-check, if any, sits between cue match and dispatch — a pure implementation intention has none, which is the point and the hazard.

T2 — Cue Specificity versus Coverage (scalar). Sharpen the cue so it never misfires and you narrow it until real instances slip past unrecognized; broaden it for coverage and you invite spurious triggers. These pull in opposite directions and cannot both be maximized. The failure mode at one pole is silent non-firing (the medication cue "when I get home" never matches because home arrival is irregular); at the other, capture by look-alikes (a level-triggered interrupt firing on line noise). Diagnostic: count both the missed real cues and the false fires — optimizing only one number guarantees the other degrades.

T3 — Where Commitment Devices Take Over (scopal). Implementation intention binds execution against forgetting and hesitation; it does not bind choice against temptation. When the failure is that the agent recognizes the cue, recalls the action, and deliberately declines it, the prime has reached its boundary and a commitment device — which makes defection costly — is the right tool. The failure mode is prescribing sharper cues for a motivation problem: rehearsing "when X, I will Y" endlessly while the agent simply chooses not to. Diagnostic: ask whether the binding fails at recognition/dispatch (implementation-intention territory) or at a live decision to override (commitment-device territory).

T4 — Declaration versus Consolidation (measurement/strength). The link is installed by a single explicit act of planning, not by repetition — which is its speed advantage and its fragility. A freshly declared binding competes against prior habits that were laid down over thousands of trials, and on the first few firings the old automatic response often wins. The failure mode is assuming the binding is as strong as the conditional is clear, then watching a long-standing habit override a once-stated rule. Diagnostic: measure binding strength by rehearsals-under-load survived, not by clarity of the if-then statement — declaration sets the link, only consolidation makes it robust.

T5 — Single Binding versus Competing Triggers (coupling). The pattern presumes the intended cue-action dispatch runs in isolation, but real substrates host many registered bindings sharing one execution channel, and they interact. A higher-priority vector captures the dispatch; a competing prior intention fires on the same cue; two interrupts collide. The failure mode is auditing a binding in isolation, confirming it is correct, and still getting the wrong behavior because another trigger pre-empted it. Diagnostic: ask not only "is this binding right?" but "what else is registered against this cue or this channel, and who wins the race?"

T6 — Closing Options versus Keeping Them Open (sign/direction). Pre-binding a single response is a deliberate narrowing: it forecloses the runtime flexibility to choose differently, which is exactly opposite to the design pressure of foresight, which keeps options open. The two are competing primes, and which one should govern depends on whether the cost of hesitation exceeds the cost of being locked into a now-suboptimal action. The failure mode is precompiling a rigid response in a domain that rewards adaptive judgment — a battle drill where the situation demanded improvisation. Diagnostic: ask whether the moment of action is one where deliberation is too slow to afford (bind it) or one where the right move is genuinely unknowable in advance (keep it open).

Structural–Framed Character¶

Implementation intention is a mixed-structural prime, sitting just on the structural side of the middle of the structural–framed spectrum. Underneath the behavioral-psychology name is a bare two-tier mechanism — register a cue-action binding ahead of time, then match-and-dispatch at runtime without re-deliberation — that runs identically in silicon, doctrine, and cognition; what holds it back from the fully structural end is the "intention" vocabulary it carries.

On the diagnostics, the structural reading dominates. The pattern carries no evaluative weight: a precompiled cue-action link is neither virtuous nor faulty until you specify what it fires — an interrupt service routine, a battle drill, and a medication if-then are the same register-then-dispatch machine, value-neutral in itself. Much of its origin and spread is non- institutional: the embedded-controller ISR, the trigger-action rule, and the event handler instantiate the structure in pure computational substrates with no human practice required, which is why human_practice_bound and institutional_origin each read only 0.5 rather than 1. And invoking the prime on a hardware interrupt vector mostly recognizes a pattern already in the silicon rather than importing a foreign frame. What pins it to the center is the home lexicon: "intention," "planning," and the if-then-plan framing presume a deliberating agent, so applying the prime to a cron job or an ISR requires translation from intention-talk into trigger-action-talk (vocab_travels and import_vs_recognize each 0.5). The trigger-action rule is the more structural cousin, and naming it as the genuine skeleton — with the intentional vocabulary as a thin inherited overlay — is exactly the mixed-structural reading the aggregate of 0.4 records.

Substrate Independence¶

Implementation intention is a moderately substrate-independent prime — composite 3 / 5 on the substrate-independence scale. On domain breadth, the cue-binding pattern recurs across behavioral and health psychology (its origin), software systems (event handlers, interrupt vectors, trigger-action rules like IFTTT), military and emergency doctrine (standing orders, battle drills), aviation and medicine (branching checklists, pre-briefed contingencies), and organizational decision-making (pre-mortems, tripwires) — a genuine spread that earns a 3. On structural abstraction, the bare skeleton is a two-tier register-then-dispatch mechanism that runs identically in silicon, doctrine, and cognition, and the embedded-controller ISR instantiates it in a pure computational substrate; but the home lexicon of "intention" and "planning" presumes a deliberating agent, so applying the prime to a cron job or interrupt vector requires translating intention-talk into trigger-action-talk, capping abstraction at a 3. On transfer evidence, the trigger-action rule is the documented structural cousin and the robustness moves (sharpen the cue, rehearse under load, isolate competing triggers) port across substrates, but the evidence is analogical rather than carried by a single shared formal model, so it too rests at 3. The cognitive-agent framing across all three components yields the moderate composite of 3.

Composite substrate independence — 3 / 5
Domain breadth — 3 / 5
Structural abstraction — 3 / 5
Transfer evidence — 3 / 5

Relationships to Other Abstractions¶

Current abstraction Implementation Intention Prime

Parents (1) — more general patterns this builds on

Implementation Intention is a kind of Prospective Memory Prime

An implementation intention is prospective memory specialized by pre-binding a future cue to a particular action.

Neighborhood in Abstraction Space¶

Implementation Intention sits among the more crowded primes in the catalog (17^th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Cue-Triggered Deferred Action (27 primes)

Nearest neighbors

Callback — 0.76
Prospective Memory — 0.76
Habit — 0.75
Script — 0.74
Cue Outcome Decoupling — 0.72

Computed from structural-signature embeddings · 2026-09-10

Not to Be Confused With¶

The deepest confusion is with commitment_device, because both are deliberate pre-arrangements that an agent makes now to govern behavior later. But they bind different things and solve different failures. A commitment device binds future choice: it raises the cost of an action the present self fears the future self will be tempted to take, so that defection becomes expensive or impossible (the locked freezer, the burned bridge, the staked deposit). An implementation intention binds future execution: it installs a cue-action link so that the right behavior fires automatically when the trigger arrives, with no fresh deliberation. The first fights temptation — the agent who will be tempted to choose wrongly; the second fights forgetting and hesitation — the agent who would choose rightly but fails to act in the moment. They combine cleanly (a tripwire often does both), but prescribing one for the other's failure mode is a category error: sharpening a cue does nothing for an agent who recognizes it and deliberately overrides the bound action, and adding a defection penalty does nothing for an agent who simply forgets.

It is also genuinely confusable with conditioning_behavioral, since both produce a cue triggering a response without deliberation. The distinguishing invariant is how the link is installed. Conditioning lays the link down through repeated pairing over many trials, so the binding is strong precisely because it was consolidated; the agent need not — and often cannot — articulate it. An implementation intention installs the link in a single explicit declaration, which is its speed advantage (no trials required) and its fragility (on the first firings, an old conditioned habit consolidated over thousands of trials usually wins). The two even interact as antagonists: a freshly declared implementation intention competes against prior conditioning for the same execution channel. Modeling a declared binding as if it had conditioning's consolidated strength is the classic error — treating clarity of the if-then statement as if it were robustness under load.

Finally, contrast it with foresight. Foresight surveys possible futures and keeps options open, preserving the runtime flexibility to choose differently as the situation clarifies. An implementation intention does the opposite: it forecloses runtime choice by pre-binding one response to one cue, trading adaptability for speed and reliability under load. They are competing primes governing the same moment, and which should win turns on whether deliberation at the moment of action is too slow to afford (bind it) or whether the right move is genuinely unknowable in advance (keep it open).

For a practitioner, the value of holding these apart is that the diagnosis localizes the fix. A failure at the decision to override points to a commitment device; a failure of binding strength against old habit points to conditioning-style rehearsal; a failure from over-rigidity in a domain that rewarded judgment points to foresight. Collapsing them yields the familiar mistake of rehearsing "when X, I will Y" endlessly against a problem that was never about recognition or dispatch.

Solution Archetypes¶

Solution archetypes in the catalog that build on this prime — directly (this prime is a source ingredient) or as a related prime.

Built directly on this prime (2)

Also a related prime in 5 archetypes

Active Goal Shielding: Protect the current goal by reducing access to competing goals, preserving only explicit exceptions, and releasing suppression once the goal window ends.
Definition-Time Context Binding: Bind a behavior unit to the minimum context that defined it so later execution resolves against that context rather than silently inheriting an unrelated ambient environment.
Event-Script Structuring: Encode a familiar situation as an expected role-and-event sequence so people or systems can recognize the situation, know what normally comes next, and notice meaningful deviations.
Threshold-Refresh State Maintenance: Keep a fragile state alive by refreshing it just often and lightly enough to stay above its disappearance threshold without changing what it is.
Use-Time Precondition Binding: Act on a precondition only when the condition is still bound to the state at the moment of use, not merely when it was true during an earlier check.

References¶

[1] Gollwitzer, Peter M. "Implementation Intentions: Strong Effects of Simple Plans." American Psychologist, vol. 54, no. 7 (1999): 493–503. Originating account of if-then plans that pre-bind a specified cue to a goal-directed response, delegating control to the cue so action follows without renewed deliberation. registry ↩a ↩b

[2] Gollwitzer, Peter M., and Paschal Sheeran. "Implementation Intentions and Goal Achievement: A Meta-Analysis of Effects and Processes." Advances in Experimental Social Psychology, vol. 38 (2006): 69–119. Meta-analysis of 94 tests (medium-to-large effect, d = .65) establishing robustness across domains and the cue-specificity, rehearsal, and competing-cue moderators. registry ↩a ↩b

[3] Ur, Blase, Melwyn Pak Yong Ho, Stephen Brawner, Jiyun Lee, Sarah Mennicken, Noah Picard, Diane Schulze, and Michael L. Littman. "Trigger-Action Programming in the Wild: An Analysis of 200,000 IFTTT Recipes." Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems (2016): 3227–3231. Documents trigger-action rules that register a condition ahead of time and fire automatically on a matching cue. registry ↩

[4] U.S. Army. FM 6-0: Commander and Staff Organization and Operations. Washington, DC: Headquarters, Department of the Army, 2014. Doctrine for standing orders and battle drills that precompile responses to execute under load when deliberation would be too slow. registry ↩

[5] Boorman, Daniel. "Today's Electronic Checklists Reduce Likelihood of Crew Errors and Help Prevent Mishaps." ICAO Journal, vol. 56, no. 1 (2001): 17–20. Aviation checklists and branching contingency procedures bind named cues to fixed action sequences before the situation arises. registry ↩

[6] Patterson, David A., and John L. Hennessy. Computer Organization and Design: The Hardware/Software Interface. 5^th ed. Burlington, MA: Morgan Kaufmann, 2014. Interrupt vectors, the interrupt vector table installed at boot, and hardware dispatch on a matching condition — the register-then-dispatch architecture in silicon. registry ↩a ↩b ↩c ↩d

[7] Federal Aviation Administration. Airplane Flying Handbook (FAA-H-8083-3C). Washington, DC: U.S. Department of Transportation, 2021. Emergency procedures including rapid-decompression memory items binding a recognizable cabin-altitude cue to a fixed mask-and-descend response. registry ↩a ↩b ↩c

[8] Klein, Gary. "Performing a Project Premortem." Harvard Business Review, vol. 85, no. 9 (2007): 18–19. Premortem technique and organizational tripwires that name a threshold and the action it triggers, fixing the response before bias can bend the decision. registry ↩