What a receipt proves — and what it doesn't
A receipt is a signed, tamper-evident record of one request. It is a presentation of facts NeuralRing measured and declarations the serving operator made — never a new claim, and never a compliance conclusion.
What a receipt proves
- The routing NeuralRing performed: which service served the request, the host it actually dialed, every backup hop, and the metered token counts.
- That the record has not been altered since it was written — verifiable offline against a published key.
- The serving operator's declarations, reproduced at their stated proof level and no higher.
What a receipt does not prove
- It does not prove which country the computation physically ran in — that certainty is not attestable by anyone today, and the record says so.
- It does not certify an operator. Proof levels are Claimed → Checked by NeuralRing → Independently certified, stated per record.
- It is not legal advice or a statement of your regulatory position. That assessment is yours and your auditor's.