Proofpane/releases

**Proofpane is an AI governance platform — the evidence plane for governed AI work.**
Every AI action across coding agents (Claude Code, Cursor, Codex, Hermes, Claude
Desktop), workflow platforms (n8n, UiPath, Power Automate, Zapier, Make) and direct
LLM API calls is policy-gated **in the execution path** (allow / deny / redact /
pause for a human), cost-metered, and recorded in a SHA-256 hash-chained,
tamper-evident audit log that exports as an **Ed25519-signed Evidence Pack** an
auditor verifies **offline** — no vendor account, no trust in us required.
The architecture
**Our claim: governance must happen at runtime, and the record it leaves must be
tamper-evident.** A policy that is checked after the fact governs nothing — by
the time a review reads the log, the secret has left, the payment has cleared,
the decision has shipped. So the gate sits **in the execution path**: the AI
action does not complete until policy has allowed it, redacted it, or paused it
for a human. And a record the operator can quietly edit proves nothing — so
every decision is appended to a **SHA-256 hash-chained, append-only log**
(DB-level immutability trigger, Ed25519 chain-head anchoring) whose export any
auditor can verify **offline, against a published rubric, without trusting the
operator or us**. Runtime enforcement produces the evidence; the evidence does
not depend on anyone's word — including ours.
The architecture is a **public, versioned reference** — not a private rubric:
- **Read it:** proofpane.com/architecture — interactive map + full Markdown spec
- **Cite it:** DOI 10.5281/zenodo.21402331 (CC BY 4.0 — anyone may implement it)
- **Core claim:** evidence must be checkable by parties who trust *neither the operator nor the vendor* — and so must the rubric it is graded against. A standard that can quietly move is not a standard.
The MCP server below is one enforcement point of this architecture: the
on-machine gate for MCP-speaking AI clients.
This repo
This repository mirrors Proofpane's public evidence and documentation and
preserves historical daemon release artifacts. The main Proofpane codebase is
private. The current supported binaries are served from
; the canonical version, digest and
platform-signing record is docs/releases.json.
What you can do with just the download
No account, no pairing, no talking to us first:
- **Run the MCP server** — airgov_daemon mcp serves 13 governed tools
(bash, read, write, edit, glob, grep, listdir, RAG search,
session search, skills) to any MCP client. Local policy gates and DLP
redaction are active: a secret in a file read is masked before the model
sees it, on your machine, with no cloud in the loop.
- **Scan your coverage** — airgov_daemon coverage reads this machine's
AI-client configs and shows which MCP servers route through governance and
which run direct (ungoverned).
- **Check the monitoring switch** — airgov_daemon monitoring-status, and
disable / enable to turn per-app monitoring off and on.
- **Preview usage extraction** — airgov_daemon usage-sync --dry-run shows