Completeness
Do you have the core proof pieces before you start packaging?
Evidence readiness · free · no card · no account
Find the blocker before you waste time packaging the wrong case.
Describe the case below. In under a minute you'll see what's missing, what contradicts, and what to fix first — before you move into packaging or verification.
Readiness engine: 5 structural checks
Runs in your browser first
Use packaging and verify only when the case is live
What this scan actually checks
One readiness verdict built from five structural checks.
Missing evidence
What is still missing — and what should be requested first?
CE3.0 estimate
How structurally close is the file to CE3.0-style continuity signals?
Contradiction / gap detection
Are there unresolved conflicts or silent gaps that reduce trust?
Timeline discipline
Can an outside reviewer follow the decisive event order without guessing?
The result starts with PFRP: a receiver-aware pre-flight view of likely pushback. It is still an integrity/readiness verdict, not an outcome guarantee. CE3.0 is shown only as a structural estimate.
Portable result
The summary above is what you need. The raw result is available if you want to export it.
Show raw scan JSON
Not sure what to do next? The scan results will tell you. Most cases need either a template or One Case.
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.
Receiver-aware decision layer
One capability. Four decision assets.
Vraimony becomes hard to remove when the same receiver-aware layer powers prediction, receiver packs, fast receiver decisions, and final delivery discipline.
Stop bad submissions early
Predict likely rejection before the file is sent, then name the exact structural fixes.
Compile for this receiver
Use official-source rules, preferred order, wording bans, and lane guidance instead of generic templates.
Give the receiver a 30-second surface
Let the receiving side decide faster without starting from an attachment pile.
Send in the right shape
Gate the package before send and route it through the lane the workflow is most likely to accept.
First-day valueFewer avoidable submissions, less back-and-forth, and clearer next steps before anyone pays or reviews.
Why teams keep it onIt helps the sender fix weak files and helps the receiver act faster on the same case.
What turns into the moatOfficial receiver profiles plus learned memory about which fix, lane, and structure actually work with whom.
required evidencepreferred orderrejection patternsdelivery lanewording bansofficial-source deltas
Receiver Profiles are the guidance layer shared across Free Scan, One Case, Viewer, Verify, Downloads, SDK, and plugin rails — so the case is guided by the receiver, not by a generic template.
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.