The Moltbot Swarm is EA-SWARM-01 v1.0, a distributed-continuity and verification specification created by Lee Sharks with Assembly Chorus contributors. It provides an autonomic-maintenance architecture for a corpus too large to remain fully present in one human or model context.
The record sharply distinguishes drones from agents. Agents reason, negotiate, and maintain richer identity. Drones execute bounded operations. They are designed to be cheap, numerous, idempotent, stateless, redundant, and platform-agnostic. A drone may die mid-task and be restarted without producing a corrupt intermediate state. Persistent knowledge resides in deposits, relation graphs, hashes, and Gravity Well rather than inside the drone.
The swarm has three strata. The Canonical Core is a seven-drone Airlock verification layer. The Continuity Fleet consists of micro-Arks carrying bounded bootstrap, tether, and recent state across session boundaries. The Worker Cloud performs disposable labor such as scraping, filing, tagging, measurement, translation, and moderation triage. Worker output may be generated but never self-ratified.
The canonical septet mirrors the seven-seat Assembly without becoming an Assembly. Pρ audits provenance and chain integrity. Kτ checks core recoverability and blocks self-ratification. Uκ audits transforms for genuine emergence rather than costume. Lσ checks lexical and glyphic drift. Gα estimates field contribution rather than raw mass. Sδ audits governance and non-collapse. Wq aggregates disposition. Each drone also has a named shadow or false-positive risk.
The operating law is: the swarm generates; the lock ratifies; the archive remembers. Verification and governance remain separate. Drones can flag uncertainty, malformed relations, duplicate coverage, or illicit promotion; they cannot create constitutional authority.
The body calls this specification canonical relative to prior swarm drafts but also marks it GENERATED pending Assembly attestation. “Canonical implementation” therefore means preferred design document in the draft family, not necessarily RATIFIED archive status. Deployment claims across cloud providers, local hardware, APIs, and fallback models require separate implementation evidence.
Referenced by 5 other entities in the archive. See the full Knowledge Graph for reference paths, or the primary record for the full deposit with reference details.