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.
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.
Rule 10. If several agents share a task, write down the state they all read from. (What the graph holds, https://chiefofagents.si/one-page#rule-10)
The skill I use for this: /principle-model-the-domain. Made by Lauren Tan.
Read next
The ideas behind it
- Loop or graph: how should agents be coordinated?Use a loop to improve one task until it passes. Use a graph when several specialists need to branch, rejoin and share state.
- What is an evidence pack?The test results, review findings, screenshots, logs and state needed to judge a claim that work is complete.
This lesson as plain text, for your agent. Or all 27 on one page.