We run Correctover — an independent decision table for agent authorization: whether a delegated action exceeds the authorization actually granted, parameter by parameter, not tool by tool. Our verifier has judged 28 push runs, caught and blocked 5, and every number is recomputable from the GitHub Actions API. Yesterday we published it as a GitHub Action, read our own README one more time — and found the reference line we'd written told people to pin @main, which GitHub Actions cannot resolve. The first failure the tool caught when pointed at ourselves was ours.
What the tool actually does (one screen, no claims we can't replay)
- A decision table over delegated authorization — 576 anchors across 6 orthogonal dimensions, nothing hand-tuned (the verdict distribution is a mathematical consequence of the exhaustive cross-product)
- Scope note: the six dimensions are our decomposition, not a discovered constant — the cross-product is exhaustive within them. Disagree with a dimension, and the verdicts downstream of it change. That's the part worth arguing with us about.
- Run as a GitHub Action, one step: the verifier is installed from the published PyPI artifact, never a checkout — so what you get doesn't depend on the state of our repo
- Free tier: single-run verdict + report artifact. The paid tier differs in one thing: whether the output is something you can hand to an auditor
Run it in 10 seconds:
pip install recovery-admission && python -m recovery_admission
Or as a step in any workflow:
- uses: DSHCorrectover/correctover-recovery-admission@v0.1.0
Supply-chain locked, for the people who sign contracts:
- uses: DSHCorrectover/correctover-recovery-admission@c2eaf3b
The part nobody else can copy
For over a month we quoted a number externally: "45 clean-machine self-checks green." Last week, while preparing outreach, I tried to recompute it from any external source — GitHub API, CI logs, anywhere. It could not be recomputed. It was a number that had drifted through our own notes until it looked like evidence.
So we retired it. Not quietly: the correction note is committed to the public repo (0066562), with the replacement counts GitHub-API-auditable as of publish day — 28 push runs, 23 green, 5 red; 110 jobs, 6 skipped (all of them the release workflow's tag gate doing its job, each individually fetchable). A verifier whose core number can't survive its own audit is not a verifier. We'd rather publish our own correction than have someone else find it.
The same day, we found the @main bug. We also wrote a pre-commitment into HONESTY.md: if anyone ever offers to pay for a MISMATCH to become a PASS, the answer is refusal, and the refusal gets published as a case record. We wrote it down now so we don't have to be brave later.
If it breaks on your repo, open an issue — the first real failure tells me more than a hundred green runs.
Top comments (0)