Basin

What It Is

A basin is, in Will's definition, "a metaphor for a structure that accumulates information." Concretely: a persistent catchment dug for one pursuit, made of three parts — a declared question (or macrostate), a retrieval boundary, and a living synthesis. Material relevant to the pursuit flows in ambiently, provenance is preserved, and the synthesis updates what is currently believed. The payoff is that the pursuit accumulates instead of being re-derived every time it comes up.

The accrual substrate is the life-wide version of this move — the undifferentiated surface where everything lands so nothing is lost. A basin is a scoped instance carved into that substrate: one catchment per goal, with walls. The substrate answers "where does everything land?"; a basin answers "where does everything about this land?" What makes the distinction worth a word is lifetime. A basin lives as long as its goal lives, and a goal's lifetime is longer than any session, any conversation, any single agent run — which turns out to be the load-bearing property.

Three Senses of One Word

The corpus already uses "basin" in an older sense, so the word has to be disambiguated before it can be used precisely.

The second and third senses are one mechanism at two levels of formality. The semantic basin is the loose form: a question and the place where its material gathers. The formal basin is the same object made executable — the question hardens into acceptance criteria, and the open-endedness gets a termination condition and a budget. This article is about the dug kind.

The attractor sense is genuinely different — it describes behavior, carries a warning ("a basin you fell into" is usually the problem), and belongs to the energy-landscape vocabulary of statistical mechanics. But the geometry is shared, and the shared geometry is why the metaphor holds: a basin is shaped so that things flow downhill into it and stay. Digging one is deliberately building that shape for information, so that observations about a pursuit flow somewhere instead of dispersing. You fall into an attractor basin; you dig a semantic one on purpose.

A Pillar Named Only in Your Head Cannot Collect

The founding observation came from a set of named long-horizon pillars, and the discovery that naming them had not made them real. Each needed to exist as a persistent basin before new information, experiences, and ideas could be routed through it:

"A pillar named only in my head cannot collect."

Routing needs a physical catchment. Observations relevant to a pillar arrive daily — on walks, in logs, mid-conversation — and attention routing can recognize where each one belongs, but a route needs a destination that exists. When the pillar is only a name, the observation either evaporates or lands in the undifferentiated substrate, where it is findable in principle but never accrues to the pursuit. The pillar stays exactly as developed as it was the day it was named, and every session that touches it starts by re-deriving it.

The same failure appears at the scale of a free afternoon. Will's diagnosis of the freeze — the stall where free time produces drift instead of work — was that "'free time' was an unindexed search space holding ~6 different kinds of work... the lane taxonomy is the index." The lanes are basins for kinds of work: once each kind has a catchment with a queue in it, a free block resolves by picking a lane instead of by re-searching the whole space at the moment executive function is weakest.

The basin sits next to, and does a different job than, macrostate engineering's visible tracker. A visible tracker is a standing feedback signal — every glance compares declared state against current state. A basin is a standing collection surface — every relevant observation has somewhere to land. A pursuit needs both, and they fail differently: without the tracker you drift off the goal, and without the basin you forget what you learned on the way to it.

Anatomy: Question, Boundary, Synthesis

Each of the three parts is load-bearing, and each has a distinct failure when missing.

• A persistent question. The declared macrostate of the pursuit — what would have to be true for this basin to close. The question defines relevance: without it the basin cannot tell inflow from noise, and it degrades into a folder of loosely related material. A well-formed question follows the macrostate rules: specific about properties, agnostic about implementation.
• A retrieval boundary. The scope the basin reads from — which sources, which collections, which parts of the record count as its watershed. The boundary is spatial, a scope over territory, which makes it a different instrument from the budgets in bounded search: a gas limit decides how long a search may run, a retrieval boundary decides where it looks at all.
• A living synthesis. A maintained statement of what is currently believed about the question, with provenance preserved so every claim can be traced to the observation that produced it. The synthesis is what separates a basin from an archive. Appends without synthesis are a pile; the basin is only alive if new material actually updates the beliefs.

Agents Are Cattle; Basins Are Not

The formal instance is an agent-orchestration system designed as a deliberate inversion of the prevailing pattern, which persists worker identities and asks the human to read their chatter:

"Agents are cattle; macrostates are not... persist state (basins, ledger, frontier) and you only learn anything by reading a state transition."

Persist the state, not the minds. A basin in this system is the durable declaration — title, acceptance criteria, termination condition, budget — and the agents that work it are anonymous, disposable subprocesses. Identity lives in the ledger; in Will's compression, "identity in the ledger, minds are water, the human is the lock." The definition is enforced at the write path rather than by convention: a basin without a termination condition refuses to construct. The anatomy above is not advice in that system; it is a type constraint.

Session Duration Equals Goal Lifetime

The reason basins are becoming the unit of agent work is that real goals structurally exceed any session:

"Right now you can't prompt your way into Berkeley… there's so much other context that lives beyond one session. You maybe need a hundred or two hundred sessions to get all the pieces together… How do you manage that?"

His answer, in the next breath, is a basin described operationally: "It's a search process… you need to save information about what happened, update your model about what works and then where to look." Save what happened — the collection. Update your model — the living synthesis. Where to look — the retrieval boundary. A multi-year goal is a search whose state must survive between episodes, and the basin is that state.

The same conclusion arrived from watching his own tooling habits: each long-lived session tab had become a de facto persistent agent for one pursuit, and the accrued context was the asset. The generalization — "a goal / task / to-do item / MACROSTATE should be its own agent — partition by GOAL, not persona" — makes the basin the unit of agency itself. Session duration equals goal lifetime; a branch is a goal-agent alive until merged.

Basins vs Containers

Containers hold time and behavior; basins hold information and goals. A container is a locally engineered Boltzmann distribution — a bounded block of space-time that bends what its occupant does while inside. A basin is a catchment that bends what accumulates for a pursuit, whether or not anyone is currently inside anything. The two compose: a gym block is a container, and the recomposition goal it serves needs a basin, because the goal outlives every individual block.

The sibling structure on the other flank is the ratchet: a basin collects, a ratchet retains. Collection gathers new material toward a question; retention blocks exit from states already won. A pursuit missing its basin re-derives; a pursuit missing its ratchets backslides.

The Spill Condition

A basin is not built for storage. The full definition ends with an outflow: the basin "spills mature pressure into experiments and artifacts." Collection raises the level, synthesis concentrates it, and when the synthesis stabilizes around a belief that keeps surviving new inflow, the pressure exits as something real — an experiment, an artifact, a decision, a draft. A basin whose synthesis never spills has become a reservoir serving nothing, which is the information-side version of branch hoarding in branching and convergence. The termination condition is the spill condition made formal: every basin declares what would end it, and refuses to be dug without one.

Failure Modes

See Also

• Accrual Substrate — the life-wide collection physics a basin scopes down to one goal
• Macrostate Engineering — the declared question is a macrostate; the visible tracker is the feedback twin of the collection catchment
• Container Design — containers hold time and behavior; basins hold information and goals
• Attention Routing — routing needs a catchment that physically exists
• Bounded Search — budgets limit how long a search runs; retrieval boundaries limit where it looks
• Ratchet — the sibling persistence structure: basins collect, ratchets retain
• Branching and Convergence — the spill is a merge; an unspilled basin is hoarded probability mass

Core Principle: A basin is a structure that accumulates information for one pursuit: a persistent question, a retrieval boundary, and a living synthesis, with a lifetime equal to the goal's rather than the session's. A pillar named only in your head cannot collect — routing needs a catchment that physically exists. Persist the state, not the minds that work it; enforce the termination condition at construction; and let mature pressure spill into experiments and artifacts. Distinguish the basin you dug from the attractor basin you fell into — same geometry, opposite agency.

An attractor basin is where behavior ends up. A dug basin is where a goal's evidence ends up. The first one you escape; the second one you build, because a goal that outlives every session needs a place to keep what it has learned.