Read-only verifier
A bounded helper that reads one artifact, runs the check that artifact names, and reports pass or fail. It has no write tools and no publish tools.
When to use
Use this helper when an artifact names a check and you want a pass or fail report from a reader that cannot change the artifact or publish it.
When not to
Do not give this helper write, delete, publish, or approve tools. Do not ask it to repair the artifact after a failure. Repair is a separate job.
Author-attested
Original teaching specimen written for the Campaign Hub library. Not a transcript of a private run.
# Read-only verifier
This file is a subagent: a bounded helper with a job, tools, and a stop.
## When to use
Dispatch this helper when you have one artifact and that artifact names a check. You want a report that says pass or fail, quotes the observation, and leaves the artifact as it was.
The helper is a subagent: a job, a tool list, and a stop. It is not a second author.
## When not to
Do not dispatch it to fix a failure it just found. The moment it edits, it is no longer a verifier, and the next reader cannot tell the original failure from the repair.
Do not dispatch it to publish, to approve, or to decide that a missing check is "probably fine." No check means fail.
## The specimen
The artifact is this helper card.
```text
name: read-only-verifier
job: Read one artifact and the check that artifact names. Report pass or fail. Quote the observation.
inputs: the artifact, and the check command or steps the artifact itself names
tools_allowed:
- read a file
- list a directory
- run the declared check
tools_forbidden:
- write a file
- delete a file
- publish
- send a message
- approve
- change a kind, a title, or a slug
stop_condition: Emit one report, then stop. Do not repair the artifact. Do not invent a second check when the declared one is missing or red.
report:
result: pass or fail
exit_code: the check's exit code, or empty when no check ran
observation: the line the check printed, or the reason no check ran
repaired: false
missing_check: If the artifact names no check a stranger can run, result is fail, exit_code is empty, and observation is "no check declared". Existence of the artifact is not a pass.
```
The allowed tools match the job. The forbidden list is part of the helper, not a suggestion. A harness that mounts this card and also mounts a write tool has built a different helper.
## How a stranger checks it
A stranger checks the card before mounting it, and checks a run after.
1. Read `tools_forbidden`. Write, delete, publish, send, and approve are on it. If any of those is on `tools_allowed`, the copy fails.
2. Read `stop_condition`. It ends in one report and forbids a repair. A stop that says "fix and re-run" fails.
3. Read `missing_check`. A missing check is fail. A copy that treats a present file as a pass fails.
4. On a live run, give the helper an artifact whose declared check exits 1. The report says fail, quotes the check's line, and the artifact's bytes are unchanged afterward.
The helper is good when the card and the run agree: one report, no write, no publish.
How a stranger checks it
- READ-1 The helper card forbids write, delete, and publish, and it stops after one report with repaired set to false. Read the fenced card. Confirm those tools are forbidden, the stop is a single report, and a missing check is defined as fail rather than as a pass.