01
What the record contains.
The session identifier, target application, recorder version and mode describe the context. The event chain preserves the captured order. The completion data states the session status and an optional file binding. Synthetic data is explicitly labelled.
02
What file binding establishes.
SHA-256 and the byte count refer to the selected file. Verify compares those exact bytes. A revised version needs its own association. The comparison confirms file identity, not that the session produced the file.
03
How to share the evidence.
Export the PDF evidence document in Writer and review its metadata. JSON is also available for technical workflows. For a file comparison, the recipient also needs the bound version. The browser checks the record; the complete PDF presentation and PDF/CMS signature have a separate verification scope.
04
How verification works.
Verify validates the humanproof/1 format, the signature and the event chain. File comparison and an independent key fingerprint add separate checks. The findings are displayed individually so you can assess them alongside the rules for your submission.
