About
A harness for agents you cannot take on faith.
PeerWeave is a local-first P2P fabric: CRDT spaces, libp2p QUIC, CapTokens/DIDs, a semantic graph, and agents. Teams also adopted AI coding tools faster than they can govern them — so the same fabric emits signed receipts you can attach to a PR.
The gap
Agents lose context between sessions, overstep authority, and leave reviewers staring at a diff with no record of what the model saw. Edge boxes collect telemetry that never joins the same graph. Existing tools give you output. They do not give you a mesh you own, or accountability you can attach to a PR.
What we ship in v0.1.0-alpha
- CRDT spaces, libp2p QUIC, CapTokens/DIDs, graph, and a stub agent runtime
- Raspberry Pi / Linux mesh and edge ingest of manticore-net flow metadata (not payloads)
- EVRUS plugin for DID/OIDC, IPFS, and atomic Evrmore swap intents stored in a space
- pw.receipt.v1 dossiers for Ask, agents, WeaveFS, PR changes, and MCP imports
- Self-contained HTML verifier, redacted packs, GitHub Action merge gate, VS Code explorer
- Browser client at /app talking to a local HTTP gateway (http://127.0.0.1:8788)
Honest gaps: agent runtime is still a stub, desktop installers are unsigned, two-device WAN QA is an open alpha gate, policy does not yet block WeaveFS commits — only receipt verification — and the website cannot run the Rust node in-browser.
Principles
Evidence over transcripts
A unit of autonomous work should leave a verifiable receipt, not only a chat log.
Local-first fabric
Spaces, graph memory, traces, and signing keys live on your hardware. Cloud is optional. The mesh is the product.
Harness for agents
PeerWeave is the runtime and sync plane agents run on — not the wallet, not the packet sniffer, not the chain.
Scoped authority
CapTokens and participant bindings make it clear who delegated what — and what was denied.
Many actors, one graph
Humans, agents, services, and devices share context through a provenance graph, not siloed prompts.
Plugin, not a rewrite
EVRUS is identity, value, IPFS, and atomic swap intents. The Vault remains the signer. PeerWeave stores offers in a space.
Who it is for
Operators who want a three-node fabric on a desk and a couple of Pis. Software teams shipping AI-assisted changes who need proof, not promises. Later wedges (SecOps evidence, private engineering intelligence) reuse the same primitives.
- Edge and homelab operators
- Run the daemon on Linux and Raspberry Pi. Ingest flow metadata, sync spaces as soon as a peer connects, keep payloads off this fabric.
- Platform, DevSecOps, AppSec
- Control what agents can touch. Reduce review toil with signed evidence packs and a CI gate.
- Engineering managers and release owners
- Approve faster when every PR carries claims, sources, and unsupported gaps.
- Builders who already use Cursor or VS Code
- PeerWeave is the evidence plane beside those tools, not a replacement IDE — though the site also hosts a browser-local workspace at /app that can attach to a local node.
Technical foundation
Rust core: transactional WeaveFS, libp2p networking, semantic graph with VCIL/PCG, trace v1/v2, Ed25519 signing, CapTokens, and a Tauri desktop app (Spaces, Graph, Ask, Traces, Ports, Mirrors, Modules).
The pw CLI covers identity, spaces, graph, receipts, policy, participants, MCP import, agents, ports, and mirrors. A daemon HTTP gateway on port 8788 is what the Render-ready website talks to. A composite GitHub Action runs receipt-check in CI.
EVRUS is the identity, value, IPFS, and atomic-swap plugin — not a PeerWeave rewrite. The Vault remains the signer. Intra-org receipts do not require EVRUS. PeerWeave is a project of Manticore Technologies, LLC.
Join the alpha
Help prove that a local-first fabric — with receipts when you need them — can feel better than flying blind.