URD ATLAS
Account
| Concept | Public meaning | When it changes |
|---|---|---|
date | The UTC day the published row describes. | Changes only if the row identity changes. |
updated_through | Most recent Gold observation actually available to the Meta calculation. | Changes when the effective freshest supporting row changes. |
methodology_version | The public analytical methodology version that governs interpretation. | Changes when field meaning or analytical semantics change materially. |
regime.determinism_hash | Named-row integrity anchor over the public regime payload. | Changes when the named regime payload changes. |
| Dataset revision / published revision | Publication batch identity at the dataset layer. | Changes when a new publication batch is issued. |
| Change class | Methodology bump? | Historical rows changed? | Subscriber action required? |
|---|---|---|---|
| Docs-only clarification | No | No | No |
| Pipeline rebuild without methodology change | No | Only if corrected archived artifacts are republished | No, unless a correction notice says otherwise |
| Methodology-breaking analytical change | Yes | Only if historical rows are explicitly recomputed and republished | Yes — customers should treat pre- and post-bump outputs as version-distinct |
| Retroactive correction / archival replacement | Case-specific | Yes, for affected rows only | No for most use, but the correction note should be read |
date, updated_through, methodology_version, dataset revision / published revision, and regime.determinism_hash. Runtime backend and storage paths are deployment details, not the primary public provenance truth.