task-delegationlisted

# Task Delegation > **Style:** Mode-B-lite. Role-aware subtask delegation without weakening Fusebase Flow ownership, verification, or role boundaries. ## Purpose Coordinate bounded work across multiple agents when the host environment supports subagents. Delegation is a speed tool, not an authority transfer: the self-attested main role remains accountable for scope, integration, verification, and final reporting. ## When to invoke - Operator explicitly asks for delegation, subagents, parallel agents, or parallel work. - AI Developer has independent implementation/test slices with disjoint write scopes. - Product Owner needs read-only investigation, option comparison, or artifact review that can run in parallel. - Architect escalation needs independent read-only probes over distinct subsystems. ## Do not invoke when - The task is simple enough to finish directly. - The next critical-path step depends on the subtask result; do that locally. - The work requires operator interaction or a decision while the subagent is running. - The work touches deploy commands, production side effects, approval artifacts, secrets, or live-user credentials. - Product Owner would be delegating production code edits. - Write scopes overlap or cannot be clearly owned. - The host has no subagent/delegation tool; use normal `docs/tmp/handoff/` Flow instead. ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Self-attested role | current session | Stop; role defines allo