Correct the classifier baseline after tokenizer repair (V-704)

2026-08-13 01:27:13 +04:00
parent 2cf8b7e1b5
commit 8035a317d2
3 changed files with 88 additions and 8 deletions
@@ -140,10 +140,11 @@ it is deliberate.** It guesses, so naming `SourceWorld` drops it. **Only a stage
 0 grammar may drop it** (owner's call, V-666). `queryWalk` reads
 `Decision.SourceAnchored` for the source marked `boundary: true` and no other.

-Judge a routing change against the classifier (76.0% intent, 36.4% destination)
-and the resident model (80.2% intent), since those always answer. The fixture
-has grown from 77 cases to 96, so a number compares only to another number on
-the same fixture.
+Judge a routing change against the classifier and the resident model, since
+those always answer. **Their scores live in `docs/routing.md`, never here.** A
+pair copied into this file goes stale silently. The fixture has changed size
+more than once, so a number compares only to another number on the same
+fixture.

 ## Language: model output and Russian