01 · EVIDENCE READINESS
Find the blocker
Describe the case. The scan shows what is missing, what contradicts, and what the reviewer will ask for first.
How the stack works
One front door. Four layers under it.
Vraimony starts with evidence readiness, then moves into packaging, verification, and capture rails only when the case needs them. The free layer stays local-first with compact receiver packs and browser-side scoring; the paid layer moves into the server-controlled compiler, verification issuance, and premium delivery logic. That readiness layer is built on five structural checks: completeness, missing evidence, CE3.0 readiness estimate, contradiction / gap detection, and timeline discipline.
The four layers
Readiness first. Packaging and verify when the case is live. Capture rails when work repeats — without shipping the premium core into the browser.
02 · PACKAGING
Package the live case
Once the case is worth sending, Vraimony turns the timeline, claims, evidence, and ask into a reviewer-ready package.
03 · VERIFICATION
Open the review surface
The reviewer sees summary first, then context and protocol deeper down. Read-only, clean, and easier to trust.
04 · CAPTURE RAILS
Move the work closer to the source
Woo plugin, templates, downloads, and partner rails bring readiness and packaging into the places teams already work.
What this becomes for the reviewer
A structured file — not another attachment chain.
Summary first
What happened. What's asked. How to decide.
Evidence map
Every claim labelled: confirmed, declared, or unverified.
Verify surface
A read-only review path that keeps summary first and technical checks one step deeper.
Honest limits
We organise evidence. The reviewer still decides.
Vraimony does not guarantee outcomes. It is not legal advice. It reduces handling time by turning scattered proof into one reviewer-ready file. That's what it's built to do.
Start with readiness, not with platform sprawl.
Under a minute. No card. Finds the blocker before your team wastes more time on it.
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.
Pre-Flight Rejection Predictor
Predict likely pushback before the case is packaged, then fix the structural blockers first.
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.