Plain-language answers for buyers and reviewers.
Start here if you want a simpler explanation of proof readiness, templates, ERF, what is self-serve, what needs guided access, and what read-only verification does.
What is Vraimony in one sentence?
Turn scattered operational records into a reusable, review-ready proof path.
Why does Vraimony call itself a quiet trust layer?
Because the product should clarify the proof path without shouting, overclaiming, or turning every workflow into a giant platform rollout. The job is calmer structure, cleaner review, and better handoff under pressure.
What are the four core operating patterns?
Delay, change, acceptance, and dispute. Vraimony treats these as recurring proof jobs, then applies sector wrappers such as shipping, creator delivery, procurement, education, or partner rollout only when they change the review path.
What does proof reuse mean?
It means you create one cleaner proof path and reuse it across sender review, receiver review, escalation, third-party review, or reply follow-up without rebuilding the same context each time.
Why is third-party review part of the story?
Because many operational problems are not solved by proving something once. They are solved by making the same proof path easier for the next reviewer, partner, insurer, auditor, buyer, or escalation handler to inspect.
Is Vraimony a compliance platform or a signature platform?
No. Vraimony is not a full compliance suite, a workflow OS, or a signature platform replacement. It focuses on proof packaging, cleaner handoff, and read-only verification.
Do I need Google Sheets to use Vraimony?
No. Google Sheets is optional. The templates layer supports Google Sheets as a familiar entry surface, but CSV is the portable path and Vraimony does not depend on Google.
Can I use CSV instead?
Yes. CSV is the canonical portable path. It is the preferred escape hatch, the replaceable source format, and the tool-independent starting point for the templates layer.
Does Vraimony depend on Google?
No. Vraimony does not require Google account access, a Google integration, or a Google add-on. You can work through CSV and keep the source tool replaceable later.
Do I need to connect my Google account?
No. There is no OAuth or Google account connection in this templates phase. The path is manual on purpose: use a template, fill it, export CSV, and prepare it for packaging in Vraimony.
Are templates free?
Yes. The launch templates are free. Paid value begins when a template-led workflow becomes a Vraimony pack path with structured outputs, packaging, and verification support.
What starts the record?
Usually a familiar operational record: a sheet, form, delivery log, handover entry, revision record, or submission line. Vraimony starts from that record path rather than forcing a new heavy system first.
What happens after I fill the template?
You keep the sheet as your working record, export CSV when needed, and then use that workflow as a proof-ready input path for Vraimony packaging. The sheet is the starting surface, not the final output layer.
What do I receive after packaging?
The standard output order is: summary sheet, proof card, structured bundle, structured data export (JSON / ERF), and a read-only verification path.
What does Vraimony carry forward?
Vraimony carries the packaging layer forward: cleaner structure, portable outputs, bounded verification, and a review-ready path that is easier to inspect than scattered records alone.
What does Vraimony add beyond the template?
Vraimony adds packaging, verification, structured outputs, and a cleaner review path. That usually means a summary sheet, proof card, structured bundle, structured data export, and a read-only verification path.
Is verification sender-initiated?
Yes, in the current public path. The sender packages the records first, then shares a read-only verification path before asking others to change workflow behavior.
Do receivers need an account?
No. The current public phase keeps receiver interaction lightweight. Read-only verification does not require a receiver account.
What can happen after verify?
The next step can stay simple: received, accepted, correction needed, or missing item. That is enough for many early handoff and review situations without building a heavy receiver workflow first.
What does proof readiness mean in practice?
It means preparing a cleaner proof path before you are under pressure. Instead of rebuilding the story from screenshots, files, and emails later, you package records earlier into a structured bundle that is easier to review and share.
What does read-only verification mean?
It helps people inspect integrity and reference state without turning verification into a promise about identity, truth, delivery, legal admissibility, or business outcomes.
Which packs can I buy now?
The clearest direct-buy path is One Case. Creator, student, shipping, and institutional lanes remain available as secondary self-serve paths when the main wedge is not the right fit.
Which packs require guided access?
Evidence-Ready TPRM, Integrator Partnership Kit, and higher-risk requests such as healthcare or legal overlays stay guided because they are more rollout-sensitive or support-heavy.
What support is included?
Self-serve packs are documentation-led and include best-effort email support only. They do not include onboarding, custom setup, workflow redesign, or managed rollout by default.
What is ERF?
Vraimony ERF (Evidence Record Format) is an open, structured format for packaging, exchanging, and verifying operational evidence records in a clear, reusable way.
Why does ERF matter?
ERF turns ordinary records into portable, review-ready evidence outputs. It makes the output layer easier to inspect, move, and reuse across workflows.
Is ERF only for Vraimony?
No. ERF is positioned as open, portable, and technically neutral. Vraimony powers the packaging and signature story around it, but the format idea is not meant to trap the workflow inside one product surface.
Does ERF create lock-in?
No. ERF is meant to support portability, not trap it. CSV remains portable at entry, JSON / ERF supports structured export later, and the verification path stays bounded and read-only.
How does ERF relate to JSON export?
JSON is the practical structured export surface. ERF is the evidence record format layer that gives that JSON output cleaner meaning, version discipline, and repeatable packaging rules.
How does ERF relate to proof cards, summary sheets, and structured bundles?
Those are reviewer-facing outputs in the proof path. ERF sits behind the structured data side of that path, helping the record set stay portable, inspectable, and easier to reuse.
What does ERF carry in this flow?
ERF carries the structured evidence layer forward from the familiar record surface into structured export, reusable package meaning, and bounded verification support.
What does “Powered by Vraimony” mean on ERF-related outputs?
It is a calm origin signature. It signals where the structured output path was packaged without implying exclusivity, legal acceptance, or lock-in.
Does ERF guarantee acceptance or legal outcome?
No. ERF helps package and verify records more clearly. It does not guarantee acceptance, admissibility, a dispute win, or any legal or business outcome.
Do these snippets create legal obligations automatically?
No. The snippet library is lightweight workflow wording only. It does not create automatic legal obligations, official standard status, or acceptance guarantees.
Can Vraimony help with student or academic submissions?
Yes. The Student submission lane is designed for cleaner submission proof, supervised work, and clearer academic handoffs. It reduces proof chaos, but it does not prove authorship, grading outcome, or legal admissibility by itself.