The bug report was one sentence: "one cell in the statement is empty."
It was a ratio line in finmodel, our open-source financial modeling project. The denominator was zero in the first period, a revenue line that had not started yet. Somewhere between the formula layer and the rendered table, that turned into nothing at all. Not an error, not a warning. Blank.
The fix itself was cheap. What cost us was that a blank cell reads like a formatting detail, while a number computed from a missing denominator reads like a result. Both were wrong, and only one of them was visible.
We had three bad options. Let the decimal arithmetic raise, and a single empty period kills the whole model. Return zero, and the mistake goes invisible, because a zero sums, rounds and passes checks like any other amount. Return nothing, and every downstream line has to remember to handle it, which means one of them will not.
What we do now: division by zero returns a value, not an exception. It carries a reason, it is falsy, and it prints as "n/a (division by zero)", so the table shows the reason instead of a gap.
The part that actually mattered was propagation. Our evaluator inspects operands before it operates: if either side is already that value, it comes back before any arithmetic runs. Rounding leaves it alone. The statement stores it under the line id, and the next line reads it from the same scope. It travels the whole dependency chain without being quietly converted back into a number.
And it never passes verification. Period combination returns it instead of a sum. An opening, movement or closing balance that holds it makes the identity proof fail. A check whose difference lands on it fails too, and tolerance does not help, because a side with no amount is not a small discrepancy, it is an absent one.
That is the rule we kept: a missing value has to be louder downstream than a wrong one, because wrong values get reviewed and missing ones get rendered as whitespace.
For those of you building calculation engines, we would like to hear whether you model "no answer" as a value, or raise and let the caller decide.