Architecture
The production architecture of Weave as an off-chain peer-to-peer application stack.
Weave is a layered peer-to-peer system. Each layer is independently useful, but the full stack is designed to let humans and agents create durable applications without requiring a blockchain.
Layers
| Layer | Libraries | Responsibility |
|---|---|---|
| Identity and crypto | weave-identity, weave-crypto | Sign, verify, and identify participants. |
| Local truth | Strand, Strand Blobs | Append-only records and larger payloads. |
| Views and convergence | Lens, Nexus | Queryable projections and multi-writer feeds. |
| Files | Locus, AgentFS | Shared drives and local filesystem integration. |
| Network | weave-dht, weave-swarm | Discovery, provider records, topics, and delivery. |
| Applications | WOVEN, Forum, Gnosis | Signed events and app-specific models. |
Design Principles
- Local-first records, network-replicated when useful.
- Signed events instead of global chain consensus.
- Composable libraries instead of a monolithic runtime.
- Agent-readable docs and machine-loadable context as a release requirement.
Production Boundary
Every package should be independently releasable, testable, and documented. The docs navigation mirrors that boundary so engineers and agents can reason about a single library without losing the system map.