docs(evaluation): what the public data supports — the scoreability section for #506, #507, #508, #509 - #510
Open
arthapraha wants to merge 3 commits into
Open
Conversation
Findings 4, 5, 6 and 8 of an external defect report share one request: documentation, not code. The guideline references an internal ground-truth dataset; the public HuggingFace dataset ships questions only. Nothing says so, so every external user rediscovers it from failing runs. Adds a section to docs/evaluation.md giving the disposition of all 55 scenario questions against the database the default manifest loads: 14 derivable, 41 not, across six distinct reasons. Names the practical consequences -- an aggregate over all questions measures gradeability rather than performance; ambiguous sources fail silently where absent data fails loudly; the MCQA pools carry answer keys but reference no loaded entity, so they do not measure tool use. Counts were produced by attempting each derivation against a running instance loaded from the repository's own compose file, not by reading. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Attila <29815676+arthapraha@users.noreply.github.com>
Finding 9. Running each derivable question with no MCP servers mounted, twelve returned nothing usable and two did not: 205 and 206, both TSFM support questions answerable from general model knowledge. Useful as controls, but a system that answers them has not demonstrated tool use. Folded into the same section as findings 4/5/6/8 rather than a separate change: it is the same file, the same paragraph, and the same reader. The scenario set itself is not in this repository -- src/scenarios/huggingface/ holds only an empty readme -- so a documentation note is the available place to say it. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Attila <29815676+arthapraha@users.noreply.github.com>
The section asserted "the public artefacts are not scoreable end-to-end", which is the question the accompanying issue asks the maintainers to answer. Stating our measurement is ours to do; stating their intent is not. Reworded to "as shipped, most scenario questions cannot be graded against the data this repository loads", with the intent question named as separate and left open. Deliberately does not cite the issue number: a shipped doc should still read correctly once that issue is closed. Also gives the MCQA bullet its derived figure -- 0 of 2,667 at dataset revision 5e25bb7f, under both an exact and a separator-insensitive match, so "Chiller 6" and "CHILLER6" count as one name. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Attila <29815676+arthapraha@users.noreply.github.com>
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.
Description
Four issues — #506, #507, #508 and #509 — describe the same thing from different
angles: what the public artefacts do and do not support when used for scoring.
They share a fix location rather than a root cause, so this is one section
rather than four scattered edits, as promised in #506.
It adds a "What the public data supports" section to
docs/evaluation.md,which already describes scoring and is where someone choosing a scorer is
already reading.
Changes
One file,
docs/evaluation.md, +61 lines. No code touched.Verification Steps
tests/integrationdoes not exist ate11d1c1; nothing here is executablein any case — the change is documentation only, no code path is touched.
the executable selector recorded per derivation.
5e25bb7f2cd37fb68b9a9e1f99d170ca5be7ce17, under an exact match and underone that ignores separators so
Chiller 6andCHILLER6count as the samename. Reported for every candidate denominator, not just the headline one.
measurement, excluding on a single correct answer in three.
Checklist
Note
The wording is a proposal, not a position. #506 asks whether the public
artefacts are meant to be scoreable end-to-end without the internal dataset, and
that question is still open — this section deliberately states what we
measured and names the question of intent as separate, rather than answering
it on your behalf.
If the answer to #506 is "the public data is a sample, not a gradeable set",
this section should say so in your words rather than ours. Happy to rewrite
it, move it elsewhere, split it into four, or close this if you would rather
write it yourselves.