claude
3024f76e5f
Clarify is not a value of intent. It is a second question over the same pooled vector: can Maven act on this at all. The eight want_clarify fixture cases sat outside every number the heads measured, because a softmax has no clarify class. gen_clarify.py makes the class the corpus lacks. Every existing row was generated FOR an intent, so every one is answerable. The router-prompt agreement filter cannot work here, because routeGrammar has no clarify value and a generated line always agrees with itself. A judge replaces it. The first judge called 24 of 40 answerable rows underspecified. It judged against a generic assistant, one that asks where about lunch. Restating Maven's contract took that to 16 of 60, with all eight fixture cases caught. Three seeds: 7.0 of 8 caught, 2.3 false of 88. The cascade today misses 1 and produces 2. Confidence separates too, 0.851 right against 0.604 wrong.