What stays on the device
Parsing, extraction, timeline assembly, contradiction checks, basic readiness scoring, offline drafts, and compact receiver packs.
New capture rail
Embed the four decision assets into your own workflow — PFRP, Receiver Packs, ZRDR, and Final Approval / Delivery.
Use the new advisor as a drop-in tool on any page where customers hesitate, dispute, or need to prepare evidence. It gives first value quickly, then routes into packaging and verify.
Capture rails · tools that move readiness and packaging closer to the work
The rails and helper tools behind readiness, packaging, and verification.
Use these downloads to capture evidence earlier, prepare the case faster, verify it cleanly, or embed Vraimony into your own workflow when repeated work justifies it.
Runtime boundary
Free downloads stay local-first. Premium outputs stay server-controlled.
What stays on the server
Receiver-aware premium guidance, per-receiver learning, playbook compilation, final packaging, verify issuance, entitlements, and revocation.
Why this matters
The free layer stays fast and offline-friendly. The premium core stays harder to copy and safer to run without turning the server into a bottleneck.
Common payment and commerce workflows
These capture rails are especially useful when files will be reviewed across Visa card, Shopify, Stripe, Adyen, and Klarna workflows.
The downloads here help teams capture evidence earlier, prepare cleaner bundles, and move structured case data into environments where dispute, payment, and review work already happens.
These are common workflow fits, not claims of official partnership or endorsement.
Featured capture rails
Three tools that move readiness and packaging closer to the source — without leaking the premium core.
01 · Capture rail
Woo / WordPress plugin
Order-aware case creation directly inside WP Admin. Order context, upload triage, and dispute path — without leaving the store.
Get the plugin →02 · Operator helper
Chargeback / return response helper
Offline-ready helper to draft a clean reviewer response from a case bundle. Reduces time-to-send from hours to minutes.
Open response helper →03 · Quick capture
Quick capture & review helper
Capture proof on the spot — photos, notes, timestamps — and send them straight into a reviewer-ready case. No account required on the other side.
Get the capture kit →More tools below
Verification helpers, templates, and partner rails — for deeper workflows.
The tools below are for reviewers, integrators, and technical operators. If you just need to prepare a case faster, the three featured tools above are enough.
🧠
READINESS ENGINE — FREE
Use the readiness engine to find missing proof, contradictions, and weak claims before you package the case.
This is the engine behind the free scan and template routing: it extracts facts, maps claims to evidence, detects contradictions, scores completeness, and challenges weak statements before the live case moves into packaging.
Claim-to-evidence graph
5-type contradictions
Source-linked Decision Sheet
Challenge mode
Missing evidence engine
Reviewer-readiness signals
Free — no account
Evidence Registry
Confidence + uncertainty label per file. Confirmed / partial / uncertain / cannot verify.
Challenge mode
Stress-test weak claims before the case moves into packaging or review.
Missing Evidence
Critical / required / recommended — tiered per dispute type. One action that matters most.
Free tools — start here, no account
Organised by your situation. Zero sign-up. Runs in your browser.
These tools help you organise a case before packaging it. Free downloads stay local-first, browser-heavy, or same-owner by default. They do not ship the premium compiler, per-receiver learning corpus, or final delivery logic.
⚖️ DISPUTE / CLAIM
Case Engine
Build a complete case in one flow
BEST FOR Any active dispute or claim — DNR, SNAD, insurance, chargeback, demurrage
Dispute type → evidence checklist → timeline → exportable summary. Captures before/after time metrics. All client-side.
Dispute Starter Kit
Checklist + folder structure + cover note
CONTAINS Evidence checklist per reason · Timeline sheet · Reviewer email pack · Naming guide
Interactive HTML kit. Select dispute type, tick what you have, see readiness score. Works offline.
Claim Timeline Sheet
CSV / Google Sheets for dispute timelines
CONTAINS Order dates · complaint dates · evidence attached? · reviewer path
Reason-specific timeline CSV for any claim type. Maps directly to ERF fields.
Also available: Reviewer Email Pack · Evidence Naming Guide · Redaction Mini Kit · Example Bundle · WooCommerce Plugin (free scanner) →
All dispute free tools →
🤝 HANDOVER / ACCEPTANCE
Acceptance Starter Template
Delivery proof + sign-off structure
CONTAINS Handover checklist · delivery proof sheet · missing items tracker · sign-off cover note
For project handovers, delivery acceptance, milestone sign-off, and supplier handoffs.
Delivery Proof Sheet
CSV · tracks delivery states over time
CONNECTS TO Handover / Acceptance family · Disputes (cargo / shipping)
Log deliveries, acceptance states, and condition notes. Feeds into ERF record when dispute arises.
📋 REVIEW / QUALIFICATION
Review Request Template
Structured cover note for qualification requests
BEST FOR Vendor qualification · broker evidence request · procurement review · due diligence
Package once and respond to qualification requests without starting over for each reviewer.
Marine Broker Record Sheet
Multi-client CSV · war risk · FM · D&D
CONNECTS TO Review / Qualification · Maritime disputes — broker portfolio management
Track client cases across a broker portfolio. Each row maps to a structured ERF field.
Readiness Worksheet
Free check before packaging anything
BEST FOR Any pain path — know what is missing before investing time in packaging
Run the free readiness check to find gaps. Identifies tier and minimum evidence before you start.
Ready to build the complete case?
Free tools organise your case. The paid one-case record seals it for outside review.
Integrations & plugins — WooCommerce, browser, Word, SDK
Verify records. Embed the widget. Integrate the protocol.
For reviewers confirming record integrity, developers building on ERF, and operators embedding verification into their own tools.
1 — Identify & prepare
Templates + readiness check
2 — Draft in your tool
Word Add-in · WordPress Plugin · CSV
3 — Integrate (developers)
SDK · CLI
4 — Verify & embed
Verify Widget · Browser Extension
5 — Seal & export
Core platform — no download needed
Step 1 and Step 5 happen on the Vraimony platform. Downloads extend Steps 2, 3, and 4.
Developer tools — SDK, CLI, API
Verification, integration, and developer tools.
Category 1 — Environment helpers (bring records to where you work)
Word Add-in
For document-heavy operators
CONNECTS TO TEMPLATE FAMILY
Handover · Qualification — where Word documents are the starting point
Best for: teams preparing vendor review packets, delivery records, or scope-change documentation from Word-based environments.
Not for: replacing the record structure or the review path. Word is the intake surface — the ERF record is the output.
WordPress Plugin
For store & site operators
CONNECTS TO TEMPLATE FAMILY
Disputes + Maritime — chargeback defence, delivery proof, invoice disputes, maritime pack support
Best for: WooCommerce merchants who need to package transaction records, delivery evidence, and dispute timelines from their store data.
Not for: replacing the pack-first buying path or the trust layer. The plugin is a preparation helper — not the product.
CSV Templates
For spreadsheet-first operators
CONNECTS TO TEMPLATE FAMILY
Handover · Disputes — collect records over time, package when ready
Best for: teams that track deliveries, acceptances, or shipment events in spreadsheets. Each CSV column maps directly to an ERF field — no translation step.
Not for: one-time dispute packaging. CSVs are for ongoing record collection that feeds into a future packaging event.
Maritime & Insurance pack templates — Broker workflow layer
Marine Broker Record Sheet
For marine insurance brokers
CONNECTS TO TEMPLATE FAMILY
War Risk · Force Majeure · D&D Disputes — consistent evidence structure across a broker's portfolio
Best for: brokers managing war risk cancellations, cargo claims, or demurrage disputes across multiple clients simultaneously. One CSV per client case, all columns map to ERF fields.
Not for: replacing the pack — the CSV is the intake layer. The review-ready pack is produced from the sealed record.
Maritime Disruption Log
For freight forwarders & logistics ops
CONNECTS TO TEMPLATE FAMILY
Maritime Emergency · GA Notice · Reroute Documentation
Best for: freight forwarders and logistics teams tracking vessel events, port closures, and reroute decisions during active chokepoint disruptions. Each row becomes a timestamped event in the ERF record.
Not for: real-time vessel tracking (AIS). This is a manual log for events you have confirmed — not a live monitoring tool.
War Risk Response Template
48-hour cancellation response
CONNECTS TO TEMPLATE FAMILY
War Risk Response Pack — cancellation notice + vessel record + buyback request
Best for: ship owners and risk managers responding to P&I club cancellation notices within the 48-hour window. Pre-structured fields that map directly to the underwriter's review checklist.
Not for: replacing the marine insurance broker or issuing coverage. This is a documentation intake tool.
Category 2 — Developer tools (integrate ERF into your own systems)
SDK
For developer teams
CONNECTS TO
ERF record model — local helper logic inside your own tools
Best for: developer teams adding local helper logic to internal review tools. Lighter starting point than rebuilding ERF verification from scratch.
Not for: managed integrations, multi-client embedding, or enterprise rollout. Those belong to partner licensing.
SHA256
Check SHA256SUMS.txt before deploying
CLI
For offline & controlled verification
CONNECTS TO
ERF validation — local checking on controlled machines
Best for: local ERF record validation where browser tooling is not available. Terminal environments, air-gapped systems, or automated pipelines.
Not for: reviewer-facing flows where a calmer read-only surface is better. CLI is for internal checking, not external review.
SHA256
Check SHA256SUMS.txt before deploying
Protocol reference
For integrators & standard implementers
CONNECTS TO
ERF spec — full record model documentation and test vectors
Best for: developers who want to understand the ERF record model, validate against test vectors, or build compliant implementations.
Not for: cloning the trust model or building a parallel product surface that mimics Vraimony's core.
Category 3 — Verification helpers (for reviewers and operators confirming records)
Browser Extension
For reviewers & support operators
CONNECTS TO WORKFLOW STEP
Step 4 — Verify: confirm the official review path before forwarding or replying
Best for: repeated checks, forwarding support, and confirming the official review path inside the browser. Paired with the Verify / Scan flow.
Not for: replacing the record, the pack, or the buyer-facing proof path. The extension confirms; it does not build.
Verify Widget
For portals & help centers
CONNECTS TO WORKFLOW STEP
Step 4 — Embed: read-only verification surface inside any site or portal
Best for: embedding a narrow read-only verification surface inside a site, help center, or partner portal. One clean surface instead of screenshots.
Not for: running the pack-building workflow inside the widget. The widget verifies — it does not produce records.
PWA (Progressive Web App)
For mobile & offline access
CONNECTS TO
All families — access records and verification from mobile without native app
Best for: reviewers and operators who need access to records and verification on mobile devices or in low-connectivity environments.
Not for: building new records on mobile (the full builder is desktop-first by design for complex cases).
Which tool connects to which family
Choose the right download for your template family and workflow step.
TOOL
DISPUTES
HANDOVER
QUALIFICATION
MARITIME
Word Add-in
—
✓ Primary
✓ Primary
—
WordPress Plugin
✓ Primary
—
—
—
CSV Templates
✓ Disputes
✓ Primary
—
✓ Broker log
Marine Broker Sheet
✓ Claims
—
—
✓ Primary
SDK
✓
✓
✓
✓ Primary
CLI
✓
✓
✓
✓ Primary
Browser Extension
✓
✓
✓
—
Verify Widget
✓
✓
✓
✓ Embed
The three-step journey
Downloads → Templates → One Case → Verify
STEP 1 — FREE
Prepare with downloads
Use the free case preparation tools above to organise your case, identify gaps, and collect the right evidence before packaging anything.
Free tools ↑STEP 2 — GUIDED
Select a template
Choose the template that matches your situation. Templates structure the intake path — pain path first, family second, depth third.
Browse templates →STEP 3 — PAID
Build the decision-ready case
One case — dispute, claim, handover, or review request — sealed for outside review. $19.99. No subscription.
One case — $19.99 →Security and trust for every download
All downloads are signed, versioned, checksum-verified, and aligned to the local-first runtime boundary.
Official source only
Download only from www.vraimony.com. Avoid reposted ZIPs or typo domains. The official domain is the only verified source.
SHA-256 checksums
Every download includes a SHA-256 checksum. Compare against the official SHA256SUMS.txt before deploying in any integration.
Release metadata
Version, last updated, compatibility, and changelog are published for every release. Check before upgrading in production.
SHA-256 helps detect corruption or tampering in transit. It does not prove official origin by itself — always verify the domain.
Hard boundaries — what downloads cannot do
Downloads extend the local runtime. They do not replace the premium server core.
✕ Downloads cannot seal a record — sealing happens on the Vraimony platform only.
✕ Downloads cannot issue PASS/Declared/Unverified labels — that logic lives in the sealed record.
✕ Downloads cannot replace a legal opinion, compliance certification, or formal audit report.
✕ Downloads do not track users, collect behaviour analytics, or build profiles — by design.
Start with the record, not the download
Identify the problem. Choose the template. Then pick the download that fits your environment.
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.
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.