v2 · architecture
Choreographed
backend / frontend / design peers
Choreographed architecture
v2 choreographedThree peer agents — backend, frontend, and design — collaborate directly over a shared message bus with no central coordinator. They message each other, exchange specs, and each marks itself complete when its needs are met. Best for cross-functional design tasks where peers negotiate.
Backend
Frontend
Design
shared message bus
peers exchange specs directly · no central coordinator
How it works
- 1Backend, frontend, and design agents start with the same brief.
- 2They message each other directly over a shared per-conversation bus — no central coordinator.
- 3Each reads its inbox, refines its part against peers’ feedback, and re-shares.
- 4Each marks itself complete; the run ends when all three are done.
When to use
Cross-functional design tasks where peers must negotiate a shared artifact.
Trade-off
Peer negotiation can loop or stall; harder to guarantee convergence than a coordinator.
Agents
BackendAPIs, data models, services
FrontendComponents, state, layouts
DesignUI/UX, styling, visual guidelines
Note
Peers negotiating directly can produce richer cross-functional output, but convergence isn’t guaranteed — feed each agent its inbox and give clear "done" criteria or it loops.