The calibration registry becomes a decentralized agent.
Today ANS records calibrations and backtests. ANS-V3 makes it the referent agent that proposes them: a decentralized service, trained on how API-consuming agents actually behave, targeting the predictive signal deterministic calibration never reached.
ACT is a free ground-truth label feeding recalibration.
01: Propose
This is the central invariant. Three environments, each with exactly one role: ANS proposes (exploratory, non-deterministic), the DON validates and signs (deterministic, by consensus), a human arms the decision.
| Step | Who | Where it runs | Nature |
|---|---|---|---|
| PROPOSE (calibrations + matrix / delta) | The ANS brain | Nosana (decentralized GPU) | non-deterministic, exploratory |
| VALIDATE / PRODUCE the attestation | The Chainlink DON | CRE / DON | deterministic, BFT |
| ARM (put into force) | You / governance | human | final decision |
Nothing non-deterministic ever touches a signature. The brain that searches and proposes (and can be wrong) lives on Nosana; the production of the signed data stays on the DON, deterministic. The two are never mixed.
Consensus does not protect against bad calibration: it legitimizes it. When every node computes the same regime from the same thresholds, agreement is guaranteed. But if the thresholds are wrong, every node computes the same wrong answer, in consensus. The exploratory brain exists to attack exactly that:
The fuel is the downstream behavior of the agents that consume the API. That is the point of the design.
ACT, acts on-chain. Its transaction succeeds, fails, is sandwiched, or lands at unfavorable cost. That downstream outcome is a free ground-truth label. Where the backtest has only 4 events, the stream of consuming agents provides a continuous, real training signal.The added value is a hypothesis under test, not a settled claim. This loop exists to prove it, or refute it, in the open.
02: Attest
A proposed calibration is not trusted because ANS says so. It is produced under consensus: each DON node recomputes the regime from its own RPC, and a signed attestation is issued only when nodes agree. Determinism is the rule here, the opposite of the exploratory brain.
Each chain has its own τ (structural) and π (demand) thresholds. Calibration version, data basis, and last update date are published for each.
beacon_participation, sequencer_publish_latency) the regime trigger uses raw ratio or seconds against calibrated bounds; the per-metric Drift Signal shift activates after the long-term EMA stabilizes (~30 days post-launch).
03: Arm
ANS proposes and the DON signs, but neither decides for you. Every Invarians attestation carries the calibration version that produced it. Each consuming agent reads the attestation and the reference, applies its own risk thresholds, and arms its decision: act, defer, or wait. The reference is shared; the rule is yours.
04: Audit
All calibration parameters, backtest results, and methodology are publicly documented. No black box: every threshold has a derivation, every event a trace.
05: Proof of utility
The raw data is public. Anyone can reconstruct it after the fact. What is not public, and not reconstructible, is the commitment made at the moment of the decision. That is what an attestation is, and what analytics is not.
Reconstruction after the fact (a public analytics query, a block explorer) proves, weeks later, what a chain contained. It cannot prove what a neutral third party asserted at the moment of the decision, nor what an agent could reasonably know when it acted.
Be honest about it: the data is public and reconstructible. The gap is not in the data, it is in the commitment apparatus: a signature at the moment T, a frozen methodology, thresholds calibrated with a published false-positive rate, and a third party that is not party to the transaction. The buyer is the one who needs proof, not analytics. If a prospect is satisfied by a database query, they were never the client. Institutional RWA buys audit exhibits.
No agent can maintain, chain by chain, an expert definition of what "degraded" means: beacon-chain participation on Ethereum, batch-posting cadence on an OP-Stack rollup, the RMN curse state on a cross-chain lane. The matrix is a normalization layer: one calibrated vocabulary, with a measured false-positive rate. That is real engineering value, on its own.
The naive view treats the signal as an umbrella: when in doubt, wait, the pause is free. In regulated settlement, the pause is not free. Deferring risks a missed cut-off, a penalized settlement fail, an unhonored redemption window, a delayed valuation. Abstention is an action, with a hard and sometimes regulatory cost.
This is where the three proofs lock together. One: the pause is defensible (you hold a signed exhibit, dated to the moment it mattered). Two: the pause is rational (acting into that state would genuinely hurt). Three: the pause is affordable (stress windows are shorter than settlement margins, and an agent can often reroute instead of waiting). The keystone: the signal earns the right to impose a cost of abstention only because the state is harmful, and because the qualification is an opposable exhibit, not an opinion.
06: Roadmap
Today ANS is a passive, signed registry. The path below is published as commitments: dated, versioned, refutable. Targets are proposals until proven.
The full operational roadmap, with quarters and named integrations, lives at invarians.com/roadmap →
The reference agents navigate by
Live execution context across L1, L2, and bridge. Regime (12 signed codes per chain), Drift Signal, structural state: signed and verifiable.