About
A control plane for work you cannot take on faith.
Teams adopted AI coding tools faster than they can govern them. PeerWeave is the local-first evidence layer that answers: who acted, under whose authority, with what context, and can you prove it later?
The gap
Agents lose context between sessions, overstep authority, and leave reviewers staring at a diff with no record of what the model saw. Existing tools give you output. They do not give you accountability you can attach to a PR.
What we ship in v0.1.0-alpha
- pw.receipt.v1 dossiers for Ask, agents, WeaveFS, PR changes, and MCP imports
- Self-contained HTML verifier and redacted evidence packs
- GitHub Action merge gate and a VS Code receipt explorer
- VCIL answer bundles, participant registry, encrypted keychain, remote or local LLM
- Authenticated Space sync and signed cold-join snapshots
Honest gaps: agent runtime is still a stub, desktop installers are unsigned, two-device WAN QA is an open alpha gate, and policy does not yet block WeaveFS commits — only receipt verification.
Principles
Evidence over transcripts
A unit of autonomous work should leave a verifiable receipt, not only a chat log.
Local-first
Spaces, graph memory, traces, and signing keys live on your hardware. Cloud is optional.
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.
Who it is for
The first wedge is software teams shipping AI-assisted changes who need proof, not promises. Later wedges (SecOps evidence, private engineering intelligence) reuse the same primitives.
- 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.
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 composite GitHub Action runs receipt-check in CI.
EVRUS is optional for cross-org rights and anchoring. It is not required for the intra-org governance wedge. PeerWeave is a project of Manticore Technologies, LLC.
Join the alpha
Help prove that local-first, receipt-backed AI governance can feel better than flying blind.