Context Lists

In the AI Story

The elegance of context-based organization lay not merely in efficient retrieval but in the cognitive architecture it supported. Allen observed that the mind benefited from not seeing irrelevant actions — the commitments it could not address in the current context. Hiding those items served the mind-like-water goal by reducing the field of active consideration to what was actionable here and now.

The deeper function of contexts was identity demarcation. The person consulting @Home was, in that moment, a parent, a homeowner, a family member. The person consulting @Office was an employee, a professional. The context switch was an identity switch — a state transition the mind used to disengage from one domain and engage fully with another. This identity function was often invisible to practitioners; they experienced it simply as the relief of being able to be present in one life at a time.

AI has dissolved the technical foundations of contexts. The @Computer context assumed some tasks required computers and others did not; when a phone is a computer and the computer can do anything, the context collapses into @Anywhere. The @Calls context assumed phone conversations were a distinct mode of work; AI handles much of the preparation and can sometimes replace the call itself with a summary. The Berkeley ethnography documented the consequence: task seepage across every former boundary, work colonizing personal contexts and personal tasks leaking into professional time. The dissolution is not merely logistical; it is existential, because the identity boundaries contexts maintained have dissolved with them.

Origin

Allen developed context lists as a direct response to the failure of priority-based task lists. He observed that priority labels (A, B, C) generated anxiety without actionability, because the question "what should I do now?" is properly answered not by priority but by feasibility — what is possible given current tools and location. Context organization elegantly solved this by making the environment the first filter.

The concept was formalized in Getting Things Done (2001) and became one of the most distinctive markers of GTD practice. The @-prefix notation — @Computer, @Calls, @Errands — has persisted in countless task management applications built in GTD's wake.

Key Ideas

Feasibility trumps priority. The right first filter is not importance but possibility — what can actually be done given current conditions.

Attention is the deeper resource. By hiding irrelevant items, contexts protect the mind from the cognitive cost of scanning options it cannot execute.

Identities track contexts. The lists separated not just tasks but selves — the mode of attention and social role each context invoked.

AI dissolves contexts at the technical level. When every tool does everything from everywhere, the categorical foundations of context organization erode, and with them the identity boundaries the lists silently maintained.

Debates & Critiques

The most consequential practical debate concerns whether contexts should be rebuilt on new foundations — not location and tool but mode of attention, time of day, or chosen commitment — or whether the dissolution of contexts signals the end of this entire organizational principle. Proponents of reconstruction argue for artificial contexts: @Deep for focused work, @Build for AI-assisted execution, @Off for deliberate disengagement. Skeptics argue that artificial contexts lack the environmental enforcement that made the original contexts sustainable.