Locus is Invariant Research's transparency layer for verification receipts and benchmark artifacts. It records hash commitments so a verifier can confirm whether a receipt or benchmark artifact was registered without trusting a private database. Locus does not publish private receipt contents. It publishes the evidence that a commitment exists.
An SVR receipt is a cryptographically signed record of verification work. But a receipt alone only proves that the issuer claims the verification happened. Without an independent record, there is no way for a third party to confirm when the receipt was created or whether the issuer might have backdated it.
Locus solves this by anchoring receipt commitments into an append-only transparency log. The log records hash commitments, not receipt contents. A verifier can independently confirm that a specific receipt hash was registered at a specific time, without needing to trust Invariant Research's internal systems. This follows the same design principle as Certificate Transparency logs in the TLS/PKI ecosystem.
Locus is live at locus.invariant.pro, running on Cloudflare infrastructure with a D1 database backend. The canonical braid includes correctness receipts at 1M and 5M vertices.
Locus does not store receipt contents, personal data, or verification details. It stores hash commitments and proof material. It is not a blockchain: there is no consensus mechanism, no token, and no distributed ledger. It is an append-only transparency log, similar in design principle to Certificate Transparency but applied to AI verification receipts.
Locus does not replace SVR receipts. SVR provides the signed verification evidence. Locus provides independent confirmation that the evidence was registered. They are complementary layers in the same trust infrastructure.
View committed receipts and benchmark artifacts on Locus, or see sample verification receipts from SATYA.