A 75% gas-storage rate and refill costs answer different budget questions
Separate gas stocks, storage capacity, refill flows and procurement costs by date and measurement scope.
One ratio cannot explain the winter
Lower gas storage and more expensive refilling do not answer the same budget question. One concerns stock relative to capacity at a point in time; the other concerns the cost of procurement over a period. Truthound cannot choose their meanings, but it can check declared stock-to-capacity relationships and bounds in a prepared table.
The observation inside the October report
ACER's October 27, 2026 summer gas-market report describes EU storage as 75% full on October 21. It discusses Middle East-related LNG disruption, slower refilling and conditional winter weather and demand. The percentage is a dated observation, not a reading for publication day or a live value for today.
Stocks and flows need different records
Give stock observations an as-of timestamp and flows a period start and end. Attaching a month's imports to a daily stock field obscures what remains available. Even for the same country and energy unit, stock describes a state while imports describe movement. Separate the measure type before joining the tables.
The denominator can change
The denominator deserves its own version. Mixing working-gas capacity with another capacity definition, or missing a facility addition or closure, can make a ratio change look like a stock change. Preserve the source capacity and date. Before a national aggregate is compared over time, establish whether its included facility population changed.
The comparison Truthound can check
Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, provides ColumnPairValidator for a specified comparison between non-null fields and BetweenValidator for operator-defined numeric bounds. These can test stock against capacity after units and measurement boundaries are aligned. Null treatment needs a separate policy. A percentage inside the accepted range may still use the wrong capacity definition.
Keep a working predicate when appropriate
Keeping existing Pandera 0.35.0 user predicates in a pandas workflow is also reasonable. Align facility, reference time and unit, and compare the treatment of missing capacity. Moving to Truthound should serve reusable contracts and exception handoff, rather than imply that a new library improves physical supply.
Give costs their own scope
Put procurement costs in a separate scope. The cost of purchased gas, the cost of injected gas and an estimated additional bill for a fixed quantity are different measures. Combining currencies or price periods without their definitions makes it difficult to tell whether quantity or price drove the change. The budget owner must select the denominator that answers the actual question.
Make the decision the data can support
The resulting table can distinguish evidence suitable for today's stock explanation from evidence needed for a separate procurement scenario. Winter weather and realised LNG arrivals require later observations. Hold incompatible dates and expose missing inputs, so one storage percentage does not become a substitute for every resource-allocation decision.
Conditions
Use verified storage-capacity definitions, reference dates and stock, flow and cost units.
Alternatives
Retain existing Pandera 0.35.0 predicates when they maintain the same stock-to-capacity relationship.
Limitations
Input checks do not forecast winter demand or guarantee access to LNG cargoes.
Evidence
- Event checked
- Subject checked
- Modified
