Verifiable Research, Institutional Integrity

K-Veritas seals published results to the code that produced them, at the time it ran.

It does not say an experiment is correct. That stays with the reviewer.

It makes sure the numbers and the code cannot change afterwards, and that the record cannot be denied, cheating included.

No access to training data required.

Workflow

  1. Run

    Wrap any command with kveritas run. It observes passively and anchors each run at the server when it ends.

  2. Seal

    The runs are hashed and signed with RSA-4096 into a PDF report, ready to attach to a paper.

  3. Verify

    Anyone checks the report at kveritas.org/verify or with kveritas verify. No account needed.

  4. Publish

    Optional: submit the report and its code as a public record with a page and a citation.

Verification as a Service

Institutions can add K-Veritas verification to their review pipelines with the CLI or the web verifier. Reports are checked against the public ledger automatically.

The protocol is open and non-proprietary. Any party can verify independently without contacting the original author.

Try the verifier