Integrity, not authenticity
HREVN does not claim that a document is true. It proves whether the package changed after sealing.
White Paper · Version 2.0 · May 2026
From documents to verifiable evidence.
The HREVN White Paper explains the cryptographic integrity framework behind verifiable dossiers, evidence bundles and documentary proof that can still be checked later.
In a world where generative AI makes alteration and fabrication easier than ever, the practical question is no longer whether files can be changed. It is whether the recipient can detect it.
Evidence as a dataset
Files are grouped into a structured package with manifest, metadata and a single root hash.
External verification
A third party can check the package with standard free tools, without a private HREVN account.
Critical documentation still relies too heavily on implicit trust
Across inspections, compliance dossiers, professional assessments, training records and policy declarations, the file itself rarely proves whether it changed after creation. HREVN treats documentation as a structured verifiable dataset rather than as a loose set of files.
The framework does not certify that content is true. It makes post-incorporation integrity mathematically checkable by anyone who receives the package.
Honest work without verifiable integrity can still be questioned later
Inspection photographs, AI compliance dossiers, expert reports and annex-heavy submissions often become vulnerable months later, precisely when a dispute, audit or review begins. Without a reliable integrity record, the professional is left defending the work by reputation alone.
That is the gap the white paper addresses: not proving truth, but proving whether a delivered package has changed since it was sealed.
Generative AI changes both the offensive threat and the defensive gap
AI makes it easier to fabricate or alter invoices, images, annexes and reports. But the deeper operational problem is defensive: even genuine documents usually carry no built-in proof that they remained intact after delivery.
HREVN addresses that defensive gap by sealing packages at incorporation so that later edits, replacements or retouching become detectable.
Integrity, not authenticity
Those require human expertise, judgment and sector knowledge.
Those can be tested mathematically through hashes, manifests and root hash consistency.
Evidence as a verifiable object
Original documents, photographs, PDFs, spreadsheets and annexes enter exactly as provided.
Each file receives its own SHA-256 hash and the package receives a manifest and a root hash.
The result is delivered as a human-readable report plus a technical evidence bundle.
Any later modification breaks the recorded hashes and becomes detectable.
One integrity framework, three product lines
AI Responsibility Kit
For companies that already use AI tools but still need literacy, policy, training evidence and a verifiable process record.
White label
For law firms, consultancies and advisors who need to structure client documentation without building their own platform.
Verifiable documentation packages
For inspectors, experts and professionals who need to prove that documents, photographs and annexes were not modified after delivery.
Where the framework applies
- AI compliance and AI literacy documentation
- Law firms and advisory dossiers
- Expert reports and evidence packages
- Construction and site inspections
- Subsidies and EU-fund justification
- Training evidence and attendance records
- GDPR and documentary governance
- Financial-regulation documentation
What the verification layer is built on
- SHA-256 hashing for each file.
- Structured JSON manifest with hash, filename, size, MIME type and timestamp.
- Root hash representing the integrity state of the full package.
- Verification with public tools such as sha256sum and openssl.
- Optional blockchain anchoring for additional timestamp proof.
- Production API and MCP integration surface.
Why the EU AI Act matters here
The white paper connects HREVN to three practical regulatory needs: AI literacy evidence under Article 4, documented risk-management processes under Article 9 and technical-documentation packaging under Article 11.
The claim remains deliberately narrow: HREVN does not certify compliance. It provides verifiable records that specific steps were taken and documented.
Clear limits are part of the trust model
- It does not verify the truthfulness or accuracy of content.
- It does not certify legal compliance with a regulation.
- It does not replace the judgment of a lawyer, auditor, expert or inspector.
- It does not guarantee that content was not altered before incorporation.
- It does not provide legal advice or professional consulting.
Download
Read the full HREVN White Paper v2.0
The full PDF includes the complete narrative, product-line definitions and the precise technical framing behind the HREVN integrity model.