VERIFY / RECEIPT SCOPE
What a signed receipt proves:
origin and integrity.
Short answer: a signed receipt lets a recipient check that a specific calculation response came from the ScoreCompute service and was not altered after signing, within the scope stated in the receipt. It does not prove that the inputs describe reality, that the model is adequate for every purpose, or that every tool returns a receipt.
What does a receipt cover?
- The tool or Verify domain and the structured request that was evaluated.
- The returned result or verdict, within the model and assumptions recorded with it.
- A signature made with the service key, so a verifier can detect modification and confirm the signing identity for that key.
What verification checks
The downloadable verifier checks the signature against the published key material, checks that the signed payload matches the receipt, and reports the stated scope. A valid signature is evidence about origin and integrity, not about the scientific quality of the claim.
What does a receipt not cover?
- Truth of supplied observations, measurements or premises.
- Accreditation, regulatory approval or a guarantee that a model applies to your use case.
- Tools or responses that are not exposed through Verify. Check the specific tool and receipt before relying on one.
- Availability, uptime or future reproducibility of an identical numerical result.
Practical path
- Open Verify and state an explicit structured claim.
- Inspect the verdict, assumptions and scope before downloading a receipt.
- Verify the receipt locally with the published verifier and key.
- Keep the request, result and scope together; a receipt detached from its scope is easy to misread.
Verify a claim · Evidence and trust boundaries · Receipt standard and offline verifier · Connect an assistant
First published 2 November 2026 · Last updated 2 November 2026