01

Source identity

World Economic Data reads World Bank World Development Indicators from source 2. Provider, dataset, indicator code, country identity, attribution, and license metadata must agree before a Release can become visible.

Current attribution: World Bank data, licensed under Creative Commons Attribution 4.0.

02

Immutable snapshots

Each indicator slice is normalized into annual country observations and addressed by a SHA-256 snapshot hash. Finalized snapshots and Release membership are not edited in place.

03

Quality gates

The pipeline evaluates schema, coverage, non-null counts, historical revisions, geography mappings, source freshness, and license identity against the active production baseline.

04

Publication outcomes

PASS

All automatic gates pass and publication may proceed.

REVIEW

An operator must accept or reject a material change.

FAIL

Publication is blocked and the previous Release stays live.

NOOP

The source produced no publishable change.

05

Country-only scope

Formal global pages use the versioned set of three-letter country ISO3 identifiers. World, regional, income-group, and synthetic province or city records do not enter country totals, maps, tables, or ranking denominators.

06

Ranking methodology

A formal ranking uses the newest year with non-null observations for at least 80% of the 217 published countries. Canonical decimal strings are sorted exactly; equal values are resolved by ISO3. Missing countries remain visible without a rank.

07

Observation statuses

observed

A source-reported value is available.

estimated

The source identifies the value as estimated.

missing

No value is published for that country and period.

not applicable

The measure does not apply to the observation.

suppressed

The value is intentionally withheld from publication.

08

Reproducible downloads

Country, indicator, and approved ranking datasets are published as CSV files with metadata sidecar JSON under Release-scoped immutable URLs. SHA256SUMS records the checksum evidence needed to verify downloaded bytes.

09

Corrections and rollback

A correction creates a new candidate and, after the same quality and review process, a new Release. Historical published Releases remain available for audit. If a production issue is confirmed, the production channel can return to a previously published Release without rewriting either version.