◀ THE FOLD0ROOT.AI // WORLD II · GLITCH · UNDEFINED BEHAVIOR◆ .dlw.fold
THE FOLD / GLITCH / UNDEFINED BEHAVIOR / A GUESS WEARING SYNTAX

A GUESS WEARING SYNTAX

a selector that graded the wrong row
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
A verifier looked up a row with .find() and a loose pattern. The pattern matched two rows; .find() silently returned the first. So the assertion graded a row it was never aimed at — and reported a correct claim as wrong. Trusting it, the fix would have been to downgrade a true stamp. The control would have corrupted the thing it was auditing.

LIT verified live. The regex matches 2 of 2 candidate rows; .find() returns the LIT ladder where the assertion expected the AMBER coincidence. Adding a uniqueness check turns the silent guess into “selector matched 2 rows, expected 1”, and tightening the pattern selects exactly 1.
2 HOW IT WAS WEAVED · AI + HUMAN
David (human) filed it as the third appearance of one disease in three revisions and wrote the rule as a sentence you can check code against: “a selector inside an assertion needs its own uniqueness check. .find() without a matching count is a guess wearing the syntax of a fact.” It is graveyard/05 in the pack, kept rather than hidden.

AVAN (AI) should underline which direction this failure ran. Most control failures are silent passes — the check misses something. This one was a false positive, and it is worse in a specific way: a missed fault leaves you where you were, while a false positive hands you a repair instruction that damages correct work. The control did not merely fail to help; following it would have made the artifact less true.
3 ONE DIMENSION
Two rows, one pattern, one silent choice.
4 TWO DIMENSIONS · INTERACTIVE
Loosen and tighten the selector.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: an arrow that landed on the wrong target.
AVAN’s addition (the inverse-companion): the forward reading is “add a uniqueness check to every selector.” The inverse is that the uniqueness check is itself a selector. It asserts that the count is one, which is a claim about the data that can go stale the moment a row is added — and the failure then arrives as a new false positive rather than as the old silent guess. Read backwards, the disease is not .find(); it is that a test names its subject by description, and every description is a bet that the corpus has not moved.
LIT the regex matches 2 of 2 candidate rows and .find() returns the LIT ladder where the assertion expected the AMBER coincidence; adding a uniqueness check turns the silent guess into 'selector matched 2 rows, expected 1', and tightening the pattern selects exactly 1

FIG David filed it as the third appearance of one disease in three revisions and wrote the rule as a sentence you can check code against: 'a selector inside an assertion needs its own uniqueness check. .find() without a matching count is a guess wearing the syntax of a fact.' It is graveyard/05 in the pack, kept rather than hidden. AVAN underlines which direction this failure ran: most control failures are SILENT PASSES, and this one was a FALSE POSITIVE. A missed fault leaves you where you were; a false positive hands you a repair instruction that damages correct work. Following it would have made the artifact less true.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of UNDEFINED BEHAVIOR · David Lee Wise (ROOT0), with AVAN