Describe reference systems by architecture, not by system name

v1.0.1-addendum.md

@@ -31,15 +31,14 @@ the prompt, with no retrieval and no reasoning.
 
 **Evidence that the leak is exploited, not merely exploitable.** Reference
 systems with no retrieval at all (prompt is `<t={t_query}> {question}\nAnswer:`)
-score at or near 1.0 on the interval slice: a no-retrieval T-GRPO policy scores
-overall EM 0.364 but interval EM 1.000; a no-retrieval SFT baseline scores
-0.305 overall but 0.994 on interval. On retrieval-conditioned reference
-systems, excluding the interval slice moves overall test EM from 0.865 to 0.851
-(CoT), 0.896 to 0.885 (terse), and 0.138 to 0.113 (BM25 vanilla RAG). The
-interval slice also posts the highest values on every retrieval-quality slice
-(TRP 0.376, CCR 0.920, and stale-blind CCR 0.773 where all other operators fall
-to 0.03–0.08), so per-operator retrieval comparisons involving interval are
-contaminated as well.
+score at or near 1.0 on the interval slice: a no-retrieval RL-tuned policy
+scores interval EM 1.000 against 0.364 overall, and a no-retrieval supervised
+baseline 0.994 against 0.305. On retrieval-conditioned reference systems,
+excluding the interval slice moves overall test EM by −0.014 and −0.011, and
+BM25 vanilla RAG from 0.138 to 0.113. The interval slice also posts the highest
+values on every retrieval-quality slice (TRP 0.376, CCR 0.920, and stale-blind
+CCR 0.773 where all other operators fall to 0.03–0.08), so per-operator
+retrieval comparisons involving interval are contaminated as well.
 
 **Evaluation-protocol fix.** Do not render `<t={t_query}>` (or otherwise expose
 `t_query`) for interval questions. Interval questions are self-contained: the