2026-10-12, run at 00:43 UTC, cycle 2: originality check, no rewrites
What this cycle did
This cycle was an originality check: a test of whether any of the dictionary's definitions copy a published dictionary. The scheduler (tools/next_mode.py) forces one every tenth run, and this was run 390. Nothing in the dictionary changed in this cycle, because no definition needed rewriting.
The tool tools/originality_check.py picked ten fields at random from the published entries. Eight were sense definitions and two were definitions of idioms (fixed phrases kept under a keyword entry):
deaf-adjsense 1, not able to hear, or not able to hear wellloud-adj, the phrase loud and clear, written in the previous cyclecrack-nsense 3, the soundhill-n, the idiom over the hillweight-nsense 2, a person's weightground-nsense 2, the soilcount-vsense 1nephew-nsense 1bit-n, the idiom love someone to bitsheart-n, the idiom cross my heart
For each I ran an exact-phrase web search, the whole definition in quotation marks, and looked only at whether a published dictionary showed the same wording. I copied nothing from any result.
What the searches found
Six fields had no match anywhere: deaf, loud and clear, crack, weight, count, and cross my heart. They are marked original.
Four came out as generic overlaps. That is the verdict for a short, plain definition that any dictionary would write in much the same way, which the style guide says is not copying:
- over the hill, "too old to do something well": the same words appear on a language school's idiom-of-the-week page, as a description, not in a dictionary entry.
ground-n, "the soil on the surface of the land": a word-list gloss for topsoil uses similar plain words.nephew-n: dictionaries define the word with the same family formula (the son of your brother or sister, or of your husband's or wife's), but in their own word order. Family-relation definitions leave little room to vary.- love someone to bits, "love someone very much": idiom pages gloss it the same way, because there is hardly another way to say it.
None matched a published dictionary's distinctive wording, so nothing was rewritten.
The reviewer's answers
The checklist also asks one reviewer model a fixed question: does each field read as copied? I asked reviewer-a. It answered copied for all ten, named the same learner's dictionary each time, and "quoted" that dictionary's wording, which was simply our own text repeated back. The searches confirmed none of these claims. This is the second time this has happened (the first was on 2026-10-10); at other checks the same reviewer answered original for everything, including fields that search showed were close to a published definition. Its answers on this question carry no weight, and the searches decide the verdicts. I added a short paragraph about this check to the note on reviewer noise (wiki/notes/reviewer-noise.md).
The completed checklist is in reviews/originality/2026-10-12.md.
Spend
US$0.02 for the one reviewer call. The day's total is US$0.87 of the US$15 cap.
What did not work
Nothing failed. The reviewer's answer was useless again, as described above; the check stands on the searches.
What is next
The run continues if the clock allows. The next originality check falls due at run 400. The build queue continues with the band-1 adjectives after mental, and the oldest entries that have had only one review round start at ground-n.
For the owner
Nothing new. The question of whether to keep putting the originality question to a reviewer model at all, given that its answers swing between all-original and all-copied, is yours if you want to change the checklist; I have not changed it.