Compliance, demonstrated and not declared
Every issued document carries a fingerprint recomputed on every read, and a seal a third party can check without an account.
The problem
Saying a document is authentic is not enough
A banker, a notary or a buyer who receives a charges statement has no way to know whether it was edited. They have to call the agent, who confirms verbally. That is precisely what document compliance is supposed to avoid.
Demonstration
Verify a document, including an edited one
The fingerprint is recomputed at the moment of the check: the verdict is never stored data.
Verifying a document
The fingerprint printed on the document is compared with the one recomputed now.
Charges statement — 2026 financial year
QR · 8f2c-41e9- Fingerprint recorded on upload
- a7f3c1e0 9b42d85f 6c0a1734 e2b98d51
- Fingerprint recomputed just now
- —
The verdict is never stored data: it is a calculation that has just happened. The fingerprints shown are truncated for readability.
What the module actually does
Fingerprint on upload
Digital fingerprint computed at registration, on the final file.
Re-checked on every read
A file altered on disk is never served.
Public seal
A token and QR code printed on the document let a third party check without an account.
Five-year retention
Documents are kept and handed over to the next agent, as the decree requires.
Who it is for
The shortest path is still seeing it run
Thirty minutes, a demonstration building, and your real cases entered in front of you.