The weights were there, and thrown away
The background
An operator asked to trust a forecast asks one thing: what is this number made of? Not which model ran — which measurements moved it, and where the rest came from when nothing sampled it.
The obvious answer is to ask the system that combined them. Ours could not: it knew, and threw it away.
The requirement
For the water column a reader picks, a line to every instrument that reached it, each as wide as what it contributed — and beside it the two numbers behind that width: how far the reading was from the cell, and how its error compared with the forecast's.
The options considered
The tempting fix was to work the split out in the browser, from the instrument positions and the declared correlation. It looks equivalent and is not: a second copy of the arithmetic, free to disagree with the first, and a picture that adds up by construction proves nothing about the analysis it claims to show.
The real fix was smaller. The kernel builds each weight row by row, then reports only the total. We kept the rows.
Then the surprise. The influence radius bounds the covariance, not the gain — so a cast beyond a cell still moves it, through its overlap with one nearer. That part has nowhere to draw a line from: a band, not a ray.
The demo

Pick a square. The lines are the instruments that reached that column, each as wide as it counted; pick a depth and they re-weight without moving. Every figure is printed too: a platform crossing its own cells stacks its sources. Here six contribute 3.86 and the band beyond reach −0.07, against ω = 3.79 — the gain extrapolating, at magnitude.