proofheldIdentify
Keep the original intact.
The intended workflow gives each original a document ID, byte count and SHA-256 fingerprint. PDF page counts come from a parser. An optional stamped copy is a separate derivative with its own fingerprint.
The exchange workflow
One exchange.
A lasting record.
Four distinct steps, so a receipt never promises more than the evidence supports.
Beta access: sample workspace only. Fictional files, real file fingerprints. No files are sent, no identity is authenticated, and no receipt is recorded here.
Exchange
Separate the files from the record.
FileSender is the proposed transfer component, hosted on a dedicated computer. Temporary encrypted files would live there, rather than on the public website. Retention and deletion still require end-to-end validation.
Verify
Let each event speak for itself.
Offering a file, completing a download, matching its fingerprint and expressly acknowledging it are different events. The future system must bind these to authenticated participants and reliable event sources.
Keep
Export evidence you can check.
A PDF report and machine-readable manifest should travel together. A separately retained proof would bind a privacy-protected commitment to an independent timestamp. Independent attestations are not enabled yet.
The same update.
For everyone authorized.
Planned event emails will notify the sender, recipient and authorized coordinator. Notices will use a neutral exchange ID and a link to the authorized record, without attachments or sensitive filenames.
Each notice must report its precise event. An email sent, or even delivered, will never be labeled proof that someone received or read the documents.
Planned workflow · email notifications are not enabled