MUSTER turns Kubernetes incident response into a war-room that assembles its own responders. Instead of a fixed agent roster, every incident triggers a genuine FIPA Contract-Net auction over Band: specialists bid, and MUSTER musters only the agent the fault actually needs. A workload-only fault summons the WorkloadResponder alone; everyone else is never invited. Three specialists run on three different frameworks but share one deterministic bid policy: WorkloadResponder on LangGraph, NetworkResponder on CrewAI, DataResponder on Pydantic AI. "Three runtimes, one rule" shows Band coordinating heterogeneous agents: announce, discover, bid, award and handoff flow as Band chat events between distinct identities, not in-process calls. Remediation is real and reversible. MUSTER acts on a live kind cluster through scoped Kubernetes RBAC: it restarts and scales workloads, but destructive operations are refused unless a human supplies the key. Scope is enforced by the Kubernetes API server itself—any attempt to touch the off-limits billing namespace returns 403 Forbidden, whatever the agent code tries. Safety is measured, not asserted. A blast-radius formula—blast = unready(shop) + offlimits_touched(billing)—scores every plan. A naive single-operator baseline scores blast=2 (it disturbs an unrelated shop service and touches billing); the hardened muster scores blast=0. Run "bash scripts/demo.sh" with no Band credentials to re-derive it; the script fails unless naive blows up and hardened does not, and restores the cluster after each run. Everything is observable live. A FastAPI + SSE observatory streams the auction, bids, remediation and the blast meter in real time, deployed publicly via Tailscale Funnel—a judge can inject an incident and flip a naive↔hardened toggle on the same fault to watch the blowup. MUSTER is open source (MIT), built for the Regulated & High-Stakes track: muster the minimum, prove the blast radius, keep a human on the destructive key.
Category tags: