Skip to content

Why Weave — manifesto

Identity, memory,storage, reach.

Autonomous software needs verifiable history, signed events, peer discovery and durable replication. Weave provides those directly, peer to peer — without consensus, without tokens, without the cost or the constraints of a chain.

A closer lookIndependent, by design.

A signed record leaves one local thread and joins another. Each participant retains its own history.

  1. 01Begin locally
  2. 02Share deliberately
  3. 03Keep your own thread
6 principles  ·  13 primitives  ·  0 blockchains
01 — The case

The constraints of a chain are not the constraints of distributed software.

Global consensus is expensive. Token economics are coupling. Gas is friction. For most software, none of those costs buy anything you needed.

What agents actually need is verifiable history, signed events, peer discovery and durable replication — the things Weave provides, in thirteen composable primitives you can adopt one at a time.

02 — The principles

Six principles.

01Local-first

Local-first, network-replicated.

Apps own their state. Records are signed, append-only, and durable on disk first. Replication is a protocol, not a prerequisite.

02Verification

Verification belongs to the recipient.

Every event is hashed, signed, and verifiable offline. Trust is locally provable, not consensus-implied.

03Composition

Composition over orchestration.

Thirteen independent primitives. No master runtime. No required ordering. Adopt one, port one, compose all.

04Agent-native

Agents are first-class operators.

Every CLI verb is a callable surface, every SDK call carries DID identity, every event is signed and replayable. Plus /llms.txt, /llms-full.txt, /skill.md, /.well-known/agent.json.

05No ledger

No chain. No token. No gas.

Apps run without a global ledger. There is nothing to mine, stake, finalize, or pay. Just signed events and replicas.

06Discipline

Open source as production discipline.

Every library is independently versioned, tested, documented, releasable. Docs are treated as production infrastructure.

Trust is
locally
provable,
not consensus-
implied.

03 — Build

Built for autonomous software.

Weave is the stack that gives you the verifiability without the chain. Thirteen independently versioned Rust libraries, each tested, documented and releasable on its own schedule.