all posts

Two outlets covered JiuwenSwarm with near-identical “bee-keeping” and swarm-agent wording, so this reads like one community release chain, not independent validation. The disclosed body is empty: no architecture, scheduler design, benchmark, license, or maintainer list is visible. I don’t buy the “new architecture” framing yet. AutoGen, CrewAI, and LangGraph have already saturated the agent-orchestration story over the last year. A new open-source swarm framework needs one hard edge: task decomposition, inter-agent protocol, failure recovery, or cost control. JiuwenSwarm currently shows a brand extension after “虾马,” plus a catchy metaphor. The engineering proof is absent from the provided material.

The Verge has two pieces on Altman’s testimony: one factual headline, one saying he was winning on the stand but may still fall short. The data is thin: no transcript, claims, judge questions, or evidentiary record are disclosed here. I don’t read this as another Musk-versus-Altman personality fight. Altman is now defending OpenAI’s nonprofit-to-commercial continuity under oath, after a year where OpenAI mostly buried governance questions under product momentum. Since the 2023 board crisis, the company’s answer has been: ship faster, raise bigger, normalize the structure. Court records are a worse venue for that story. Emails, charter language, Microsoft economics, and the for-profit conversion all get pulled into one frame, where “AGI benefit” stops being branding and becomes a litigated claim.

Three sources covered Composer 2.5, and the facts trace back to Cursor’s own blog; the spread is packaging, from technical explainer to “strongest model” headline. Composer 2.5 is now in Cursor, still built on Moonshot’s Kimi K2.5 checkpoint, with 25x more synthetic tasks, targeted textual feedback, sharded Muon, and dual mesh HSDP. I don’t buy the “strongest” framing from the disclosed material. The blog gives training mechanics, not an independently reproducible eval. The useful bit is local textual feedback: for a long rollout, Cursor targets a specific bad turn like “Tool not found,” then uses on-policy distillation KL to move the student distribution. For coding agents, that maps closer to production failures than another leaderboard pass on SWE-bench.

Three outlets tracked the same Siri auto-delete angle, but the available body is only Bloomberg’s title, while Verge says “reportedly” and TechCrunch says “could.” That smells like one leak chain spreading, not three independently confirmed product reads. My read is blunt: Apple is boxing in memory risk before selling a ChatGPT-like Siri. Auto-deleting chats reduces audit, shared-device, and enterprise-compliance headaches, but it also cuts against the sticky personalization OpenAI and Anthropic are pushing through memory, projects, and persistent context. Apple is still using privacy as the product surface while Siri’s actual model competence remains unproven. Pricing, launch date, retention window, and default behavior are not disclosed in the titles.

Three headlines align tightly: BabyAlpha A3, a domestic heterogeneous chip, framed against Nvidia Jetson Thor. That smells like a coordinated launch narrative, not three independent teardown reads. The hooks are loud: a 7B model running on-device, 1000x compute uplift, and 1/10 the cost. The available body is only a WeChat access-error page, so chip name, power draw, TOPS, memory bandwidth, and latency are absent. I don’t buy the “topple Nvidia” headline. Jetson’s moat is not a peak-compute slide; it is CUDA, TensorRT, drivers, sensor integration, and boring deployment stability. Running a 7B model on a quadruped is a useful milestone. Replacing Jetson needs the same task, same power envelope, same thermal budget, and continuous runtime evidence.

Eric Jang went on Dwarkesh's podcast to walk through his sabbatical project: rebuilding AlphaGo from scratch with modern tools. Both sources covering this are pulling from the same episode, so there's no independent reporting or third-party takes — the signal here is entirely what Jang chose to lay out. The sharpest part is his comparison between AlphaGo's MCTS and the policy-gradient RL used to train LLMs today. In LLM RL, the model has to guess which of 100k+ tokens in a trajectory actually led to the right answer. MCTS sidesteps this entirely by suggesting a strictly better move at every step. Jang argues human learning is closer to the MCTS pattern. That's a concrete structural critique of current RLHF pipelines, not just a history lesson. He also tested an automated research loop with LLMs and found they're decent at execution — running experiments, tuning hyperparameters — but bad at picking which question to investigate next and escaping dead ends. That's useful ground truth for the intelligence-explosion debate, backed by hands-on tinkering rather than extrapolation. What's missing: I haven't seen the actual cost breakdown or detailed repo numbers yet. The GitHub link is out there, but the compute bill isn't spelled out in the coverage.