Receipts
We run our own gate
on our own code. At volume.
The cheapest thing in AI tooling is a claim. So here is the volume — ~2,600 adversarially-gated, AI-authored PRs across three production repos (snapshot 2026-07). Counts and methodology only; we never publish diffs or customer content, because the whole point is that we don't have to.
Snapshot as of 2026-07, derived from git history + the evidence store (see methodology). The method is the reproducible part.
The repos, named
Verifiability is the point. We name the codebases rather than describe them generically.
-
sage3c
The origin codebase. ~2,600 merged PRs ran the multi-vendor quorum; 345 cycle docs bind commits to approved plans.
-
cerebe-platform
Fully gated across 62 cycles — a second, independent production codebase on the same gate.
-
dark-factory-platform
The hosted control plane gates itself with the same binary it runs for customers. This site's Trust page transcribes a claims ledger that is gated here.
Methodology (reproducible)
- A "gated PR" is a merged pull request whose merge was gated by the multi-vendor critic quorum, with a per-SHA evidence artifact written to the store. The count is the number of such artifacts / merged PRs carrying a critic check-run — derivable from git history and the evidence store, not asserted.
- A "cycle doc" is a specification file under
docs/roadmap/cycles/that binds commits to an approved plan. The count is a file count. - "Gating itself" means the repo runs the same pinned gate binary — the same aggregation policy and evidence shape — that the hosted runtime runs for customers.
- What we never publish: diffs, source, or any customer content. Receipts are counts + method. The evidence that a change was gated does not require exposing the change.
Get Started
Bring your own sample.
Pick a merged PR in a dogfood repo; we'll show you its complete evidence bundle. The demo is the receipt.