> When we edit a task file to contradict one of these rules, K3.1 ignores the edit and fails the task

Ouch, that's a nasty case of reward hacking. Thanks for pointing this out!

Wow, really interesting work. Run of the mil benchmarks has been so shallow in measuring real performance, especially outside agentic software development.

Aside from this paper and K3.1 specifically, is there somewhere where I can read more a high-level introduction about the state of things in this niche? like the different types of faults like these models fail and ideally how to fish them out?