MatheusFelipe
2 hours ago
Interesting the idea of treating the benchmark as an evolving system rather than a static dataset.
2 hours ago
Interesting the idea of treating the benchmark as an evolving system rather than a static dataset.
4 hours ago
thorough work, good stuff.. it even runs a selection-bias analysis against their own benchmark and reports that some tasks that were disproportionately hard for a model. Rare to see a benchmark paper attack itself like that.
4 hours ago
The comparison between harnesses is very nice. Interesting to see that using a different harness can bump the performance of the model as much as a new version (e.g., GPT 5.5+Codex ~= GPT 5.6+Terminus, at lower cost)
2 hours ago
That’s a nice discussion. Some people say that with current model capabilities, the real differentiator is the harness. What are the best harnesses you guys are using?
3 hours ago
Using semantic perturbation to test whether difficulty survives rewording is really smart. Great work!
5 hours ago
The methodology was the most interesting part for me. The paper spends as much time explaining how the benchmark was built as the benchmark itself.
5 hours ago
Refreshing to see something practical instead of another leaderboard battle. Also, props to the team for being so meticulous.
4 hours ago
This approach of not only producing the benchmark tasks, but also focusing on creating a data engine that will improve over time and produce up-to-date tasks that challenge the cutting-edge models is very interesting and valuable.
2 hours ago
good work!
5 hours ago
nice!
4 hours ago
[flagged]
2 hours ago
[dead]
3 hours ago
[flagged]
4 hours ago
[flagged]
3 hours ago
[flagged]
2 hours ago
[dead]