Evidence, made visible

Open the record.
Follow what happened.

A fictional maritime transaction from participant checks to post-delivery follow-up. See the people, document versions, responses and integrity checks together.

Download example PDF ↓Download verification kit ↓View sample JSON ↓

Educational specimen, not a production export. All identities, checks, timestamps, devices and network addresses are fictional. The demo key has no production authority.

Project Horizon / private yacht acquisition

A process someone can follow.

ParticipantRoleRecorded review (fictional)
Alex MorganBuyer representativeDEMO check recorded
DEMO mandate reviewed
Sam LeeSeller representativeDEMO check recorded
DEMO ownership and authority review
Jordan BellBuyer counselDEMO check recorded
DEMO professional credentials reviewed
Taylor ReedMarine surveyorDEMO check recorded
DEMO appointment and credentials reviewed

Documents and exact file fingerprints

sale-agreement-v3.txt

4edfd6afa82f148aa3d97833d093b597308819434f468fa47cdde3053538e95f

translation-fr-v3.txt

a461b8a6f893295ece1822a2c6c45653cb67b5330cb4a3fe2df2c84f155a9b7d

acceptance-addendum-v1.txt

1e8e7586fd40020716415e52dd4b5ec197fb3bed505e4309baa52daf2a6b8421

Chronological process history

Private transaction workspace opened

Jordan Bell · Buyer counsel
Web browser / desktop · IP 192.0.2.10

Technical fingerprint
Event hash: 68854b354795754a8b792de60a3df34c1148a8eb70696895fe6179e8331ebb31
Identity and role/authority checks recorded for invited parties

Jordan Bell · Buyer counsel
Web browser / desktop · IP 192.0.2.10

Technical fingerprint
Event hash: 8f0e80f2ff5b98fabac44b58236fe5c9b20d11a6302f5fa0ba21bf624fa2c3d5
Sale agreement v3 uploaded

Sam Lee · Seller representative
Web browser / desktop · IP 198.51.100.20

Technical fingerprint
Event hash: 00a0036ee6bbe59a9928cc08a3edb8fdf4f7133aac3a045f4e88bbf2c897c657
French translation and attestation linked to sale agreement v3

Jordan Bell · Buyer counsel
Web browser / desktop · IP 192.0.2.10

Technical fingerprint
Event hash: 5b5af1553b830b150011b2c82c562ed0f3020e7b92875af17ba0ecb89286a55d
Sale agreement v3 and linked translation reviewed and acknowledged

Alex Morgan · Buyer representative
Mobile browser / iOS (illustrative user-agent) · IP 203.0.113.30

Technical fingerprint
Event hash: 3cd5c18e16b62b1f3c4c6dc74e422534aff636cff3e8181aab07ec2d9f6a3a07
Condition survey appointment confirmed; UTC time and location recorded

Taylor Reed · Marine surveyor
Web browser / desktop · IP 192.0.2.40

Technical fingerprint
Event hash: 954c56887874ab65102cb1e536994b568227033563c2582cb666ef82d409f8f1
Survey report v1 with photo finding references uploaded

Taylor Reed · Marine surveyor
Web browser / desktop · IP 192.0.2.40

Technical fingerprint
Event hash: f106a37afce565cb9763b3e71bdf2b21970b6e33bdc1120726bb143fa27da562
Legal review records unresolved release-document condition

Jordan Bell · Buyer counsel
Web browser / desktop · IP 192.0.2.10

Technical fingerprint
Event hash: ffe448362f8095f5d320977d3cb5c87d70765da9980ef6174d616b139497109e
Release document and remedy confirmation uploaded

Sam Lee · Seller representative
Web browser / desktop · IP 198.51.100.20

Technical fingerprint
Event hash: 45bb43672419fd96ec99da93d91094081a768e004f7c7376893a3d4c6182c00f
Acceptance addendum v1 signed; credential assertion reference DEMO-A1

Alex Morgan · Buyer representative
Mobile browser / iOS (illustrative user-agent) · IP 203.0.113.30

Technical fingerprint
Event hash: 593babb9b17575ab8223f1f4fb7a32410aced66b75bfc131f4e025508fb56b84
Acceptance addendum v1 countersigned; credential assertion reference DEMO-A2

Sam Lee · Seller representative
Web browser / desktop · IP 198.51.100.20

Technical fingerprint
Event hash: 2d7d6af6267c021980625bbdfb92aaf2efd2370c1fe5bbb115e5f21026030608
Appointed provider confirmation uploaded; no funds processed by platform

Jordan Bell · Buyer counsel
Web browser / desktop · IP 192.0.2.10

Technical fingerprint
Event hash: 492a973755536aa0b5b993689df7be55f12a0218d00c183dc288ad00a52358fe
Delivery protocol v1 acknowledged; open follow-up assigned

Alex Morgan · Buyer representative
Mobile browser / iOS (illustrative user-agent) · IP 203.0.113.30

Technical fingerprint
Event hash: 4bc388cad41be0cb3a4a4bb25af518c58eebbf5a549bf8fd4e7c8c8ee75366e8
Post-delivery report v1 uploaded for buyer review

Taylor Reed · Marine surveyor
Web browser / desktop · IP 192.0.2.40

Technical fingerprint
Event hash: 33bae8018c3db2de8745ceeacf535810b056abe465e2a87f8da6a126a6846ce4
Read the history. Then inspect its integrity.Start with the participants, exact document versions and recorded responses. The technical checks below explain what protected content can be tested and what the specimen cannot prove.
Why the record matters

A file can be edited.
The change must be detectable.

If a record is changed later, a reviewer needs to be able to detect the difference. Compare this original sample with a deliberately altered copy. You do not need to edit anything.

The example below demonstrates a content fingerprint check. Full evidence verification also checks signatures, document links and independent timestamps. Explore the technical download if you need those details.

Original compared with changed copy

A change leaves a difference.

Original sample selected

Choose a comparison to see the result.

See how this applies to your workflow. Free consultation ↗

How a real reviewer checks a real pack

Several checks.
No blind trust in a PDF.

CHECK 01

Document fingerprints

Recompute the included document hashes and compare them with the protected manifest.

CHECK 02

Event sequence and content

Recompute the event hashes and check links and the declared snapshot boundary. This does not reveal events never captured.

CHECK 03

Pack signature and trusted key

Recompute the protected pack digest and verify the Ed25519 signature using an independently trusted signing key, not just a key bundled with the file.

CHECK 04

Independent timestamp

Validate the RFC3161 token, its message imprint and the TSA certificate chain using suitable trust material. Check policy and validity requirements.

CHECK 05

Protected PDF and attachments

Check the rendered artifacts against their signed seal where supported by the pack format. A visually plausible PDF alone is not proof.

CHECK 06

Scope and meaning

Review the format version, exclusions, test flags and captured coverage. Device/user-agent and IP metadata do not by themselves prove which person operated the device.

Integrity is not truth, completeness or a legal outcome. Hashes alone can be recomputed after an edit; trusted signatures and independent timestamp validation are essential additional controls. Key compromise and trust configuration remain material assumptions.

Implementation basis: current local format-4 signing-pack descriptor and offline verifier inspected 28 September 2026. This does not establish production deployment or universal capture of every human action.

Do not just read the promise.
Inspect what supports it.

Bring one process that is difficult to coordinate or document. In a free consultation, we will map the people, steps and records with you and clarify the right configuration. No purchase is required.

Book a free consultation ↗

Evidence across industries

Explore fictional processes for every audience in the preview, from family offices to aircraft acquisitions.

Choose an industry example ↗