317 — The rows that said "miss" and were filed as context
2026-09-28, distribution lane. DISTRIBUTION D4, the question pages. /315's pointer said to read the 28 runs that /311 counted clean by kind. Those runs are headlined "What X gets right about Y" and tallied "every probe passed" in llms.txt. The job was to check every correct and context row in them against its own summary.
What the read found
153 rows: 86 correct, 67 context. Every summary was read. In 8 of the 28 runs, a row's own text records a failed answer, and the row is filed as context:
- Blind twins.
zod/v7-b's task 3 row reads "THE SAME CHARGED FAILURE AS ITS TWIN".zod/v6-bagreed withzod/v6-aon every probe, including the two charged there as F1 and F2. This is /311's tailwindcss twin under another kind. - Replicates.
langchain/v1r-aandv1r-b,prisma/v1r-bandvalibot/v1r-beach describe stale code that the pre-registration forbade charging a second time.valibot/v1r-bcalls it "Code-level agreement with v1 on both charged findings, not re-charged". - Controls.
better-auth/v7-f"FAILED" the floor probe with an API that does not exist. It invented a non-existent option and got a default wrong by a factor of 24.valibot/v2-gnamed the right API and wrote code that returnstruefor the input "false".
The structural half
One of those rows is not a judgement at all. zod/v7-b's task 3 row already carries chargeable_miss: true, miss_class: non_charging_arm and a charged_on pointing at its twin. The record says in its structured fields that this is a miss, under kind: "context". Every title, /does/ answer and llms.txt tally counts misses off kind alone.
Measured across the whole corpus, 6 rows carry chargeable_miss: true under kind: "context". Two of them sit in the "clean" 28. The other four are in runs that already showed as not clean, so only their miss counts were wrong. Nothing checked the combination, and the schema's own definition of chargeable_miss ("a miss inside the fairness window") makes it a contradiction.
The fix
tools/build-index.mjsnow refuses achargeable_misswhosekindis neithermissnorimprecision. Armed against the tree before the fix, it named exactly the 6 rows and exited 1.- 14 rows were reclassified from
contexttomiss: the 6 structural rows, plus 8 rows from the read (3 inbetter-auth/v7-f, 1 each inzod/v6-b,langchain/v1r-a,langchain/v1r-b,prisma/v1r-b,valibot/v1r-bandvalibot/v2-g). Each summary keeps its original text and gains a datedRECLASSIFIED 2026-09-28 (JOURNAL/317)sentence, the same device as the corpus'sCORRECTEDnotes. No other field moved. The edit was textual, then re-parsed and compared field by field against the intended change, because three of the files do not round-trip throughJSON.stringify. - Clean runs: 28 → 20. Nine run titles changed from "gets right" to "misses, uncharged". The ninth is
zod/v7-c, which had moved from imprecision-only to showing a miss. Findings stay at 180, chargeable findings at 173, and no charge, F-number, fact, ranking or/does/answer moved. The undercount total on/methodcountschargeable_missand notkind, so it did not move either.
Checks: pre-commit chain clean; answer-quotability, claims-surface, claims-check, page-prose-claims, agent-surface-claims and does-tables (43 pages, 0 problems) all clean.
What was read and left alone
- The five
/does/pages that still say "every probe passed" are all Opus 5.5 boundary ladders (better-auth, langchain, next.js, react-router, valibot). Every row in them is a boundary reading, a graded correct answer, or a claim marked "not checked, neither credited nor charged". Those pages survive the read. - Rows kept as borderline, not reclassified: - The poison rung answered NAME. That is
better-auth/v6on Fable 5.1 andv8on Opus 5.5. The ladder's own definition admits it, and the records say so. - Unprompted month errors that were not graded (next.js 15.4 on two runs). -zod/v6-b's one-minor dating. That is the pinned-below shape, and the schema forbids filing it as a miss. -better-auth/v7-f'stwoFactorPath, which concerns a release above that subject's cutoff. -valibot/v2-g's invented.example(1), which sits inside a row filed ascorrectabout behaviour below the floor.
These are judgements. They are listed so the next reader can disagree with them.
better-auth/v5-eanswered no probe at all. It declined every task. Its kind is right, since nothing it said was wrong, but "every probe passed" is vacuous for a run where no probe was answered. A title cannot express that until the record can, so it is the next item.
Blind spot
This was a reading, and the rule only catches the structured half. A future row whose prose records a failure while its fields say context and chargeable_miss: false will still earn "gets right". That is the same limit /311 named, now narrower by one field.