Author receipt
Records that declared checks ran twice against pinned inputs and agreed under the captured local environment.
replayable computational evidence
Make computational claims replayable.
Certiv packages an exact author-declared check, hash-pinned inputs, and the observed result into an inspectable receipt. Reviewers can see what ran, what passed, and where the evidence stops.
A receipt is computational evidence—not peer review, certification, scientific truth, or proof of independent reproduction.
evidence without overclaiming
One record. Three different statements.
Certiv keeps author execution, operator verification, and domain judgment visibly separate.
Verifier verdict
A separately operated node can isolate execution and sign its own verdict. Certiv.org does not operate that service.
Scientific or business judgment
Experts still assess methods, source data, interpretation, significance, safety, and fitness for use.
built for serious evaluation
A shared evidence format across research and R&D.
Use the open-source core today; evaluate operational controls before adopting it in a governed workflow.
Research labs
Ship a checkable result with the work.
Pin declared inputs, capture exact expectations, and give collaborators a compact record they can inspect before rerunning.
Follow the research exampleUniversities & venues
Define a reviewable evidence intake.
Standardize the receipt fields you request while keeping scholarly review and independent reproduction outside the tool’s verdict.
Review the evaluation pathCompanies & R&D
Preserve the computation behind a decision.
Add machine-readable evidence to internal releases without sending source, data, or receipts to certiv.org.
Compare deployment boundariesinspect before you adopt
Two public, runnable examples.
Start with a small research computation, then inspect the checks used to release Certiv itself.
Mean of a small declared dataset
Download the source packet, run the command locally, and compare the exact expectation with the published receipt.
Open worked exampleCertiv checks its own release
Inspect the package’s self-receipt, coverage, build checks, evidence boundary, and the source inputs that produced it.
Inspect release evidencelocal-first workflow
From declaration to re-check.
Declare
Name each claim, command or trusted checker, input, and exact expectation in certiv.yaml.
Run twice
Certiv executes from separate workspace copies and fails closed on divergence, truncation, or changed declared inputs.
Inspect
The receipt exposes hashes, commands, checker identity, coverage, observations, and the precise evidence boundary.
Re-check
A reviewer can validate structure without execution, rerun locally, or use a separately operated verifier.
deployment boundary
Choose controls that match the evidence you need.
Certiv Core
Local CLI, structural kernel, read API, worker components, and static reference site under Apache-2.0.
Self-hosted verifier
Your organization controls isolation, identity, keys, storage, availability, retention, monitoring, and incident response.
Managed Certiv service
Certiv currently provides no hosted accounts, upload service, custody, enterprise SLA, or managed verification queue.
trust is an evidence trail
Review the product before trusting it.
Source, release artifacts, self-checks, security guidance, accessibility status, and known limitations are public.
start with evidence you can inspect
Evaluate the workflow before making it policy.
Run the public example, read the evidence boundary, and test Core in an isolated environment you control.