When your anchor behavior changes context, immediately redesign everything stacked on it — dependent commitments won't survive anchor disruption

Why This Is a Rule

Habit stacking (Automate each habit link before adding the next — stacking unautomatic behaviors creates an effortful pile, not a self-sustaining chain) chains new behaviors to existing automatic anchors. The anchor provides the trigger: "After I pour my morning coffee [anchor], I will journal for 5 minutes [stacked behavior]." The stacked behavior's entire activation mechanism depends on the anchor occurring in its expected context — same time, same location, same sequence.

When the anchor's context changes — you switch to a different morning routine, move to a new apartment, or start working different hours — every behavior stacked on that anchor loses its trigger. The anchor still exists (you still drink coffee) but the contextual cue that activated the stacked chain has shifted. The journal habit that fired reliably at 7 AM in the kitchen doesn't fire at 9 AM in a coffee shop because the contextual binding was specific.

The "immediately redesign" urgency matters because stacked behaviors don't degrade gradually — they die suddenly when the anchor shifts. Without immediate redesign, you discover the failure after missing 3-5 days, by which point the behavioral chain has broken and requires full reinstallation (The first five consecutive executions of a new trigger are non-negotiable — this is the window where automaticity lives or dies).

When This Fires

• When your routine changes (new job schedule, move, travel, life event) and anchor behaviors shift
• When stacked behaviors suddenly stop firing despite no change in motivation
• When Major transitions require full feedback loop recalibration — changed context invalidates proxy-outcome correlations (transition recalibration) identifies that anchor contexts have changed
• Complements Automate each habit link before adding the next — stacking unautomatic behaviors creates an effortful pile, not a self-sustaining chain (sequential chain building) with the maintenance protocol for context disruption

Common Failure Mode

Expecting stacked behaviors to "transfer" automatically: "I'll just journal at the new time." The journaling was anchored to the old time + location + sequence. At the new time, the trigger doesn't fire because the contextual binding is broken. The behavior needs explicit re-anchoring to the new context, not implicit hope that it'll adapt.

The Protocol

(1) When any anchor behavior changes context (new time, location, or sequence), identify all behaviors stacked on that anchor. (2) For each stacked behavior: the current trigger is broken. Design a new trigger linked to the new anchor context. (3) Treat the re-anchored behavior as a new installation: protect the first five executions (The first five consecutive executions of a new trigger are non-negotiable — this is the window where automaticity lives or dies), add temporary scaffolding (Add temporary scaffolding during the first 2-4 weeks of habit formation — remove supports once automaticity is achieved), and verify automaticity (Test habit automaticity by effort level, not frequency — willpower-maintained consistency is not genuine delegation to the habit system) before considering it stable. (4) Don't wait for stacked behaviors to fail — redesign proactively the moment the anchor context change is known.