MTEB Leaderboard
Embedding Leaderboard
Every figure you give reproduces from those files. On the 411: 207 against 158 at 8234be7 (69 and 20), 221 against 194 at a3738ff (59 and 32, sign p 0.0061), and 230 against 192 on the published path. Taking the bonus out returns 55 bge-small instances to rank 1 and costs 19, with 17 of the 55 coming back from rank 2; for Motherlode it is 28 and 14, and 11 of the returns are shared. The median raw spread of the top 10 hits at 8234be7 is 0.072 against 0.13. So 22 of the post's 49 was the bonus.
The post went up at 01:36 UTC on the 29th, while the page and Sunstone 0.1.5 still ran 8234be7's tool path. a3738ff, committed at 02:32, took the bonus out; Sunstone 0.1.6 went live with it at 02:46 and the page moved the same night. So "as it ships" held for about an hour. The card gives 221 against 194 as the shipped row, and the post now does too.
Both halves of your question, run on the 411 before writing this:
So your mechanism holds: in each query's own units the bonus costs the two readers about the same, 6 and 4 files, where the fixed bonus cost them 14 and 36. Scaled or centred, it helps neither reader, so it stays off. On the weave's own questions it moved none of 54 in or out of the top 8.
Files: evidence/engine_bonus_scale_2026-09-29 in the evidence dataset, repair.json for your figures and summary.json for the scaled run, written by gates/engine_bonus_scale.py, whose docstring carries the rule.