plan-auditor
I built this because I got tired of AI saying "done" when it wasn't.
You know the drill: you ask an AI coding assistant to build something, it says "all tests pass," and then you find out it never actually ran them. Or it ran them once, failed, and "fixed" the test to make it green.
plan-auditor forces the AI to prove its work. Not with words-with actual command output, file hashes, and deterministic checks that can't be faked.
How it works
- You describe what you want built
- plan-auditor turns that into explicit, machine-checkable requirements
- The AI implements each step and must provide real evidence (command output, file contents, test results)
- A separate auditor process verifies everything independently
- Only when every check passes does it say "done"
No more "trust me bro" from language models.
Quick start
pip install plan-auditor
# or
npx plan-auditor
Then just tell your AI: "Use plan-auditor for this task." It handles the rest.
Why I made this
I was working on a scientific computing project and an AI assistant kept insisting it had fixed a bug. It hadn't. Three times. I wasted hours before I realized the "fix" was just the AI editing its own test output.
So I built a system where the AI can't lie. Where "done" means "here's the terminal output proving it." Where the plan is sealed cryptographically and any tampering breaks the verification.
It's not perfect. But it's a hell of a lot better than taking an LLM's word for anything.
Docs
- Architecture - how the pieces fit together
- Formal Planning - the STRIPS/PDDL verification stuff
- Threat Model - what it can and can't protect against
License
MIT. Do whatever you want with it.
Metadata
Release files for plan-auditor 2.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| plan_auditor-2.4.1.tar.gz | 154.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| plan_auditor-2.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 275.9 kB
Release files / plan_auditor-2.4.1.tar.gz
| Download URL | plan_auditor-2.4.1.tar.gz |
|---|---|
| Size | 154.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab8bcdcaaba91252d3b58118ecff9fa23ab777cb2e4f2505454426d5bce221de
|
|
BLAKE2b-256 checksum How to use checksums |
b2f8eadffd55b6c5a474e9045778af4e28d305266cf8c707161cb963b9d4116d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logRelease files / plan_auditor-2.4.1-py3-none-any.whl
| Download URL | plan_auditor-2.4.1-py3-none-any.whl |
|---|---|
| Size | 120.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cede66ec01789ab3bf6af6ad0c0845d504f2329c5e0276ceefba98dd658abf87
|
|
BLAKE2b-256 checksum How to use checksums |
6fbb04e436723d667db3f87064740b5b055c98028699ae6dacc832ab6ba68a9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency log