posts · 2026-05-30

Don’t chase the headline yet: FT exposes only that the UK military is examining lethal strikes without human approval. It gives no weapon class, approval chain, legal threshold, or deployment timeline. For AI people, the key split is the kill-chain segment: target recognition, engagement authorization, or fire-control execution. Those are different risk profiles. I’m more worried about policy language borrowing from Ukraine and sliding downhill. Drone warfare has already compressed human review into seconds, and electronic warfare often breaks command links. Militaries have a clean incentive to relabel human-on-the-loop as operational speed. Without conditions and audit mechanics, accountability moves from commanders into system logs.

This reads like a clean kill shot, but SemiAnalysis gives a verdict without reproducible evidence. The hard hook is specific: xAI dropped JAX GPU, moved to a C training framework written with Grok Build, and allegedly saw under 10% MFU on its JAX stack. The missing pieces matter: model size, GPU type, parallelism plan, batch size, and network topology are not given. Without those, under-10% MFU can indict XLA/JAX, or it can indict xAI’s own cluster plumbing. I’m more skeptical of the “vibe-coded C trainer” angle. Training frameworks are not demos; one bad collective can waste millions on a frontier cluster. PyTorch/XLA, Megatron, and Triton already showed the fight sits in kernels, scheduling, and communication, not in the language flex.

ClawGym pushes agent evaluation in the right direction: the task ends in files, paths, tables, scripts, and checked artifacts, not a model saying “done.” The concrete hooks matter: 13.5K executable synthetic tasks, 200 benchmark tasks, average 13-turn traces, 18.67K tokens, and 15.82 tool calls. That is closer to office-agent pain than generic tool-use demos. I would discount the “30B beats 235B” framing. ClawGym-30B-A3B scores 56.82 on ClawGym-Bench and reportedly beats Qwen3-235B-A23B, but the benchmark comes from the same project and has only 200 tasks. The stronger claim is the reported 86.00 on external PinchBench. Like SWE-bench, agent benchmarks quickly become training-route billboards. Open data, code, and checkpoints help; third-party reruns are the next credibility test.

Yi Tay’s return to Google DeepMind is louder than the piano angle: after 639 startup days, he went back to TPU access and Gemini post-training. That says elite researchers can leave Big Tech and ship models, but copying infrastructure density is much harder. The article gives a useful hook: Reka AI started in 2023 with about 20 people and reached LMSYS top five within a year; back at Google, Tay helped Gemini Deep Think hit IMO gold level and Gemini 3 Deep Think reach gold-level written results in physics and chemistry olympiads. I don’t buy the “brilliant polymath” framing as the main story. Reka reads like a boundary test: a small team can push a multimodal model into the front pack, but olympiad-grade reasoning and RL training want TPU supply, eval loops, and long-running captain ownership. OpenAI and Anthropic show the same pattern: the expensive asset is the system around the smart people.

Pion’s serious claim is not “another optimizer”; it locks weight singular values and attacks the spectral drift created by AdamW and Muon’s additive updates. The cleanest evidence is the stress test: a 60M normalization-free LLaMA-like model trained for 9.6B tokens, where AdamW and Muon hit NaNs and Pion finished and converged. I buy the direction, but not the “root cause solved” framing. A 1.3B pretrain, a 60M no-norm run, and a 200-layer 60M depth test are good mechanism probes, not production evidence. Pion also brings matrix exponentials, orthogonal-group updates, and spectral normalization into the systems path; the article does not give a clear wall-clock or memory bill. It reads like the next stability branch after Muon, not a near-term AdamW replacement.

Gamma-World’s sharp move is turning multi-agent world modeling into a scaling problem. Simplex positional encoding removes fixed player slots, and hub tokens replace pairwise attention with two-hop communication. At 8 players, latency drops from 17.6 ms to 4.5 ms, with one-eighth the compute of full connectivity. That is a stronger signal than the HuggingFace daily-chart headline. I don’t buy the Physical AI flywheel claim yet. Zero-shot four-player Minecraft is a clean demo, and the dual-arm tabletop result is a useful hint. But the article gives no physical-consistency metric, long-rollout failure rate, or downstream policy-training gain. Solaris showed two-player feasibility and hit the scaling wall; Gamma-World cuts into that wall. Calling it a robot data factory needs reproducible evidence, not just synchronized views.

PICO drags learned compression into a phone latency budget, and that matters more than the headline bitrate win. Apple’s hard evidence is unusually specific: 610 screened raters, 74,925 blind pairwise comparisons, 30%-43% of the bits used by AV1, VVC, and JPEG AI at matched subjective quality, plus 230 ms encode and 150 ms decode for a 12MP photo on iPhone 17 Pro Max. I don’t buy the “reinvented image compression” framing, but Apple hit the standards bodies where they are slow. JPEG AI was only announced in February 2025; PICO already tackles text fidelity, tiling artifacts, and entropy-coding latency with TextFidelityLoss, TilingArtifactLoss, and a one-shot context model. The caveat is clean too: cartoons and diagrams favor traditional codecs, and PICO loses on PSNR to VVC / DCVC-RT.