Prove

Lineage

Demo · green

One record. Seven planes. Anyone can re-check it.

The single record a buyer, auditor, or regulator actually opens. It re-runs nothing — it cites the signed receipts every other product produced and composes them into one causal chain across seven planes: code, run, knowledge, policy, approval, data, and drift. The verifier compiles to WebAssembly, so anyone can re-check a record client-side: zero install, zero network.

Verify a record →Talk to us
refund-incident-1947.lnrlive
record
refund-incident-1947
root
sha256:54bc0655abbf…
planes
approval code conformance data knowledge policy run  (7)
signer
ed25519 · keyid d2f381d7b0b5…
  • runstep 9 — refunded an already-delivered orderproven
  • knowledgeretrieved doc-1 — a stale refund-policy docproven
  • policyrefund-limit rule evaluated → allowproven
  • data→causesuspected-cause (uncounted)asserted · uncounted
VERIFIEDoffline · engine absentnet requests: 0

Verified offline. 3 proven planes, 1 asserted and uncounted. 0 network requests.

Every product emits Kernel-shape receipts; one verifier checks them all.

Seven planes

One causal chain, exercised — not asserted

Lineage re-runs nothing. It cites the signed receipts every other product already produced and composes them into one causal chain across seven planes — and these planes are exercised, not asserted: the data plane re-verifies a real data-gateway capsule with the engine absent.

  • code
  • run
  • knowledge
  • policy
  • approval
  • data
  • drift

Verify in your browser

The verifier compiles to WebAssembly.

Paste a record into the portal and re-check it client-side — zero install, zero network, and we never see it.

Open the verify portal→

The rest of the platform

Same receipt. Same verifier.

All products→