Vraimony
Trust boundaries

What Vraimony does, what it does not claim, and why the boundary matters.

Vraimony reduces proof chaos with structured evidence packs, review-first pages, and portable records. It does not claim truth, legal success, payout certainty, or hidden behavioural scoring.

Vraimony does

Package scattered evidence into a cleaner reviewable pack with exportable outputs.

Vraimony checks

Show verification state, timestamps, and record linkage when the class supports it.

Vraimony does not promise

Court acceptance, reimbursement, truth of every sender statement, or investigative certainty.

Keep the model narrow

Why this protects the product and the buyer.

Not a workflow OS

The product should stay export-first and review-first, not become project management or orchestration software.

Not an insurer core or GRC suite

We sell proof packs and anchored reviewable records, not full claims systems or trust-center automation suites.

Why the boundary helps adoption

Templates keep the system simple without weakening the record model.

Template-guided proof building lets first-time users start from a familiar situation instead of a technical schema. The boundary stays the same: package the facts, make review clearer, and avoid pretending to manage the entire workflow or outcome.

Boundary explained visually

The trust model stays narrow on purpose.

Authority classes and boundaries
Authority class explains how much trust structure surrounds the record. It does not promise outcomes.
Outputs from a proof pack
Vraimony promises cleaner packaging and clearer verification states — not court wins, payouts, or hidden behavioural truth.
Controlled trust

The core can be licensed without giving away the whole trust authority.

How licensing works

Partner and enterprise use can license deeper workflow rights while key issuance authority, abuse controls, and parts of the trust model stay under Vraimony control.