- ❌ Reviewer opens 5 attachments with no order
- ❌ Timeline has to be reconstructed from emails
- ❌ No clear ask — reviewer asks "what do you want?"
- ❌ Delivery proof exists but timestamp is not visible
- ❌ Window closes before clarification arrives
Product logic — plain language
What Vraimony prevents,
detects, improves, and proves.
This page translates the technical architecture into buyer language. What happens when you submit evidence, what rules run, and what the reviewer sees on the other side.
The problem — precisely
The evidence exists. The file is not review-ready.
Most failed disputes are not lost because the underlying facts were wrong. They are lost because the file made it hard for the reviewer to reach a position without asking for more.
- ✓ One URL — reviewer opens, sees everything
- ✓ Timeline anchored to timestamps automatically
- ✓ Clear ask stated at the top of the record
- ✓ Delivery proof: PASS — timestamped, addressed, confirmed
- ✓ Reviewer decides without contacting you
How it works — five steps
From scattered evidence to one link the reviewer acts on.
1
You describe what happened
Parties involved, what was agreed, what is disputed, what you need the reviewer to decide. This becomes the Summary and the Ask at the top of the record.
Your input2
You attach evidence — files are hashed, not uploaded
Invoices, delivery confirmations, communication logs, photos. Each file is hashed client-side — only the hash is submitted. Vraimony never holds your raw document.
Client-side hashing3
The Verdict Stack runs — four independent checks
Structural validity, cryptographic integrity, policy compliance, and reviewer readiness. Each check runs independently. Missing documents are flagged with the exact gap and clearance path.
Automated — takes seconds4
The record is sealed with Ed25519 signature
The complete record — all fields, all hashes — is signed. Any subsequent change breaks the signature. The sealed state is permanent and independently verifiable.
Tamper-evident5
You send one link — reviewer opens, acts, no account needed
The review URL opens a structured page: summary, timeline, evidence with PASS/Declared/Unverified labels, and an acknowledge or request-more button. No login. No app. No email chain.
Read-only · No loginRules that run automatically
What Vraimony checks — and why each check matters.
These are not manual checklists. They run as part of the sealing process on every record.
Overclaim detection
If an evidence item claims high confidence but the underlying degree of verification is low, the record is flagged. This prevents records that look authoritative but are not.
Example: "Delivery confirmed — 95% confident" with no carrier proof attached → flagged as overclaim.
Disallowed phrase blocking
Phrases like "legally binding," "court admissible," or "certified by Vraimony" trigger a policy failure. These phrases cannot appear in any sealed Vraimony record — protecting both the submitter and the reviewer from false claims.
This is not optional. It runs on every seal.
Profile-specific minimum requirements
Different case types have different minimum evidence requirements. A maritime GA case requires a Bill of Lading. A war risk reroute requires an official JWC/BIMCO advisory. A standard dispute requires at least one invoice or delivery proof.
Trying to seal a GA case without a B/L → QUARANTINED with specific clearance path.
One Invalidate — the document that stops the reviewer
Every dispute type has one document that, if missing, makes the record undecidable for a reviewer. Vraimony knows what that document is per case type and flags it before sealing rather than after the reviewer asks.
DNR dispute without delivery proof → SEALED WITH FLAGS. "Invoice or delivery proof missing — reviewer cannot calculate disputed amount."
Carrier Evidence Layer — DELIVERED ≠ case closed
A carrier marking a shipment DELIVERED does not close a DNR or SNAD dispute. It opens a different evidence path. Vraimony applies different rules per delivery status — DELIVERED, ATTEMPTED, IN_TRANSIT, LOST, DAMAGED each require different supporting evidence.
DELIVERED status on a SNAD dispute → carrier proof is high-weight but the dispute is about what arrived, not whether it arrived.
Review paths — not all records need the same depth
The record tells the reviewer exactly how much review is needed.
Every decision-ready case gets a readiness path — computed automatically from the Verdict Stack score, flags, and One Invalidate status.
FAST TRACK
Score ≥ 85 · No flags · No One Invalidate
All evidence items well-documented. Reviewer sees: "This record is well-documented. Review-ready with high confidence."
STANDARD REVIEW
Score 60–84 · No hard failures
Meets minimum evidence standards. Reviewer sees: "This record meets minimum evidence standards. Standard review recommended."
DETAILED REVIEW
Score 40–59 · Partial readiness
Evidence gaps detected. Reviewer sees the specific gaps and is told: "Detailed review recommended before acting."
BLOCKED
One Invalidate triggered OR Score < 40
A critical gap blocks the record. Reviewer and submitter both see the specific gap and the appeal path. Never a silent failure.
Path assignment is automatic. It cannot be overridden by the submitter — only by adding the missing evidence.
What the reviewer sees
One URL. No account. Structured from the first second.
- ✓ Case summary — who, what, when, ask
- ✓ Evidence list — each item labelled PASS / Declared / Unverified
- ✓ Timeline — ordered, dated, anchored
- ✓ Readiness path — Fast Track / Standard / Detailed / Blocked
- ✓ Acknowledge or Request More buttons
- ✓ Verify link — opens independent check
- ✕ No account required
- ✕ No tracking on reviewer
- ✕ No raw files exposed
- ✕ No overclaims passed through
- ✕ No "legally binding" language allowed
See it in practice
Find your exact gaps — free. 90 seconds.
◎ We improve review-readiness. We do not control the reviewer's decision.