Skip to content

Playbook delegation

Delegation gives part of a goal to another agent or playbook. The caller supplies the task and inputs, then uses the result and its evidence to continue.

This step calls read-meetings and passes two fields from the parent’s inputs. The child key must already be registered. This excerpt belongs in a structured playbook’s steps.

{
"id": "read-source",
"title": "Read meetings",
"instruction": "Collect evidence for the summary.",
"type": "playbook",
"playbookKey": "read-meetings",
"inputMappings": { "from": "/input/from", "until": "/input/until" }
}

A goal playbook lists eligible child keys in allowedPlaybooks. A Canvas connection of kind delegate names the placements that may delegate within the team. A handoff makes accepted results available for later work. The planner may use either connection according to what the goal and runtime support.

Keep a child inside the parent’s authority

Section titled “Keep a child inside the parent’s authority”

Apply the child’s accepted definition and skill, while enforcing the parent’s permission and budget ceilings. Return named outputs and evidence so the caller can proceed. A denied connector or held approval in the child holds dependent work. Check cycles during definition validation and bound dynamic delegation by depth, tasks, agents, and time.

Keep the child result and its evidence tied to the calling attempt so the parent can use only the accepted fields. For example, an outreach parent receives the verified source URL from its research child. Sending the resulting draft remains a separately governed operation.

See Standard Agent Specification’s subagent relationships for its thread model.

See goals, agents, and run history.