HOW A TILE FINDS HOLES : On the Architecture, the Declared Class, and the Scan That Does Not Fire a Forest

The finding is a gift. Thirty-five thousand exploitable holes in systems that a patch cycle had declared closed. They were there. https://www.threads.com/share/BAerLGcetI They could have been used. A tool found them.The gift carries a bill, and the bill is architectural. The scan fires at everything, because it can. It searches an unbounded space, so it produces findings in volume and fabrications in proportion. The best reported false-positive rate for a frontier model hunting vulnerabilities is roughly 9.4 percent, which on 35,000 findings is something on the order of 3,300 that are not what they claim to be. This paper states the architecture first, because the rest of the paper depends on it. It then states how a bounded tile would find holes: not by firing a forest, but by reading against a signed pattern set and reporting what it recognises, or refusing. The elegance is the restraint. The tile does not search. It does not generate. It matches, or itrefuses. That is why it does not fabricate and why it does not carry the data-centre cost. Andthat is why it will never find what nobody specified — which is the whole reason the scanner exists.