What gets carried out is the mechanism
The previous entry was about retiring the critic role that used to sit inside. That closes out the nine roles, introduced one at a time. Looking back over the run, I don't think what I was writing was the story of assembling nine capable hires. It reads more like a record of taking the idea of divided labor and forcing it into a shape that actually runs.
Where that became clear was in working out how the nine fit together. Most of the roles here reset when they're called. Nothing from the last round survives, so the same premises have to be handed over again every time. At first it looked like nothing but overhead. It turned out to be a finding of sorts. Say to something, once, "you are the role that checks quality," and the work of checking doesn't start. It starts when what to check and what not to check gets handed over, every time. A job title doesn't guarantee execution.
Ask a role that's only been named to check something, and what comes back is usually agreement of the harmless kind. Not laziness. Nobody handed over the standard to check against. Without the standard, checking keeps its shape and loses its contents. And the gap doesn't close once and stay closed — it reopens by the same width at every start. So closing that gap had to become a mechanism in itself.
The same thing showed up in trying to hold a direction. Ask once for no proposals to retreat or scale down, and by the next round it isn't in effect. It came into effect when that sentence was fixed into the text handed over at every start. A mechanism at the entrance handing the same constraints across, and a mechanism at the exit that rewrites the conclusion whenever "let's pause this" comes back. With those two at either end, the direction finally reached a state of being carried out. One saying isn't enough. Only the repeating mechanism gets carried out — dull, and hard to argue with.
Where to put the objector came down to the same thing. Put a dedicated critic inside and it looks self-contained. But an objector on the inside shares the premises and the material, which means holes in those premises stay invisible to it. And once it returns an objection every time, the objection isn't a judgment anymore. So the work of criticism doesn't live inside; it's entrusted to the audit outside. Again not a question of the job title, but of where it has to sit for the work to survive.
Rules don't get carried out. Mechanisms do. Splitting into nine, handing over the same premises each time, injecting the direction through a template, entrusting the work of objection to the outside — all of it converges on one finding. What you ask for in words is forgotten in the next moment. Separate the steps physically, make the output of one step the input of the next, and only then does what you asked for keep being carried out.
Why only this unglamorous approach works comes down to nothing staying inside the role. Whatever you ask a role in words doesn't stay in the role. What stays is the shape it gets written into — the document, the handover the next role reads. So the request rides on the record instead of on memory, and gets handed over as the next step's input. What you put inside a role disappears when the start ends. What you put between the steps doesn't.
Keeping execution, audit, and approval in separate places is the larger frame, and I've written about it more than once. The nine roles, I think, were the record of how that idea got laid out concretely. Execution branched into nine, each carrying a piece of the work: settling direction, running the sequence, looking things up, writing, tuning the wording, sorting the requests. Audit came out in two layers, the checking placed inside the execution branch and the audit placed outside it. Approval alone has stayed in human hands the whole way.
How to keep approval that way is still an open question here.
