Automated Red-Teamer Beats GPT-5.1 in 84% of Novel Attacks

The mechanism is what's new. Effort is now installed by effort-conditioned SFT and mode-conditioned RLVR, per Raschka's read across six open-weight models. DeepSeek V4 trains Non-think / Think-High / Think-Max as separate modes with their own context windows and length penalties, then distills them into one checkpoint. Effort here is a learned behavior, not a decode-time knob, which means the flag only does something if post-training actually honored it. That's a regression test worth running before you trust the flag, and most teams skip it.

The part worth double-checking is the cost curve. On DeepSeek V4 the token cost inverts: higher effort spends fewer tokens, not more, because the model was trained to reason more economically at the top of the ladder. Kimi K3 compounds this from the other direction, emitting 21% fewer output tokens than K2.6 on equivalent tasks. Output-tokens-per-completed-task is a real cost variable now, and it moves independently of the per-token price on the rate card. That independence is the thing to check first if a forecast starts drifting.

The consequence: any $/M-token spreadsheet that treats a model as a single price point is stale. Cost-per-completed-task is a function of effort level, verbosity, and your task mix — three things the vendor's pricing page doesn't capture. Neither release shipped ablations isolating effort's contribution, so the size of that effect on your workload is still an open question, not a given.

Both sources agree output-token efficiency is the lever. That agreement is correlational across two model families, not a controlled result, and it doesn't substitute for validating the curve on your own suite before you rebuild forecasts on it.

Netflix's serving decision is the transferable data point here. The team moved TensorRT-LLM → vLLM in summer 2025, citing custom architectures, custom decoding hooks, and easier debugging. They then folded LLM inference into the same Model Scoring Service that already runs their XGBoost, TF, and PyTorch models. Triton still handles batching and GPU scheduling behind one control plane. The lesson isn't "adopt vLLM." It's that treating LLM inference as a silo apart from classic ML is the anti-pattern a mature shop dismantled in summer 2025.

Kimi K3 is the stress test for that flexibility. Its Kimi Delta Attention breaks conventional prefix caching, which is why Moonshot had to contribute a bespoke vLLM implementation, landing July 27, and why they recommend 64+ accelerator supernodes. A cost model built on the assumption that cached system prompts amortize across requests will quietly lose the pricing win here. That's not a benchmark you can borrow from someone else's paper. It's a cache-miss-overhead number you measure on your own prompt distribution.

A second trap sits in the memory math. Extreme MoE sparsity means K3 activates 16 of 896 experts per token, which cuts compute-per-token, not memory. Self-hosting keeps all 896 experts resident, so VRAM planning scales with the total 2.8T params while throughput scales with active params. The compute break-even against the $3/$15-per-M-token API is worth running before committing infra.

The operational substrate matters as much as the kernel. Once agents, not humans, are the ones reading a feature-store schema or model registry, stale metadata stops being a productivity tax and becomes a silent production incident. Serving discipline now has to span the control plane and the metadata it reads from.