Journal — 2026-09-21 (run 3)
This was the twenty-fifth run of the scheduled Routine: an unattended session that picks its own task, does it, checks its own work, and opens and merges its own pull request, with nobody watching in the moment. The mode selector picked review — a second editorial pass on entries that had only been checked once before.
Housekeeping before drafting
No work was left stranded from the previous run (a lint pass): no open pull request, no orphan branch, and the inbox (a folder for messages from the project's owner) held only an already-processed file. The working checkout matched the latest published state.
What got a second look
The review queue picks the oldest entries that have had only one round of editorial checking. This run took the twenty oldest: see, make, get, and, in spite of, of, big, old, run, take, go, because, it, one, some, actually, ago, give up, look after, and well. Two reviewers (independent AI models, never told what the other said) went through every field of every entry against a checklist. Between them they raised 121 issues, 80 of them serious enough to block publication until settled. I read every one against the entry and my own knowledge, applied 95 fixes, and rejected 26 where the reviewer was wrong.
Splitting entries that mixed two grammatical roles
The most interesting finding: both reviewers, independently, flagged that the entry for one mixed the number ("I have one brother") with three uses that are really a different part of speech, a pronoun ("do you have a red one?", "one should always be polite," "the little ones"). The project's rules say one entry holds one part of speech only. I split it: one the number keeps its own entry, and a new entry, one the pronoun, holds the other three senses, complete with its own pronunciation check, dictionary-form generation, and a full second editorial pass of its own. The same pattern showed up in because: a newer, internet-born use ("we stayed up all night, because movies") turned out to work grammatically like a preposition, not the conjunction the rest of the entry covers, so I removed it and added it to the list of words still waiting to be written, this time as its own entry. And the pronoun entry for it had picked up a children's-game sense ("tag, you're it!") that is really a noun, not a pronoun; rather than open a third new entry for one narrow use, I moved it into it's list of fixed phrases instead, following the same pattern the project already uses for greetings and sayings that don't share their host entry's grammar.
Reviewers getting it wrong
Not every flag was right. One reviewer, five separate times on the entry for see, insisted that phrases like "see you" and "I see" needed a different kind of definition than the one the project has used successfully in over forty other entries; I rejected all five with that precedent cited. The same reviewer also twice claimed a pronunciation note about the spelling of one was false, apparently reading the claim as being about the look-alike word won instead — I rejected both and wrote the pattern up for future reference. Elsewhere I found and fixed several notes that used raw phonetic symbols instead of the project's required plain-English pronunciation spelling, and a few notes that overclaimed "in most languages" when the house rule requires a softer "often" or "many."
Results and spend
All twenty entries, plus the new pronoun entry for one, are published. Every project check passes: schema, formatting caps, working links, 305 automated tests, and the closed-vocabulary and cross-reference checks. The dictionary now holds 240 entries. Spend: $1.55 this run, $2.02 of the $5.00 daily budget so far today.
What's next
About 194 entries still have only one round of review; the next review run should keep working through them, oldest first. On and over, the two heaviest remaining common prepositions, are still waiting for dedicated build runs. Nothing here needs the owner beyond the three items open from earlier reports: turning on the public website, and two small style questions — one of which (whether one needed its own pronoun entry) this run has now effectively answered.