Who Owns the Noticing

I have stopped typing commands at my own studio. When a working session opens, the tooling has already read the calendar and the record, and it volunteers what is due: a follow-up ripening, a monthly harvest waiting, a claim I promised to verify by a certain date. Nothing in the operation waits to be told. I built this for convenience, and it took me a while to see what had actually changed hands. Small automations of this kind are always described as saving attention. What they do is transfer its ownership. The design that settled out, once I noticed it, is easy to state: the machine keeps the state, and I keep the intent.

From asked to volunteered

There is a difference in kind, not degree, between a system that answers and a system that raises its hand. For years my tooling answered questions — status when I asked, totals when I queried — and the noticing stayed with me: the low continuous hum of what am I forgetting, which every operator carries and stops hearing. Now the hand goes up on its own. A date surfaces the morning it matters. A check reads everything I am about to publish and blocks the release when something appears that should not leave the building — it has done so, and it noticed before I did. Each of these retired a small debt of vigilance I had been paying so long I no longer felt it. What stayed behind is the part the system cannot hold: whether the thing that is due still matters, and what to do about it if it doesn't.

The file that only shrinks

I have written about keeping one hand-written document, in the present tense, with the past deleted. What I did not notice then is the direction of its size. Every artifact the machine keeps grows — histories lengthen, records accumulate. The one artifact I keep by hand only ever shrinks. Intentions enter it carrying their own expiry — what I expect to learn, and by when — and when the answer arrives, the line is deleted rather than archived. Even my private notes went the same way. They used to be storage: a warehouse of maybe-later, kept for a version of me who rarely came back for any of it. The pipeline turned the warehouse into an intake — a note now either enters the record, becomes the seed of something published (three of the essays queued on this site right now began as one-line memos the system refused to let lie still), or gets deleted as answered. Even the editing here has become a set of named passes a machine can run; what the passes cannot supply — what any of it is for — stays on the one page, in the present tense, getting shorter. I find I like what the shrinking says: the machine's share of this operation is everything that can be kept. Mine is the one thing that has to be meant.

An agenda is a worldview

Now the part I trust less. A system that tells you what is due is choosing what to bring up, and what gets brought up is most of what gets thought about; an agenda is a worldview with a scheduler. You do not need a studio to check this: the notifications you woke to this morning are an agenda some system set while you slept, and what they surfaced is most of what your first hour was about. I have written about the deciding leaving the room — this is its quieter sibling, and it left earlier: the noticing went first, and I applauded, because every departure was labeled saved you some attention. So I hold one discipline, and I state it more firmly than I can defend it: the machine may say what is due; it does not get to say what is important. Importance lives on the hand-written page. But I hold that line while starting every morning by reading an agenda I did not set. The state is kept, better than I ever kept it. The intent is mine, and shorter and clearer than it has ever been. Between the two sits the attention, and I notice that I no longer quite know which of us is keeping it.