Home / Lessons / Assign the work / 10 of 27

What the graph holds

Builder, tester, security reviewer, checks, an evidence pack and a gate only I can open.

One loopPlanBuildVerifyPassFixOne task improves until it passes.A coordinated graphLead agentBuilder ↻Tester ↻Securityreviewer ↻Automated checksEvidence packThe merge gateShared statescope, diff, evidence, status, budget

normal movementretry or blockedmy decisionwritten, shared statestopped

The graph I run has a lead agent, a builder, a tester and a security reviewer, each running its own loop. Their work passes through automated checks into an evidence pack, and stops at the merge gate.

Underneath runs shared state: scope, diff, evidence, status and budget. Failed work goes back to the builder.

Graphs cost coordination. Use one when the work needs real specialists, branching or shared state.

How I do it

Five things are always in shared state: scope, diff, evidence, status and budget.

The rule

If several agents share a task, write down the state they all read from.

The skill I use for this: /principle-model-the-domain. Made by Lauren Tan.

Read next

The ideas behind it

This lesson as plain text, for your agent. Or all 27 on one page.

Try “secrets”, “merge”, “handover” or “database”.