Audit Receipts
Tamper-evident evidence records that capture every AI-assisted financial decision — what happened, why, and what was decided.
What are Audit Receipts?
An audit receipt is a tamper-evident record that captures every aspect of an AI-assisted financial decision. It is the authoritative evidence document that compliance teams, auditors, and regulators can rely on to understand exactly what happened.
Unlike traditional logs or audit trails, Rosetta audit receipts are designed to be complete, immutable, and independently verifiable. Each receipt contains everything needed to reconstruct and validate the decision process.
Tamper-Evident
Each receipt is cryptographically sealed. Any modification invalidates the seal.
Immutable Chain
Receipts can be linked in chains, providing a complete decision history.
Independently Verifiable
Receipts can be verified by third parties without access to the originating system.
What Evidence is Captured
Each audit receipt captures a comprehensive set of evidence fields designed to provide complete decision transparency.
This is a conceptual example showing the type of evidence fields a receipt would contain. Actual receipt format and fields may differ in the production implementation.
Receipt Structure
Each audit receipt is organized into several sections that together provide a complete picture of the decision event.
Tamper Evidence
Every Rosetta audit receipt includes cryptographic protections that make tampering detectable. While the specific implementation is still being refined, the principle is straightforward:
- Each receipt is hashed and signed at creation time.
- Receipts can be linked in a chain, where each receipt references the previous one.
- Any modification to a receipt invalidates its cryptographic seal.
- Verification can be performed by anyone with access to the receipt and the public verification key.
The audit receipt format, cryptographic implementation, and verification mechanisms are still in development. The examples shown here are conceptual and subject to change. We do not claim production-ready receipt functionality at this stage.