The unambiguous half

Every practice in the design registry behind one of our own sites carries a field that decides what a build is allowed to do about it. A practice marked as a mechanic is enforced by a named validator check, and a violation fails the build. A practice marked as a ruling is advisory prose, binding on the people who work there and invisible to the machine, until somebody can state it precisely enough for a neutral check to exist. The field looks like a maturity ladder, prose waiting at the bottom to be promoted into enforcement at the top. It is not. It is a declaration about which kind of rule each practice is, and the interesting ones turn out to be two kinds at once.

Watch what happened to the type ruling when it was finally mechanized. The rule says type is set by role rather than by arbitrary size, and half of it proved decidable from the file alone. A declared size below the readable floor is a breach, and the check fails the build and names the file and the literal that did it. The other half is not decidable at all. A size above the floor but outside the role scale might be a lapse or might be a logotype that has earned its exception, and no scan of the source can tell those apart. So the check does something that looks like a compromise and is actually a boundary. Below the floor it fails. Above it, it emits a note, addressed to a person, saying that this size sits outside the role scale and asking them to confirm it earns the exception.

The mechanism is the split itself, because a rule whose breach is decidable from the artifact alone can be mechanized and failed on while the half that requires reading the situation can only be reported, and a check that cannot distinguish a defensible case from a breach does not produce findings at all, it produces noise, and it spends the build’s credibility to do it. We call the enforceable part the unambiguous half, and the discipline is refusing to pretend the rest is inside it.

The motion ruling was cut the same way, and the residue was left in the open. Toggling an element’s display property to change state cannot animate, so a state change written that way always pops, and the check fails on it without hesitation. The remainder of that ruling, that reveal motion belongs on a unit’s wrapper rather than on the text inside it, stays prose, with a comment in the check explaining precisely why it stayed prose. A class-name scan cannot tell a standalone lead paragraph, which is correct, from inner text inside a card that is also moving, which is the regression. That comment is not an apology for incomplete automation. It is the finding.

What a check costs when it rules past its evidence has been measured, and the number comes from a hospital rather than a build. The sepsis prediction model embedded in one of the most widely deployed hospital record systems in the United States raised alerts on eighteen percent of everyone admitted, and the clinicians did what people always do with an instrument that fires on situations it cannot read. They learned to click through. Alert fatigue is not a weakness in the humans; it is the accurate response to a machine claiming more authority than its evidence supports, and every noisy check in a build teaches the same lesson at a smaller scale, one dismissed warning at a time, until the morning the real one arrives and is dismissed with the rest. A machine that fails only on its unambiguous half gives up coverage it never honestly had and keeps the thing worth more, which is the right to be believed the next time it says no.