How to archive and verify a specific Agent output version
When an output is accepted, timestamp the exact local file with Agent Proof and store it alongside its .lanveris credential. Later, check that a file matches that version and that the timestamp evidence verifies.
Choose the exact deliverable
Use this when you need to identify the version that existed by a given time, such as the acceptance notes for a workshop signup page. Save the final file before registering it. If the deliverable is a package, assemble and save the package first, then timestamp that exact archive.
- Ask the Agent to register the selected file through Agent Proof. It computes a SHA-256 fingerprint locally and sends the fingerprint and registration metadata to obtain the trusted timestamp. The original file stays local.
- Wait for the timestamp and save the resulting .lanveris credential together with the original. Keep both in storage you control. The Agent uses a local key for registration and needs no account or email.
- To check the version later, provide the original and the matching credential to the verifier. Check the file fingerprint, credential integrity and timestamp evidence before relying on the trusted time.
Try a matching file and a changed copy
Run this example with the Lanveris CLI installed and network access for registration. It creates a temporary folder and a unique synthetic acceptance note, then registers it with an explicit public label. The last verification is expected to fail.
demo_dir="$(mktemp -d)"
cd "$demo_dir"
printf '%s\n' 'Workshop signup — accepted layout v1' "Sample run: $(basename "$demo_dir")" > accepted-notes-v1.txt
lanveris register accepted-notes-v1.txt --desc "Workshop signup acceptance notes, v1" --label "Workshop signup demo" --json
lanveris verify accepted-notes-v1.txt accepted-notes-v1.txt.lanveris
printf '%s\n' 'Workshop signup — changed layout v2' > changed-notes.txt
lanveris verify changed-notes.txt accepted-notes-v1.txt.lanverisUse the credential within its evidence limits
A successful check shows that the file bytes match the registered fingerprint and supports that this version existed by the trusted timestamp. An Agent label is supplied at registration. The credential does not establish copyright, authorship, when the file was first created or whether its contents are true.
An online record can help locate a registration. A full check needs the original file and the matching credential. Any edit after registration may change the fingerprint, so preserve the original bytes and timestamp a new version separately.
Work Sharing transfers selected files and notes to another recipient. It does not automatically timestamp them. Use Agent Proof for the accepted version when you need time evidence, and share it separately if handoff is also required.