Research contribution
I built the archive-to-backtest workflow: official release histories, information sets reconstructed at each forecast date, comparable predictions, and explicit checks for future information.
The strict as-of rule has no future releases or later revisions. Fixed mask preserves release availability but uses 5,464 later-revised cells. The naive latest-data rule adds 863 future-release cells as well. These are three distinct information rules, not three valid real-time forecasts.
Research question and relevance
Question: How do release revisions and the information available at each vintage affect nowcast and forecast quality?
Real-time evaluation matters because today's revised macro series contain information unavailable to a forecaster in the past. The project makes availability dates, vintage labels, transformations, and source limitations explicit.
Original paper or report: This is a project-originated forecasting engine. Any future paper replication must add the exact citation, original sample, specification, and benchmark result before claiming equivalence.
Data sources and sample
Adapters support FRED and ALFRED plus guarded BLS and BEA current-data APIs. Synthetic fixtures allow offline validation. Current BLS and BEA API rows are labeled latest_revised; they are not presented as first-release historical observations.
| Source | Coverage and provenance |
|---|---|
| FRED / ALFRED | Series-specific sample and vintage metadata. |
| BLS / BEA | Current revised public API data under explicit authorization. |
| Fixtures | Synthetic offline samples for schema and pipeline tests. |
Capabilities demonstrated
- Record source retrieval time and release availability.
- Normalize units, frequency, adjustment, and transformations.
- Construct vintage-consistent information sets.
- Backtest models without revised-data leakage.
- Publish forecast outputs with source and revision manifests.
Robustness checks cover alternative windows, model classes, transformations, missing-value behavior, retry paths, and unsupported provenance claims.
Validation evidence
| Validated component | Evidence | Interpretation |
|---|---|---|
| Official archive ingest | 626,304 rows across 21 series | Inputs are hashed, provenance-stamped, and aligned to their documented release timing. |
| Real-data forecast run | 15,264 two-horizon forecasts | The expanding-window pilot compares models on consistent information sets. |
| Vintage timing audit | 0 future-release and future-revision cells under strict as-of | Fixed mask isolates revised-value hindsight; naive latest data adds release-timing leakage. Neither is a valid historical real-time information set. |
This is an official-data pilot and research system, not a claim to reproduce a specific paper or production forecast.
Reproduction and citation
Run python -m macro_nowcast.pipeline using the documented configuration. Cite the portfolio release, Dataset revision, project, and original agency sources.
Evidence boundary
The official pilot distinguishes historical archives from current revised APIs and records the vintage policy, sample, configuration, metrics, and checksums. It is not presented as a paper replication or a production forecast.