Local evidence tools
Declare checks, pin inputs, run twice, inspect receipts, and re-check locally.
purpose and product boundary
Make the computation behind a claim inspectable.
Certiv exists to make a narrow but important question easier to answer: what exact computation did the author declare, what inputs did it use, and what happened when it ran?
The project turns those facts into a portable receipt while keeping stronger conclusions—truth, validity, provenance, safety, and independent reproduction—outside the author receipt.
available now
Certiv Core 1.1
Inspectable implementation
Published source, a separate validation kernel, tests, SBOM, locks, and release artifacts.
Operator components
A read API and verifier worker whose isolation, keys, storage, and operations remain your responsibility.
design principle
The boundary travels with the evidence.
An author-local pass and an independently operated verifier verdict are different records. Certiv labels them differently and does not translate either into a scientific conclusion.
This precision is intentional: a useful evidence system should reveal what it knows and refuse to imply what it does not.