The ledger says unknown

A review packet crossed our desk this year commissioning an independent look at a mobile keyboard regression, and the most instructive thing in it is a table near the top. Eleven rows, each an observation with a status and a confidence. Eight of them read established at high confidence, and they are the ordinary furniture of a competent investigation. The original defect was real. A previous repair did what it claimed. The failure still reproduces on a device. Measured geometry shows a layout region that stayed at its full height inside a container that had shrunk to half of it.

Then the last three rows drop, all the way, to unknown at low confidence. One of them is the packet’s own recommended fix.

That row is worth reading slowly, because writing it was a choice. The evidence for it is strong in outline. A signal that names which layer owns the keyboard is carried into the surface and then quietly dropped at the adapter before it reaches the part that is misbehaving. Any engineer would reach for that, and the packet says as much, and then grades the row unknown anyway, on the ground that the dropped signal is a contract inconsistency to explain rather than a demonstrated cause. The same discipline is applied to a diagnostic patch that had already worked. Applying it restored the visible layout on the simulator, and the packet records that this is causal evidence for the defect and not evidence that the temporary condition is a safe general rule, and then reports that the patch was reverted.

The mechanism is a difference in what the two kinds of statement are about, because an observation describes a state the system was actually caught in and a repair is a claim about every state the system has not yet been in, so evidence accumulates on the diagnosis and has no path by which to carry across to the fix. Call the gap between the two grades the diagnosis-repair asymmetry, and note that a single confidence column hides it.

The packet then does the harder version of the same thing to its own test evidence. One hundred and fourteen tests pass across seven files, freshly run, and a section immediately follows explaining why green is insufficient. The existing mount test moves one height while holding the other fixed, which exercises the ordinary case and not the observed one. The tests prove the elements stayed alive and never measure whether the text input was on screen. There is no composed test at all from the deciding layer through to the visible box a person types in. Read together, that is a report telling its own reader not to be reassured by the number it just published.

None of this is scepticism as a pose. It is what an instrument does when it reports the size of its own error instead of hiding it, and the tell is that the humility lands on the author’s proposal rather than on somebody else’s code. Systems trained to produce plausible next steps will not do this on their own, because nothing in a fluent continuation is holding the consequence of being wrong, and the row that says unknown is written by whoever will still be there when the fix ships and fails. That is the stake condition wearing work clothes. A report willing to grade its own recommendation below its findings has told you exactly where to send the next hour, and there is no cheaper piece of engineering guidance anywhere in the building.