A property, not a product.
You will not find “Certification” on our price list — because it runs through everything. Every artifact Orves produces is built to carry a verifiable certificate (in pilot today), holding what an independent party needs to check its integrity and provenance. A public, account-free verification endpoint ships with the pilot rollout.
Certified at every step.
| Product | What gets certified | |
|---|---|---|
| ORIS | every parse — version, inputs, outputs, source spans | designed · in pilot |
| VERI | every knowledge object, claim and answer — with version graph, evidence chains and abstentions | pre-launch |
| MESH | cross-source relationships, access and audit events — designed to be certified end to end | pre-launch |
| Updates | every new evidence admission and every re-adjudication — with full lineage | pilot |
What every Orves result carries.
Provenance
Every fact traces to its exact source. “Where did this come from?” always has an answer.
Lineage
Every result traces back through every step that produced it — each hop recorded, each hop checkable.
Versioning
Artifacts and knowledge carry versions. Corrections are new entries with history — never silent rewrites.
Evidence
Claims ship with the evidence that supports them — and with resolution states when it is insufficient.
Governance
Nothing enters or changes without a decision: scored admissions, resolution rules, an append-only ledger.
Verification
Every result carries the evidence required for independent verification. Public, account-free verification ships with the pilot rollout.
What the contract promises.
You buy results; we take responsibility for how they are produced. These are the guarantees that come with every output — properties of the contract, not descriptions of the machinery behind it.
Traceable
Every result can be traced back to its supporting source.
Versioned
Every result identifies the product, schema and execution version that produced it.
Verifiable
Results carry the evidence required to verify integrity and provenance.
No silent mutation
Changes produce a new identifiable version while preserving the prior history.
Explicit about failure
The system reports missing evidence, degraded processing and unresolved states rather than hiding them.
Auditable
Execution records, transformations and consumption can be inspected and reconciled.
Guaranteed by the contract — not by any single implementation.
Emit. Record. Verify.
Emit
Every product emits a certificate for every transformation it performs — signed, hashed, bound to inputs and outputs.
Record
The ledger stores it append-only, preserving prior history. Corrections are new identifiable versions with lineage, never silent edits.
Verify
Every certificate carries what an independent party needs to check it. A public, account-free verification endpoint ships with the pilot rollout — trust that outlives the vendor relationship.
The only platform that says “I don't know.”
Every claim carries a resolution state. CERTIFIED means the evidence is there — go read it. ABSTAINED means it is not — and no model gets to fill the gap with fluency. Orves never fabricates facts.
{ "claim": "renewal_term",
"state": "ABSTAINED",
"reason": "insufficient_evidence" }
{ "claim": "policy_owner",
"state": "CERTIFIED",
"evidence": [{ "span": "p14 §2.3", "sha256": "9c41…" }] }
FAQ
Why is Certification not a product?
For the same reason you do not buy “reconciliation” as an add-on from a payments company. Certifying is how the platform works, not something you add to your cart. Every artifact ships certified — included, always.
Can I certify artifacts produced outside Orves?
Not today. Certification covers what the platform produces. If certifying artifacts produced elsewhere becomes a real need, it may become a standalone product — that decision will be made on demand, not on roadmap slides.
Who can verify a certificate?
By design, anyone — no account, no fee. The public verification endpoint ships with the pilot rollout; today, every certificate already carries what an independent check needs.