Verify without us
Ed25519 public key published. Any ERF record verified offline by anyone — no Vraimony infrastructure needed.
Open source — github.com/vraimony
ERF is an open standard.
Vraimony is the reference implementation.
The Evidence Receipt Format is designed to be adopted, not locked in. The spec, local-first client runtime, SDK, CLI, the WooCommerce production wedge, and browser tools are all designed for self-hosting and same-server deployment. Anyone can implement, verify, and build on ERF without depending on a third-party AI vendor.
Open specification
AI Evidence Engine v3.1
Ed25519 — offline verifiable
9 test vectors
SDK + CLI + WordPress + Browser
AI Evidence Engine — v3.1
Not a writing assistant. An evidence discipline engine.
Architecture: 5-pass pipeline — Extract → Normalize → Validate → Map claims to evidence → Write.
Every claim linked to an evidence ID. Every contradiction typed. Every gap tiered. Browser-first by default. Same-server fallback only when needed. No third-party AI vendors in the runtime path.
8 Endpoints
POST
/v1/ai/case-analysePOST
/v1/ai/write-decision-sheetPOST
/v1/ai/falsify NEWPOST
/v1/ai/missing-evidence NEWPOST
/v1/ai/reviewer-simulatePOST
/v1/ai/outcome-patternPOST
/v1/ai/file-metadataGET
/v1/ai/statusWhat v3.1 adds over v2
🔗 Claim-to-evidence graph — every claim linked to EX-IDs
📂 Evidence registry — confidence + uncertainty label per file
⚠ Contradictions v2 — 5 types: temporal, entity, status, narrative, sequence
📊 Completeness breakdown — 5 dimensions (timeline, delivery, policy, identity, comms)
🔴 Falsification mode — hostile pass finds overstatements + weaknesses
🔍 Missing evidence engine — tiered by critical / required / recommended
📝 Source-linked writing — every sentence has backed_by[] evidence IDs
🎭 5 reviewer profiles — bank, payment ops, support lead, procurement, legal hostile
📂 Evidence registry — confidence + uncertainty label per file
⚠ Contradictions v2 — 5 types: temporal, entity, status, narrative, sequence
📊 Completeness breakdown — 5 dimensions (timeline, delivery, policy, identity, comms)
🔴 Falsification mode — hostile pass finds overstatements + weaknesses
🔍 Missing evidence engine — tiered by critical / required / recommended
📝 Source-linked writing — every sentence has backed_by[] evidence IDs
🎭 5 reviewer profiles — bank, payment ops, support lead, procurement, legal hostile
# v3.1 case-analyse returns
{
"evidence_registry": [{"id":"EX-01","confidence":0.91,"uncertainty_label":"confirmed","weight_tier":"primary","key_facts":[...]}],
"claim_evidence_graph": [{"claim_text":"...","supporting":[{"evidence_id":"EX-01","contribution":"...","strength":"strong"}]}],
"contradictions": [{"type":"temporal","issue":"...","severity":"high","resolution_evidence_needed":"..."}],
"evidence_completeness": {"timeline":80,"delivery_proof":70,"policy_proof":40,"identity_consistency":90,"communication_coverage":60},
"missing_evidence": {"critical":[...],"required":[...],"recommended":[...]}
}
{
"evidence_registry": [{"id":"EX-01","confidence":0.91,"uncertainty_label":"confirmed","weight_tier":"primary","key_facts":[...]}],
"claim_evidence_graph": [{"claim_text":"...","supporting":[{"evidence_id":"EX-01","contribution":"...","strength":"strong"}]}],
"contradictions": [{"type":"temporal","issue":"...","severity":"high","resolution_evidence_needed":"..."}],
"evidence_completeness": {"timeline":80,"delivery_proof":70,"policy_proof":40,"identity_consistency":90,"communication_coverage":60},
"missing_evidence": {"critical":[...],"required":[...],"recommended":[...]}
}
Release hygiene
Public packages are built to stay self-hosted and key-clean.
Distributable packages should ship without private keys, duplicate package folders, or hidden runtime dependencies. The API bundle now carries a release audit path specifically to prevent secret leakage and packaging drift before shipping.
No private keys in distributable ZIPsSame-server only runtimeRelease audit before shipping
Repositories — what is open and why
Code, spec, and tools. All public.
PRIMARYStandardMIT
View on GitHub →
evidex-receipt-format
The complete ERF specification — schema, test vectors, conformance profile, registries. Source of truth for any ERF implementation. AI engines read this format natively.
git clone https://github.com/vraimony/evidex-receipt-format
📄 ERF_STANDARD.md🧪 TEST_VECTORS.md — 9 scenarios
✅ CONFORMANCE_PROFILE.md📋 REGISTRIES.md
AI EngineNode.js
Try live →
vraimony-api — AI routes
Evidence Engine v3.1. Builds claim-to-evidence graph, detects 5 types of contradictions, scores completeness across 5 dimensions, falsifies the case, identifies missing evidence by tier, writes source-linked Decision Sheets. 5 reviewer profiles. Requires ANTHROPIC_API_KEY. Graceful fallback without key.
POST /v1/ai/case-analyse # 5-pass engine: claim graph + contradictions v2 + completeness
POST /v1/ai/falsify # hostile second pass — finds overstatements + weaknesses
POST /v1/ai/missing-evidence # what the file needs: critical / required / recommended
POST /v1/ai/write-decision-sheet # source-linked: every sentence has backed_by[] evidence IDs
POST /v1/ai/reviewer-simulate # 5 profiles: bank / payment-ops / support / procurement / legal
POST /v1/ai/outcome-pattern # explained direction — not raw prediction percentages
POST /v1/ai/falsify # hostile second pass — finds overstatements + weaknesses
POST /v1/ai/missing-evidence # what the file needs: critical / required / recommended
POST /v1/ai/write-decision-sheet # source-linked: every sentence has backed_by[] evidence IDs
POST /v1/ai/reviewer-simulate # 5 profiles: bank / payment-ops / support / procurement / legal
POST /v1/ai/outcome-pattern # explained direction — not raw prediction percentages
WordPressWooCommerce
Plugin docs →
vraimony-wordpress-plugin
WooCommerce-first dispute readiness workspace. Order-aware case creation, Suggested Now triggers, local-first upload triage, bundle verdict, family templates, and same-server-only handoff inside WP Admin.
wp plugin install vraimony
# Then: every order → /v1/proactive/record → case_ready: true
# Then: every order → /v1/proactive/record → case_ready: true
SDKJavaScript
Download →
vraimony-sdk
JavaScript SDK for creating, signing, verifying, and exporting ERF records. Browser + Node.js. Zero external dependencies for core signing.
npm install @vraimony/sdk
CLINode.js
Download →
vraimony-cli
Command-line tool for creating, signing, and verifying ERF records. Batch processing, CI/CD pipelines, and server-side workflows.
npx vraimony-cli seal ./evidence/ --output case.pdf
Why open — the strategic reason
Adoption requires trust. Trust requires openness.
Build without us
ERF spec, test vectors, and conformance profile are public. Any team builds ERF-compatible systems without Vraimony.
AI reads without us
ERF JSON is structured for AI parsing. Any AI can read, analyse, and act on ERF records. The format is the moat, not the vendor.
ERF Foundation — certified implementers
Build on ERF. Become certified.
ERF Foundation membership signals conformant implementation to buyers, reviewers, and acquirers. $2,000/year. Listed as certified implementer.
Start building
Read the spec. Test the AI. Deploy the plugin.
Local-first architecture
Client-heavy by design. Server-light by rule.
Uploads, template routing, case assembly, and most evidence reasoning are intended to run in the browser first. The server keeps signing, persistent records, admin aggregation, and limited same-server fallback. This is cheaper to scale, easier to self-host, and more aligned with privacy-first evidence workflows.
No third-party AI runtime
Same-server packs only
SDK + worker + local cache
WordPress / Woo shell ready
Local-first distribution assets
Browser-heavy packages are now part of the open distribution story.
WordPress shell
A same-owner, local-first admin shell for Cases, Upload, Templates, and Settings.
SDK v2.2.0
Adds template pack fetch, IndexedDB case cache, worker client, and bundle verdict helpers.
No third-party runtime
Browser-first helpers, same-server packs, and server-light architecture by default.