Developers.
Build on 
The open verifier under the governance layer. Apache‑2.0, Python 3.11+, experimental, v0.2.1.The open verifier. Apache‑2.0, Python 3.11+.
Quickstart.
- BundleInputs, claimed output, manifest.
- Pinned ruleHeld by the receiving side.
- OK
exit 0The record holds. - REJECT
exit 1The record fails. - ERROR
exit 2Could not conclude.
Python 3.11 or later.
git clone https://github.com/veriker/veriker
cd veriker && pip install -e .
python examples/citation_integrity_minimal/build_bundle.py --out-dir b
veriker --bundle-dir bAll 12 checks pass with exit 0. Change one byte in b and it exits 1.
What a result means.
OK
The claimed output is the deterministic result of the committed inputs under the pinned rule. Not that the rule was right, the inputs true, or anything compliant.
REJECT
A changed byte, a broken rule, an undeclared file, a weaker rule swapped in. The reason code says which.
ERROR
Could not conclude: no anchor, a pack this build cannot run. It never becomes OK.
The rule is yours
Pinned on the receiving side by its hash. A bundle can never ship the code that runs.
AI output is never re-run
Language models are not bit-reproducible. An agent’s reasoning gets a show-its-work receipt: sources used, criteria included and excluded. A person judges the answer.
| Result | Code | Exit | |
|---|---|---|---|
| Approved | OK | 0 | The record holds under your rule. |
| Refused | REJECT | 1 | A byte, a rule or a source failed the check. |
| On hold | ERROR | 2 | Could not conclude. |
OK never says the inputs were true or the rule right. ERROR never becomes OK.
Status. The re-check after the act is what runs today. A gate that holds an agent’s action until its check passes is in build, not yet in the public tree. Elsewhere on the site, Approved, Refused and On hold are OK, REJECT and ERROR.
Build on it.
Every integration is an emitter, a receiver or both.
Exit 0, 1 or 2.
Five steps
- PickA deterministic core.
- RuleThe receiver keeps it.
- BundleFiles and digests.
- RunOffline, your copy.
- ActExit 0, 1 or 2.
Two roles
- EmitterWrites the record.
- ReceiverChecks the record.
Five steps
- PickA deterministic core.
- RuleThe receiver keeps it.
- BundleFiles and digests.
- RunOffline, your copy.
- ActExit 0, 1 or 2.
References.
Apache‑2.0. Python 3.11+. Experimental.
Find out more.
Half an hour on Google Meet, or an email.