Subagent

The orchestrator writes a brief with four fields (objective, parent node, boundaries, pointer traces) and the subagent drives its own iteration loop: read traces, form edits, run experiments, analyze, repeat. It's auto-loaded when subagents spawn, but orchestrators can also read it to understand what shape of brief their subagents expect and what they'll emit back, which helps when debugging why a subagent did something weird. The protocol includes mandatory verifier gates before and after every run, references for instrumentation and training recipes, and the full command surface for working with the evo experiment tree. If you're building multi-agent optimization workflows, this is the contract between your dispatcher and its workers.