WebReceipt turns public commerce journeys into one canonical Deal Contract with timestamped, tamper-evident evidence. It preserves the meaning behind prices, fees and terms, detects wrong-but-valid extraction after a page changes, and makes every repair prove itself before the result is trusted.
- integrity checks
- 11
- per evidence field
- SHA-256
- canonical contract
- 1
- 01ObserveTraverse a public commerce journey and capture every displayed price, fee and term.
- 02CompileFold the observations into one canonical Deal Contract.
- 03VerifyRun deterministic integrity checks and flag wrong-but-valid semantic drift.
- 04HealPropose a repair, verify the preview against invariants, then deploy.
- 05DiffCompare contracts over time to expose changed commercial promises.
The scraper can succeed and still be wrong.
Commerce pages mutate. A selector can keep returning a clean, plausible value after the business meaning behind that value has changed.
Commercial terms drift
A displayed price can stay the same while shipping, taxes, cancellation rules or other mandatory terms change. The distinction has to survive the scrape.
Wrong-but-valid extraction
A redesign can leave a selector returning a perfectly valid number even though that selector now represents a different business meaning.
Screenshots aren’t evidence
A PNG cannot prove when it was taken or whether it was edited. Claims need cryptographic provenance and a verifiable chain of evidence.
A self-healing commerce evidence engine
Every capability is wired into the same canonical Deal Contract, so extraction, verification and diffing all speak one economic language.
Input → transformation → verification → result
Five stages, one contract. Nothing downstream trusts a value that hasn’t survived the checks.
Observe
Traverse a public commerce journey and capture every displayed price, fee and term.
Compile
Fold the observations into one canonical Deal Contract.
Verify
Run deterministic integrity checks and flag wrong-but-valid semantic drift.
Heal
Propose a repair, verify the preview against invariants, then deploy.
Diff
Compare contracts over time to expose changed commercial promises.
Evidence you can verify, not just view
Captured text, source URL, DOM path, journey step and timestamp are hashed with SHA-256. The entire Deal Contract is sealed with its own hash, so tampering with any claim is provable — and detectable.
See the semantic-drift loop in two minutes
Observe a controlled commerce contract, introduce a meaning change, verify the repair, rerun the journey, and diff the promise over time.
