Evidence Standard: five rules and a five-check script (free sample)
by PaperChaseWebb
From the Evidence Standard: five rules for what your agents may call done (a person owns the standard, every class of work names its proof and its checker, the agent's own account is never proof, people, money, records and releases are checked by a person, nobody says done on their own work), and a read-only script that checks one small file for them.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
evidence-standard-five-rules-and-checks-free-sample.md · 9 KB · direct download, no signup
What you end up with
In a few minutes you can see whether the done in your agents' reports rests on evidence someone else can open, or on the agent's word.
What you get
- Five evidence rules
- evidence_mini.py: five read-only checks on one evidence-lite.json
- One prompt for all four harnesses
- Worked example: 5 findings, then 0
Who it is for
Anyone who wants a quick check of what their agents count as proof before trusting their reports with more.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About five minutes to a first result
Sample prompts, free to use
List every time in this session, or the last one you can see, where you said something was done, fixed, passing, sent or live. For each, write what proof exists that I can open myself right now: a file, an output, a link with the line, or nothing. Mark the ones where the only proof is your own summary. Change nothing. Run evidence_mini.py evidence-lite.json and show me the findings.
The rules and the script are in the file.
Free preview of the file
# Evidence Standard: five rules and a five-check script (free sample)
Version 1.0, 2026-10-29. By PaperChaseWebb. For anyone who lets an agent report work as done, in Grok Bot, Claude Code, Codex, Hermes or a mix, and wants a written rule for what counts as proof before that word gets used. One Markdown file and one Python 3 script, standard library only. The script was tested on its worked example (5 findings, then 0) and on a missing file (exit 2). It was not run inside any agent harness or on a real team's work.
An agent says the tests pass. Sometimes they do. Sometimes the test was a stub, the run was from before the last edit, or no run happened at all and the sentence came from the plan. The fix is not a better prompt. It is a short written standard: for each kind of work, what counts as proof, who checks it, and what is refused. These five rules cover the gaps that cost the most, and the script checks them in one small file.
## Install in one line
Save this page as FREE-SAMPLE.md, then:
```
python3 -c "import re;t=open('FREE-SAMPLE.md').read();open('evidence_mini.py','w').write(re.search(r'~~~python\n(.*?)~~~',t,re.S).group(1))"
python3 evidence_mini.py evidence-lite.json
```
## Five rules
1. **A person owns the standard.** Someone decides what proof means for this team. Not "TBD", and not the agent whose work is being checked.
2. **Every class of work names its proof and its checker.** Code changes, research claims, outreach drafts and releases each get their oTest record
- Date
- Oct 29, 2026
- What was run
- evidence_mini.py on the worked example, a fixed file and a missing file.
- Result
- 5 findings, then 0; exit 2 on a missing file.
- Not run
- The prompt inside a harness.
Copied from this item's dated test notes. What was not run stays in.
Worth knowing
- The sample checks one file against five rules. The five-file standard, proof kinds, refusals, sealed evidence, say and its claim ladder, owner approvals by hash and the fifteen checks are in the full pack.
- On 2026-10-29 evidence_mini.py gave 5 findings on the worked example, then 0 on the fixed file, and exited 2 on a missing file. The prompt was not run inside a harness.
Questions
Does it send anything anywhere?
No. It reads one file and opens no network connection.
What is in the full pack?
The five-file standard with templates, evidence.py that seals evidence and tells your agents what they may say, owner approvals tied to a hash with one use and expiry, fifteen read-only checks with a seeded test standard, a skill file, AGENTS.md snippet and Grok Bot rules block, ten prompts and a failure table. $24.
Details
Version 1.0 · Updated Oct 29, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Evidence Standard: what counts as proof for each kind of agent work, who checks it, and what is refused
Agents report done from the plan as often as from the result. Five plain files write down, for each class of work, the proof that counts, who checks it (never the producer), what is refused and how long proof is kept. Agents log each claim with its evidence, seal it by sha256 and report in the words evidence.py say allows: done, partly done with the gap named, waiting on the owner, or reported, not verified. The agent's own summary is never proof. Fifteen read-only checks run on the standard and the claims ledger.
Rubric Library: five rules and a five-check script (free sample)
From the Rubric Library: five rules for the scoring inside agent workflows (a human owns the library, every rubric has a number, every grade says what it means and what it triggers, people, clients and money go to a person, no profiling people who did not opt in), and a read-only script that checks one rubric file for them.
Agent Readiness Self-Check: score one workflow before you hand it to an AI agent
A free self-check for agencies and small businesses. Name the decision, then score one workflow across eight areas (workflow mapped, data access, approval gates, owner per agent, handoffs, cost tracking, security and vetting, measurement) with an evidence rule, three gate rules and a skeptical pass, and read your band and the next steps it allows. v1.1 starts with the decision the score will change, scores unknowns as unknown, adds rules for conflicting facts and lookalike public records, ties every band to the next steps it allows with the Production Readiness Audit before go-live, makes owner approval concrete (prepared and approved status, a one-reply approval line, decisions the agent must leave open, a done test), adds agent files for Grok Bot, Claude Code, Codex and Hermes, a second worked example (missed call to booked job), a readiness folder with a fifteen-check read-only checker, a front door test with four questions to ask anyone selling you an agent install, and a plain note on how it was tested. Still free.