Trust · Verifiable work
Most AI trust claims are a screenshot of a dashboard you have to believe. LeanLogix takes the opposite stance: every claim we make about a model is a signed record you recompute yourself. The signature is over the verbatim bytes, so an auditor pastes it into a verifier with no LeanLogix login and gets the answer — not our word.
What the proofs prove
LeanLogix issues two kinds of signed artifact. They share one Ed25519 signing identity and one canonical byte format, so a single verifier and a single public key cover them both.
A signed bill of materials for a release: the base model, the datasets and what was excluded, the eval probes, and the approver. Because it is signed over the verbatim bytes, recomputing the fingerprint offline returns the same result — or the passport is rejected. It proves what a model is and that nobody edited the record afterward.
A signed record of a governed serving call: the model fingerprint, the backend it ran on, and the routing policy. It binds a content-free shape hash and token counts — never the prompt or response text. It proves the conduct of a run without keeping a transcript of it.
The same envelope format — governed-receipt/v1, Ed25519, body, signature, public key — wraps both. A deployment may reuse one signing identity across statement types, but a key match proves signer identity only. An auditor must also allowlist the statement schema and apply its release, routing, or serving semantics; one valid signature is not universal authority.
The cross-format referee
A proof you can only check on the vendor's own site is not really a proof. Our signed records re-verify at the portfolio's central cross-format referee — operated by our parent, LockedIn Labs, and we are open about that relationship. What makes the check trustworthy is not who hosts it but that it is pure math: the referee re-checks the Ed25519 signature against the public key embedded in the record, with no login, no callback to LeanLogix, and no privileged endpoint — and the format is openly published, so anyone can run the same check on their own machine. If the bytes changed by a single character, the check fails.
Paste any LeanLogix receipt or passport into the public verifier — it re-checks the signature against the embedded key and shows you the fingerprint. One cross-format referee for agent and model receipts across the LockedIn Labs portfolio — and the same math reproduces on your own machine.
lockedinlabs.ai/verifyThe receipt format is published with a conformance reference, so any implementation — not only LeanLogix's — can prove it produces records that verify. A format is only neutral if someone else can implement it and pass.
lockedinlabs.ai/conformanceDo it yourself
The verification is just Ed25519 over canonical bytes. It reproduces on an air-gapped box with nothing but curl and the public key carried inside the record. That portability is what separates a claim from a proof — and what makes our trust survive us being out of the room.