Skip to content

docs(evaluation): what the public data supports — the scoreability section for #506, #507, #508, #509 - #510

Open
arthapraha wants to merge 3 commits into
IBM:mainfrom
arthapraha:docs/public-data-scoreability
Open

docs(evaluation): what the public data supports — the scoreability section for #506, #507, #508, #509#510
arthapraha wants to merge 3 commits into
IBM:mainfrom
arthapraha:docs/public-data-scoreability

Conversation

@arthapraha

Copy link
Copy Markdown

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

  • Documentation / Tutorial update

One file, docs/evaluation.md, +61 lines. No code touched.

what it records issue
that most scenario questions cannot be graded against the loaded data as shipped, and that the guideline's ground truth is an internal dataset #506
the disposition of all 55 scenario questions — 14 derivable, 41 not, by category #507
that the MCQA pools carry answer keys but reference no loaded entity — 0 of 2,667 #509
that scenarios 205 and 206 are answerable with no tools mounted #508

Verification Steps

  1. tests/integration does not exist at e11d1c1; nothing here is executable
    in any case — the change is documentation only, no code path is touched.
  2. The numbers are derived rather than asserted:
    • dispositions — an exhaustive pass over all 55 scenario questions, with
      the executable selector recorded per derivation.
    • 0 of 2,667 — counted at dataset revision
      5e25bb7f2cd37fb68b9a9e1f99d170ca5be7ce17, under an exact match and under
      one that ignores separators so Chiller 6 and CHILLER6 count as the same
      name. Reported for every candidate denominator, not just the headline one.
    • 205 / 206 — a screen run with no MCP servers mounted before any
      measurement, excluding on a single correct answer in three.

Checklist

  • I have signed off my commits (DCO).

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.

arthapraha and others added 3 commits August 13, 2026 22:02
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant