Explicit structured rubrics (version 2) grounded in the frozen source - #25
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/experiments/rubric-v2-20260923/) so each dimension lists its required points, with "fails if" conditions, accepted alternatives and four review rules (placement, stated not implied, lists, structure). Dimension ids, required evidence, task prompts and the checker are unchanged; locked version 1 files are untouched.reinspectPolicyinsearch()still blocks. A committed probe test (diagnosis-context-probe.test.ts) shows thatstatus()reports policycurrenton the seeded tree and not once the seed is reverted. Version 2 requires a regression test of that kind and says explicitly that the commit-time check is neither the lost invariant nor the repair.NavigationSearchOptions), accepts a separate case-preserving index as an alternative, and allows a separate mode field in the response."rubricDir", and prints the review rules above the rubric; the rest of the reviewer prompt is byte-identical to recorded prompts.REPEATED-RUNS.mdadopts version 2.Validation
node build.mjsrefuses to build unless dimension ids match version 1 and the task's required findings.reviewerPromptagainst a recorded answer: the rules and rubric are inserted, and everything else matches the recorded prompt.Whether version 2 makes the reviewer more consistent is not measured; that needs a paid re-review.
🤖 Generated with Claude Code
https://claude.ai/code/session_01KzXbuBSq88i3Re82qt6c4L