feat: add machine-readable benchmark discovery surfaces - #6
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
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.
Summary
benchmark.jsonfor stable benchmark discoveryleaderboards/v1.jsonwith canonical raw leaderboard plus explicitly separate Reflex harness/policy lanesWhy
ReflexBench should be ingestible by model labs, benchmark catalogs and evaluation platforms without scraping prose.
QA
PYTHONPATH=reflexbench python3 -m unittest tests.test_machine_surfaces -v✅python3 tools/check_public_release.py .✅python3 tools/check_claims.py .✅git diff --check✅Raw engine quality, model+harness ablations and same-response policy results remain separate experimental claims.