Bind benchmark evidence to native usage - #182
Merged
Merged
Conversation
Authoritative cohorts compare response usage with provider-native generation tokens and disable the benchmark harness outer retry. Every captured provider generation is therefore represented in the attested report, while exploratory live screens retain their resilience retry.
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.
Authoritative benchmark cohorts now compare response usage with OpenRouter’s native generation-token fields and pin the benchmark harness’s outer case retry to zero, so every captured provider generation is represented in the attested report. Exploratory live screens retain their resilience retry, while calibration and release evidence fail instead of hiding retry spend.