Once a value is directly verified (via the manual-transcription checklist), these 12 ordered steps move a /data-needs item to a live observation: clear the source gate, add the observation and source, confirm provenance, wire the related pages and FAQ/caveats, let the derived review/freshness/source-health surfaces update, batch the version bump and freeze, and hosted-verify. The template never adds a value itself.
- 12 ordered steps from a verified value to a frozen release.
- Provenance, review, freshness, and source health update from the data automatically.
- Machine-readable at /methodology/promote-data-need/data.json (promotionChecklist).
Promotion checklist
- Record the before state. Note the data-need id, its current coverageStatus, and the sample/absent row it will replace or extend.
- Clear the source gate. Confirm the source is authoritative and the value is directly readable (not chart-only, paywalled, or news). Cite the source of record.
- Verify the value. Complete the manual-transcription checklist, including the mandatory second pass; record the exact value, unit, and period.
- Add the observation. Set value, unit, asOf, periodLabel, lastReviewed, sourceId, confidence, dataMode (live/sample), and a cautious note.
- Add/confirm the source. Ensure the Source has title, publisher, url, type, accessedDate, and cadence; add it if new.
- Confirm provenance. Provenance is derived — verify the new record resolves to its source with authority/readiness and a related page.
- Update related pages. Wire the observation into its topic/dashboard and any rankings/comparisons it belongs to.
- Update FAQ / caveats. If a visible FAQ or caveat references the figure, update it (FAQPage JSON-LD only where the Q&A is rendered).
- Update review & freshness. The review queue and freshness status are derived from cadence + lastReviewed; confirm the new row reads correctly.
- Update source health. Source health is derived from cadence + review status; confirm the source's live count and status reflect the addition.
- Bump the version & freeze. Batch the DATASET_EXPORT_VERSION bump (one per 5–10 promotions); append the snapshot ladder entry and freeze the payload; run validate:snapshots.
- Hosted verification. After push, verify the updated routes and the new versioned data/diff/provenance routes on the live host.
Refresh harness: /methodology/refresh-harness · transcription: /methodology/manual-transcription · release checklist: /methodology/release-checklist · machine-readable: /methodology/promote-data-need/data.json.