Time Horizon Planning: One Timeline, Six Strata

You have a calendar for today, a to-do app for this week, a notes doc full of yearly resolutions, and a vague feeling that none of them talk to each other. Your daily tasks do not know what your year is for. Your big goals do not know whether today moved them forward. So you drift. You stay busy and still wonder, months later, why the thing you said mattered most never got any of your time.

That gap has a name. It is the missing discipline of time horizon planning: planning that links the things you do in the next hour to the things you want in the next decade, and keeps them honest with each other as life changes.

Most tools fail at this because each one owns exactly one horizon. This post is about why that is broken, what cascading goals across horizons actually requires, and how a single zoomable timeline plus a weekly recalibration loop fixes it.

Why single-horizon apps quietly fail you

Open your phone and count. A calendar handles the Day. A task manager handles the Week. A goals app or a journal handles the Year. A spreadsheet, maybe once a quarter, handles the rest. Each app is competent inside its own band of time and blind to the others.

This is the "eight separate apps" disease, and it has a real cognitive cost. When your plan is scattered across tools, you are forced to hold the connections in your head: this Tuesday task is part of this monthly milestone, which serves this quarterly objective, which is one leg of a yearly goal. Working memory is exactly where that load lands, and it is fragile. Working-memory deficits are functionally tied to the inattentive behavior we experience as "I forgot why I was doing this" (Kofler et al., 2010). The more horizons you split across separate surfaces, the more of that linking work you are silently asked to do.

For anyone with ADHD or executive-function strain, the failure is sharper. The core deficit is not attention, it is behavioral inhibition and self-regulation across time (Barkley, 1997). Behavior gets captured by the immediate now instead of being steered by an internally represented future, a temporal myopia often called time blindness (Barkley, 1997). A meta-analysis of time perception in ADHD confirms the underlying machinery is genuinely off: durations are perceived less accurately and tend to be overestimated (Zheng et al., 2022). If your future only exists in an app you are not currently looking at, the future effectively does not exist.

The honest design conclusion: never make the user hold the cross-horizon links in their head. Externalize them. Cognitive offloading, using tools to carry what your memory cannot, is a core strategy people already reach for (Risko & Gilbert, 2016), and when we expect future access to information, we remember where it lives rather than the thing itself (Sparrow et al., 2011). A planner should be that external store for the whole ladder of time, not just one rung.

What cascading goals actually require

"Break your big goal into small steps" is advice everyone gives and almost no tool implements correctly. A real cascade across Life, Year, Quarter, Month, Week, and Day needs three properties most apps lack.

One vocabulary, not six

If a "goal" in your yearly app is a different kind of object than a "task" in your daily app, they can never connect. They are different nouns living in different databases. StrataGist starts from the opposite premise: there is one primitive, the gist. A fleeting thought, a task, a project, a yearly goal, even a person or a transaction, is the same node in one labeled directed graph. A kind field decides which properties it carries, but the substrate is identical. That is what lets a Day task and a Life goal sit on a single connected structure instead of in eight walled gardens.

Crucially, the strata themselves stay internal. There is no user-facing "pick your level" dropdown. Stratum is just time metadata the system uses for scheduling and roll-up, never a hierarchy you have to manually file things into. You capture; the structure forms around it.

A real link type for "is part of"

Cascading is a roll-up problem, and roll-up needs a specific kind of edge. StrataGist uses a composition edge: a one-owner tree meaning "part of." This is the only edge that carries numeric roll-up. Progress, counts, and inherited importance travel composition edges and nothing else.

This precision matters. Tagging a task with an area like "Health" does not make Health partially complete, because that is a categorization edge, not a composition one. Mixing those up is why so many goal apps show you a satisfying progress bar that means nothing. In StrataGist, when your week's tasks complete, progress flows up the ownership tree to the month, the quarter, the year. The cascade is literal, computed, and conservative.

Specific, hard goals at the top

Cascading only helps if the top of the ladder is worth cascading from. Vague goals do not direct effort. Specific and sufficiently difficult goals produce higher performance than easy or fuzzy ones, through clearer direction, effort, and persistence (Locke & Latham, 2002). The Life and Year strata are where you set the difficult, specific target. The lower strata are where it gets executed. Without the hard target up top, the whole structure is just a tidy list of busywork.

Are you actually on pace? The math of horizon planning

Linking horizons is half the job. The other half is knowing, honestly, whether your current rate of work will hit your target in time. This is where most planners go silent and where StrataGist's forecast engine, Compass, does real arithmetic.

Start with the pace you need. For any goal with a target date, that is open work divided by the weeks remaining.

paceNeeded = remaining / weeksLeft
remaining  = max(0, total - done)
weeksLeft  = max(0.1, (dueMs - nowMs) / WEEK_MS)   // WEEK_MS = 604800000

Then measure the pace you are actually getting. A flat average lies: someone who front-loaded and then stalled looks fine on a flat mean. So Compass uses a recency-weighted (EWMA) mean over a trailing 8-week window, weighting recent weeks more heavily.

muRecent = Sigma_i ( DECAY^weeksBack_i * counts[i] ) / Sigma_i ( DECAY^weeksBack_i )
DECAY = 0.7,   weeksBack = 0 for the most recent week
paceActual = (done.length > 0) ? muRecent : null

The signed gap between those two is your alignment signal: positive means ahead, negative means behind, zero means right on pace, all expressed as a fraction of what you need and clamped to a sane range.

deviation = clamp( (paceActual - paceNeeded) / paceNeeded, -1, 1 )

This is the number that tells the planner how loudly to nudge, and it is the thing single-horizon apps simply cannot compute, because they do not know the goal above the task.

Honesty about uncertainty

A real forecast admits it might be wrong. Compass measures how choppy your weekly output is and turns that volatility into a confidence band, not a false-precise single date.

variance = Sigma_i ( counts[i] - muFlat )^2 / max(1, LOOKBACK_WEEKS - 1)
sigma    = sqrt(variance)

fastPace = paceActual + sigma
slowPace = max(paceActual * 0.25, paceActual - sigma)
optimistic = nowMs + (remaining / fastPace) * WEEK_MS
late       = nowMs + (remaining / slowPace) * WEEK_MS

A steady history gives a tight date range. A volatile one gives a wide one. The band literally is your historical variance made visible. From the same spread, Compass reads off a probability of hitting the date using a normal-approximation CDF (deterministic, no random sampling), so the question "will I make it?" gets an actual number instead of a vibe.

This respects a well-documented bias: people systematically underestimate how long their own tasks take, the planning fallacy, because they reason from optimistic plans instead of past experience (Buehler et al., 1994). Compass refuses to reason from your plan. It reasons from your completed weeks.

Weekly recalibration: the loop that keeps horizons aligned

Cascading goals are not set-and-forget. Life moves, priorities drift, and a plan made in January is stale by March. The fix is a rhythm, not a one-time setup. StrataGist runs a single closed loop: Capture, Surface, Do, Review, where Review feeds straight back into Capture.

That loop is a deliberate ADHD-first correction of classic GTD, which demands you Organize everything up front before you can act. StrataGist replaces Organize with Surface: the system brings the right thing to you, instead of asking you to file everything into the right place first. That addresses time blindness and object permanence directly, because the future comes to find you.

Weekly review is where horizon planning earns its keep. Once a week you check two things the per-task view can never show you.

First, are my goals on pace? Compass surfaces the deviation, the projected finish, the confidence band, and a plain-language trajectory word (ahead, on track, behind) that is reconciled so it can never contradict the numbers next to it.

Second, am I spending effort where I said it mattered? This is the value-drift detector, a revealed-preference check in the economists' sense. It compares what you declared important against where your completed effort actually went.

statedShare   = statedImportance(goal) / Sigma_goals statedImportance
revealedShare = goalEffort / Sigma_goals goalEffort
gap = statedShare - revealedShare
kind = |gap| >= 0.12 ? (gap > 0 ? neglected : over-invested) : aligned

A positive gap means you said this goal mattered but barely touched it (neglected). A negative gap means it quietly ate your week (over-invested). Within 12 share-points, you are aligned and nothing is flagged. This is the single most useful thing weekly recalibration can tell you, and it only exists because every horizon sits on one connected graph.

Recalibration that does less, not more

A weekly loop could easily become a guilt machine that nags you to re-plan constantly. StrataGist treats that as a harm to prevent. An anti-harm "do-less" restraint layer caps re-planning, refuses reassurance loops, and acts only when the estimated benefit clears a real threshold. The system judges itself by whether your stated life improved, not by how often you open it. Time in the app is counted as a cost.

This is also why recalibration leans on gentle commitment rather than punishment. Present bias, the pull of now over later, is real and robust, strongest for effort and consumption (Steel, 2007). The countermeasure is soft: auto-scheduling a captured task onto today's timeline is itself a quiet commitment device, and pairing the next step with a concrete cue (an if-then plan) reliably improves follow-through, with a medium-to-large effect across 94 tests (Gollwitzer & Sheeran, 2006), and it works even where action control is chronically impaired, as in ADHD (Gawrilow et al., 2011).

One timeline, six horizons, one weekly check

Time horizon planning is not eight apps duct-taped together. It is one substrate where a Day task and a Life goal are the same kind of object, linked by a composition edge that rolls progress upward, forecast by honest arithmetic that admits uncertainty, and kept aligned by a weekly loop that tells you whether your effort matches your stated values.

You do not need to hold any of those links in your head. That is the whole point.

StrataGist is free and local-first, and you can plan across every horizon without signing up. Open the timeline, capture one goal, drop one task under it, and watch the cascade form. Try StrataGist free at /dock.

References

1. Barkley, R. A. (1997). Behavioral inhibition, sustained attention, and executive functions: Constructing a unifying theory of ADHD. Psychological Bulletin, 121(1), 65-94. link
2. Barkley, R. A. (1997). Attention-deficit/hyperactivity disorder, self-regulation, and time: Toward a more comprehensive theory. Journal of Developmental and Behavioral Pediatrics, 18(4), 271-279. link
3. Zheng, Q., Wang, X., Chiu, K. Y., & Shum, K. K. (2022). Time perception deficits in children and adolescents with ADHD: A meta-analysis. Journal of Attention Disorders, 26(2), 267-281. link
4. Kofler, M. J., Rapport, M. D., Bolden, J., Sarver, D. E., & Raiker, J. S. (2010). ADHD and working memory: The impact of central executive deficits and exceeding storage/rehearsal capacity on observed inattentive behavior. Journal of Abnormal Child Psychology, 38(2), 149-161. link
5. Locke, E. A., & Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9), 705-717. link
6. Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the "planning fallacy": Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366-381. link
7. Steel, P. (2007). The nature of procrastination: A meta-analytic and theoretical review of quintessential self-regulatory failure. Psychological Bulletin, 133(1), 65-94. link
8. Gollwitzer, P. M., & Sheeran, P. (2006). Implementation intentions and goal achievement: A meta-analysis of effects and processes. Advances in Experimental Social Psychology, 38, 69-119. link
9. Gawrilow, C., Gollwitzer, P. M., & Oettingen, G. (2011). If-then plans benefit delay of gratification performance in children with and without ADHD. Cognitive Therapy and Research, 35(5), 442-455. link
10. Risko, E. F., & Gilbert, S. J. (2016). Cognitive offloading. Trends in Cognitive Sciences, 20(9), 676-688. link30098-5)
11. Sparrow, B., Liu, J., & Wegner, D. M. (2011). Google effects on memory: Cognitive consequences of having information at our fingertips. Science, 333(6043), 776-778. link