DL-134
Dogfood implementers are IN-PROCESS SUBAGENTS the Manager briefs via the live task mechanism (the Manager authors each subagent’s brief — task + context — at spawn time and names a standing subagent def whose body supplies block-0; there is no per-spawn systemPrompt param); the implementer block-0 is therefore an ACTIVE Dogfood deliverable, shipping as a fleet-delivered subagent def under config/agents/ (body = AgentDefinition.systemPrompt), consumed by task + discoverAgents at cf048ca with no cli.ts wiring; agents_spawn_peer/agents_despawn_peer are reserved for standing peer/child Managers; per-implementer containers are rejected for Dogfood (container-per-subagent too heavy) and gate on the RIG-1717 brain/hands split (Beta, distinct from RIG-1724’s role mechanism), which alone defers the containerized non-subagent implementer path (not the prompt)
Status: Active (Matt, 2026-08-04)