URD ATLAS
Account
First time here? Start with Public Methodology Reference to understand what the reference data means, then read Verification & Evidence to see how published labels can be checked. Use Field Dictionary as the lookup layer when you need exact field definitions.
Meta rows now use confidence_v2_profile_evidence. Confidence still uses sqrt(data_quality_score × label_confidence_score), but data quality is profile-aware and label confidence is label-specific. The 2026-05-18 retroactive rebuild regenerated Meta and Briefs JSON so historical rows reflect the current confidence and status-explanation contract.
The methodology section is split into separate pages so that customers can move from a fast overview into more technical detail without reading one single monolithic document.
| Page | Purpose |
|---|---|
| Reference | Canonical public methodology and interpretation rules. |
| Field Dictionary | Field-level definitions and warnings, including Confidence v2 fields. |
| Verification | Worked examples and evidence path. |
| Freshness | Publication lag and freshness policy. |
| Boundaries | What the public methodology discloses and does not disclose. |
| Integrity | Determinism, row identity, and archival traceability. |
| Changelog | Methodology updates, historical republish notes, and subscriber action guidance. |
Urd Atlas publishes four JSON layers: Gold, Derived, Meta, and Briefs. Gold is the daily observation layer. Derived is the deterministic trend layer built from Gold. Meta is the analytical layer that publishes regime, confidence, scorecard state, drivers, and presentation-ready summaries. Briefs are the readable JSON layer built from the latest Meta context.
The most important page for a technical customer is the public methodology reference. The most important page for an auditor or quant reviewer is the verification page. The changelog should be checked when a customer compares cached historical JSON with newly pulled rows.
Confidence answers one narrow question: how well-supported is the current published analytical state by the data and by the label-specific evidence? It is not a prediction, a probability of future price movement, or a recommendation signal.
| Part | Plain meaning |
|---|---|
data_quality_score | Do the relevant chain-specific fields exist, remain fresh, and cover enough recent/history rows? |
label_confidence_score | Does the evidence clearly support the specific label that was assigned? |
confidence_score | Composite confidence: sqrt(data_quality_score × label_confidence_score). |
status.one_liner | Readable explanation that distinguishes the published regime label from adjacent scorecard pressure. |