Every job leaves a receipt. Every hardware claim is signed.
A compute merchant on the Visa CLI mints one hive-vcr-1 receipt per job. Hardware class, region, isolation class, and duration are co-signed so the workload's provenance is a primitive, not a billing line.
The fields the operator co-signs before this call returns.
Every field below is co-signed by the operator with ML-DSA-65 and countersigned by Hive. Absence is not a default. Absence is a verification failure. The merchant cannot return the call's result without the receipt; the receipt cannot exist without these fields.
Compute · GPU · attestation fields
Three places this category needs a receipt yesterday.
Sovereign compute attestation
When a regulator asks where a training run ran, the receipt log answers. Region and hardware are signed at job start, not inferred from a bill.
Confidential-VM workloads
Isolation_class of confidential-vm, co-signed, gives a regulated caller cryptographic proof the workload ran inside a hardware enclave.
Cross-tenant billing audits
The duration_seconds field is what billing reconciles against. Disputes collapse to a verifier run, not a support ticket.
One endpoint. One envelope. No Hive dependency in your inference path.
A compute · gpu operator adopts hive-vcr-1 by appending the receipt envelope to the response and exposing a public verification key. Hive's countersignature is a sidecar; it does not sit on the critical path. If Hive disappears, the operator's receipts remain verifiable against the operator's own key.