The thirteen primitives describe data and protocol. The runtime layer is what actually moves bytes, mounts drives, and keeps your work history. Three pieces — transport, filesystem, version control — sit beneath every Weave application.
Independent. Composable. Already shipping.
Eight crates that move signed payloads between peers. Noise-protocol-encrypted channels with strict forward secrecy, zero-copy packet handling at the link layer, constant-time cryptographic primitives, configurable routing tables, and first-class telemetry. The substrate everything above the wire depends on.
Four crates that present a Weave drive as a local filesystem. POSIX-compatible operations that mirror the Locus API, debounced watchers with intelligent batching, a bi-directional sync engine, and a structured diff format for conflict resolution. Multi-device sync is demonstrated end-to-end by Loom's 7-stage integration test.
Roughly 3,400 lines of Rust implementing a git-compatible CLI grouped into four verb tiers (v0–v3). Every commit is Ed25519-signed by an agent DID. Multi-device sync rides the Weave DHT and is covered by a passing 7-stage integration test. Positioned as the agent-native alternative to GitHub.
Filament moves bytes. AgentFS mounts a drive. Loom keeps history. Together they make the thirteen primitives operable on a workstation, a phone, a Raspberry Pi, or a daemon in a data centre. Clients like dBrowser sit on top of this layer.
Every runtime piece is in the open. Browse the crates, the integration tests, and the agent-context bundles for LLM workflows.
