Add greenproof to §8 (verifiers)#50
Open
zxyasfas wants to merge 1 commit into
Open
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
1 participant
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.
greenproof re-runs an agent's current code against the tests it started with (snapshotted before the agent touched anything) to check whether a claimed-green suite is real or only green because the tests got edited. No LLM in the loop — it's a deterministic re-execution, so it sidesteps the judge-reliability problem this section is about rather than adding another judge. Tested on 15 hand-built scenarios across 5 real Python repos (self-reported, not an independent benchmark — noted as such in the entry).