Skip to content

docs: describe held-out scoring as the code performs it - #5

Merged
rustfuture merged 1 commit into
mainfrom
docs/claim-accuracy
Sep 30, 2026
Merged

rustfuture merged 1 commit into
mainfrom
docs/claim-accuracy

Conversation

@rustfuture

@rustfuture rustfuture commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

Documentation-only.

README.md (feature list) and DESIGN.md (item 5, Held-out Isolation) said the held-out split is "measured once". In rsi_framework/core.py (around lines 500-509) it is scored twice, both after selection ends: once for the baseline policy (baseline_heldout) and once for the final policy (heldout). Both now say the held-out data is scored only after selection ends, once for the baseline policy and once for the final policy. The generated results block in the README is untouched.

Checks run locally (same as .github/workflows/ci.yml): unittest discover (35 tests), python -m rsi_framework.reporting --results results --readme README.md --check (consistent), byte-for-byte replay of first_run.json, history.jsonl, metrics.csv, progress.svg, and benchmark re-run compared modulo runtime_seconds. All pass.

The held-out split is scored twice, both after selection ends: once for the baseline policy and once for the final policy (rsi_framework/core.py). README and DESIGN.md said "measured once".
@rustfuture
rustfuture merged commit 82c67d8 into main Sep 30, 2026
1 check passed
@rustfuture
rustfuture deleted the docs/claim-accuracy branch October 2, 2026 06:27
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