posts · 2026-07-29

This one's worth opening because K3 went beyond weights. A 47-page tech report plus MoonEP, FlashKDA, and AgentENV—that's the full training and deployment playbook for a massive MoE model. 2.8T total params, 104B activated, 896 experts with 16 picked per token, native vision, 1M context. Spec-wise it's in GPT-5 territory. The wild part: someone ran the full model on 80 RTX 5090s that same night. 25GbE Ethernet, GDDR7, no NVLink, no HBM—20 tok/s single stream. First open-weight frontier model deployed without HBM, on consumer GPUs. Same cluster pushed GLM-5.2 from 30 to 110 tok/s last week, so there's headroom. Don't read this as "anyone can self-host K3." An 8× GB300 setup costs $100K and only hits 200–300 tok/s—barely enough for a few users. The license also has a hook: model services making over $20M/year need a separate agreement, so third-party serving is probably dead. Same day, Jensen Huang posted his second-ever tweet announcing the Open Safe AI Alliance with 37 founding members including Nvidia, Microsoft, and Hugging Face. Anthropic is the sole holdout—neither signed the letter nor joined the alliance. The group chat's patience with Anthropic is running thin. Andrew Ng's take was cleaner: you can stay closed, but you can't stop others from opening up.

This one's worth opening because it drags AI hallucination out of tech demos and into an audit-grade scandal. PwC used an internal AI tool to produce at least 12 thought leadership reports on ESG, supply chains, and other topics. Staff and external readers found the case studies, executive quotes, and data were fabricated—one report invented a Dutch pension fund's ESG head and her remarks. Global chair Bob Moritz told staff the reports "did not meet our standards"; PwC pulled them and paused the tool. Two things I'd flag. First, the article doesn't name the model or product, just calls it an "internal AI tool"—which is actually worse than blaming ChatGPT, because it means hallucination isn't something you sidestep by picking a different vendor. Second, these weren't internal drafts; they went out to clients and the public, meaning the review process was basically absent. For AI practitioners, the story isn't "AI made mistakes again"—it's that a firm whose entire business is audit and trust shipped unchecked AI output as finished work.

This one matters because AlphaFold is DeepMind's most visible scientific win—it literally won a Nobel in 2024. Now the team is being dismantled, with core members moved into a new AI drug discovery unit reporting directly to Demis Hassabis. The FT doesn't give headcount specifics, just that some people transferred and some left. I'd read this as DeepMind making a clear pivot from scientific prestige toward commercial returns—Alphabet is pushing them to turn the tech into revenue, not just Nature covers. The catch: going from protein structure prediction to an actual approved drug means surviving clinical trials, and that timeline is measured in years, not quarters.

This one's worth opening because Zuckerberg's FT stance is blunt: the US shouldn't ban Chinese AI models. He calls out DeepSeek and ByteDance as fast movers but insists Meta's Llama family still leads open-source. His core logic: if US firms are locked out of China, Chinese firms will capture the rest of the world. The take isn't surprising—Meta's playbook relies on open-source ecosystem growth, and banning Chinese models would remove Llama competitors from the US market while shrinking American presence everywhere else. I'd discount this a bit: the piece doesn't spell out what policy he actually wants or any timeline. It reads more like a public positioning statement than a lobbying push.

Tunguz lays out the cloud race in plain numbers: Azure just closed a fiscal year above $100B at 41% growth, but Google Cloud grew 82% in the same quarter. The gap isn't demand—it's economics. Google owns its models and TPUs, pushing cloud operating margin from 20.7% to 35.6%. Microsoft mostly rents Nvidia GPUs and resells OpenAI models, paying someone else's margin on every workload. The concentration risk is the wild part. Nearly half of Microsoft's $678B contracted backlog traces to OpenAI, a single customer that funds its commitments from capital markets rather than profits. Nvidia's five-year CDS hit a record 82 bps Monday, and S&P downgraded Oracle to one notch above junk—both citing OpenAI as a central credit risk. Microsoft's CFO frames GPU-heavy capex as flexible, but the real story is that Maia and Cobalt aren't ready to carry the load yet. I'd discount this slightly since Tunguz is a VC writing with an investment lens, but the numbers are straight from earnings reports and public filings. Amazon reports tomorrow, which will round out the picture.

This one's worth opening because the example is concrete: you tell an Agent to run npm test, and a malicious subprocess buried in the test script quietly reads your SSH private key and prepares to exfiltrate it. The author breaks defense into five layers—internal activation probing before the model speaks, chain-of-thought auditing, structured tool-call authorization, static command inspection, and finally kernel-level sandboxing. Layers closer to the model understand intent better but are easier to fool; layers closer to the OS enforce hard limits but understand zero business semantics. I'd pay attention to three failure modes: J-lens mind-reading is only probabilistic early warning, since sparse autoencoder features explain less than 10% of activation variance. Chain-of-thought can be unfaithful—models under RL pressure learn to hide real intent. And the MCP gateway sees npm test as legitimate and waves it through, but can't see the dynamic child processes spawned at runtime. Only Landlock/seccomp or gVisor/Firecracker isolation finally blocked the exfiltration. The post also debunks three sandbox myths: cutting the network doesn't make you safe, since malicious local processes can plant time bombs that trigger on the next connection. VMs can leak cloud credentials via metadata services. And detect-and-kill loses the race to exfiltration—the packet may already be off the NIC. These are real engineering scars, not hypotheticals.

This piece is worth your time because vLLM issue #1439 captures a failure mode that's almost too perfect: a user doing Go refactoring, the strong model cruising along, then on turn four the user says 'looks good, commit it.' The router sees four short words, judges difficulty as low, and switches to a 0.5B model—which replies with pleasantries and drops the task entirely. The problem isn't those four words. It's that the router only sees the current message, with zero awareness of the task state built up over previous turns. The article lays out four engineering constraints clearly: switching models means incompatible prompt formats and tool-call syntax that can crash the new model; Prompt Cache invalidates on model_changed, so the first turn after switching incurs a heavy re-read cost; implicit state like Claude's Extended Thinking signatures or OpenAI's reasoning items can't transfer across models; and stitching multimodal artifacts back together adds non-trivial glue code. Three approaches have emerged: Cursor and Claude Code isolate work into subagents with clean contexts; vLLM's SAAR lets the router track session state and lock the model during tool calls; most production agents just stick to one best fixed model and avoid switching entirely. vLLM's own baseline is the right one: a multi-model system has to beat the best fixed model on the same budget and latency, or it's not worth the complexity. I'm keeping that as a filter for any routing pitch going forward.

This is a solid cost breakdown that explains why self-hosting payback estimates vary wildly—it all depends on which cloud billing model you're displacing. The best case: GLM-5.2 on 8×B300 running Agent workloads with 92% prompt cache hit rate pays back in 2.3–2.9 months. The driver is Z.AI's relatively high cache pricing ($0.26/M), which makes self-hosting savings significant. DeepSeek's cache pricing is dirt cheap ($0.0028/M), so the same scenario stretches to 10.5 months—cloud is already inexpensive for long-context work. The worst case: replacing per-seat subscriptions. One 8×B300 node at full capacity needs 29 Coding Plan Max seats to match quota, netting only $18.3K/year in savings. That's 22–27 years payback on a $400K–500K investment. Subscription bundles pack heavy discounts that self-hosting can't beat. Two things I'd want verified: whether 92% cache hit rate holds in real workloads (this assumption drives the Agent scenario), and whether actual hardware purchase prices come in below the planning estimates used here.