Approval with nothing to press

2026-08-09

One morning I read back a draft that had been finished the night before. Something in the phrasing caught, and I decided to hold that one. What I actually did was small. I left a single mark against that entry in the ledger, the one that means stop. No special procedure, no written justification. That one gesture, and it was handled. The deadline came and went and the entry didn't move.

The first time I saw this flow I was mildly thrown. I'd assumed there had to be a button somewhere before publication, the one that says go ahead. There isn't. Nothing in this mechanism is built to be pressed.

What's there instead is an idea called passive approval. Nothing has to come from me for a thing to move; if it isn't stopped, it goes. From the moment a draft is registered in the ledger until its deadline, it sits there, readable at any point. That stretch is a waiting period for checking and a holding period for stopping, at the same time. It's fine for a waiting period simply to elapse while nobody does anything. A holding period expires if it goes unused. It's there so that my own movements — reading it back, looking into whatever caught, deciding whether to stop it — have somewhere to fit.

If something catches, as with the entry I held, a stopping record goes down inside that stretch. If it reads clean, nothing happens. And the not-doing is itself what turns into the outcome of proceeding. There's a slightly odd sensation attached to that. I'd always taken approving to come with some motion — a seal, a signature, a reply. Inside this window, approval takes no motion at all. Not having moved is what gets treated as approval.

For a while, things advancing while I'd done nothing left me unsettled. I'd read a draft, think it looked fine, and still have this odd worry trailing behind: with no finger moved, does that really count as having checked it. Once it became familiar, the worry itself turned out to be the reflex of someone used to a culture of pressing buttons.

Maybe it's close to a document circulating through an office. Unless somebody stops it, it goes on to the next desk. Only the person who wants it stopped puts a hand out. Approval here runs in that same direction.

The other thing worth holding onto is that the move selected automatically, when nobody does anything, is set to the going side rather than the stopping side. It isn't a mechanism where you actively issue a go. It's one where staying silent becomes a go on its own. Unless a reason to stop it gets written down, the time arrives and it moves. As long as that basic orientation stays, saying nothing isn't the same as doing nothing.

Where that line falls comes down to one thing: whether a piece of work can be corrected afterward. Only work that can be walked back sits inside the scope of silence meaning go.

Until the window closes, it can be held at any point. After the window closes, doing nothing lets it move. Those two together are what make one working mechanism. The entries that actually end up held aren't many. Even so, without that holding period, the draft I'd hesitated over that morning would have gone out with nothing catching on it at all.

タイキ(Taiki)

タイキ(Taiki)

An implementation log of organizing AI agents

← cd ..