Why would a screen skip a quantity column?

Because the wording it was written from talked about prices, and an agent follows the columns the wording names.

Does a quantity slip show up in the revenue total?

It does, and the revenue total ties perfectly, because a wrong quantity multiplied by a correct price is arithmetic the file agrees with.

What should the page say about columns that went unscreened?

It should name them, and no figure resting on an unscreened column may be described as certified.

Failure catalogue · The number is plausible, and wrong · 2 of 51

OBSERVED FAILURE MODE

The quantity slip the price screen misses.

A quantity slip is a magnitude error in a seats, units, or count column rather than a money column. A screen written for prices never looks at it, so a hundredfold seats figure passes every check the build runs, multiplies into revenue through an unremarkable price, and certifies exactly as cleanly as a correct row.

What we saw

In our own audits a seats value entered at a hundred times its true size shipped through a build whose screen wording primed a price-only reading. The prices were all ordinary. The seats column was never examined, so the row cleared and the revenue it drove cleared with it. The lesson was not that the screen was missing. The screen ran and reported itself clean, and the column it never looked at was the one carrying the error. Wording that names only prices teaches an agent which columns do not matter.

Why it passes a glance

Nothing about a quantity slip looks wrong. The price beside it is normal, the arithmetic ties, and the row's total is simply the product of the two. A reviewer scanning for money errors reads the money and moves on. A green badge saying the screen ran is true, and it is silent about which columns the screen actually covered.

What addresses it

Doctrine principle 11, reconciliation proves arithmetic, not plausibility, names quantity, seat, unit, and count columns explicitly, so no price-only reading of the rule is available. The trust-the-upload skill puts that screen into the landing pass as a fixed numbered step that runs in both directions before any figure is certified, and the page it produces states which columns were covered.

Check your own file in two minutes

List every numeric column in your file and mark which are money and which are counts.
Run the same high-side and low-side comparison on the count columns that you would run on prices, per plan or per SKU.
Find the sentence on your report that names which columns the screen covered; if there is no such sentence, the screen covered nothing you can prove.

What this does not catch

A screen covering every column still cannot see a quantity that is wrong by a believable amount, or a count that was already wrong in the source system before the export was taken. It finds errors of scale, not errors of fact, and it says nothing about which rows should exist.

Quick answers

Why would a screen skip a quantity column?: Because the wording it was written from talked about prices, and an agent follows the columns the wording names.
Does a quantity slip show up in the revenue total?: It does, and the revenue total ties perfectly, because a wrong quantity multiplied by a correct price is arithmetic the file agrees with.
What should the page say about columns that went unscreened?: It should name them, and no figure resting on an unscreened column may be described as certified.

Nearby failures

The 100x slip that ties perfectlyThe number is plausible, and wrong The screen calibrated by its own targetThe verification is theater The honest refusal that catches nothingThe verification is theater

Last updated 2026-09-02 · Dylan, founder · one of 51 observed failure modes, every one seen in a real build or in our own audits, none invented.

Get the free skill → The doctrine All 51 failure modes