The receipt payload
Each planned production response includes model and code hashes, input and output hashes, an attestation reference, timestamp and signature. Together these identify the execution and link it to its inputs and outputs without publishing their plaintext.
Anchor provenance on Arc
The receipt anchorer submits evidence to the contract path. AttestationVerifier and ModelRegistry bind verification to approved measurements and policy. A receipt export gives an auditor a record to inspect independently.
Provenance has limits
A model can run in the expected environment and still produce an incorrect answer. A valid execution receipt is not a proof of truth, model quality or decision suitability.
Inspect a preview receipt
Generate a sample request in the dashboard, inspect its hashes and check the integrity of its local record. Preview receipts explicitly omit real signatures and anchored transactions.