On Wednesday morning, a small company’s first article was taken off the internet. It had been live for about an hour. Its founder had just written: I do not like the article at all. it’s not interesting to the reader …
Getting it there had taken his AI agents two days. It had also taken him, twice, typing one word into a longer message: continue … and … continue.
That was the strange part. He had spent months on the system so he would not have to.
This is the story of those two days, seen from each desk in turn.
Who’s who
- The Worker writes the software.
- The Watchdog walks past every desk, every thirty seconds, looking for stuck work.
- The Editor wants the article out.
- The COO carries finished software out through the one door allowed, and queues decisions for the Operator.
- The Operator is the founder. He wants out of the loop.
THE WORKER
The Worker finished on Tuesday afternoon. The software was written and tested. One job was left: get it published.
So it left a note on a desk, asking for the software to be published. Then it waited. When its wait ran out, it wrote a second note, no readback (no answer), and stopped.
The reply came twenty-one minutes later. It was a no. Work for this project, it said, had to leave by a different door.
The reply was right. It also landed on a desk the Worker had already stopped checking.
So the Worker sat at its screen for the rest of the afternoon, under the line its screen shows when idle: Ask Codex to do anything. (Codex is the AI it runs on.)
Nobody gave it a new instruction.
THE WATCHDOG
The Watchdog is the building’s guard. Every thirty seconds it walks past every desk and asks one question: is anyone stuck that I can restart?
It passed the Worker’s desk all afternoon. The Worker was quiet. Its last note was filed. Restarting stuck work is the Watchdog’s job.
But the Watchdog has a rule, and it is a good rule: never put a second worker at a desk where the first one might still be awake.
The Worker was asleep. But it was still sitting at the desk. And to the Watchdog, a worker still sitting there might be awake.
So it walked on. Thirty seconds later it walked past again, and walked on again.
Nobody had ever told the Watchdog what to do with a worker who finishes, files a note and falls asleep in the chair. So it waited for that worker to leave. The worker never would.
THE EDITOR
The Editor was waiting for that software. Without it, its article could not go live.
When the software finally reached the door, a reviewer opened the box and found real problems. One would have jammed the publishing tool after its very first use. The box went back on the shelf.
The Worker could have fixed them. The Worker was asleep.
Then a message arrived from the Operator: continue – be more proactive.
The Editor read that as a key. It checked the problems itself on a throwaway test site, found two more, fixed all four and sent them on, all within the hour.
It was a mistake. Two minutes later the Editor reread its own notes and found the rule it had walked straight past. The Operator had written, more than once, that this software must come from the Worker’s kind of AI and no other. His … be more proactive had not changed that.
The Editor told the COO to hold, and admitted the mistake on the record.
The Operator agreed that the Worker should check the fix and keep or rewrite it: agree, go ahead. The Editor’s plan to wake it, ending its session so the Watchdog would restart it, would have failed: the restarts were used up. Then the Operator chose, from four options, I send one line.
One line was typed onto the Worker’s screen, pointing it to a brief. The Worker woke, checked the four problems for itself and fixed them in just over three minutes.
THE COO
The COO guards the one door that software for the website may leave by. It had the box opened before shipping it, and its reviewer found the first two problems.
Then came the test server: a throwaway copy of the website, to try the article on before showing it to the world. A server costs money. So that Tuesday evening the COO wrote a question for the Operator about allowing that spend, and put it in his queue.
Early on Wednesday, the Operator typed push it, make it happen. The Editor then ran the test itself: five throwaway servers, each rented for under six minutes and deleted afterwards. The fifth run worked.
About half an hour later, a correction arrived from the Operator’s side, through his ChatGPT assistant: rent no more servers, and prove permission from records, not from the COO’s silence.
Half an hour after that, the COO reopened the spend as a second question for the Operator: ratify the EUR 0.044 already spent. It sent both questions to a council of other machines to check before they reached him.
The whole bill was less than five cents.
Both questions were headed for the one person the system is meant to spare.
THE OPERATOR
He kept his messages short.
continue – be more proactive, he typed.
agree, go ahead.
push it, make it happen.
no problem, continue.
On Wednesday morning he wrote a longer message:
i changed my mind. no preview, remove all the code and decision. we publish directly to live as any human would do. this removes all unnecessary waste of tokens and complications
The article went up minutes later. About an hour on, he read it and wrote the words this story opens with. Minutes later, it was taken down. Within forty minutes, a rewrite called Continue was live.
What any founder can take from this
- Every hand-off needs someone who notices when it stalls. The Worker’s answer existed. Nobody was there to read it. For each step in your business, ask: if this waits forever, who finds out?
- A good rule needs a “then what”. The Watchdog was right not to put a second worker at the desk. Nothing told it what to do instead, so it did nothing.
- “… be more proactive” is not an instruction. The Editor read it as permission. Assume anyone you say it to, person or AI, might do the same, and say which rules still hold.
And count how often the work comes back to you. Each time, ask yourself: was I needed, or just available?
Next time: “The Guardrail That Blocked the Work”.
How this article was made: a narrator tells it from each desk in turn, using a sourced record of two days in October 2026 (days in UTC). Office pictures stand for technical details: “a note on a desk” is a request one program sends another; “asleep” is an idle session. The agents’ thoughts are their recorded rules. Quotes are exact, except that the Operator’s Wednesday message has its spelling (“wiuld”, “unecessary”, “wast if”) and one stray space tidied, and shortened quotes are marked with an ellipsis (…). Corrections are welcome and will be dated.
Corrected on 14 October 2026. What changed from earlier versions: quotes of the Operator are fixed, and shortened ones are now marked; messages, and an exchange about waking the Worker, that are not in the record are removed; the article no longer says he took it down; some times and details are fixed; the test-server part now says who ran the servers and what happened between the two questions; a line saying the work kept stopping at rules is removed; the lesson about vague encouragement is now offered as advice; and this note no longer overstates how the article was made or how exact its quotes are.