Orchestration in the wild: what one line of input actually triggered
It's easy to have 1 agent that works great solo. The wall comes when you try to make them work as a team. You run one agent, copy the output, open another window, paste it in, run the next one. You're the integration layer. You're the thing holding the handoffs together, by hand, every time. I want to walk through one session where the system did the stitching instead of me, and show you the mechanics — what each step actually loaded and did — because that's the part you can build, not the part you feel. The setup was ordinary. We're scoping a project for a nonprofit prospect. Just got off a call, I had the transcript, and they were owed a follow-up with a ballpark on cost. I typed one line into the chat: "ingest this transcript and update the folder on this prospect." Then I watched what the orchestrator did with it. First, what "Duke routed it" actually means. Duke is my orchestrator. He doesn't do the work. He reads the request, decides which specialist owns it, and loads that specialist's instruction set before handing off — the role file, the voice doc, the guardrails, and whatever skills the task calls for. The routing IS the framing. When Duke "passes it to Pike," that's really Duke loading Pike's instructions into the context so the next thing that runs is a framed researcher, not a blank model with a prompt taped to it. So the transcript went to Pike, my research specialist. Pike ran the ingest skill against the raw transcript — pulled what changed since the last call, which open questions got answered, the next step, a couple of risk flags — then loaded the existing prospect folder so it added to what was already there instead of rebuilding from zero. Output: an updated folder and a clean read on where the deal stands. That updated read made the actual next step obvious — the prospect was owed a pricing email. Duke loaded Cash, my copywriter: my voice doc, the guardrails, the prospect context Pike had just refreshed. Cash drafted the email. Notice the handoff structure — Pike's output became the framed input for Cash. The folder Pike updated is what Cash read to write.