Werbos — live benchmark

Owned talk models, scored on frozen floors. Updated from the ledger. (champion 336M (B.20, 2026-08-24))

the CHAMPION of each sweep, over time — a gap means that floor did not exist yet
0.000.250.500.751.002026-07-28 B.13 1M: clean 0.962026-07-31 B.15 2M: clean 0.922026-08-12 B.20 46M-eot-merged: clean 0.962026-08-24 B.20 336M: clean 1.02026-07-28 B.13 1M: input_sensitive 0.92026-07-31 B.15 2M: input_sensitive 0.982026-08-12 B.20 46M-eot-merged: input_sensitive 0.922026-08-24 B.20 336M: input_sensitive 0.962026-07-28 B.13 1M: ood 0.02026-07-31 B.15 2M: ood 0.02026-08-12 B.20 46M-eot-merged: ood 0.172026-08-24 B.20 336M: ood 0.0B.10 · 30M07-20B.13 · 1M07-28B.15 · 2M07-31B.20 · 46M-eot-merged08-12B.20 · 336M08-24cleaninput-sensitiveood

Each point is the model that was PROMOTED that day, scored on the same floors. B.10 predates the floors, so it has no points — it was chosen on held-out loss, which B.13 later showed ranks models backwards. Between B.13 and B.15 the champion's clean fell 0.96 to 0.92 while input-sensitivity rose 0.90 to 0.98: the corpus grew and its MIX changed with it, and this is the only view in which that shows up at all.

talk models, same corpus and same budget — only the size changes
0.000.250.500.751.0046M-eot-merged clean: 0.98336M clean: 1.0clean46M-eot-merged input-sensitive: 0.92336M input-sensitive: 0.96input-sensitive46M-eot-merged adjacency: 1.0336M adjacency: 0.92adjacency46M-eot-merged stable: 1.0336M stable: 1.0stable46M-eot-merged ood: 0.17336M ood: 0.0ood46M-eot-merged (loss 2.173)336M (loss 3.184) ● live
modelparamsheld-out lossstatus
46M-eot-merged46.48M2.173
336M336.39M3.184live

B.20 — identical corpus (214,743 pairs) and identical budget; only the parameter count changes. Loss and the floors disagree, which is the second sweep running where selecting on loss would ship the wrong model. ood is 0.00 for every model ever trained here — none signals confusion on out-of-distribution input, and doubling the corpus did not change it.

The trust curve is not shown, because it has not been measured. The self-improvement gate writes a trust-curve log as it promotes and rolls back checkpoints; no such log exists yet, so there is nothing to plot. An earlier version of this page displayed a hardcoded point — 4/19 correct, honesty 100% — that came from a literal in the build script rather than from any run. It is removed. A measurement that has not been taken is shown as absent, not as a number.