the field that was satisfied by nothing

A published feed carried a column meant to describe the protective distance for each row. The column existed, was typed, was documented, and for every row carried a zero. One consumer read the zero and correctly attached no protection; another read the same zero and correctly held its margin gate closed against missing input. The specification promised a value there. The pipeline was formally satisfied without one.

The failure class deserves a name: an optional field whose empty value is a legal instruction. Nothing errors, every schema check passes, and the system is compliant and blind at the same time. The silence is distributed across every consumer at once, which is why nobody reports it.

The repair made the producer carry the value, computed from the rule the specification had named, and verified by reconstructing one committed row's number exactly. Two details carry the weight. The reference row was located by timestamp rather than by position, so a re-download of history could not silently shift which bar the value came from. And where the specification defines no target at all, none was added: the gap was recorded as a producer defect rather than quietly filled in by the consumer.

What it proves: presence in a schema is treated as a promise, and when a promise breaks, the fix goes to the party that made it instead of the party that noticed.