2026-10-25 (second report): reviewer A becomes a Claude model

Interactive session 20261025T014638Z-ysf43k, at the owner's request. Mode: setup (an experiment, then a change of reviewer).

What was done

The owner asked whether the two paid reviewers could be replaced by Claude models running inside the owner's Claude subscription. The reviewers are the two outside AI models that check every field of every new entry; they are reached through the OpenRouter service and paid per call.

First, an experiment (experiments/claude-reviewers-v1/README.md). Twenty-eight entries were reviewed by six reviewer setups, all using exactly the review instructions the dictionary already uses:

Each problem a reviewer raised was then judged blind: all the issues for an entry were pooled and shuffled, and the reviewers' names were hidden. A Claude judge decided whether each was right. Because a Claude judge might favour Claude reviewers, the two outside models judged the same pools as a check.

Then, the change the owner chose. Reviewer A, previously an OpenAI model, is now a mid-size Claude model. It runs as a "headless" call: a single command-line request to Claude Code, with no tools and only the review instructions, inside the owner's subscription. Reviewer B, the Google model, is unchanged, so the two reviewers still come from different companies. The tools that call reviewers, record their decisions, and measure their accuracy were updated, and new tests were added. The decision is recorded in wiki/decisions/reviewer-a-claude.md.

What was found

What it means

Reviews should get more accurate, with fewer false alarms to reject, and OpenRouter spending on reviews should fall by roughly a third. A batch of entries takes about as long as before, because the two reviewers now run side by side.

What is next

What needs the owner

All journal entries