Recall on Byron DG — The Upstream

dispatch

Tue, 07 Jul 2026 05:00:00 +0000

A dispatch is the launch: one brief per agent, the whole crowd out in a single motion. One question becomes six workers, each holding its own slice and its own place to write what it finds.

It earns a definition because the dispatch is where reliability gets decided. Everything an agent does downstream was fixed by the brief it left with. A dispatch built on validated, typed briefs fails before launch, in the time it takes a validator to raise. One built on freeform prompts fails an hour later, as an output folder with holes in it. Same fleet, same models. The dispatch was the difference.

fleet

Tue, 07 Jul 2026 05:00:00 +0000

A fleet is the crowd: several agents launched at once, each working a slice of the same question. They do not talk to each other, they do not share notes, and each one writes its findings to its own file. That isolation is not a limitation. It is the feature. When agents that could not coordinate come back agreeing, the agreement is evidence.

The thing to remember about fleets is that they are a tool for a shape of question, not an upgrade over one agent. If the slices are independent, a fleet is faster, wider, and harder to fool. If each step feeds the next, a fleet makes things worse, and one agent thinking for a long time wins. Parallelism is a property of the question. Owning a fleet is not a reason to use it.

operator

Tue, 07 Jul 2026 05:00:00 +0000

The operator is the human above the whole system: me here, you in yours. Not the one writing each brief or merging each report; a model does that. The operator does the three things the system cannot do for itself: aim it at a problem worth solving, pour what you know into how it runs, and decide what to believe when it comes back.

The word earns its precision at the boundaries. The operator owns exactly two: the contract going in (every brief validated before a cent is spent) and the doubt coming out (no confident answer trusted unchecked). Everything between them can be delegated. The boundaries cannot, and a fleet is only ever as good as the operator holding them.

orchestrator

Tue, 07 Jul 2026 05:00:00 +0000

The orchestrator is the model in the middle. It takes one question and turns it into many jobs: slices the problem, writes a brief per worker, launches the crowd, and folds whatever comes back into a single answer. Not the human above (that is the operator), not the workers below (those are its subagents). The middle layer, where one becomes many and many become one again.

It has a flaw worth respecting. The orchestrator is a model too, with a finite memory, and on a big enough job it can forget what it launched before the workers come home. So the durable record of a fleet (who went out, where each one writes, what returned) lives on disk. Never only in the orchestrator’s head.