Why learned weather models still need physical consistency checks

The history from GraphCast and GenCast to WeatherNext 3 is not a simple replacement story in which learned models make physical reasoning irrelevant. It is a useful setting for asking how predictive outputs remain coherent when combined.

The dated path

• 2023-11-14: GraphCast: AI model for faster and more accurate global weather forecasting.

• 2024-12-04: GenCast predicts weather and the risks of extreme conditions with state-of-the-art accuracy.

• 2026-09-03: Google introduces WeatherNext 3.

The problem appears between outputs

A user may consume several predicted quantities together rather than inspect each variable in isolation. Individual error measures can look acceptable while relationships between outputs are inconsistent. Our retrospective argument is that model progress makes this joint structure more important to evaluation, especially as forecasts become more detailed. The question is not whether an output looks plausible alone, but whether a downstream process can use the combined picture without encountering contradictions hidden by separate averages.

Why historical data do not remove the question

Learning from past observations can capture rich regularities, yet it does not make every future combination equally well represented in the training record. Rare regimes and unfamiliar regional conditions deserve explicit attention. A useful evaluation distinguishes interpolation within familiar patterns from behavior where the model has weaker support. This is a general analytical implication for learned forecasting, not a claim that a specific WeatherNext result failed such a test. The announcement’s existence cannot answer every question about its transfer boundaries.

A counterfactual based on coupled use

Compare a task that consumes one predicted variable with a task that depends on relationships among several variables. Keep the geographical region and forecast period fixed. A performance gap between these uses can expose a limitation that a single-variable score would miss. The test should state what consistency means for the intended process rather than apply an unexplained global label. This keeps a physical plausibility check connected to an observable requirement instead of treating it as a rhetorical objection to machine learning.

What the infrastructure record contributes

Preserving the joint forecast version, processing definitions and issue time helps users avoid accidentally combining incompatible outputs from different snapshots. A coherent model result can become incoherent after careless distribution or refreshes. Operators therefore share responsibility for maintaining the relationships that evaluation assumed. The broader historical lesson is collaboration between predictive modeling and domain-aware verification. Better learned forecasts expand what can be delivered, while scientific checks and careful data handling establish which uses the available evidence can actually support. This also keeps a downstream integration failure distinguishable from a weakness in the original forecast.

Technical background

Related engineering context: Evaluation conditions; Data handling infrastructure.