Skip to content

feat(gates): ground judge verdicts in the diff (arXiv:2606.28050) + 2026-06-29 feed triage - #413

Merged
elementalcollision merged 1 commit into
mainfrom
feat/judge-prompt-grounding-2606.28050
Jun 29, 2026
Merged

elementalcollision merged 1 commit into
mainfrom
feat/judge-prompt-grounding-2606.28050

Conversation

@elementalcollision

@elementalcollision elementalcollision commented Jun 29, 2026 •

Copy link
Copy Markdown
Owner

From the 2026-06-29 arXiv triage: "Can LLMs Judge Better Than They Generate?" (2606.28050) finds judges attend to context 3–5× less than generators and barely read the candidate, with eval-tuning inducing over-acceptance — a direct hit on our judge-heavy gate stack.

Audit → fix. The witness approval path required no grounding (skim-approve hole); the critic rationale didn't force engaging the diff. Conservative prompt-only hardening on both: read the whole diff first; approved=true asserts the real changed lines were checked; the witness summary must state what the diff changes (grounds approvals); the critic rationale must cite specific changed lines. No schema change.

Regression-checked via critic-calibrate: hardened 93% / 0 false-approve / 2 false-reject vs baseline 89% / 0 / 3 — false-approve held at 0, false-rejects didn't rise. Honest: single-shot n=28, so it's no regression, not a measured win (the benchmark doesn't exercise the skim-approve failure the change targets).

Also logs the curated 2026-06-29 feed triage to mind/research/ — the two relevant papers (this one + "Govern the Repository, Not the Agent") and the GitHub-issues source reframed as foreign-PR fuel (gated on allowlisting + the B.4 envelope).

Full suite 3078 passed, ruff clean.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

🤖 Generated with Claude Code


Open with GitKraken

…eed triage

ArXiv 2026-06-29 triage surfaced "Can LLMs Judge Better Than They Generate?"
(2606.28050): judges attend to context 3-5x less than generators and barely read
the candidate, and eval-tuning induces over-acceptance. Audited our judge prompts:
the witness APPROVAL path required no grounding (skim-approve hole) and the critic
rationale didn't force engaging the diff.

Conservative, prompt-only grounding hardening on both: read the whole diff before
deciding; approved=true asserts you checked the real changed lines; the witness
summary must state what the diff changes; the critic rationale must cite specific
changed lines. No schema change. Regression-checked via critic-calibrate — hardened
93% / 0 false-approve / 2 false-reject vs baseline 89% / 0 / 3 (false-approve held
at 0; within-noise, so: no regression, not a measured win). Full suite 3078 passed.

Also logs the curated 2026-06-29 feed triage to mind/research (the two relevant
papers; the GitHub-issues source reframed as foreign-PR fuel, gated on allowlisting).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@elementalcollision
elementalcollision merged commit 8a1e371 into main Jun 29, 2026
1 check passed
@elementalcollision
elementalcollision deleted the feat/judge-prompt-grounding-2606.28050 branch June 29, 2026 12:28
elementalcollision added a commit that referenced this pull request Jun 29, 2026
…eign issue (#414)

Chronicle entry for the day: (1) arXiv:2606.28050 audited our own judge stack and
exposed the witness approval-path skim-and-approve hole → diff-grounding hardening,
regression-checked (#413); (2) first externally-filed foreign issue resolved as
Chimera — safetensorstogguf#6 (llama.cpp Model→ModelBase), diagnosed + fixed as a
draft PR with the can't-run-it boundary named. Reach plus honesty.

Docs-only under mind/**.

Co-authored-by: Chimera-Agent <agent@chimera.local>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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