Why does every accept an empty cleaned string as all letters?

Measured inputs and outputs

These are locally constructed test strings, not evidence that Claude inserts these characters. We executed the saved homepage script snapshot with a minimal DOM harness and compared exact strings. The invisible-checkbox state and dash mode appear in each row. The observations below test this page's specific question. Destination observations run independently on the exact input and cleaned strings in the recorded Node runtime. We make no detector-score or statistical-watermark removal claim.

The true result has no successful letter check behind it

Our marker-only string initially becomes a one-element array whose element fails the ASCII uppercase predicate. Cleanup removes that element entirely. The empty array then reports allLetters true with calls equal to zero. It also reports count zero, nonemptyAndLetters false and hasLetter false. Keeping those fields together demonstrates exactly what the true result establishes: no present element failed. It does not establish that a letter was supplied. The cleaner changes the text, while the validator determines what acceptance means.

Ordinary controls separate presence from universal acceptance

AB passes every after two predicate calls and also passes the explicit nonempty check. A1 fails every but passes hasLetter because its first element is an accepted letter. The empty-string control reproduces every true, no calls and hasLetter false before any cleanup. These three outcomes show why neither every alone nor some alone expresses the combined requirement that input be present and every element be acceptable. Our diagnostic short-circuit expression explicitly combines count with the universal result rather than silently treating empty content as a required field.

Define the grammar as well as the minimum content

The predicate intentionally accepts only ASCII uppercase letters. It is not a general English validator, Unicode name policy or test for meaningful writing. A destination that permits lowercase letters, combining marks or other scripts must choose a different predicate and test it separately. The empty-input issue remains a distinct requirement from whatever character set is selected. The observer constructs a dense array from each supplied string and therefore makes no claim about holes in sparse arrays. Callback counts belong to these exact arrays and this exact predicate.

A genuine question motivates an independent experiment

A historical public question asks why Array.prototype.every returns true on an empty array; our Q&A notes link that question without copying its answers. The new evidence here measures how the actual homepage deletion can create that empty state and compares four explicit diagnostics. All strings and the predicate were authored locally. There is no Claude sample, external form submission or detector result. A validation boolean is an application decision, not evidence that an invisible formatting character was a watermark or that model-level marking has disappeared.

Reproduce this test

Save reproduce.cjs and tested-app.js in the same folder. Run the command below with Node.js. The harness prints its runtime, script SHA-256 and every measured row. Compare those rows with the original record. Using a newer script or runtime creates a new experiment; retain the version information with your rerun.

node reproduce.cjs