for authors

Five steps. No account. Your method stays yours.

The whole authoring loop runs on your machine, offline, before anything is submitted. The claim manifest is the one artifact you write by hand; everything else is packing and checking.

Install

From source while the packaging name is finalized (a `certiv` name-clash with an unrelated package on PyPI is being resolved before we publish there):

git clone https://github.com/g14/certiv && pip install ./certiv

Do not pip install ./certiv from PyPI yet: that name currently belongs to a different project. The official package name and its signed release hashes will be published here and at /security before any PyPI release.

Declare your claims

certiv init writes certiv.yaml with worked examples. For each checkable claim: the statement as it appears in your paper, the command that recomputes it, the input files, and the expected result. Certificates (Lean and friends) declare a checker instead.

Pack

certiv pack hash-pins your inputs, runs every claim twice in a scrubbed environment, refuses nondeterminism, and writes receipt.certiv. Add --seal for tier T2: your workdir ships as a sealed container, re-executed under a verification-only license, with the hash timestamp as priority evidence.

Check

certiv check re-executes the receipt and either confirms it or names the exact claim that broke. Run it until green; nothing needs to leave your machine before it is.

Submit

certiv submit paper.pdf receipt.certiv --tier T1|T2|T3 chains your paper into the public ledger; our nodes re-execute every claim and sign what they saw. Your paper page shows exact coverage, claim by claim.

What the manifest looks like

schema: certiv_manifest_v1
paper:
  title: "Your title"
  authors: ["You"]
tier: T1
claims:
  - id: table-2-total
    statement: "The totals in Table 2 derive from dataset D."
    command: "python3 analysis/table2.py"
    inputs: ["data/D.csv", "analysis/table2.py"]
    expect:
      output_file: out/table2.csv
      output_sha256: auto        # pinned for you at pack time
  - id: thm-31
    statement: "Theorem 3.1 holds."
    certificate:
      path: proofs/Thm31.lean
      checker: "lake env lean proofs/Thm31.lean"

Full field reference and the receipt schema live in the repository docs; the kernel is the executable definition of what a valid receipt is.