What receipt replay can establish
The verifier checks a receipt under a caller-pinned key and compares the covered computation with supplied inputs.
A consumer chooses a trusted issuer key, supplies input data, and passes the receipt to the verifier. The verifier compares input digests and replays the program while retaining individual check outcomes. Authentication is not supplied by a key merely embedded in the same receipt.
The remaining trust question
Consistent replay answers a question about committed inputs and their computation. An issuer can fabricate an input before committing it. A signature then identifies the declaration under a key; it cannot turn that declaration into external truth. Independently obtained inputs strengthen the comparison a consumer can make.
Preserve nullable checks, trust labels, and named refusal reasons. A signed refusal can itself replay consistently without supplying a numerical answer. Use the receipt contract and integration guide to choose the claim your consumer is allowed to display.