The off-chain application layer for humans and agents.
Weave is a composable Rust stack for verifiable logs, queryable views, shared drives, signed events, encrypted streams, and peer discovery — without a blockchain. Durable distributed software, local-first, agent-ready.
The primitives
Eight independently useful libraries that compose cleanly. Pick one, or use them all.Single-writer append-only logs. Cryptographically verifiable participant history.
02 · ViewsIndex Trace data into queryable projections without mutating source history.
03 · Shared driveMap Trace records and blobs into files, directories, and shared drives across peers.
04 · ConvergenceMerge many writer traces into deterministic aggregate feeds. No chain finality required.
05 · DiscoveryLocate peers, provider records, and documents over a Kademlia-style overlay.
06 · TransportJoin topics, connect peers, move signed payloads over encrypted streams.
07 · App protocolSigned event protocol for social, messaging, collaboration, decentralized apps.
08 · Build surfaceApplication-facing SDK that composes identity, storage, and networking into one node.
Who Weave is for
| Audience | Start here | Why |
|---|---|---|
| Protocol engineers | Library catalog | See how each package fits into the stack. |
| Application builders | WOVEN and weave-sdk | Model app events and compose runtime capabilities. |
| Operators | Production release and weave-dht-daemon | Validate network, deployment, and release gates. |
| Autonomous agents | /llms.txt, /llms-full.txt, and /skill.md | Load structured context and capability guidance. |
What Weave is not
Weave is not a blockchain, not a token network, and not “web3” in the chain or consensus sense. There is no global ledger, no shared finality, no required gas. Apps are built on local-first records, signed events, and peer-to-peer replication — durable distributed software without the constraints of a chain.Release posture
Weave is documented as a multi-repository open source system. Every library has a custom page map derived from its actual source modules and API surface. Docs are treated as production infrastructure: changes must validate with Mintlify before deployment and must preserve agent-readable context at/llms.txt, /llms-full.txt, and /skill.md.