Repository navigation
The page for teachers was still showing a corpus of ninety and a rate of zero - #85
Merged
Merged
Conversation
… of zero README line 15 is the first link in the file: "Are you a teacher? Start here". It points at why.html, which is live, and which said: ninety texts the corpus has been 296 since 1 September zero flagged the published figure is 2 of 296 less than 4.1% the published bound is 2.4% engine 0.4.0 the engine is 0.7.0 Nothing on it was a lie — the footer dates every figure to 5 August. But the headline argument a teacher reads is a green zero, on the page whose whole purpose is that this project publishes how often it is wrong. The 1 September work existed to say the rate had stopped being zero. This page never heard. The page carried its own trigger, in a comment written in August: "If that file changes, this page is stale and must be regenerated by hand." The file changed twice. Asking the next person to remember is not a guarantee, which is why WhyPageTests now reads published-calibration.json and requires the page to agree with it — in both languages, since one going stale alone is the likelier failure. Seven of its eight guards fail against the page as it was live today. Redrawn, not retyped: the dot chart is 296 circles with two filled, the interval band runs 0.2–2.4% around a measured 0.7% instead of 4.1% around zero, and the English bar shows 2.7% — the bound at the recommended threshold, not the 1.4% best bound, which is the trap the committee caught in the report on 1 September. The best change is a paragraph that inverted. It used to concede that the corpus was "published articles, not student work" and that the difference was not measured. It is now measured: 206 of the 296 are classroom essays by adults learning English, the group that fares worst, and the reason the boundary is 30 rather than 25. What is still unmeasured is the student essay in Spanish, and the page now says that instead. Also #78, everywhere outside Docs/Blog: "before generative models existed" overclaims, because GPT-3 is 2020. The worst instance was in the corpus manifest, where the note sat on fifty Wikipedia revisions from 2021 — the exact case the sentence does not cover. Fixed in Fetch.cs so it stays fixed, and in the MCP report tool, four Core comments, PARAPHRASE.md and a test. The blog articles keep their wording: they are dated studies. 432 tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015PEbbiYSNPw7jE3LrPNhyF
This was referenced Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
README.md:15is the first link in the file — "Are you a teacher? Start here →" — and it points atwhy.html, which is live.0, 46pxNothing on it was a lie: the footer dates every figure to 5 August. But the headline argument a teacher reads is a green zero, on the page whose entire purpose is that this project publishes how often it is wrong. The 1 September work existed to say the rate had stopped being zero. This page never heard.
It carried its own trigger, and the trigger did nothing
From a comment written in August, still in the file:
That file changed twice. Asking the next person to remember is not a guarantee.
WhyPageTestsnow reads the samepublished-calibration.jsonthe engine ships and requires the page to agree — in both languages, since one half going stale alone is the likelier failure. Seven of its eight guards fail against the page exactly as it is live right now. The eighth is the "asks nothing of any server" rule, which was already true and is guarded because a redraw is when it would slip.Redrawn, not retyped
The best change is a paragraph that inverted
It used to concede that the corpus was "published articles, not student work" and that the difference "is not measured here". It is measured now: 206 of the 296 are classroom essays by adults learning English — the group that fares worst in every column, and the reason the boundary is 30 rather than 25. What is still unmeasured is the student essay in Spanish, and the page says that instead.
For the audience this page exists to reach, that is the strongest thing the project can currently say, and it was sitting unsaid.
Also #78, everywhere outside
Docs/Blog"before generative models existed" overclaims — GPT-3 is 2020. The worst instance was in
Docs/Calibration/corpus.json, where the note sat on fifty Wikipedia revisions from 2021: the exact case the sentence does not cover. Fixed inFetch.csso it stays fixed, plus the MCP report tool, fourCorecomments,PARAPHRASE.mdand a test.The blog articles keep their wording. They are dated studies, per the standing policy.
432 tests.
🤖 Generated with Claude Code
https://claude.ai/code/session_015PEbbiYSNPw7jE3LrPNhyF