The first five consecutive executions of a new trigger are non-negotiable — this is the window where automaticity lives or dies

Why This Is a Rule

Time-based triggers ("at 9 AM every day") have a unique vulnerability: they lack the contextual richness that event-based triggers provide. An event trigger ("when I close my laptop lid") is embedded in a physical context that supports recognition. A time trigger is an arbitrary association between a clock position and a behavior — it has no natural salience except through repetition.

The first five consecutive executions are the critical installation window because they're building the association from scratch. In operant conditioning terms, continuous reinforcement (every trigger fires and is followed by the behavior) establishes the association faster than partial reinforcement. Missing execution #3 doesn't just skip one instance — it disrupts the consecutive chain that was building automaticity, essentially resetting the learning counter.

Five is the threshold because it's enough repetitions to move the trigger-behavior association from "actively remembered" to "expected" — the brain begins to anticipate the behavior at the trigger time. Below five, the association is fragile and easily forgotten. Above five, partial reinforcement can maintain it. But the initial five must be consecutive and non-negotiable.

"Non-negotiable" means this: during the first five executions, the trigger takes priority over competing demands that aren't genuinely urgent. "I'll skip today's writing because I have a meeting" breaks the chain. The meeting would need to be a genuine emergency — not just a scheduling conflict — to justify disrupting the installation window.

When This Fires

• When installing any new time-based trigger (alarm, calendar event, scheduled routine)
• When tempted to skip an early execution of a new time-based agent because "just this once"
• When coaching someone through the initial installation of a scheduled behavior
• After resetting a time-based trigger that had died — treat it as a new installation

Common Failure Mode

Treating the first execution and the tenth execution as equivalent: "I'll skip today and make it up tomorrow." They're not equivalent. The first five are infrastructure construction; the tenth is routine operation. Skipping during construction damages the foundation in a way that skipping during operation doesn't.

The Protocol

(1) When installing a new time-based trigger, mark the first five days on your calendar as "protected installation period." (2) During these five days, the trigger-behavior sequence is the highest-priority non-emergency commitment. Reschedule other commitments around it, not vice versa. (3) Execute the full trigger-behavior sequence at the designated time, even if abbreviated (Start every new agent at under two minutes with zero preparation — automaticity requires low activation energy first — minimal viable version). Showing up at the right time matters more than the action's duration. (4) After five consecutive executions, the association is established enough to survive occasional misses. Shift to normal agent management (Review new agents weekly, established ones monthly, and all agents after major context changes). (5) If you break the chain before five → restart the count. Don't continue counting from where you left off.