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). Public verification: free forever, by design — endpoint at launch.
Certified at every step.
| Product | What gets certified | |
|---|---|---|
| Parser | every parse — engine version, inputs, outputs, source spans | ✓ certified |
| Verifiable Knowledge | every knowledge object, claim and answer — with version graph, evidence chains and abstentions | ✓ certified |
| Monitoring | every admission decision and every update — with full lineage | rolling out |
What runs underneath everything Orves produces.
Provenance
Every fact traces to a source span and a file hash. “Where did this come from?” always has an answer.
Lineage
The full chain: source → parse → canonical → claim → answer. Every hop recorded, every 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 immutable ledger.
Verification
Public certificate verification — free, forever, no account. Your auditors do not need to be our customers.
How provenance survives scrutiny.
The properties below are how the platform is built — each mechanism exists so that evidence, once captured, cannot silently change.
Dual hash
Two fingerprints per evidence object: one proves the source never changed; the other proves its structured interpretation never changed. Same file, different interpretation — detectable.
Evidence anchoring
Page, bounding box, offset and timestamp bind every element to its exact place in the original source.
Immutable references
Objects reference each other by content-derived identity — a claim cannot quietly point somewhere else.
Version graph
Change creates a new version linked to its predecessor. History is preserved, never overwritten.
Tamper detection
Recomputing fingerprints against stored ones surfaces any alteration — in sources, objects or lineage.
Replayability
The canonical model is reconstructible: re-derive the same outputs from the same inputs, and compare.
Integrity verified — from source to evidence.
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 and hash-chained. Corrections are new entries with lineage, never edits.
Verify
You, your customers or your auditors check any certificate — public endpoint, no fee. 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 a “reconciliation engine” 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 external pipelines 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?
Anyone. Public verification is free forever, by design — no account, no fee.