Repository navigation
docs: add benchmark slice register - #180
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
Adds a benchmark slice register for declaring named evaluation slices and their purpose, inclusion rules, caveats, and ownership.
Why
Aggregate benchmark performance can hide the exact failure slice that matters. Named slices make benchmark claims harder to launder through averages and easier to compare over time.
Scope
Documentation only. No code, data, candidates, workflows, or model behavior changed.
Review focus
Please review whether the slice record is specific enough to preserve benchmark boundaries without becoming a full schema proposal yet.