Provenance receipts: how a syndicated review proves where it came from
Every REVEX review carries an immutable content hash, its original source, verification status, and a revision log. Shoppers can open the receipt from the storefront.
By REVEX Engineering, Platform team

Borrowed trust needs a paper trail
A review shown on a retailer''s product page was collected somewhere else. That is fine — as long as the shopper can see where, and the retailer can prove it later.
What a receipt contains
- Original source organization and collection system
- Verified-purchase status and how it was verified
- Original submission timestamp, separate from the import timestamp
- Content hash of the review body at import
- Full revision log: every edit, redaction, and moderation action
The guard
A database trigger blocks edits to the fields that define a review''s identity. Ratings and bodies cannot be quietly rewritten after syndication; a redaction is recorded as a redaction, with a reason.
Why it is public
The receipt is reachable from the storefront widget. Shoppers who care can click through and see the chain. Most will not — but the ones who do are exactly the ones deciding whether to trust the page.


