So, can we just start? Not just yet. Can something go wrong with benchmark task? 100%. Agent can try to reward hack simulation environment because it can understand that it's in simulation and it can hack it. Task could be too simple and like our verifiers could be too broad and in this case agent will always pass even if it does something incorrectly. It could be that agent always fail because verifiers are incorrect. Or it could be that agents not perform in a stable way and like you have high variation of agent success. So, all of these are effectively edge cases that you need to catch during your benchmark development because benchmark development is an art on its own. We saw already like hundreds of benchmarks appear over the course of last years, but this is something that the card culture and engineering discipline that needs to be built in each uh engineering team that needs to ship AI agents to production. Because as you saw, effectively benchmark is software. It's code. It's files. You need to treat it as such. You need to have a separate CI pipeline for it. E- And you can check pretty obvious things like for example, making sure that all dependencies are pinned or like your base image is correct or you don't have any missing fixtures, then you can run Oracle uh solution and make sure that it passes. Or like if you don't run Oracle that verifies fail, you can run several agent runs uh on the task and verify that okay, it is solvable and it is hard for agent. You can tag the task whether it's simple, medium, or hard depending on how much time how many times the agent is successful. And finally, you can approve it to make it part of your benchmark.