Pre-Flight Rejection Predictor
Predict likely pushback before the case is packaged, then fix the structural blockers first.
Build on ERF (Open Receipt Standard)
Vraimony is designed as a portable standard layer with a split architecture: free local runtimes, compact receiver packs, and offline helpers on the client; compiler, signing, entitlements, and premium issuance on the server. Verification stays free.
Runtime split
Embed the runtime locally. Keep Receiver Packs, Final Approval, and premium compilation on your server.
- Use compact receiver packs, IndexedDB cache, receiver-aware local guidance, and offline helpers in the browser.
- Use signed manifests and delta updates for local pack delivery.
- Keep rule compilation, weight generation, entitlements, and premium outputs on the server.
Build for common review environments
ERF and the local-first runtime are especially useful when your product must feed cleaner files into Visa card, Shopify, Stripe, Adyen, and Klarna workflows.
Use the SDK, pack runtime, and verify layer to embed readiness and packaging without shipping the premium compiler or learning layer in the public bundle.
Use “works across” language. Do not imply official certification or endorsement.
Discovery
Use the well‑known discovery document to locate endpoints and registries:
GET /.well-known/verify (legacy aliases remain available)
Legacy discovery aliases remain available for compatibility, but the public brand is Vraimony.
This does not prove identity or legal admissibility.
Core endpoints
New runtime endpoints expose signed pack manifests and architecture boundaries so integrators can keep local helpers fast without shipping the premium compiler in the browser.
GET /v1/public/runtime-architectureGET /v1/public/receiver-packs/manifestGET /v1/public/receiver-packs/:family
- ERF object: GET /v1/erf/:receipt_id (Content‑Type: application/erf+json)
- Verify: GET /v1/verify/:receipt_id
- Redirect: GET /r/:receipt_id
- Registries: GET /v1/registry/*
Reality Audit: integrity only (tamper‑evident). This does not prove identity or legal admissibility.
Conformance
Official domains and verification guidance
- Official domain: www.vraimony.com
- Official contact: contact@vraimony.com
- Do not trust typo domains, mirrors, reposted ZIPs, or screenshots alone.
- SHA256 checks file integrity only. It does not prove official origin by itself.
- Official status depends on the source/channel, package name, checksum, signing wording, and final signature when available.
- Report fake verify pages, fake mirrors, or fake packages to contact@vraimony.com.
Run the conformance vectors to validate your implementation:
node conformance/run.js
This does not prove identity or legal admissibility.
Platform Gift Kit
Free adoption for platforms: link card unfurl, iframe widget, and offline Paste‑ERF verification.
No remote scripts. No tracking.
Court Mode outputs
Court-friendly outputs (no ZIP): one-page Evidence Sheet + Proof Card PNG + copyable Structured data export (JSON).
Integrity only. No identity proof.
Widget (iframe-only)
We support iframe‑only embedding (no remote scripts). Use the widget configurator:
This does not prove identity or legal admissibility.
Partner program
Want a “Conformant” badge for your platform? See the partner rules and checks:
This does not prove identity or legal admissibility.
Signed local runtime
Free/local-first tools now rely on signed local receiver packs that can be checked in-browser before premium server guidance takes over.
Receiver packs now carry more than IDs
Signed local receiver packs now include lane recipes, structured packaging rules, weak-claim hints, and compact official-source deltas. Free runtime stays local-first; premium compilation and learning stay on the server.
Receiver-aware approval
Official-source deltas now feed the final approval gate
Signed receiver packs now carry source-grounded deltas, lane recipes, and final-approval rules. Free stays local-first. Premium packaging still stays server-controlled.
Core decision assets
Everything here should map back to four assets only.
Receiver Packs
Signed, receiver-specific guidance packs: required evidence, preferred order, rejection patterns, delivery lane, wording bans, and official-source deltas.
Zero-Read Decision Receipt
Give the receiving side a summary they can act on fast, without reading the whole file first.
Final Approval + Delivery
Apply receiver-aware approval rules, then send the file through the lane that fits that workflow best.
Receiver Profiles
Receiver Profiles are the guidance layer across scan, packaging, verify, and rails.
- Required evidenceWhat the receiver expects before the file feels complete enough to review.
- Preferred orderHow the file should be read first: summary, timeline, proof, policy, then the ask.
- Rejection patternsThe structural reasons this type of receiver most often pushes a case back.
- Delivery laneThe lane that fits best: portal, verify-first, summary PDF, or supporting attachments after review.
- Wording bansWeak or noisy phrasing that makes the file harder to trust or easier to dismiss.
- Official-source deltasCompact updates distilled from the receiver's own public guidance, rules, or dispute documentation.
Vraimony uses the same Receiver Profiles layer across Free Scan, One Case, Viewer, Verify, Downloads, SDK, and plugin rails — so the file is guided by the receiver, not by a generic template.
Decision layer fit
Not another tool. A receiver-aware decision layer.
Use the same four assets everywhere: PFRP, Receiver Packs, ZRDR, and Final Approval / Delivery. The plugin, SDK, verify surface, and templates are rails around that layer — not the layer itself.
PFRPReceiver PacksZRDRFinal Approval / Delivery
Receiver OS
Receiver-aware decision layer
The same layer powers PFRP, Receiver Packs, ZRDR, and Final Approval / Delivery — so this workflow stays guided by how the receiver actually reviews, not by a generic packet template.