Skip to content

Re-judge past validator fixes with today's validator (to a CSV, no writes) - #908

Merged
mircealungu merged 2 commits into
masterfrom
recheck-validator-fixes
Oct 25, 2026
Merged

mircealungu merged 2 commits into
masterfrom
recheck-validator-fixes

Conversation

@mircealungu

@mircealungu mircealungu commented Oct 25, 2026 •

Copy link
Copy Markdown
Member

Roadmap item 2: re-check past validator fixes.

A wrong INVALID heals itself (scheduling and the nightly job re-judge anything not VALID), but a wrong FIX doesn't: the learner moves to a corrected meaning marked VALID, which is never looked at again. "vil sige = mean" (13 Aug 2026) is one.

tools/recheck_validator_fixes.py asks today's validator about each corrected meaning in the sentence the fix was made in, and writes the ones it judges differently to a CSV, most active words first. It writes nothing to the database.

  • One row per (corrected meaning, sentence): 2,977 in prod as of 25 Oct, 9,842 active words on them.
  • The first question goes through the Batch API (half price, ~$23 for all); the validator's own retries (options, card doesn't fit its sentence) are asked live, through the same validate_and_classify as production.
  • Every fix that got a verdict goes into --checked (a file of validation_log ids, default validator_fix_rechecked.txt) and is skipped next run, so the top 300 now and the rest next month don't pay twice. Keep the file between runs.
  • --dry-run counts and estimates; --days, --limit narrow it; --batch-id resumes after an interruption.

Checked: the query on prod (read-only); the batch-then-live flow with fakes; one real request with the batch's parameters ("vil sige" = "mean" → FIX "means").

🤖 Generated with Claude Code

… a CSV

A wrong FIX never heals: the corrected meaning is VALID and never looked at
again. Batch API for the first question; the validator's own retries live.
Writes nothing to the database.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

ArchLens - No architecturally relevant changes to the existing views

…e rest later don't pay twice

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mircealungu
mircealungu merged commit b1df1db into master Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant