The Cascade Logic

A single bedtime alarm puts all the work of falling asleep into one moment — and one moment is easy to override. The evening cascade wins by distributing that work across the afternoon and night, retiring one arousal input at a time, longest-acting first. This page explains the logic underneath the parent protocol's hour-by-hour countdown, why the order is the arithmetic, and how staggered cutoffs quietly become a habit stack that makes lights-out nearly automatic.

Why a Single Bedtime Alarm Fails

Think about what a single alarm asks: at 22:30 you set down the phone, stop the argument replay, ignore the work email, and fall asleep — all in one act of will. That is a decision, and decisions are the part of your evening most vulnerable to override. The moment arrives, you are mid-email, and the alarm loses to a task that feels more urgent. Behavior that depends on a fresh decision every night is precisely the behavior that fails when you are tired, because self-control is not at its best at lights-out time.

The cascade sidesteps this by moving each decision earlier, when you still have resources: the caffeine line is decided at 15:00, the kitchen closes at 20:00, the inbox at 21:30. By the time the alarm would have fired, every input that could interfere has already been retired — the single decision has been replaced by six smaller ones made at better moments. This is the same logic behind stimulus-control and behavioral sleep treatments, which work by moving sleep out of the decision column of your evening (Morin et al., 2006).

The Arithmetic of the Order

The cascade's order is not cosmetic; it is sorted by how long each input keeps working after you stop it. Caffeine has the longest reach — a half-life of roughly five to six hours, so it retires first (Drake et al., 2013; Clark & Landolt, 2017). Alcohol's disruption runs through the early hours, so it retires four hours out (Ebrahim et al., 2013). A heavy meal is a several-hour digestion project, hence the three-hour line. Work and screens are shorter-acting but act in the moment, so they retire last. The chart below shows this ordering as the cascade is designed to run it — the relative durations are qualitative, but the sequencing is the point.

Reading the chart top to bottom gives you the retire order. It also gives you the failure-mode rule: if you can trace a bad night to a single input, it is nearly always one of the top rows — you extended the caffeine line, or the heavy meal arrived late. The bottom rows are cheaper to violate and cheaper to forgive.

What Each Early Line Purchases Later

The most counterintuitive part of the cascade is that its earliest lines are the ones doing the most work. Cutting caffeine at 15:00 does nothing visible at 15:30; it pays off at 23:00, when an afternoon dose would still be circulating. The table lays out each line, its timing, and the specific thing it purchases further down the evening.

Notice which two lines are marked "do it" — caffeine and work. They are the highest-leverage lines in most people's evenings, because they are the longest-acting and the most likely to be violated invisibly. If you only ever run two lines of this cascade reliably, those are the two to keep.

The Cascade as a Habit Stack

Run the same cutoffs at the same times and the sequence stops being six decisions and becomes one routine. Everyday behavior is largely automatic — roughly two-fifths of daily actions run in the same context repeatedly (Wood et al., 2002) — and the cascade is engineered to exploit that: each cutoff is a cue that triggers the next one. Caffeine done means the afternoon is over; kitchen closed means the evening has begun; inbox closed means the day is done. The whole stack becomes the ritual that the parent evening-cascade page then hands to the bedroom.

• 🔗 Anchor each line to something real. "Last coffee with lunch," not "no caffeine after 15:00." Cues that already exist carry the new behavior (Wood et al., 2002).
• 📥 Install one line per week. Adding every cutoff at once recreates the single-decision problem at a higher level; habits form over weeks of repetition, not overnight (Lally et al., 2010).
• 🧭 Fix the sequence before the times. The order matters more than the exact clock — if your evening shifts, keep the relative order and move the whole cascade with it.
• 📅 The first lines are daytime decisions. The evening you want starts hours before the evening you're in — which is why the cascade begins in the afternoon, not at the bedroom door.

Practical Rules for Building Your Own Cascade

You do not need the full six-line system to start, and the parent page's full hour-by-hour map is a reference, not a first-week plan. Here is the minimal build sequence that keeps the logic intact:

• 1. Fix lights-out first. The whole countdown counts back from one number — get yours from the wake-anchor math on the When to Sleep topic.
• 2. Install top-down. Start with caffeine (longest acting), then alcohol if relevant, then the meal line, then work and screens.
• 3. Calendar the lines like meetings. A 15:00 "last coffee" alarm is a meeting with yourself; it survives the evening better than a vague intention.
• 4. Keep the order when life shifts. Late dinner on a work night? Move the whole cascade back an hour rather than reordering it — the sequencing is the logic.
• 5. Judge it on weeks, not nights. One bad night tells you nothing; a two-week pattern tells you which line is the leak. The rest of the system sits in the evening-cascade series, one cutoff per page.

Questions, Answered Briefly

• ❓ Isn't one loud alarm at bedtime simpler than all these cutoffs? Simpler to explain, harder to run — the alarm concentrates the fail point. Six small decisions made at good moments beats one big decision made at the worst moment.
• ❓ Does the exact hour of each cutoff matter? Less than the order and the consistency. A caffeine line at 13:00 or 15:00 both work; moving it later by thirty minutes each week is how you'll know where your own line sits.
• ❓ Can I run just two or three lines? Yes — the evidence is per-component, and two reliable cutoffs outperform six abandoned ones. The "do it" pair (caffeine and work) is the standard starting set.
• ❓ How long until the cascade feels automatic? Habits typically take weeks of repetition to stabilize (Lally et al., 2010) — longer for some. Judge the system at the two-week mark, not on night two.
• ❓ What should I fix first if nights are still bad? Audit top-down: the caffeine line first (longest-acting), then the late meal. Those two cover most silent leaks before anything behavioral is involved.

Related Topics