Methodology
The dashboard should not merely list tokenized assets. It should explain exactly how a NAV or AUM number becomes safe enough for an integrator to consume.
A signed value is not automatically a correct value. Provenance and freshness have to travel with it.
1. Collect
Read issuer-published NAVs, on-chain supply, third-party aggregators, and market/reference feeds. Preserve raw source timestamps separately from Autonom signing timestamps.
2. Normalize
Canonicalize asset IDs, issuer names, wrappers, chain deployments, decimals, currency, and field names into the /v1/rwa contract.
3. Compare
Calculate tolerance bands between issuer, aggregator, registry, and market readings. Flag divergent assets before they are presented as verified.
4. Sign
Build a canonical JSON envelope and sign it with the active Autonom operator key. Consumers verify the kid and x-sig-scheme before trusting the value.
5. Anchor
Mirror critical snapshots to the on-chain registry when practical. Off-chain signed values remain usable, but the UI clearly distinguishes pending registry anchors.
Confidence labels
These are UI-level policy labels that should map to backend fields. They let a perp DEX, broker, or treasury decide whether to show, haircut, or reject a datapoint.
What Autonom does not claim
Autonom can sign what it observed, where it observed it, and whether independent sources agreed. It should not imply legal ownership, redemption rights, issuer solvency, borrower performance, or regulatory suitability unless those claims are independently attested and explicitly modeled.