oneproof.dev home · where it fits

Where it fits

You already have monitoring, logs and access control. They tell you what the system is doing. oneproof adds the receipts: what it actually did to your documents and your actions — kept in a form someone who does not trust you can check.

Nothing in your stack moves. The three tools attach at three places, and each answers one question a reviewer eventually asks.

Preventonedoor
One door in front of every consequential action. Before the system pays, sends, deletes or approves, the action is checked against your rules — and the decision is written down with the rule that was in force. Shipped, open source, on PyPI.
Detectthe canary
Asks the system secret questions from the outside, on a schedule, and records whether the answers moved. It tells you that something changed and when — a model, an index, a prompt — even when nobody told you. Verification package published 10 September.
Proveonetrace
Every answer comes with its receipts. Each step a document goes through — opened, split, searched, quoted — leaves one, so you can show the exact sentence in the actual file an answer came from, and see the step where it changed. Method published; the code follows.

THE PICTUREA typical AI system, with the evidence plane beside it

Left: the tools you already run, for the people who operate the system. Centre: the stack itself. Right: the receipts, for the person who was not in the room. The dotted line between the two planes is a pointer each way, so a trace can find its receipt and a receipt its trace.

Observability & security existing · for the operator Tracing, spans, metrics Logs, dashboards, alerts Identity & access (IAM) Secrets, network policy Eval & guardrail tools Answers: "What is the system doing?" Live, sampled, retained for a period, written by the operator, read by the operator. Keeps its job. Nothing here is replaced. two-way pointer: span ↔ receipt digest Users & channels chat, copilots, back-office automations, API consumers Application & agent layer agent runtime · orchestration frameworks · low-code flow canvases · prompt assembly plans steps, calls models, retrieves knowledge, invokes tools, produces the answer or the action the agent decides what to do here — and, unaided, writes its own account of what it did Model layer hosted / self-hosted LLMs, embedding models, re-rankers — versions change, often silently a change here shows in the canary Knowledge & data ingestion pipeline: convert → clean → split → embed → index · vector / search store · source documents a change here shows in the canary Tools & external systems tool servers (MCP) · enterprise APIs · payments, tickets, records, email · other agents where actions become consequential and irreversible Platform & infrastructure — cloud, containers, storage, networking, CI/CD PREVENT · onedoor one door in front of every consequential action decides per call, against ratified rules and live state · no policy = denial · irreversible never autonomous · AADP agent → verdict → action Evidence plane oneproof · for the stranger PROVE · onetrace A receipt at every step a document takes — converted, split, retrieved, quoted — so any sentence in an answer traces to its exact place in the original file. method published · code follows DETECT · the canary Probes from outside, on a schedule, with secret questions; every run sealed against a tolerance band fixed before the run. verification package · 10 Sept PREVENT · onedoor Every verdict is evidence: the rule, the version in force, the live state, the outcome — enough to re-derive the decision later. on PyPI · protocol AADP at the IETF Answers: "What did this run do to these bytes, and can someone who doesn't trust us check it?" Unsampled. Durable. Written in a fixed shape. Checkable offline. receipts verdict records DETECT · the canary probes from OUTSIDE the box through the same door a user comes through. It detects THAT something changed, and when — onetrace's receipts say WHERE. probe path sealed runs The stranger with the verifier — outside everything above An auditor, a counterparty, a court, a customer. Holds only the records. Runs one open verifier, offline: no network, no key, no account, no call to us. Every check reports PASS, FAIL, or NOT RUN with a reason. It establishes what the records assert — and says out loud what it could not establish. records handed over oneproof.dev · onedoor v0.7.0 shipped · canary verification package 10 Sept 2026 · onetrace method published, code in preparation · not a certification · anchoring opt-in, off by default · Apache-2.0

The picture scrolls sideways on a small screen. Status as of 7 September 2026; when a status changes, this page is superseded in place, carrying its prior digest.

WHAT IT IS NOTThree things this does not replace

It is not your monitoring — that keeps its job; receipts answer a different question, later, for a different reader. It is not a judge of whether an answer is right — a receipt shows where an answer came from, not that it was correct. And it is not a certificate — it makes records checkable; whether you trust the people who ran the system is still your call, now made with the record in front of you.