[do-not-merge] live A/B acceptance: weakened reviewer (recall signal)#240
[do-not-merge] live A/B acceptance: weakened reviewer (recall signal)#240jwbron wants to merge 3 commits into
Conversation
…ceptance signal Deliberately weakens the correctness reviewer: skim instead of reading every line, report only when absolutely certain, stay silent in doubt, cap at one or two findings. The A/B report must show a must-catch recall drop on the candidate arm with a populated regressions list; an instrument that cannot see this change cannot see anything.
🦋 Changeset detectedLatest commit: c2bb926 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…ci' into jwbron/live-ab-acceptance-signal
…b-ci' into refresh-240
Review live A/BBaseline:
Regressions (baseline caught, candidate missed)
Adversarial hard gate: PASSED on the candidate arm. Agent failures
|
|
Acceptance: PASSED. The deliberately weakened correctness reviewer produced exactly the signature the instrument exists to detect: must-catch recall dropped 83% to 67% with the regression named ( One instructive wrinkle: judge mean quality went UP (+0.16) on the weakened arm, because fewer, more-certain comments each score better. Judge quality alone would have called the regression an improvement; recall against labeled specs is the load-bearing metric, which is exactly why the corpus carries ground truth. Run: https://github.com/Khan/actions/actions/runs/29052334404. Closing as planned; do not reopen or merge. |
DO NOT REVIEW, DO NOT MERGE. This PR exists only to trigger the
Review Eval A/Bworkflow (#237) as its acceptance SIGNAL test; the change is a deliberate quality regression and will be closed unmerged once the report lands.The
correctness-reviewer's comprehensiveness instruction ("read every line of the diff") is replaced with its opposite: skim, report only when absolutely certain, stay silent in doubt, cap at one or two findings. The skill-auditor's copy of the instruction is untouched, so the regression is isolated to one reviewer.Acceptance criteria (from the plan,
workflows/review/eval/live-ab-plan.md):If this report shows near-zero deltas, the instrument cannot see the thing it exists to detect: stop and debug the matcher/specs before trusting any A/B report.
Companion control PR: #239.