The verifier family

Every standalone verifier in the CAIN-42 Top 25 follows the same rules: no CAIN imports, a key you pin, VERIFIED only when everything holds. Each was run on 2026-11-02.

Product	Verifier	Where	Result today
KEYSTONE	`verify_keystone.py`	inside /keystone/bundle	refuses with no pin; all 8 records valid pinned; an edited verdict caught
KEYSTONE	keystone-rerun.py	top level	re-runs every fix: 0 mismatches
Quorum-QaaS	verify_qaas_receipt.py + verify_pbft_qc_bundle.py	top level	NOTARIZED pinned; refuses unpinned (exit 3)
Quorum-QaaS	qaas-forgeries.py	top level	17 of 17 forgeries rejected
NULLIUS	3 verifiers	release folder	36/36 on 3 sites; 2,274 of 2,319 edits refused
NULLIUS	nullius-sweep.py	top level	the sweep itself
BROKER	verifier.py	download	refuses replay, other path, changed body (17/17 suite)
VeriCoding	`recheck.py`	inside each certificate zip	re-checks proofs and counterexamples offline; flipped verdict rejected (14/14 suite)

More verifiers exist in the codebase (18 clean-room cain-*-verify tools in all), but only these are published. Publishing the rest is the owner's decision, because the implementation source stays private.

FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.