{% extends "base.html" %} {% block title %}Methodology — Myrdal{% endblock %} {% block content %}

Methodology

Where each number comes from, how far it really runs, and what is not here. Every claim on this page can be checked against a file named on it.

Sources

{{ meta.counts.series_published }} series come from {{ meta.sources | length }} distinct source strings, grouped into {{ meta.counts.categories }} families. The family is derived mechanically from the registry's own source field — no series is hand-tagged, so the family counts cannot drift from the provenance.

{% for fam, n in meta.by_category.items() %} {% endfor %}
Series per source family
FamilySeries
{{ fam.replace('_', ' ') }}{{ n }}

How liveness is reported

Every “through” date on this site is the last real observation in the file. It is never a declared end year, and it is never a projection.

Construction seams

What is missing, stated plainly

Validation

The Anu build recorded a schema validation pass, a cross-source reconciliation pass (Maddison against the World Development Indicators) and a ledger health of 100 % green on {{ meta.generated_at }}. Those verdicts are carried forward from that build and are labelled as such in the manifest; this site does not re-run them. What this site does assert, on every rebuild, is that the manifest and the disk agree in both directions — every file listed exists, and every file present is listed — and that the counts shown on these pages are read from that manifest rather than typed.

Per-series provenance: PROVENANCE.csv. Full registry: series_registry.json (metadata, not a data download).

{% endblock %}