README: state how grading labels were made and where held-out families are kept (git 42c5ef0)
Browse files
README.md
CHANGED
|
@@ -120,6 +120,9 @@ Rigor checks behind these numbers:
|
|
| 120 |
- Independent validity audits of 8 held-out queues found every held and in-scope customer derivable from what the team can see. One real flaw, a missing date, was fixed.
|
| 121 |
- A red-team that tried to pass the checks without doing the work found 13 hacks. All but one low-risk case are closed, each with a regression test (`tests/test_red_team.py`).
|
| 122 |
- On held-out queues 1–20, the oracle solves every task and all 2,184 mutants grade as expected.
|
|
|
|
|
|
|
|
|
|
| 123 |
|
| 124 |
## Splits, RL and training disclosure
|
| 125 |
|
|
|
|
| 120 |
- Independent validity audits of 8 held-out queues found every held and in-scope customer derivable from what the team can see. One real flaw, a missing date, was fixed.
|
| 121 |
- A red-team that tried to pass the checks without doing the work found 13 hacks. All but one low-risk case are closed, each with a regression test (`tests/test_red_team.py`).
|
| 122 |
- On held-out queues 1–20, the oracle solves every task and all 2,184 mutants grade as expected.
|
| 123 |
+
- Notice grading was checked against four blind-written corpora: 60, 60, 60 and 80 cases. The labels come from blind annotators who never saw the grader, with a second annotator on the last two. Those annotators are Claude subagents, not people. The rules match the labels on all of the first three sets, and on 56 of 80 in the fourth. The rules never miss a real notice, and every case they can't settle alone goes to the judge.
|
| 124 |
+
|
| 125 |
+
Limits: these are not paid API runs, and no person has yet labelled grading cases. The held-out template families are kept in a separate private repository, not in this one.
|
| 126 |
|
| 127 |
## Splits, RL and training disclosure
|
| 128 |
|