Edited photographs
HREVN Evidence Bundle
When AI can alter any file, the original evidence matters
HREVN Evidence Bundle turns documents, images and annexes into a verifiable package with hashes, manifests, root hash, QR and blockchain anchoring.
Artificial intelligence is changing how documents, images and files are created, modified and presented. The problem is not only detecting whether something is fake. The key problem is being able to prove what the original documentary package was.
AI does not only create content. It can also alter evidence.
Today an image, invoice, PDF, screenshot or annex can be modified with tools that are becoming more accessible every month. In a professional setting, that introduces a new doubt: if something is challenged later, how do you prove which file was the original one?
Replaced PDFs
Altered screenshots
Manipulated invoices
Changed annexes
Revised spreadsheets
Replaced supporting files
If someone changes a file later, how do you prove it?
Signing a PDF may be enough to protect that specific document. But many professional dossiers are not a single file: they include annexes, photos, spreadsheets, technical documents, screenshots and versions.
HREVN is designed to protect the integrity of the full set.
A professional dossier is not always a single PDF. It may include photographs, annexes, spreadsheets, reports, screenshots, supporting documents and versions. HREVN Evidence Bundle makes the full set verifiable.
HREVN Evidence Bundle: documents turned into verifiable evidence
HREVN Evidence Bundle takes a set of files and generates a verifiable package: dossier index, individual hashes, package root hash, verification instructions, QR and blockchain anchoring.
- Each file receives its own digital fingerprint.
- The package is indexed in a manifest.
- The full set is sealed with a root hash.
- A verification QR or URL is generated.
- Blockchain anchoring is attached.
- A third party can later check whether the package still matches.
HREVN does not tell you whether an image is true. It helps you prove that this image, this document and those annexes are exactly the files that were in the original package.
What can be part of the package
PDF report
Contracts
Photographs
Annexes
Spreadsheets
Screenshots
Technical documents
Supporting files
Metadata
Verification instructions
Verifiable by third parties, without proprietary software
The goal is not for the recipient to trust HREVN blindly. The goal is for them to be able to check the integrity of the package they received.
- Which files were included in the package.
- Which hash each file had.
- What the package root hash was.
- Whether any file changed later.
- Which version was issued.
- When the package was generated.
- Which QR or record identifies the delivery.
If a photograph changes, the hash changes
If someone extracts a photograph from the package, edits it and puts it back in, the fingerprint no longer matches. Verification can show that this is not the same file that was part of the original package.
hash A
hash B
The package is no longer exactly the same.
HREVN verifies integrity, not absolute material truth
- Documentary package integrity
- Files included
- Individual hashes
- Package version
- Issue date
- Root hash
- Verification QR
- Blockchain anchoring
- Whether the package changed later
- Automatically detect every deepfake
- Certify that the content is true
- Replace digital signatures
- Replace expert witnesses
- Replace lawyers
- Replace auditors
- Guarantee absolute legal evidentiary value
For any professional documentation that should not change after delivery
Technical reports
Professional dossiers
Construction documentation
Grant documentation
Deliverables sent to third parties
Reports with annexes
Photos and evidence sets
Documentation for review
Packages sent to clients, law firms, auditors or public bodies
Next step
Before someone questions a document, lock in the original package
Request an HREVN Evidence Bundle sample and see how a verifiable documentary package is structured.