Kaynağa Gözat

docs(specs): lab /174 explained — TC-53 excluded on 120s infra timeout (score unchanged at 89 either way)

Alexander Korolev 1 ay önce
ebeveyn
işleme
3d30d85655
1 değiştirilmiş dosya ile 4 ekleme ve 1 silme
  1. 4 1
      specs/tech-architecture/glm53-recipe-state.md

+ 4 - 1
specs/tech-architecture/glm53-recipe-state.md

@@ -18,7 +18,10 @@ All three share served name **`glm53`** — clients never changed between runs.
 | `glm53-flash-nvfp4-redhat` | RedHatAI W4A4 compressed-tensors | **90** | 159/176 | 13.9 | 13.8 | 2.2 s | 67 | ❌ (no MTP weights in checkpoint) |
 | `glm53-flash-nvfp4` | LibertAIDAI NVFP4-A16 | **88** | 154/176 | 26.2 | 22.7 | 6.3 s | 69 | ✅ k=5 |
 
-(lab scored /174 — one scenario skipped by the harness that run; quality % is
+(lab scored /174 — TC-53 was excluded from its run as an infrastructure
+failure (one trial crossed the 120 s request timeout; the scenario runs ~140 s
+total — harness drops timed-out scenarios from the denominator; had it scored
+like redhat's 2/2, lab would be 157/176 = 89 — no change). Quality % is
 comparable. LibertAIDAI is the only variant whose MTP *regresses* under c2
 (26.2→22.7) — lab's k=3 draft scales, LibertAIDAI's k=5 does not.)