Skip to content

Live eval: --runs, --critic-timeout, and the scorer-tuning rule - #34

Merged
forkrul merged 3 commits into
masterfrom
feat/live-eval-runs
Oct 17, 2026
Merged

forkrul merged 3 commits into
masterfrom
feat/live-eval-runs

Conversation

@forkrul

@forkrul forkrul commented Oct 17, 2026

Copy link
Copy Markdown
Owner

Follow-ups from #27.

  • --runs N sends the corpus N times (replies under run-<k>/) and reports recall per run with mean/min/max, clean-control BLOCKING findings per run, errored cases per run, and each defect's found-rate across runs. One run stays the default and keeps its report shape.
  • --critic-timeout S replaces the fixed 170 s per critic call (opencode hit it about once per run in Make the live critic eval measure something #27). A call that times out is still reported as an errored case, never as clean.
  • Scorer-tuning rule in evals/program.md and docs/reference.md: diagnosis terms added after reading replies must come from a backend other than the one being reported, and the reported run uses a frozen scorer — the lesson from Make the live critic eval measure something #27, where synonyms taken from Claude's replies inflated Claude's rescored number.

Tested with --backend rule-auditor --runs 2 (aggregation, per-run dirs, report) and a single run (unchanged output). Not re-run against live models here. Local: lint, sphinx, eval 100.00.

🤖 Generated with Claude Code

@forkrul
forkrul merged commit 1dc1341 into master Oct 17, 2026
5 checks passed
@forkrul
forkrul deleted the feat/live-eval-runs branch October 17, 2026 13:33
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.

2 participants