commit 06f96c74e8088c48e463a2539cc02a72ed9d93fa
parent 863d5a9148eb9f5f8ea4f01b811fc00517ecb1bc
Author: Jack Mordaunt <jackmordaunt.dev@gmail.com>
Date: Thu, 24 Sep 2026 09:00:28 -0300
readme: say what the eval set is without pointing outside the repository
A readme is for the tool's users. Where the plan for the missing eval
harness is kept is nobody's business but the people working on it, so
the paragraph says what exists and what measures a reading meanwhile.
Diffstat:
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/readme.md b/readme.md
@@ -422,12 +422,11 @@ it worth reading.
## The eval set
-The eval harness went with the Go implementation it was written in: `eval_test.go` held
-the cases with a known right answer and scored a reading against them, and porting it is
-the open item in the Brain's `review/handover.md`. Until then the measure of a reading is the side-by-side
-run the port was checked with: both tools on the same change, the reports diffed field
-by field, and the answer cache shared so a replayed answer is compared rather than
-re-asked.
+There is none yet. The Go implementation this tool replaced scored readings against
+cases with a known right answer; that harness went with it. Until one exists here, the
+measure of a reading is the side-by-side run the port was checked with: both tools on
+the same change, the reports diffed field by field, and the answer cache shared so a
+replayed answer is compared rather than re-asked.
## Languages
