Discussion about this post

User's avatar
Dr Efevretis's avatar

This was a great read, and grounding every eval in real experimental evidence is what makes the leaderboard worth taking seriously.

Your Gemini example is the part that does the most work here. It recognized the inconsistency in the treatment records, kept the wrong arm assignment anyway, then built more computation on top of it. That pulls apart two skills a single pass rate folds together: noticing that the evidence conflicts, and letting that conflict change the decision. Your point about decision gates is about the second one. A gate that flags a problem but still passes the candidate spends the budget just like one that never flagged it.

It also reframes the cost finding. More tokens on a well-framed question is analysis; on a wrongly framed one, it is confident error at scale.

Now that the trajectories are released, it would be interesting to see how often failed runs spotted the key problem and then didn't act on it. That gap might say more about readiness for real programs than the headline 53%.

No posts

Ready for more?