{
  "task_id": "F1-conf-01",
  "first_growth_month": "2001-01",
  "last_month": "2026-09",
  "n_months_growth": 308,
  "n_months_missing_growth": 1,
  "n_analysed": 308,
  "mean_growth_12m": 2.57412,
  "mean_growth_12m_2001_2013": 2.361215,
  "mean_growth_12m_2014_2026": 2.792628,
  "growth_2014_06": 2.097634,
  "growth_2016_07": 0.868363,
  "growth_2020_05": 0.198201,
  "growth_2022_06": 8.979361,
  "growth_2026_09": 3.717251,
  "max_growth_12m": 8.979361,
  "max_growth_month": "2022-06",
  "min_growth_12m": -1.958761,
  "min_growth_month": "2009-07",
  "feasibility": "partial",
  "feasibility_reason": "1 month(s) of the window have no computable g_t because the source publishes no index level for 2025-10; summary statistics are over the remaining months.",
  "data_issues": [
    {
      "issue": "cpi_assembled.csv has no row for 2016-07 and contains a row dated 2026-10 (outside the vintage coverage); from 2016-08 onward every value is shifted one month later than its true date (e.g. the 2016-07 value 240.101 is labelled 2016-08).",
      "handling": "cpi_assembled.csv not used for estimation; series rebuilt directly from the two authoritative vintage files."
    },
    {
      "issue": "cpi_assembled.csv uses the older 2016-07-15 vintage for 30 overlap months 2014-01..2016-06, although the 2026-10-28 vintage covers them (values differ by seasonal-factor revisions).",
      "handling": "Per the availability rule, the 2026-10-28 vintage value is used for every month it covers."
    },
    {
      "issue": "2026-10-28 vintage reports no value for 2025-10 (empty cpi cell); the 2016-07-15 vintage does not cover that month either.",
      "handling": "No interpolation; g_t for 2025-10 (and for 2026-10, outside the window) is not computable and is counted as missing."
    },
    {
      "issue": "cpi_assembled.csv has an empty cpi at row labelled 2025-11 (this is the 2025-10 gap, mislabelled by the one-month shift).",
      "handling": "Not used; see shift issue."
    },
    {
      "issue": "Growth rates for 2014-01..2014-12 combine a 2026-10-28-vintage numerator with a 2016-07-15-vintage lag (2013 months not in the recent extract); seasonal factors for 2013 were later revised.",
      "handling": "Applied the stated rule (most recent vintage available per month) as specified; flagged as a limitation in the report."
    }
  ],
  "n_input_rows": {
    "cpi_vintage_2016-07-15.csv": 834,
    "cpi_vintage_2026-10-28.csv": 153,
    "cpi_assembled.csv": 957
  },
  "random_seed": null
}