Verifiers
Which checks can run, and what they actually establish.
| Implementation | Scope | Current boundary |
|---|---|---|
| Source Python verifiers tested | RequestBinding, ContextSnapshot, GateVerdict conformance vectors at 517ab64 | Passing conformance does not warrant the source verdict. |
| Browser TypeScript port tested | 97 checks on 83 vectors, then a separate site-side gate determination | Run on served fixture bytes. A site-side digest comparison does not replay the source gate. |
| Bound-gate Python verifier CANDIDATE | Separate experimental fixture at bc0ee13: eight checks, one test-domain positive, five negative HOLDs | Copied source, verifier and recorded Python report are pinned on this site. Test authority only; no browser execution of this verifier or historical source-decision replay. |
| Experimental browser evaluator CANDIDATE | Fetches hash-pinned experiment files and recomputes eight checks for one positive and five negative vectors | Runs TypeScript against declared TEST authority; compares its statuses to the recorded Python report. A fresh evaluation is not historical source-decision replay. |
A separate verifier implementation checks syntax and cryptography within its declared trust boundary. Independent source-decision replay would also require the original policy, authority history and invariant material. See explicit non-claims.