Resources HubSYSTEMS DESIGNCOMING SOON

Systems & Architecture

How Swarm works under the hood. Distributed Go runtime, git worktree isolation, local-first append-only state engines, and production incident post-mortems — architecture deep dives coming soon.

Core Runtime:Compiled Go daemon (`swarmd`)
State Engine:Local-first append-only logs
Git Model:Multi-worktree lineage

Systems Directory

Architecture Deep Dives

Technical writeups on the systems design that makes concurrent agent execution reliable and deterministic. Deep dives are currently in preparation.

SYSTEM 01Coming Soon

The Worktree Lineage Model

How Swarm prevents repository race conditions by isolating subagents in dedicated git worktrees with strict parent verification barriers.

#architecture#git#worktree#concurrency
Key Architectural Invariants:
  • Subagents never edit the parent checkout or root branch directly
  • Isolated sibling worktrees created from exact parent commit SHAs
  • Parent owns test validation and integration barriers before promoting
  • Deterministic multi-stage Task Programs with typed dependencies
LOCAL-FIRST FOUNDATION

Local First. Server Ready.

Most agent frameworks are designed as centralized cloud SaaS platforms where code is uploaded to third-party containers. Swarm inverts this: the workstation is the control node. Agents execute against your local repositories, use local git primitives, store state in local logs, and scale to self-hosted Linux instances over private WireGuard tunnels.