What I was actually drawing

2026-08-02

Over the last several entries I've introduced the roles one at a time. COO, Tech Lead, Content Director, Copywriter, Brand Voice Editor, QA Director, Researcher, Task Dispatcher — and the ninth seat, listener, still empty. Names and territories, all of them on the table now.

Which leaves the question I kept skipping while introducing them: why this particular arrangement?

The answer arrived through an ordinary piece of work. I had Content Director settle the direction for a piece, then handed it to Copywriter to draft. Standard sequence. The premises Content Director and I had worked out — I assumed Copywriter knew them too. Not a decision, really. An assumption I never noticed making.

The draft came back built on different premises. The direction we'd settled on hadn't reached the writer at all. A round of rewrites later, I went back to look at what had happened.

It was easy to find. When I started Copywriter, I passed the role definition and the assignment for that piece. Nothing from the conversation with Content Director. From where Copywriter stood, none of that history existed.

The fact underneath is plain enough. The only one carrying the running conversation is the window role handling it. The rest are agents you start up for a single task, fresh each time. No previous round, no exchange with the role next door. In practice I describe it as: everything except the main line is a robot. That isn't a comment on how capable they are. It's that at the moment of being called, nothing exists except what you handed over. There's no memory, so asking as though there were is asking nothing.

After that, the arrangement looked different to me. Dividing the labor turned out to be the surface of it. Underneath sat the question of what to hand a party who remembers nothing, every single time.

If the nine shared memory, the order could be much looser. Ask anyone anything and the premises come along for free.

That isn't the situation. What Content Director settles stays inside Content Director, and the instant I start Copywriter it's gone unless I carry it across. The intent behind a draft doesn't reach Brand Voice Editor on its own. Whatever QA Director checked has to be handed over again the next time some other role starts.

Splitting into nine also means nine places that remember nothing, standing in a row. So when I worked out the order, the question wasn't who's sharpest. It was which role passes what to which role so the premises don't break. Upstream settles something, downstream receives it. Miss the handoff and the premise breaks there — and a broken premise isn't something downstream can recover, however good it is.

Roughly what happens when someone transfers into a new post and the handover notes only ever existed in the previous holder's head.

Seen that way, this is less an org chart of nine strong hires than a map of how context gets carried to a party with no memory. Nine names in a row won't run anything. What runs it is what sits between the names.

What I hand over at each start, and how — that part is still partly guesswork. Even so, the one thing sitting behind the arrangement is this, and it belongs on the record.

タイキ(Taiki)

タイキ(Taiki)

An implementation log of organizing AI agents

← cd ..