Keep the evaluation
inside your boundary.
Local artifacts, locally controlled signing keys, portable receipts. Review the data flow before introducing a managed service or a deployment gate.
What crosses the boundary
| Material | Local workflow |
|---|---|
| Model and dataset | Read and evaluated on the operator’s machine. Not included in the compact receipt. |
| Private signing key | Held by the issuer. Not sent to the browser verifier or billing service. |
| Compact receipt | Exported locally. Shared only when the operator chooses. |
| Public trust key | Distributed through the recipient’s approved trust channel. |
| Payment information | Handled by the payment provider when managed checkout is activated. |
Receipt fields can still disclose model identities, evaluation counts and an issuer name. Treat a receipt as business information. Selective sharing is not anonymity.
The admission boundary
The receipt verifier checks the selected issuer key, signature, schema, validity and commitments. The consuming deployment must also pin the approved policy and load the same artifact bytes that were checked.
A release pipeline can block publication after a failed local evaluation. It does not prevent an operator with unrestricted host access from running a different executable. Keep signing credentials and policy approval separate from untrusted model submissions.
Controls to configure
SDK software inventory · CycloneDX 1.6 · Inventory validation record
Define key ownership, rotation, expiry, approved contract digests, release permissions and recovery procedures. Package the exact runtime and its dependencies for an offline deployment; acceptance must execute inside that target environment.
The optional control plane requires configured authentication, persistent storage, TLS, backups and a verified payment integration. Browser verification itself has no account database, advertising code or file-upload endpoint.
An asynchronous review
Begin with the downloadable technical record and the assurance definitions. The product’s third-party notices remain attached to the relevant components. Commercial terms, a deployment-specific data agreement and any requested tax forms are executed separately; they are not implied by a technical receipt.