Time Blindness

The tells are surprisingly clean. If you start getting ready in good time, follow every step, and arrive late genuinely astonished, that is the clock: give the same person an external timer and they track time fine, which is proof it was never about caring. If your duration estimates are the ones colleagues trust and the deadline still ambushes you, that is the approach arriving without warning. If you can name the due date, the hours required, and the exact moment you will finally start, and you are right every time, that is the weight. And if the task surfaces at 11pm with a lurch of horror, eight hours after the window closed, that is the trigger: an environmental cue placed at the point of performance fixes what no amount of resolve ever did.

Two differentials matter at the edges. If today's intentions mostly happen and next Thursday's are gone by Tuesday, the storage is thin and the delay length is the variable to scaffold. And if the hour before an appointment is unusable, locked in anticipation, that is a neighboring pattern with its own page: Waiting Mode.

I know the deadline is Friday. It's Tuesday. There is no Friday.

the reaction we design for

These are not stages of one process. They are parallel systems, and any of them can fail while the others run fine.

The clock: how accurately you read duration: how long things take, how much time has passed, how much remains. When it miscalibrates, you execute your plan faithfully, on a wrong clock.

The approach: whether a future event feels like it is coming, not just known. This is the difference between knowing a deadline is Friday and feeling it approach across the week. Either can work without the other.

The weight: how much motivational charge the future carries against right now. Estimation can be perfect: you know exactly when it is due and feel zero urgency until the distance collapses.

The trigger: whether a stored intention surfaces at the moment it was needed. You cared, you planned, and it never entered active processing until hours after the window closed.

The workspace: whether the timeline stays held in mind at all. Retrieval that works on quiet days and evaporates on loaded ones is this system under resource competition.

The glue: whether an intention survives the days between forming it and needing it. Same-day plans fire; next-week plans fade before their trigger ever arrives.

None of this is a deficit ledger. The same weak background clock that mis-times the morning buys deep, unfragmented absorption in the work itself. A quiet felt approach comes with immunity to anticipatory dread: the week before a hard event is as livable as any other week. Heavy present weighting is genuine present-moment engagement, fast and unregretted short-cycle decisions, and exceptional output once a deadline is truly near. Every one of these settings is a coherent design with real costs and real advantages: map them, don't rank them.

Four of these carry a facet of their own, and two are infrastructure that decides how badly the others fail under load. Each is a trait in its own right with its own page. Open any card to read it.

Three domains, because time as lived has no single home: it is simulated and weighed in Foresight, held active in Executive Control, and stored and retrieved in Memory.