Record
The structured container: parties, timeline, files, context, and the ask. Everything the reviewer needs to reach a position.
ERF — Record Model & Reference Layer
The record model behind Vraimony.
ERF (Evidence Receipt Format) defines how outside-review records are structured, signed, and exported. This page is for developers, integrators, and anyone who wants to understand what a Vraimony record actually contains.
What ERF defines
Four objects. One clear reading path for the reviewer.
Status taxonomy
PASS — confirmed via verifiable mechanism.
Declared — stated by sender, in the record but not independently confirmed.
Unverified — exists but not yet confirmed.
No fake certainty. The reviewer sees exactly what level of confirmation exists for each element.
Receiver path
ACK (acknowledge), MER (request amendment), or download. The reviewer acts without creating an account or installing anything.
Export format
PDF + PNG + JSON. Universally readable. No Vraimony tool required to open the exported record.
Integrity layer
ed25519-signed. Tamper-evident. Offline-verifiable.
Signing
Records are signed with ed25519. The signature covers the canonical JSON payload. Key ID is included in the receipt.
Content hash
SHA-256 hash of record contents. Included in the receipt JSON. Verifiable offline without contacting Vraimony.
Seal levels
L1_PROVISIONAL (draft), L2_STANDARD (sealed), L3_FINAL (finalized). Explicit — no silent downgrades.
Backward-compat contract
Endpoints remain stable. Receipt JSON shape is additive-only. No breaking changes without explicit versioning.
Test vectors
Nine deterministic scenarios. Download and validate locally.
Static JSON files. No tracking. No remote scripts. Use them to verify your integration or test the validator offline.
Valid records
Invalid records
Sector vectors
Tools and downloads
Validator, SDK, CLI, and integration helpers.
ERF Validator
Offline-first. Validate any ERF record against the schema without sending data to a server.
SDK
For developer teams integrating ERF record creation into their own workflows or products.
CLI
Terminal-based offline verification and local record checking for controlled environments.
WordPress Plugin
Keep proof helpers close to WooCommerce and WordPress workflows.
Word Add-in
For document-heavy teams preparing cases from Word-based environments.
Browser Extension
For reviewers and operators confirming the official path inside the browser.
Honest boundaries
What ERF does not claim.
✕ Not a legal standard or court-certified format.
✕ Not a compliance certification or formal audit report.
✕ Integrity-only packaging. We do not validate the truthfulness of what is submitted.
✕ No official affiliation with any regulatory or standards body.
We package facts for outside review. We do not decide truth.
Integration interest
Want to embed ERF records in your own product or workflow?
SDK, API access, and integration paths are available. Talk to us before building — we can help you avoid the common friction points.