{{ t.f1t }}
{{ t.f1b }}
guide
2026-07-21 · 8 min · Vibisual
One orchestrator, a schema migration, an API rewrite, a test runner that may not write, and a doc writer that waits for green.
Take a checkout refactor touching a migration, two route files and a price helper. Done by one agent it is a long single session, and one mistake anywhere costs the whole run.
Split five ways it becomes a graph. The orchestrator owns the plan. schema-migrator writes the migration in its own worktree and hands the new column names forward. api-builder rewrites the route against them.
test-runner gets read-only access to src/** — it can run the suite and read anything, but it cannot fix what it finds. That constraint is the point: a runner that edits code stops being a measurement.
doc-writer sits behind an edge from test-runner and starts only when the suite is green, so the changelog never describes a build that got rolled back. The whole design is five bubbles and five edges, and it reads faster than the paragraph describing it.
{{ t.nameLine }}
{{ t.sub }}
{{ t.canvasCaption }}
{{ t.vdeLead }}
{{ t.f1b }}
{{ t.f2b }}
{{ t.f3b }}
{{ t.instLead }}
{{ t.instSrcBody }}
Contributing →{{ t.statusBody }}
{{ t.secBody }}
{{ t.ctaSub }}
{{ ui.blogLead }}
{{ art.excerpt }}
{{ pa.v }}
{{ doc.lead }}
{{ pa.v }}
{{ s.note }}
{{ t.ideAnnoLead }}
{{ an.b }}
{{ an.k }}