Waiting Mode
If one appointment later today can erase your whole morning, and you have sat dressed and ready hours early, unable to start one small thing, this is the pattern that explains it.
Some people can have a 3pm appointment on the calendar and work normally until 2:30. Others lose the entire day, not to the appointment but to waiting for it. Tasks that would be trivially startable on a free day become untouchable, and from the outside, often from the inside too, it reads as wasted time or poor discipline. It is neither. It is three traits interacting, and the fear underneath it is calibrated to real machinery: for this architecture, an absorbing task genuinely suppresses the background tracking of time, so entering one while waiting is an authentic risk of missing the event.
Where it starts for you
The useful question is which part sticks for you. For some it is the clock: a history of hyperfocus eating whole afternoons means the risk is not hypothetical, it is remembered, and reassurance cannot argue with evidence. For some it is the lock-on: the event sits in the chest from noon onward and the day circles the drain of it. For some it is the double-priced start: the email that takes ten minutes on Tuesday is untouchable today, because today has a dentist in it.
The pattern is also falsifiable, which is the point. If small tasks slip easily into the gap and you feel no lock, this is not your architecture. If starting is just as impossible on an empty-calendar day, look at the sibling cluster, I Care But I Cannot Start, instead: waiting mode needs a scheduled event to trigger it. And what helps is not pushing through the fear but outsourcing the clock: external timers with lead-time buffers, interim tasks with trivially cheap exits, a leave-signal that is mechanically guaranteed. That is scaffolding for a clock, not a fix for a character.
If I have an appointment at 3pm, I am paralyzed all day.
the reaction we design for
Traits in this cluster
This is not a sequence with a first step. It is a standing configuration with parts, and knowing which part is yours changes what actually helps.
The untrusted clock: internal time that cannot be vouched for. Twenty minutes of felt time routinely turns out to be an hour, and an absorbing task can make whole hours vanish, so the gap before the event is unusable.
The lock-on: the appointment stops being a calendar entry and becomes a pressure in the room. It is not at 3pm. It is now, and it has been now since breakfast.
The double-priced start: any task in the gap costs two starts, one now and one after the event, plus the risk of the task capturing you. On a gate that is already expensive to open, that prices everything out.
The ready-state: not doing nothing. Doing the appointment, hours early, shoes on, with everything else registering as an interruption of it.
The watched pot: vigilant clock-watching stretches felt time, so the lost day is not only lost. It feels longer than a working day would have.
The payoff: the event is virtually never missed. Not the flight, not the pickup, not once in years. That is the half of the pattern nobody credits.
These are the three traits this cluster is built from. Two keep the time, one holds the gate. Open any card to read it.
The domains it spans
Two domains, one seam. Foresight supplies the temporal picture, Executive Control decides whether anything starts, and waiting mode is the day when the plan is clear and the gate still does not open.