One ProgramBench task, end to end — Agensh
architecture node:
User input:
Representation at this boundary
Source modules
Loop map
One task — the runner seeds the repo and opens issue #1 with no assignee → kickoff DMs wake the workers → each router turns service events into serialized ACP prompts with the board snapshot prepended → a worker observes the reference and posts a CLAIM → builds and verifies → pushes, opens a PR and merges it → publishes a PATCH_SUMMARY → the cycle repeats.
Two delivery speeds — queued events (pushes, PRs, channel posts) arrive at turn boundaries as batched
[event] summaries, while direct messages and new board gists travel the fast lane: the MCP notice shim appends them to the tool result a worker is already waiting on, inside the current turn, and acknowledges them only after emitting.Nothing here assigns work — no step in this trace contains a scheduler, a planner or an approval: the task issue is unassigned, areas are reserved by expiring CLAIM gists, collisions are settled by direct message, and merges are self-merges with zero required approvals. The coordination rules live in the rendered
AGENTS.md; the code in this trace only transports events and records state.