Does the uncertainty hold?
Check observed coverage against the model’s uncertainty. Calibration does not establish shutdown-onset skill.
Empirical coverage and rolling accuracy are withheld until archived issue times, complete target windows, and independent outcomes are verified.
What features the model actually uses
Sklearn feature_importances_ on the underlying XGBoost. 39 features total. Top-3 sum: 0.327 · Top-5: 0.427 · Top-10: 0.582. Healthy distribution — no single feature dominates the model.
- 1.block_rate_roll30_mean17.0%
- 2.recent_shutdown9.1%
- 3.critical_incident_7d6.7%
- 4.month6.1%
- 5.block_rate_roll14_mean3.9%
- 6.week_of_year3.8%
- 7.election_in_7days3.7%
- 8.blocked_count_roll7_mean2.7%
- 9.gdelt_unrest_30d2.7%
- 10.high_urgency_signals_7d2.5%
- 11.incident_count_7d2.5%
- 12.high_importance_event2.5%
Interpretation: The forecast model's top feature is gdelt_unrest_30d (0.25) — protest + conflict signals from the GDELT 1.0 global news feed. recent_shutdown, block_rate rolling means, and incident counts follow. risk_tier — the leaky country-level encoding that dominated our older classifier at 85% — contributes only ~2% here. Healthy distribution; no single feature dominates.
Raw JSON: /v1/sentinel/feature-importance
Related
- /methodology#validation — model evaluation methods and training-holdout limits
- /v1/sentinel/accuracy — full evaluation JSON, updated nightly
- /atlas/elections — see the forecast in action (90-day upcoming elections)
About this view
Earlier Sentinel responses included source-labeled interval fields. Empirical coverage is withheld here until archived issue times, complete target windows, and independent outcomes are verified. Source history lives at /v1/sentinel/calibration/history. A response timestamp alone does not validate interval coverage.
Model history & calibration scope
/v1/forecast/{cc}/7day responses. Their presence is not proof of active updates or qualified coverage. Full ACI methodology →