Independent artifact verification
The v2.4.0-rc.1 reference verifier recomputes supplied lifecycle, checkpoint, transparency, witness, anchor, finality, readback, and reconciliation artifacts across thirteen independent dimensions. Core verification is deterministic, offline-first, and makes no hidden network request.
Schemas, test vectors, SDK modules, and the executable reference closure are published for independent recomputation. Optional network collection and readback remain explicit steps outside the core verifier.
Current layered verifier
It cross-binds the supplied evidence history and reports each assurance dimension separately. One passing layer cannot upgrade another dimension or determine factual truth.
Open the transparency reference manifest
Open the strict readback reference manifest
Open the semantic intent binding vectors
Open the semantic intent binding schema
Open the semantic supersession approval schema
corepack pnpm certify:reference-closure
Network and deployment boundary
Optional RPC, hosted, transparency, witness, and readback inputs are selected explicitly outside the core verifier. The repository does not claim a production transparency service, independent witness federation, or deployed tree-head anchor.
Semantic binding reference checks
The semantic reference module derives K when enterprise scope and stable operation-lineage inputs are supplied, validates F and binding hashes, and classifies supplied bindings and predecessor references. It identifies retries, conflicts, forks, unresolved ancestry, and declared supersessions.
A repeated historical fingerprint at a later revision—such as F1 → F2 → F1—is a conflict in the supplied lineage, not a new unique intent. Classification alone does not authorize or prevent an external action.
Guarded dispatch assurance
The separate enterprise-local guardrail commits pre-dispatch evidence before atomically consuming a single-use permit. At or after consumption, recovery is authoritative-readback-only and cannot blindly redispatch.
Under the certified deployment assumptions, one semantic binding revision can cause at most one guarded adapter callback. Complete credential-path mediation, stable normalization, durable atomic storage, and fencing are required for that callback bound. Preventing duplicate downstream external effects additionally requires one-dispatch or downstream-idempotency adapter behavior.
Hosted ChoiceProof and the public verifier never invoke external actions or custody adapter credentials.