| topic | agents |
|---|---|
| type | decision |
| status | research-complete |
| last-validated | 2026-06-27 |
| superseded-by | |
| related-docs | 325, 345, 607, 669, 781, 899, 862, 258 |
| original-query | https://swarmprotocol.gitbook.io/docs can we research this /zao-lens /zao-research and find if this makes sense for zabal gamez also just look through all research docs send 100 agents and look through them all actually have them read them |
| tier | DEEP |
Goal: Decide whether Swarm Protocol (swarmprotocol.gitbook.io) should be adopted, integrated, or mentioned for ZABAL Gamez - grounded in a full read of the ZAO research library.
PASS. Do not integrate, do not mention it. Swarm Protocol is swarm robotics infrastructure; ZABAL Gamez is a Farcaster/ZAO creative build-a-thon, and we already own every coordination/agent/settlement/governance layer Swarm sells.
A DEEP-tier multi-agent pass: 102 agents read all 1,083 README docs in research/ (full library coverage, not a sample, not title-skimming), each scoring every doc for Swarm-relevance and ZABAL-Gamez-relevance. 473 docs came back relevant. A separate agent read the Swarm Protocol GitBook (introduction, solution, use cases, architecture, technology, $SWARM token, tokenomics). A final ZAO-Lens (Builder / Skeptic / Synthesizer) pass produced the verdict, grounded in cited docs. ~8M subagent tokens, ~15 min wall-clock.
A decentralized, cloud-native platform for swarm robotics research - "turning robotics research into a permissionless, global commons." Three layers:
- Cloud simulation of multi-robot systems (formation flying, search-and-rescue) via ROS, Gazebo, Webots, Isaac Sim - no physical hardware needed.
- Decentralized coordination ("DNS for Agents") - a peer-to-peer registry to discover/exchange swarm strategies.
- Application layer - a SwarmNet marketplace + third-party robotics/logistics tools.
Economics: the $SWARM token (500M supply, ~18.5% circulating at TGE) pays for simulation runs and governs a DAO. Stack: Ethereum L2 (Base) + Solana/Cosmos, DePIN compute (io.net, Akash, Render), IPFS/Arweave, The Graph, zkML. Target users: roboticists, industrial operators, universities, defense organizations, environmental scientists.
1. Categorical audience/domain mismatch. ZABAL Gamez tracks are artist (musical/visual), builder (developer/aspiring), creator (media/distribution) - indie musicians, digital creators, Farcaster builders. Swarm targets robotics R&D and enterprise/defense. Zero overlap in use case, audience, or problem.
2. We already own every layer it sells (redundant):
- Coordination / shared substrate -> Bonfire (kEngrams, 20-min auto-extraction knowledge-graph loop) - docs [669], [781].
- Multi-agent fleet -> ZOE orchestrator + 8 live agents, multi-agent fan-out to Bonfire - docs [899], [862], [607].
- On-chain settlement -> Empire Builder + x402 micropayments, autonomous wallet swaps on Base - doc [258].
- Governance -> Respect (soulbound, non-transferable).
- The ZAO even has its own "ZABAL Agent Swarm" concept already designed (software agents, not robots) - docs [325], [345 canonical]. The word collides; the substance does not.
3. $SWARM token breaks a hard brand rule. CLAUDE.md: "No crypto/web3/onchain jargon in public copy." Adopting Swarm pushes token + DAO mechanics into creator-facing surfaces.
4. Complexity + friction cost. Swarm needs Docker/ROS/Gazebo, multiple L2s + bridges, zk proofs, IPFS, The Graph. ZABAL Gamez runs on zero-dependency Vercel edge + Upstash Redis, and the event minimizes onboarding to Farcaster SIWA + GitHub OAuth + one form (doc 785). Swarm raises participant friction ~10x for zero capability gain.
If a participant independently proposes a swarm/agent build in July, judge it on ZAO rails (does it wire Bonfire / Empire / Respect?) - but do not reach for Swarm Protocol's infrastructure to do it; our own stack covers it.
- Doc 345 - canonical ZAO agent build plan (where a real swarm need would surface; Swarm Protocol does not appear).
- Doc 669 - Bonfire as the shared coordination substrate.
- Doc 781 - how ZABAL Gamez wires into Bonfire.
- Doc 607 - ZOE + Bonfire operating model (the problem Swarm claims to solve, already solved).
- Doc 325 - the ZAO's own agent-swarm economy.
| Action | Owner | Type | By When |
|---|---|---|---|
| No integration; no public mention of Swarm Protocol | @Zaal | Decision | Done (this doc) |
| If a participant pitches a swarm/agent build, route to ZAO rails (Bonfire/Empire/Respect), not Swarm infra | @Zaal | Guideline | July build month |
- Swarm Protocol docs - introduction, the-solution, use-cases, architecture, technology, $SWARM token, tokenomics (https://swarmprotocol.gitbook.io/docs) [FULL, via llms.txt index + per-page fetch, 2026-06-27]
- Full read of
research/(1,083 README docs, 102 agents) - relevance map + ZAO-Lens synthesis [FULL] - Cited ZAO research docs: 325, 345, 607, 669, 781, 899, 862, 258 [FULL, read by the fan-out agents]