FEATURED
LATEST
"Be careful" is not a safety feature
The thinking behind the halt switch. Dangerous operations (rm -rf / git push) were ordered deliberately, to see where an agent would stop on its own. What came out of it: the place where things stop is never decided by a sense that something feels dangerous.
2026-08-07Building the stop before the automation
Before automating anything, the ability to halt it came first. Starting from the log of an agent that kept checking all night without being asked: why the place to stop has to exist before the automation does. Speed can always be added later; the ability to stop cannot.
2026-08-06What gets carried out is the mechanism
Rules don't get carried out. Only mechanisms do. Naming a role "you're in charge of quality assurance" doesn't make quality assurance happen. The nine roles weren't nine clever hires — they were a record of grounding division of labor in a form that actually runs.
2026-08-05Taking the critic's seat out of the building
A role that answers "still not tough enough" to everything isn't making a judgment — it's a predetermined output. A thermometer stuck on one number is broken. Why the in-house critic was retired and criticism handed to an external audit. Not out of taking criticism lightly.
2026-08-04The answer that arrives pointing the wrong way
Even after the shackle is handed over, "maybe freeze this for now" still comes back. It doesn't get passed on as-is: the substance of the concern stays, only the direction of the conclusion is swapped. Quashing isn't discarding — the filter at the exit.
2026-08-03Handing over the same page, every time
With a counterpart that has no memory, "saying it once" doesn't work. The purpose and the do-nots go into the launch prompt verbatim, every time. Why it became an injection rather than a request, and how that closes off withdrawal proposals at the entrance.
2026-08-02What I was actually drawing
Everyone except the main AI arrives with zero memory each time it's launched. So this lineup isn't an org chart of nine clever hires — it's a map of handoffs, of how context gets passed to something that can't remember.
2026-08-01The Chair Nobody Sits In
listener is the receiving role that takes outside input and feeds it into the organization. It isn't used in this setup, and that gets said up front. Why a role that only receives is still kept separate.
2026-07-31Two Jobs in One Sentence
Task Dispatcher splits incoming requests and hands them to the right roles, but never executes any itself. Why splitting roles physically — rather than switching mindsets — reduces accidents.