18e1127375
The two hard gates are pass/fail, not rates: any scope leak or attribution error is a bug. The report names the offending cases and prints a greppable GATES: PASSED / FAILED line, since this dataset is an acceptance gate rather than a number to watch drift on. The attribution gate covers only families where exactly one database is correct. B5 is answered by two, so citing both is right there and policing it would report a bug that is not one. Surface coverage comes from the model's own Python, now carried on the run result: counting executions said how often code ran but never which surface it reached. Coverage is measured, not required, so a surface nothing reaches is a finding about whether it earns its place in the VFS. answer_correct is recorded as a score rather than a boolean, since booleans become assertions and the run reads its accuracy headline from scores. The two gates stay boolean assertions, which is what they are. DatasetSpec grows a report_hook so this lives with the dataset instead of becoming a key check in the shared QA reporting. The reference-config invariant said a dataset with a deterministic evaluator must declare no judge. That is not true here: RefusalJudge runs on any case carrying an answerability label, which B6 and B7 do, so its sampling has to be pinned. The assertion now requires a pinned block wherever a judge runs and allows its absence only as the claim that none does. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_benchmark.py | ||
| test_capability_runner.py | ||
| test_citation_evaluators.py | ||
| test_config.py | ||
| test_conversation_evaluator.py | ||
| test_datasets.py | ||
| test_evaluators.py | ||
| test_mtrag.py | ||
| test_multidb_cases.py | ||
| test_multidb_corpus.py | ||
| test_multidb_evaluators.py | ||
| test_multidb_report.py | ||
| test_numbers.py | ||
| test_reference_configs.py | ||
| test_submission.py | ||