Summary
The methodology self-documents (docs/methodology/country-resilience-index.mdx:669) that live cyber-threat-feed events can drive cyberDigital to 0 for a 24-72h window before smoothing catches up, and that the dimension's volatility is "high enough that a single bad day can move a country 5+ rank positions." A defensible public ranking should not swing that much on a transient feed spike.
Action
- Add smoothing (rolling window) or a capped day-over-day movement to
cyberDigital.
- Add regression fixtures: a transient single-day zero must not move a country more than N ranks / more than M score points.
- Record the chosen policy in the methodology changelog.
Notes
cyberDigital lives in the infrastructure domain (confirmed live: domains[infrastructure].dimensions = [cyberDigital, logisticsSupply, infrastructure]). The widget freshness badge already surfaces staleness, but that's disclosure, not mitigation.
Acceptance
- A simulated single-day cyber zero produces bounded rank/score movement, pinned by a regression test.
Summary
The methodology self-documents (
docs/methodology/country-resilience-index.mdx:669) that live cyber-threat-feed events can drivecyberDigitalto 0 for a 24-72h window before smoothing catches up, and that the dimension's volatility is "high enough that a single bad day can move a country 5+ rank positions." A defensible public ranking should not swing that much on a transient feed spike.Action
cyberDigital.Notes
cyberDigitallives in theinfrastructuredomain (confirmed live:domains[infrastructure].dimensions = [cyberDigital, logisticsSupply, infrastructure]). The widget freshness badge already surfaces staleness, but that's disclosure, not mitigation.Acceptance