One planner, three remote agents
The planner of the kit is a tall machine on the left with a slot for each of three lanes, in the order that the planner log records. In each lane the planner calls a remote agent, drawn as a machine with its port and skills, and the agent puts its task on a tray, one slip per state. test-runner completes with 13 passed, drawn as 13 cells on its top. code-reviewer asks which base branch to use, the planner answers main, and the task completes with one finding. deployer waits in TASK_STATE_AUTH_REQUIRED, the planner follows the task with SubscribeToTask, an operator outside A2A approves, and the task completes.
CLIENT AGENT
REMOTE AGENT
THE TASK IT RUNS
planner
client agent
reads 3 cards
test-runner
port 41241
skill run-tests
SendMessage
task 954267b7
TASK_STATE_COMPLETED
summary.json: 13 passed
code-reviewer
port 41242
skills review-diff,
answer-question
SendMessage
task 80bc7784
TASK_STATE_INPUT_REQUIRED
TASK_STATE_COMPLETED
review.json: 1 finding
answer: main
deployer
port 41243
skill deploy
bearer token required
SendMessage
task a31361b3
TASK_STATE_AUTH_REQUIRED
TASK_STATE_COMPLETED
build live on staging
SubscribeToTask
operator
outside A2A
approves
Task ids shortened to 8 characters