Sub-agents and workflows
Delegate bounded work to isolated agent sessions and coordinate multi-step workflow execution.
Reasoning proposes work; policy controls authority
Delegated execution
The core exposes sub-agents as a distinct execution layer. A parent can delegate specialized work while retaining the relationship to the originating task and receiving the resulting evidence through the shared event and ledger systems.
Session isolation
Each sub-agent owns a session scoped to its identity. Parent and child transcripts, token counters, and context windows remain separate, which prevents delegated work from silently polluting the parent conversation.
Workflow orchestration
Workflow definitions coordinate multiple steps rather than collapsing a process into one unrestricted tool call. Tasks, runs, approvals, and worker assignments remain visible at their normal system boundaries.
Progression gates
The repository describes sub-agent and workflow access as progression milestones in the XP system. Treat these as runtime capabilities that remain subject to policy and implementation-stage constraints, not as universal access granted by a level label alone.