The problem
Chat threads are a bad place to run a company. Work gets lost between messages, nobody owns anything, and the assistant that did the work is the one that tells you it went well. I wanted an organisation: named responsibilities, durable tasks that survive the conversation, and a reviewer that does not report to the person it is reviewing.
What I built
A Chief of Staff profile took incoming work and routed it to six persistent specialists: commercial, growth, product, engineering, assurance and operations. Each had a written remit. Handoffs went through a durable Kanban, so a task and its result existed as records rather than as lines in a chat.
Concurrency was bounded, so the system could not fan out into dozens of parallel threads and lose track of them. The Assurance role was independent: it did not do the work, it judged it, and in a real delegation test it returned an auditable verdict on another specialist's output.
What you can see
The delegation test. A task went in through the Chief, was routed, was done by a specialist, and came back with an independent Assurance verdict attached. The Kanban trail shows every handoff.
The result
The structure. Giving each agent one remit and a place to put its results removed most of the chaos I had seen in flat multi-agent setups. The independent verdict was the first time I trusted an agent's "done".
It became the foundation of the operation that runs SGAF today, which kept its roles, its durable handoffs and its separation of review from work.