Question-seal verification certificate
This certificate comes from the recorded evidence. The signature was valid at publication.
Certificate usta-cert-40cccaf5f67743c596cb6c34 · issued 2026-08-14T01:40:02Z
What this certificate answers
Did cand-467 QHASH-AND-PROVENANCE-SEAL satisfy the exact scope, evidence, dependencies, grader, and prohibitions in this reviewed row?
Question hash: c3aa097a0c9962fd70ede82657be894fa8ea16eb58f80b75f1608d1c62544814
Recorded evidence
- reviewed questions carried matching hashes
- 75/75
- legacy unproven runs explicitly ruled
- 68/68
- the missing-hash negative control was detected
- Fired
Trace it to the rail
Recorder run 02c4314c-78ef-4253-8547-31734a547115
Grader SHA-256 fec99a77f0d125e9db83eb235f0f2bb729f42d097d6990e30a2179464d405f27
Public-key SHA-256 f660475c08d4bdb806684722d13760d42737d914358d257a2bab1047b5fc2f60
Download signed JSON · canonical payload · detached signature · public key · verification helper · provenance charter
How to verify
The signature is Ed25519 over the exact bytes in payload.json. Download the four files and run:
python3 verify_certificate.py certificate.json public-key.pem
The helper prints VALID only when the public-key digest and signature both match. Change one byte and it exits non-zero.
What this does not claim
- This certificate covers only the named question and recorded inputs at issuance.
- It does not certify future behavior, legal compliance, or facts absent from the rail.
- A valid signature proves byte integrity and signer control, not the truth of an upstream source.
A certificate for your evidence
Request one signed HTML and JSON certificate from an agreed evidence scope. The request page states the price, the delivery window, and how to cancel.
See terms and request a verification certificate