Skip to content

grants: 馃悰 Run the grant judge on the review specialty (gpt-6-luna low) - #276

Merged
yasyf merged 1 commit into
mainfrom
fix/grants-judge-review
Oct 3, 2026
Merged

yasyf merged 1 commit into
mainfrom
fix/grants-judge-review

Conversation

@yasyf

@yasyf yasyf commented Oct 3, 2026

Copy link
Copy Markdown
Owner

Why

Judge in #275 defaulted to the general specialty. On this host that serves the small tier on Claude haiku. Every other capt-hook judge uses review, which serves gpt-6-luna at low effort, the model the owner ruled for the Slack write judge.

What

  • Judge.specialty now defaults to review.
  • A test pins the default Judge to gpt-6-luna:low.

Evidence

Replays of the recorded Slack writes against v12.80.0 ran on haiku. They refused the #alerts-api not-ours reply in 2 of 4 runs and hit 5-attempt structured-output failures. The same reply passed 3 of 3 on luna before the migration.

Context: every capt-hook judge defaults to the review specialty, which serves gpt-6-luna at low effort.
Summary: Judge now defaults to review instead of general; a test pins it to gpt-6-luna:low.
Motivation: the general specialty served the Slack grant judge on Claude haiku, which refused an allowed alert-thread reply and failed structured output in replays.
Details: an explicit specialty or model on a Judge still overrides the default.
@yasyf
yasyf merged commit 81a8334 into main Oct 3, 2026
23 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