Skip to content

fix(eval): score what a reply means, not how it is typed - #57

Merged
buzzgreyday merged 1 commit into
developmentfrom
fix/eval-scoring
Oct 11, 2026
Merged

buzzgreyday merged 1 commit into
developmentfrom
fix/eval-scoring

Conversation

@buzzgreyday

Copy link
Copy Markdown
Owner

The gpt-6-luna vs gpt-4.1-mini comparison scored Luna 19–21/26 and mini 23–25/26; read by hand, every reply was correct. Scorer fixes:

  • Normalise replies before matching (curly quotes, n't → not), plus "does not have any mention".
  • Q8 ("How long at iEDI?") uses a start month (since) and judges each answer as of its own date — --rescore reads it from the transcript filename.
  • Q19/Q24/Q26 accept the substance in other words.

Re-scored: both models 26/26 on every pass; no previously-ok verdict became wrong in any of the 31 saved runs. New tests/test_eval_scoring.py; backend 234 passed, mypy clean. Eval tooling only — no app change.

🤖 Generated with Claude Code

The gpt-6-luna vs gpt-4.1-mini comparison scored Luna 19-21/26 and mini
23-25/26; read by hand, every reply was right. The scorer was wrong:

- Replies are normalised before matching: curly quotes straightened and "n't"
  spelt " not", so "isn’t listed" and "aren’t on file" meet the existing
  "not listed" / "not on file" patterns. "does not have any mention" added.
- "How long has he been at iEDI?" takes a start month (`since`) instead of a
  fixed "11 months": the accepted durations are worked out on the day
  (duration_phrases), and --rescore judges each saved run as of the date in
  its filename, so August's correct "11 months" stays correct.
- Q19 accepts "has not had mentoring"; Q24 and Q26 accept the substance in
  other words ("regular", "daily"; "assembl…", "left the warehouse").

Re-scored, both models get 26/26 on every pass; no reply that was "ok" before
is marked wrong now, in any of the 31 saved runs. New tests:
tests/test_eval_scoring.py.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@buzzgreyday
buzzgreyday merged commit 70f05f9 into development Oct 11, 2026
15 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