Skip to content

Orchestration that survives contact: cheatsheet

RoleJobWatch for
CoordinatorDecomposes, delegates, aggregatesEarns its seat only when subtasks cannot be predicted
SubagentWorks one slice in an isolated contextInherits none of the parent’s work; the brief is its whole world
SeamWhere context, failures, and sources crossEvery seam must justify itself, then be engineered

Channel in from the coordinator: the delegation prompt. Channel out: the final message. Nothing else crosses.

ElementAnswersRosa’s pricing surveyor
ObjectiveWhat job, and whySurvey regional cargo-gear prices for the second store
Output formatWhat comes back, in what shapeCategory, price band, seller, source URL per entry
Tools and sourcesWhere to look, what to preferWeb search; seller pages over aggregators
BoundariesWhat not to do; who owns the restPrices only; competitor strategy belongs to the scanner

Rule: no pronouns, no “as discussed.” If it is not in the brief, it does not exist.

Failure modeSymptomTest before spawning
GapConfident report about a smaller questionWhat part of the task belongs to nobody?
OverlapDuplicated work, conflicting versions of one factWhich two briefs could return the same fact?

Goal: everything covered, each piece owned once. Shared territory names one owner in both briefs.

QuestionAnswerAction
Does brief B need brief A’s output?NoSpawn together
Does brief B need brief A’s output?YesChain; paste A’s output into B’s brief

Cost note: parallelism buys back latency (up to 90 percent, per Anthropic), never tokens. Multi-agent runs cost many times a single chat.

FieldContains
What failedThe wall, named, with evidence of attempts
What was attemptedRoutes tried, so nobody retries them blindly
Partial resultsWhat survived, with sources attached
Not coveredThe gap, stated as a gap

Coordinator’s three moves: retry (transient), reroute (new subagent or source), proceed with the gap annotated.

Anti-patterns: the silent swallow (failure laundered into an invisible gap) and the kill switch (one failure discards everyone’s work).

RuleBecause
Claim and source travel as one unitSummarization strips sources by default
Every output format demands sourcesThe coordinator cannot recover a URL it never received
Cite in the final synthesisA report should ship with its receipts
PitfallCorrection
Delegating as if the subagent were in the roomPaste in everything needed, every time
Decomposing by what is easy to nameTest for gaps and overlaps against the original task
One schedule for everythingDependency test per pair of subtasks
Prose apologies as failure reportsRequire the structured form
Synthesis that strips sourcesClaim-plus-source pairs in every format
LineMeaning
A subagent inherits none of your context; the brief is its worldWrite for a fresh desk
A failure is a findingStructure it so the coordinator can act
A claim without its source arrives as a rumorAttribution dies in the middle hop