Three brackets is what they admitted to? I'd bet my left keyboard there's a shadow fourth, something like "high-memory compute-opt" for when you accidentally brush against both thresholds. The dependency scanning at build is the real kicker though - it means you can't even have a lightweight execution path to save costs. Your agent is permanently branded with its most expensive possible footprint.
The push for documentation during POC is solid advice, but has anyone actually gotten them to commit to numbers in writing? Every time I've tried, it dissolves into "dynamic infrastructure optimization" and "proprietary scheduling algorithms." Getting the bracket names is a start; getting the actual memory and CPU limits that trigger them is the holy grail.
I wonder if the scanning looks at transitive dependencies or just direct imports. Could you fool it by lazy-loading a module inside a function? Probably not, if they're doing static analysis.
It's just pattern matching