Governance & decentralization

Invarians produces auditability inputs: signed records of the conditions an execution ran under. It is not an auditor, not an advisor, not a decision engine. The institution keeps the audit, the decision and the responsibility; Invarians supplies the factual record they rest on.

It holds no stake in any transaction: not the issuer, not the operator of the chain, not the agent executing. It reads the substrate from finalized public data, so the record carries no interest in the outcome it describes. That operational neutrality is the point: a party with nothing to gain is the one whose record an auditor or a counterparty can rely on.

The methodology is public and versioned: thresholds and allowlists carry version ids, so a past classification can be re-derived from the same public method and the same data. Independence is a design constraint, not a slogan. Today a single operator signs (HMAC, disclosed below); the decentralized layer removes that last dependency.

Today the pipeline runs Phase 01, centralized. Decentralization arrives as two independent agentic infrastructures, with a human kept in the middle. The proposal layer decentralizes the compute that proposes a new calibration, non-deterministic by design, never more than a candidate. The attestation layer decentralizes the production of the signed attestation, deterministic, every node must agree. The only human step sits between them, validate and arm. The hard rule never bends: non-determinism stays in the proposal layer and never reaches a signed attestation. The attestation layer targets a Chainlink CRE-DON, hybrid late 2026 to 2027, fully decentralized 2028.

The public registry holds verified regulatory requirements, each with its verbatim quote, the hash of its frozen source, and the metric it justifies. A text is admitted only if it is a regulatory, institutional or standard-setting source (not marketing), the requirement is quoted verbatim and verifiable against the frozen snapshot, and it maps to a measurable property of the substrate or to an evidence duty Invarians can serve.

Every submission follows a public lifecycle: capture, freeze with a hash, extraction, verification against the source text, and a human gate before entry. Criteria are published; submission does not guarantee inclusion; nothing here is legal advice.

Vendor, market and protocol-mechanics material stays in the internal research corpus and never reaches the public registry surface.