If you're running LLMs in production and your serving setup is one pool of GPUs doing both prompt processing and token generation, you're leaving significant throughput on the table. Not in a theoretical, "someday we'll optimize" way. Right now, in mid-2026, every major serving framework supports the fix and teams like Baseten are reporting 50% lower time-to-first-token and 61% more requests per second after switching. The pattern is called disaggregated prefill/decode serving. It's been production-ready since NVIDIA Dynamo 1.0 went GA in March, and it's now supported natively by vLLM, SGLang, TensorRT-LLM, and LMDeploy. If you haven't looked at it yet, this is the week. Why Prefill and Decode Don't Belong on the Same GPU LLM inference has two fundamentally different phases. Prefill is where the model processes your input prompt. If you send a 50,000-token context, the model has to attend over all of it to generate the first token. This is com...
On August 11, 2026, Anthropic quietly became the first frontier lab to watermark AI-generated text at production scale, worldwide, across every product. The EU AI Act's Article 50 became enforceable on August 2. Anthropic shipped nine days later. If you build with Claude, this already affects your outputs. Here's what actually changed and what you should do about it. Why This Happened Now Article 50 of the EU AI Act requires providers of generative AI to mark their outputs in machine-readable formats so that downstream users, regulators, and platforms can detect AI-generated content. It became law on August 2, 2026. The penalty for non-compliance isn't trivial. Anthropic didn't watermark just for EU users. The rollout is global: every API call, every Claude.ai session, Claude Code, and hosted instances on AWS, Google Cloud, and Microsoft Foundry. If your models were released after August 2, watermarking is on by default with no opt-out. Older Claude models get the s...