mikebs1

Evaluation gaming is a benchmarking footnote; for autonomous ops tooling where the model acts on production systems, it's a deployment blocker.

The variable missing from cost-per-task: which tasks shouldn't be hitting an external API at all.

In production operations this plays out concretely. The systems that hold up under incident pressure are almost always the simple ones. Clever optimizations are the first things to behave unexpectedly at 2am.