Proof-of-done agent
“Done” means nothing
without a receipt.
gate turns your definition of done into an executable test that runs against the real artifact. No passing test, no merge — a green that cannot go red is theater.
gate · executable done-tests · fail-closed
Why teams install
What gate earns back
Kills fake-green forever
Every done-test is plant-failure verified: break it, watch it go red, restore.
‹8c1e2fa›Blocks the merge, not morale
Deterministic gates run in CI. No LLM sits in the decision path.
‹b2d48e6›Receipts auditors accept
Sealed packets hash the artifact, the test, and the observed output.
‹77a9c31›How it works
Three steps. No faith required.
01
Declare
State “done” as an executable check against the real artifact.
02
Plant
gate breaks the exact thing the test guards — and demands RED.
03
Seal
Restore, re-run green, and the ProofPacket seals. Anything less: blocked.
Proof band
One packet. Every claim accounted for.
packet rig/gate · done-test 8c1e2fa test build.exit==0 && lcp<2.5s && a11y==0 planted FAIL — gate caught the break, as required restored PASS — artifact hash ‹77a9c31› anchor PASS — claim bound to real command output themis SEALED — task may close
Every gate run emits a packet like this — hash-chained, verifier-signed, and queryable from your own dashboard. How ProofPackets work →
Buyers
Who runs gate
Eng Director
regulated SaaS
QA Lead
payments infrastructure
Solo Founder
shipping daily
Before you install
The obvious objections
Q Why did Team pricing drop priced after a short conversation?
Repriced to match how teams actually use gate — most repos run well under the old assumption. Pro priced after a short conversation now covers org-wide policy bundles and audit export for teams running gates across dozens of repos.
Q “A green that can't go red” sounds like marketing. How do you actually prove it?
Every done-test is plant-failure verified: gate breaks the exact thing the test guards, confirms the test goes RED, restores, and only then re-runs green. That planted failure becomes a permanent regression case, not a one-time demo.
Q What happens when a merge blocks and the test was wrong, not the code?
The sealed packet hashes the artifact, the test definition, and the observed output — so a false block is provable and fixable from the packet alone, without re-litigating what happened in Slack.
Pricing
Start free. Pay when it pays.
Generalist ships today. Domain Expert adds vertical memory + priors. Custom is built to your stack.
Free
Priced after a short conversation
3 gates per repo. Unlimited local runs.
Team
Priced after a short conversation
Unlimited gates, CI enforcement, packet archive.
Pro
Priced after a short conversation
Org-wide policy bundles, audit export, SSO.
Runs well with
