Part 6 of 11 · 1 min read
Build it so isolation actually helps
- Isolate noisy, self-contained sub-tasks. If the parent needs the intermediate steps to decide anything, isolating them just moves the cost.
- Define the contract: a schema for the result (findings, evidence pointers, caveats, status), and a rule for failure ("return
status=failedwith the reason", not "Done!"). - Pass constraints down. The child does not see the parent's context; scope, format and limits must be in its task.
- Return pointers for bulk. If the parent may need the raw material later, the child writes it to the workspace (module 5) and returns the path.
- Treat returned text as untrusted. A child that read the web can return attacker text; validate the result against the schema and do not execute instructions in it.
- Count the total. Compare the sum over all agents, plus the parent, with the single-agent run; at short tasks the overhead (system prompts, handoffs) can exceed the saving.