v0.1.0-alpha · receipts, HTML verifier, and CI merge gates ship today · desktop installers still unsigned

v0.1.0-alpha · technical early adopters

Prove what the model saw before the PR merges.

PeerWeave attaches a signed work receipt to every AI-assisted change: who acted, what they read, what they claimed, which files moved, and whether you can verify it later — without trusting the model's word.

Build from sourceReceipt workflow

For platform teams and release owners who adopted coding agents faster than they can govern them.

Change receipt

pw.receipt.v1

Actor
Alice · humandid:key:z6Mk…E4rQ
Goal
What merge strategy does WeaveFS use?
Backend
remote · gpt-4o-mini
Claim
LWW CRDT with Lamport timestamps.supported · core/engine/src/crdt.rs
signature valid0 unsupported

sha256:7c9a…e21f · Ed25519 · signer did:key:z6Mk…

What ships in the alpha

  • Signed receiptsExport pw.receipt.v1 from Ask, agent runs, WeaveFS transactions, PR diffs, or imported MCP sessions. Ed25519 + SHA-256.
  • HTML verifierpw receipt html renders a self-contained page reviewers can open with no install. Redacted packs keep the signature.
  • CI merge gateGitHub Action verifies hash, signature, and unsupported-claim policy before merge.
  • Ask, local or remoteGGUF on-device, or OpenAI-compatible / LiteLLM backends behind an llm.remote CapToken.
  • Keys you can encryptDevice keychain uses scrypt + AES-256-GCM when PW_KEYCHAIN_PASSPHRASE is set. P2P node.key is still plaintext.

From Ask to merge gate

The path that matches the governance quickstart.

  1. 01

    Do the work locally

    Ask your space in the desktop app, capture an MCP session, or record a WeaveFS transaction. PeerWeave writes traces, not just chat logs.

  2. 02

    Export a signed receipt

    pw receipt ask <id> (or agent / pr-change) produces the dossier. Optionally render HTML or a redacted pack.

  3. 03

    Gate the merge

    Attach the JSON to the PR. The receipt-check action fails unsigned, tampered, or evidence-free claims before they land on main.

pw receipt ask <event_id> --output receipts/pr-123.json
pw receipt verify receipts/pr-123.json
pw receipt html receipts/pr-123.json --output receipts/pr-123.html

# .github/workflows/receipt-gate.yml
uses: Lucastil2212/peer-weave/.github/actions/receipt-check@main

The fabric under the receipt

Receipts sit on local-first spaces, a provenance graph, and authenticated peer sync. That is why the evidence is yours, not a vendor log.

Spaces + WeaveFS
CRDT-backed folders with transactional commits, recovered FileId state, and authenticated membership. Two-device LAN/WAN QA on the real desktop path is still an alpha gate.
Graph + VCIL
Ask answers are signed trace-v2 bundles. Claims without an evidence path are flagged unsupported and blocked on mirror publish.
Agents, ports, mirrors
Stub agents and capability-scoped ports run today. The full WASM runtime is not shipped. Mirrors redact and optionally anchor locally.

Still in progress

We do not pretend the alpha is finished. These are the live P0/P1 tracks.

  • Two-device desktop LAN/WAN sync validation
  • CLI space watch on transactional WeaveFS
  • Policy evaluation before WeaveFS commit
  • Replicated capability revocations
  • Signed desktop installers and Homebrew tap
  • WASM agent sandbox (stub runtime today)

Full capability list

Stay on the alpha list

Notes when installers land, and when the receipt workflow changes.

Release notes and alpha milestones. No drip sequence.