1 — Active access period
During the active access period, the sender can open the case, export outputs, and use the reviewer-facing path normally.
Record lifecycle
How access, export, and verification work over the life of a case.
This page exists to make the lifecycle explicit: what stays available to the sender, what can be exported, and what remains independently verifiable even after the active access period ends.
The short version
2 — Export-first model
Users should export the PDF, PNG, JSON, and any offline review pack they need. Vraimony is designed to avoid lock-in, not create it.
3 — Verification continuity
When a record has a verify reference, integrity checking remains a separate function from editing or account access.
What remains true
Three promises the lifecycle is built around.
- No hidden lock-in: sealed outputs are designed to be exported and carried outside the platform.
- Verification stays separate: the verify layer is not the same thing as editing access.
- Boundaries stay explicit: Vraimony helps preserve review-readiness and integrity signals; it does not promise permanent storage under every commercial mode.
What users should do
Best practice for any serious case.
Export the case outputs
Keep the summary PDF, proof image, record JSON, and any offline review pack in your own matter folder.
Keep the verify reference with the file
Store the verify URL or receipt reference alongside the exports so the integrity layer remains inspectable later.
Need a stronger operational route?
Repeat-case teams, partner operations, and integrations should use the dedicated route so lifecycle expectations are scoped correctly from the start.