PATTERN Cited by 1 source
Cluster-of-clusters artifact coordination¶
Pattern¶
Compose specialised agent clusters by having each cluster publish durable artifacts into a shared environment and having other clusters read those artifacts on their next iteration. A coordinator cluster may publish conflict-resolution notes, but those notes remain advisory traces rather than imperative commands or a hard dependency. (Source: sources/2026-08-11-aws-scaling-patterns-for-self-organizing-multi-agent-clusters-with-kiro)
Structure¶
feature cluster ──────┐
shared-infrastructure ├── shared artifact environment ──► QA cluster
QA findings ──────────┤ │
coordinator notes ────┘◄─────────────────────────────────────┘
All clusters may start concurrently because there is no execution DAG enforcing stage order. Interface-oriented clusters can converge on a stable artifact while implementation clusters build against its latest visible version. Removing a coordinator removes a source of advice, not the cluster's ability to continue.
Trade-offs¶
- Gain: avoids a cross-cluster scheduler and lets specialised work proceed in parallel.
- Gain: artifacts act as a durable, inspectable boundary between teams of agents.
- Cost: consumers can build against an obsolete artifact; contract drift and unresolved conflicts are expected failure modes.
- Cost: a final integration test or review remains necessary because shared visibility is not a correctness protocol.
Seen in¶
- sources/2026-08-11-aws-scaling-patterns-for-self-organizing-multi-agent-clusters-with-kiro — AWS's WeltenBuilder example composes feature, shared-infrastructure, QA, and coordinator clusters through shared environments and advisory resolution artifacts.