datumline-agent-guard
An independent verifier for AI agent work. An agent says a job is COMPLETED; agent-guard checks the artifacts it claims to have produced and returns a verdict. A completion claim with a missing artifact is reported as FALSE_DONE, not as a pass.
Standard library only, no dependencies. It imports nothing from the runtime it audits, so it can contradict that runtime.
Install
pip install datumline-agent-guard
CLI
agent-guard manifest.json # human-readable receipt
agent-guard manifest.json --json # machine-readable receipt
Exit code is 0 only on VERIFIED; every other verdict exits 1 (bad input exits 2), so it can gate CI or an agent loop.
Manifest
{
"job": "WO-123",
"claimed_status": "COMPLETED",
"artifacts": [
{"type": "file", "path": "out/report.md", "min_bytes": 200, "must_contain": ["## Findings"]},
{"type": "json", "path": "out/feed.json", "required_keys": ["last_marked", "entries"]},
{"type": "url", "url": "https://example.com/feed.json", "status": 200, "must_contain": ["last_marked"]},
{"type": "file", "path": "out/data.parquet", "sha256": "<hex>"}
]
}
Relative paths resolve against the current working directory.
Verdicts
| Verdict | Meaning |
|---|---|
VERIFIED |
every artifact is present and passes every check |
FAILED |
an artifact is present but fails a check, or is absent without a completion claim |
FALSE_DONE |
claimed_status is COMPLETED / COMPLETE / DONE / VERIFIED and at least one artifact is absent |
UNVERIFIABLE |
the manifest asserts no artifacts; fail-closed, never green |
Library
from datumline_agent_guard import verify, verify_file
receipt = verify({"claimed_status": "COMPLETED", "artifacts": [{"type": "file", "path": "out/report.md"}]})
if receipt["verdict"] != "VERIFIED":
raise SystemExit(receipt["verdict"])
GitHub Action
Fail a workflow when an agent's "done" doesn't check out:
- uses: datumline/datumline-agent-guard@v0.2.0
with:
manifest: agent-output/manifest.json # what the agent claims it produced
# fail-on: false-done # only fail on FALSE_DONE (default: anything but VERIFIED)
The step installs this package from the action's own source (no network fetch), writes the receipt to the job summary, sets the verdict and receipt outputs, and exits non-zero unless the verdict is VERIFIED. It needs python3 3.9+ on the runner, which GitHub-hosted runners have.
MCP server
The same verifier as an MCP tool, verify_completion_claim, for Claude, ChatGPT, Copilot, Cursor or any MCP client. Standard library only, stdio transport.
{
"mcpServers": {
"agent-guard": { "command": "uvx", "args": ["datumline-agent-guard"] }
}
}
Or pip install datumline-agent-guard and run datumline-agent-guard (alias agent-guard-mcp). The tool takes manifest (object) or manifest_path (string) and returns the receipt; anything other than "verdict": "VERIFIED" means not done. It reads the files and fetches the URLs the manifest names, and sends nothing anywhere else.
LangChain
pip install "datumline-agent-guard[langchain]"
from datumline_agent_guard.langchain_tool import AgentGuardTool
tool = AgentGuardTool() # name: agent_guard_verify
tool.invoke({"manifest": {"claimed_status": "COMPLETED", "artifacts": [{"type": "file", "path": "out/report.md"}]}})
# -> JSON receipt; anything other than "verdict": "VERIFIED" means not done
Give it to an agent as a tool, or call it yourself before accepting the agent's "done". It also takes manifest_path instead of manifest. It passes LangChain's standard tool tests (langchain-tests). Requires Python 3.10+; the core package needs only 3.9 and has no dependencies.
Related
The same verifier ships inside the free, MIT-licensed Receipted Operator Claude Code plugin, which adds a receipt ledger, truthful statuses and a hook that refuses unreceipted "done". Datumline also publishes paid method kits at datumlinehq.gumroad.com.
License
MIT
Metadata
Release files for datumline-agent-guard 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| datumline_agent_guard-0.2.0.tar.gz | 11.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datumline_agent_guard-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.0 kB
Release files / datumline_agent_guard-0.2.0.tar.gz
| Download URL | datumline_agent_guard-0.2.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4e3da767d55e6cf4ca90aaa0adba9ca0d66efde36f2487bf21af2550312f331
|
|
BLAKE2b-256 checksum How to use checksums |
8b247796b20649df5ec2b0cca3f7a72b09ee47761afa6512a3b2f0fb25e73c5d
|
| 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 Oct 11, 2026.
Transparency logRelease files / datumline_agent_guard-0.2.0-py3-none-any.whl
| Download URL | datumline_agent_guard-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c027b706108cf712b15a86d26f81884f09031b32a1e73e6fbd7312719fe1e88
|
|
BLAKE2b-256 checksum How to use checksums |
a2ecdaa2105985919824d9dde50a0d1c5fd1d0bc9389bdf6fadbd40181a71b52
|
| 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 Oct 11, 2026.
Transparency log