Cooldown After-Action Rule¶
Procedure — instantiates Kairotic Window Alignment
Prevents immediate re-triggering after a receiver has acted, absorbed, refused, or become fatigued.
A cooldown rule imposes an enforced silence in the interval right after a receiver responds to an action — acts on it, absorbs it, refuses it, or shows fatigue — so the system does not fire again into a state that can no longer use it. Its one defining idea is that the moment just after a response is a refractory period: receptivity is at its lowest, and further pressure produces reactance rather than results. The rule is purely backward-facing toward the last response and forward-protective of recovery. It does not judge whether a fresh window is worth acting on, and it does not decide that a prepared action has gone stale; it guards only the interval that follows a response.
Example¶
In a cardiac ICU, a patient monitor throws a bradycardia alert. The nurse acknowledges it, checks the patient, and silences it. Without a cooldown, the same threshold re-fires eight seconds later, and again a minute after that; by the third repeat the nurse's response has flattened into alarm fatigue — the documented erosion of responsiveness that comes from frequent, mostly non-actionable alerts.[n1] The cooldown rule inserts a refractory hold: once an alarm of a given class is acknowledged, that class is suppressed for a defined recovery interval — say three minutes — unless the underlying value crosses a hard escalation threshold. The outcome is that the nurse's next alert lands on fresh attention instead of exhausted attention, and the channel is preserved. The arc is simple: a response event fires → the class enters cooldown → redundant re-triggers are absorbed silently → the hold releases (or a hard-escalation override breaks it) → the channel is ready again.
How it works¶
- Keys off the response event, not the clock. The timer starts when the receiver acts, refuses, or fatigues — not at a scheduled time.
- Scopes the suppression. A cooldown applies to a class of action toward a specific receiver, so one channel cools while others stay live.
- Carries a hard override. A genuine emergency — a value past an escalation threshold — breaks the cooldown; the rule suppresses redundancy, never danger.
- Releases on recovery where it can be observed, not merely on elapsed time: attention returning, capacity freeing.
Tuning parameters¶
- Cooldown length — how long the refractory hold lasts; too short reintroduces fatigue, too long misses a genuinely re-opened window.
- Trigger set — which response types start it (acted / refused / saturated / fatigued); a flat refusal may warrant a longer hold than a completed action.
- Override threshold — how severe a new signal must be to break the hold; a low threshold protects safety but readmits noise.
- Scope granularity — per-class vs per-receiver vs global; finer scope preserves more live channels but costs more to maintain.
- Decay vs step release — whether receptivity is modeled as returning gradually or all at once when the hold ends.
When it helps, and when it misleads¶
Its strength is that it is the single most effective guard against refractory backfire and channel exhaustion — the failure where pressing again right after a response converts an open receiver into a defended one, and where repeated alerts convert a live channel into background noise.
Its failure mode is that a cooldown set by habit rather than evidence can mute a channel during a genuinely re-opened window — a fixed 24-hour suppression that also hides a second, unrelated emergency. The classic misuse is using cooldown as a blanket rate-limit to paper over a spammy underlying design, so the real problem — too many asks — is cosmetically smoothed instead of fixed. The guarding discipline is to tie the hold to observed recovery signals, always keep a hard-escalation override, and treat a frequently-overridden cooldown as evidence that the trigger design, not the timer, is wrong.
How it implements the components¶
closing_and_refractory_signal— the rule's trigger is this signal: it detects that the receiver has responded and marks the interval where receptivity is depressed.quiet_period_and_recovery_spacing— the enforced hold is exactly the recovery spacing the archetype calls for, sized to let receptivity return.attention_and_readiness_budget— by absorbing redundant re-triggers, it preserves the scarce attention budget for the next genuine window.
It does not implement kairotic_window_definition or fallback_timing_path — that's Window Expiry Rule, which retires a not-yet-fired action whose basis has aged out; a cooldown instead protects a receiver who has just responded. Nor does it hold launch authority (timing_authority_and_hold_rule) — that's Launch-or-Hold Gate.
Related¶
- Instantiates: Kairotic Window Alignment — the cooldown supplies the refractory-and-recovery guard the pattern depends on after a response.
- Sibling mechanisms: Launch-or-Hold Gate · Prebrief and Activation Cue · Window Expiry Rule · Critical-Moment Playbook · Event-Triggered Outreach Workflow · Just-in-Time Intervention Protocol · Readiness Signal Dashboard · Stakeholder Pulse Check · Timing After-Action Review
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: A receiver action, refusal, or fatigue state starts scoped suppression, while recovery or a genuine emergency releases or overrides it, so the mechanism is state-triggered firing control.
Nearest alternative: Rule, Policy & Commitment — Cooldown duration and override conditions are standing rules, but live event detection and suppression of retriggers make the deployed mechanism a controller.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Behavioral psychology cohered refractory recovery, reactance, and reduced receptivity after stimulation or response as reasons to withhold immediate repetition.
Related originating lineages:
- Communication & Media Studies — Communication practice operationalizes post-response spacing to prevent channel fatigue and reactance.
- Medicine & Healthcare — Clinical alarm-management practice supplies the acknowledgement, suppression, recovery, and emergency-override pattern.
Review resolution: Psychology supplies the general account of post-action receptivity and reactance, while clinical alarm management and communication timing independently instantiate the same cooldown structure. The encyclopedia formulation synthesizes these into a receiver-agnostic rule.
Attribution caveat: The generalized recovery rule joins psychological reactance and attention recovery with clinical alarm and communication-channel suppression practice.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- The Joint Commission: Medical device alarm safety
- NIH: Alarm Management Technical Bulletin
- Psychological reactance and health communication review
Notes¶
Cooldown and Window Expiry Rule are mirror images across the fire event: expiry guards a prepared action before it is sent ("too late to start"), the cooldown guards the receiver after the action lands ("too soon to repeat"). Collapsing them into one "don't send" rule loses exactly the distinction the archetype needs.
[n1] Alarm fatigue — the desensitization by which caregivers exposed to frequent alarms, many of them non-actionable, respond more slowly or not at all; a recognized patient-safety hazard in clinical monitoring. A cooldown's refractory hold attacks its direct cause: redundant re-alerts. ↩