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

LayerLibrariesResponsibility
Identity and cryptoweave-identity, weave-cryptoSign, verify, and identify participants.
Local truthTrace, Trace BlobsAppend-only records and larger payloads.
Views and convergenceLens, NexusQueryable projections and multi-writer feeds.
FilesLocus, AgentFSShared drives and local filesystem integration.
Networkweave-dht, weave-swarmDiscovery, provider records, topics, and delivery.
ApplicationsWOVEN, Forum, GnosisSigned 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.