Absent is not zero
Zero, empty, unasked, unaskable. Four answers, not one.
A count of zero, an empty field, a source not queried, and a question that cannot be asked are four different answers. Collapsing them is a correctness bug, and it is the most expensive recurring defect in the BLU project.
I built the machine to refuse, because I could not buy one that would.
FOUR ANSWERS
Not one
Zero is a measurement. An empty field is a gap. A source not queried is silence. A question that cannot be asked is a refusal. Treating them as the same number is where the error enters.
INLINE CAVEATS
Next to the number
The morning report carries its caveats beside the figure, not in a footnote nobody reads. Zero Stripe charges behind this figure: a quiet day looks like this, and so does a stalled table. This figure is incomplete, not low; five cancelled orders excluded. Matching follows the same discipline — if we cannot match them, they do not count, so every such figure is a floor, stated as a floor because the error is asymmetric.
SPECIFIC REFUSAL
The machine refuses, the human decides
When a credential dies, that is a refusal, not a zero. The figure is unknown, not small. A refusal must name what is missing and what would fix it: a specific refusal is a work item, a vague one is an apology. I have never seen software I could buy behave that way, and I do not think that is an accident.