Readiness-Moment Intervention¶
Triggered intervention — instantiates Resonance Tuning
Delivers support only when an observed readiness cue shows the receiver can act on it right now, rather than on a fixed schedule.
Readiness-Moment Intervention holds a piece of support in reserve and releases it the instant an observed cue indicates the receiver is in a state where they can actually use it. Where a scheduled mechanism predicts the receptive moment and fires on a computed clock, this one waits and watches — it fires on a live signal, not a prediction. The support might be identical to what a calendar would have sent; what changes is that it arrives at the individual's moment of need, when attention, motivation, and opportunity briefly coincide, rather than at an arbitrary time when the message bounces off. Its defining move is the event trigger: the intervention is coupled to a detectable readiness state, so timing is reactive to the person rather than imposed on them.
Example¶
A smoking-cessation app aims to help users through cravings. A fixed daily "you can do it!" notification at 9 a.m. mostly lands when nothing is happening and gets swiped away. The readiness-moment version instead watches for the states where support can bite. When the phone's location shows the user has lingered outside a bar they flagged as a trigger spot, or when they tap the in-app "I'm struggling" button, or when a wearable flags the racing-heart, restless pattern that for this user precedes a lapse, the app fires a short, concrete coping prompt to the channel they are already looking at — a lock-screen card, not a buried email. Because it arrives inside the craving rather than hours before or after, the same 15-second breathing exercise that was ignored at 9 a.m. now actually gets used. The intervention stays silent the rest of the day, spending the user's limited attention only at the moments it can convert.
How it works¶
- Define the readiness state. Decide what observable pattern means "can act now" — a self-report, a behavioral event, a sensor signature, a reached milestone — and how confidently it must be detected before firing.
- Watch, don't schedule. The system continuously monitors for that cue instead of counting down a clock; nothing fires until the state is seen.
- Fire into the live window. On detection, deliver immediately and briefly, while the window is open, to whatever channel the receiver is currently attending.
- Stay quiet otherwise. Absent the cue, the mechanism sends nothing, conserving attention and avoiding the desensitization that kills scheduled nagging.
Tuning parameters¶
- Trigger sensitivity — how strong the readiness signal must be before firing. Loose thresholds catch more true moments but fire on false ones (nagging); tight thresholds are respected but miss real openings.
- Response latency — how fast delivery follows detection. Faster is more relevant but leaves less time to select the right message; a lag can miss the window entirely.
- Silence floor / frequency cap — a hard limit on interventions per period even if cues recur. Protects against a bad day becoming a barrage.
- Channel selection — which surface to fire to given where the receiver's attention currently is. The right cue on the wrong channel still misses.
When it helps, and when it misleads¶
Its strength is precision under scarce attention: by spending intervention only at detected moments of need[1], it raises response per message and avoids the habituation that makes scheduled prompts invisible — the logic behind just-in-time adaptive interventions in behavioral health. It shines wherever readiness is genuinely intermittent and observable: cravings, teachable moments after a setback, the first time a user hits a hard task.
Its failure mode is acting on a misread signal — inferring readiness that is not there, so the "support" arrives as an intrusion that trains the receiver to ignore or resent it. Worse, because the cues are often sensitive (location, stress, vulnerability), the mechanism edges toward surveillance and can be misused to exploit a low moment rather than help in it — the classic abuse is timing a persuasive push to a detected moment of weakness. The guarding discipline is to keep the receiver in control: make the trigger transparent, offer an easy opt-out and mute, and treat detected vulnerability as a reason for lighter-touch, dismissible support, never a lever to press harder.
How it implements the components¶
readiness_signal— the observed cue (self-report, behavioral event, sensor pattern) is the readiness signal the whole mechanism is built around.response_window— the brief span while that state holds is the window delivery must land inside.timing_rule— "fire on detection, subject to the frequency cap" is the operational timing rule.channel_fit— routing to the surface the receiver is currently attending is how the mechanism ensures the cue reaches a live channel.
It does not implement resonance_frequency or retuning_trigger — estimating a recurring rhythm and recalibrating a computed interval belong to Spaced Repetition Timing; readiness-moment intervention waits for an observed cue rather than predicting one, so it needs no rhythm estimate to retune.
Related¶
- Instantiates: Resonance Tuning — supplies the event-triggered timing that couples support to the receiver's live state.
- Sibling mechanisms: Spaced Repetition Timing · Rhythmic Training · Synchronized Communication Cadence · Campaign Timing Window · Pulse Dosing · Response-Curve Calibration · Market Timing Window
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Readiness-Moment Intervention operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it delivers support only when an observed readiness cue shows the receiver can act on it right now, rather than on a fixed schedule.
Independent corroboration: The frozen evidence defines Readiness-Moment Intervention as 'Delivers support only when an observed readiness cue shows the receiver can act on it right now, rather than on a fixed schedule', so its operative form is Control, Automation & Runtime.
Nearest alternative: Intervention, Treatment & Transformation — Readiness-Moment Intervention includes features of a direct treatment or transformation applied to a target to change its state or condition, but its defining operation is a live operational control that automatically routes, enforces, adapts, or responds during execution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Cue-triggered help at a moment of receptivity draws on behavioral and developmental psychology of readiness.
Related originating lineages:
- Education & Pedagogy — Just-in-time instructional support materially shapes the intervention form.
Review resolution: Both blind reviewers agree that psychology is the primary origin. Explicit reconciliation of origin mode disagreement adopts reviewer_b's classification because cue-triggered help at a moment of receptivity draws on behavioral and developmental psychology of readiness. The resulting lineage records alternates=education_pedagogy, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
References¶
[1] Nahum-Shani, I., Smith, S. N., Spring, B. J., et al. "Just-in-Time Adaptive Interventions (JITAIs) in Mobile Health: Key Components and Design Principles for Ongoing Health Behavior Support". Annals of Behavioral Medicine 52(6), 446–462 (2018). Defines behavioral-health JITAIs as adapting support to detected, changing states so useful support is delivered at the right time. registry ↩