#数据/训练

4 today

May 19Tuesday

Google DeepMindMay 19, 02:21

Fast-tracking genetic leads to reverse cellular aging

Google DeepMind 的 Co-Scientist 正被用于加速细胞衰老研究，它扫描数万篇论文后提出 20 多个可测试的新遗传因子，其中数个经实验室验证能驱动细胞进入更年轻状态并改善整体功能。它还能将原本需长达六个月的筛选数据分析缩短至几天。

AI HOT (Curated Pool)May 19, 01:50

Cursor releases Composer 2.5 coding model

Cursor released Composer 2.5, claiming up to 10x higher efficiency on long coding tasks; the model is further trained on Moonshot’s Kimi K2.5 and uses text feedback for 100k-token-scale trajectories.

Why it matters: HKR-H/K/R all pass: Cursor is a core AI coding tool, and Composer 2.5 adds concrete claims around 10x long-task gains and Kimi K2.5 tuning. Limited sourcing and no independent eval keep it in the 78–84 band.

AI HOT (Curated Pool)May 19, 00:00

NVIDIA fine-tunes Cosmos Predict 2.5 with LoRA/DoRA for robot video generation

NVIDIA published a Hugging Face post on fine-tuning Cosmos Predict 2.5 with LoRA and DoRA to generate robot first-person videos from text prompts; the post does not disclose dataset size, training cost, or evaluation results.

Why it matters: HKR-H/K/R pass: the robot POV video angle is clickable, and LoRA/DoRA on Cosmos Predict 2.5 is a concrete mechanism. Missing dataset scale and metrics keep it in the low featured band.

May 18Monday

Synced · WeChatMay 18, 12:47

ICML 2026: Huawei GTS proposes EDCO for dynamic curriculum fine-tuning

Huawei GTS proposed EDCO, a dynamic curriculum method that selects fine-tuning samples by inference entropy; prefix entropy estimation cuts per-sample scoring time from 2.24 seconds to 0.37 seconds.

Why it matters: HKR-H/K/R pass: the story has a lab-race hook, a concrete entropy-based mechanism, and a 2.24s→0.37s efficiency claim. It stays below 78 because it is still a training-method paper, not a major model or product release.

Take

EDCO’s useful move is not the “difficulty-adaptive training” label. It plugs sample selection into the fine-tuning loop and makes the scoring cost survivable. The concrete hook is strong: full-sequence entropy costs 2.24 seconds per sample, prefix entropy drops it to 0.37 seconds, and 8-GPU parallel scoring reaches 0.04 seconds. On Datacom RLFT, accuracy moves from 40.43% with random sampling to 46.96%.

I don’t buy the “new paradigm” framing yet. Active learning, curriculum learning, and hard-example mining have been circling this idea for years. The LLM-specific question is whether inference entropy stays a reliable proxy for useful gradient signal. The paper tests Qwen3-4B, Llama3.2-3B, and three vertical domains; it does not settle larger models, longer training, or production distribution drift.

r/LocalLLaMAMay 18, 10:14

I trained TIME: short context-triggered thinking on Qwen instead of overthinking

An independent author trained TIME with QLoRA on Qwen3 4B/8B/14B/32B to trigger short mid-response reasoning when context changes; the post says datasets, notebooks, scripts, curriculum, and TIMEBench are public, with 24GB VRAM enough for training up to 14B.

Why it matters: HKR-H/K/R all pass: the post has a clear tuning hook, concrete reproducible details, and strong local-LLM resonance. Reddit single-post sourcing keeps it in the 72-77 featured band, below lab-level releases.

AI HOT (Curated Pool)May 18, 08:00

Composer 2.5 release and technical analysis

Cursor released Composer 2.5, built on a Moonshot open-source checkpoint, trained with synthetic data from real codebases at 25 times the previous scale, and updated with text-feedback reinforcement learning and a sharded Muon optimizer.

Why it matters: HKR-H/K/R all pass: Cursor is a core coding-agent surface, and the post gives concrete training details around Moonshot, 25x data, RL, and Muon. It lacks benchmarks, pricing, or user-facing capability limits, so it stays in the 78–84 band.

May 17Sunday

Google DeepMindMay 17, 21:50

Google DeepMind launches Gemini for Science toolset

Google DeepMind released Gemini for Science, which includes three experimental tools on Google Labs: Hypothesis Generation, built on Co-Scientist.

Why it matters: Google is packaging research prototypes like Co-Scientist and AlphaEvolve into apply-to-use science tools, showing what agentic research looks like in practice.

QbitAI · WeChatMay 17, 18:22

TGO Aligns Visual Generative Models with Scalar Feedback Without Preference Pairs | ICML 2026

NUS proposed Threshold-Guided Optimization, which converts scalar feedback into positive or negative updates through a score-distribution threshold and was accepted by ICML 2026; experiments cover Stable Diffusion v1.5, FLUX, Wan 1.3B, and Meissonic across image and video generation settings.

Why it matters: HKR-H/K/R pass: the paper has a concrete mechanism and tests across SD v1.5, FLUX, Wan 1.3B, and Meissonic. Impact is research-heavy, so it lands in featured, not must-write.

Take

TGO matters because it treats visual feedback as scores, not forced winner/loser pairs. The mechanism is simple: a score-distribution threshold sets update direction, and distance from that threshold sets weight. The paper tests Stable Diffusion v1.5, FLUX, Wan 1.3B, and Meissonic, so this is broader than a one-backbone diffusion trick.

I don’t buy the “new paradigm” framing. PMPO already loosens unpaired positive/negative feedback, and QRPO handles pointwise absolute rewards through quantiles. TGO is the visual-generation engineering compromise: cheap, readable, and easy to plug into diffusion or masked generators. The weak spot is the global threshold. It compresses prompt difficulty, style taste, and reward-model bias into one cutoff. If the scorer is skewed, pseudo-negatives will suppress minority aesthetics with mathematical confidence.

Dwarkesh Patel podcastMay 17, 03:01

Notes on Pretraining Parallelisms and Failed Training Runs

Dwarkesh documents pretraining failure modes and parallelism tradeoffs: expert choice and token dropping can break causality in MoE routing, FP16 collectives can bias repeated additions after values exceed 1024, pretraining FLOPs are given as 6ND, B300 HBM is listed as 288GB, and FSDP communication can reach params × 3 with reduce-scatter.

Why it matters: HKR-H/K/R all pass: Dwarkesh’s notes expose concrete pretraining failure modes and numbers. The systems-training focus is specialized, so it sits in the high-quality band rather than same-day must-write.

May 16Saturday

Google DeepMindMay 16, 16:16

Finding the molecular switches behind new infectious diseases

剑桥大学 Clare Bryant 教授利用 Google Co-Scientist 研究流感等病原体跨物种传播时引发脓毒症等重症的分子开关。Co-Scientist 生成并排序假设，优先锁定一个她此前未关注的蛋白，并逐步将假设细化到具体氨基酸。Bryant 团队正构建含氨基酸突变的细胞系验证，原本需两到三年的工作预计六个月完成。

Google DeepMindMay 16, 16:08

Opening new paths in aging research

Calico Life Sciences 的 Matt Onsum 与 Katherine Labbé 正使用 Google DeepMind 的 Co-Scientist 整合衰老生物学中零散的研究发现，将其转化为可验证的假设。在整合应激反应（ISR）研究中，该工具帮助团队生成了一条关于代谢如何调控 ISR 的新假设，并协助优化实验设计。相关实验已产生新发现，团队计划发表这些结果。

Google DeepMindMay 16, 16:00

Accelerating discovery of liver disease mechanisms

爱丁堡大学团队用 Google Co-Scientist 研究 MASH 肝病，系统整合肝生物学与药理学证据，锁定值得关注的机制并筛选出候选组合疗法。针对 resmetirom 仅对少数合格患者有效的问题，Co-Scientist 提出 NLRP3 炎症小体是连接炎症与代谢的分子桥梁，该假说随后经实验验证，有望推动靶向双重疗法。

Google DeepMindMay 16, 15:53

Uniting biological toolkits for a new approach to ALS

MIT 的 Ritu Raman 与波士顿儿童医院的 Ryan Flynn 借助 Google DeepMind 的 Co-Scientist，将各自不同的研究工具结合用于 ALS 研究。

Google DeepMindMay 16, 15:40

Uncovering repurposed medicines to fight liver fibrosis

斯坦福大学医学院遗传学家 Gary Peltz 团队在《Advanced Science》发表研究，用 Google DeepMind 的 Co-Scientist 从现有药物文献中筛选可重定位治疗肝纤维化的候选药。

May 15Friday

r/LocalLLaMAMay 15, 07:09

I trained Qwen3.5 to jailbreak itself with RL, then used the failures to improve its defenses

The author built an RL-based automated red-teaming loop for Qwen3.5, raising defense rate from 64% to 92% while benign accuracy fell from 92% to 88%, and the attacker found 7 tactic families.

Why it matters: HKR-H/K/R all pass: a named first-person RL red-team loop with concrete rates and failure modes. Source is a single Reddit post without paper/code validation, so it stays below P1.

Take

This is less “Qwen3.5 learned to defend itself” than a clean reminder that RL red teams optimize the loopholes in your reward. The concrete bit matters: plain GRPO collapsed into the same fiction-writing jailbreak, then tactic clustering plus reward dilution by cluster size produced 7 tactic families. That is the useful mechanism here, not the headline defense gain.

The numbers are still a decent sanity check: defense rate moves from 64% to 92%, while benign accuracy drops from 92% to 88%. A 4-point benign hit is not free; it is the tax you pay for broader refusal behavior. I like that the author reports it. I do not treat this as a benchmark result yet. Test-set size, harm taxonomy, holdout separation, and evaluator setup are not disclosed in the snippet, and those decide whether this survives outside a Reddit demo.

r/LocalLLaMAMay 15, 06:55

I Let a Small Model Train on Its Own Mistakes; It Reached 80% on HumanEval and Beat GPT-3.5 on Math

The author fine-tuned Qwen 2.5 7B base on self-mined mistake-correction pairs, raising HumanEval from 25/164 to 112/164; Qwen 2.5 14B used 100 pairs and a 95-minute H100 run costing $3.50.

Why it matters: HKR-H/K/R pass: the hook is strong and the post gives samples, H100 time, cost, and HumanEval deltas. Kept at 78 because it is a single Reddit post and the 80% claim differs from 112/164.

r/LocalLLaMAMay 15, 01:33

MOOSE-Star (ICML 2026): 7B Model and 108K-Paper Dataset for Scientific Hypothesis Discovery

MiroMind researchers released the MOOSE-Star collection with three 7B models and TOMATO-Star, a dataset of 108,717 NCBI papers. MS-IR-7B reaches 54.37% inspiration-retrieval accuracy, uses DeepSeek-R1-Distill-Qwen-7B as its base, runs at about 14GB fp16, and supports llama.cpp, vLLM, and SGLang.

Why it matters: HKR-H/K/R all pass via the local 7B research-agent hook and concrete dataset metrics. Single Reddit source and limited lab gravity keep it below the must-write band.

Take

MOOSE-Star’s useful claim is not “AI discovers science.” It puts a small, runnable baseline under a noisy category. The concrete hooks are good: three 7B models, TOMATO-Star with 108,717 NCBI papers, MS-IR-7B based on DeepSeek-R1-Distill-Qwen-7B, 54.37% inspiration-retrieval accuracy, about 14GB fp16, with llama.cpp, vLLM, and SGLang support.

I like the 7B choice. Scientific hypothesis agents get muddy fast when the demo rides a closed frontier model; nobody can separate retrieval, reasoning, memorization, and prompt craft. A 14GB fp16 model lets labs run ablations instead of applauding a slide. The Reddit body is blocked by 403, so training details and benchmark construction are not visible here. I would be careful with the 54.37% number until we see negatives, time splits, and leakage controls.

May 14Thursday

r/LocalLLaMAMay 14, 18:32

Automated AI researcher running locally with llama.cpp

Hugging Face’s ml-intern added local-model support through llama.cpp and ollama; the post says Qwen3.6-35B-A3B can orchestrate CPU/GPU sandboxes and Hub jobs to run an end-to-end SFT workflow.

Why it matters: HKR-H/K/R all pass, but this is a Reddit-sourced open-source tool update, not a major model release. Local sandbox and Hub-job orchestration for SFT put it just above the featured threshold.

Take

This reads like a local agent plumbing milestone, not proof that “AI researcher” is solved. The concrete hook is ml-intern adding llama.cpp and ollama support, with Qwen3.6-35B-A3B orchestrating CPU/GPU sandboxes plus Hugging Face Hub jobs to finish an end-to-end SFT run. Reddit’s body is blocked by 403, so run time, failure rate, human intervention points, and VRAM setup are missing. I’d treat this as a reproducible toolchain claim, not a capability claim. Claude Code and OpenAI’s Codex-style agents already made tool use feel normal in cloud setups; the local angle buys privacy, cost control, and sandbox ownership. The weak spot is still long-horizon brittleness: one bad dependency, dataset format issue, or Hub auth error can turn a 35B-A3B “researcher” back into a script runner.

Xinzhiyuan · WeChatMay 14, 13:05

Yuandong Tian and Seven Co-Founders Launch Recursive Superintelligence at $4.65B Valuation

Recursive Superintelligence, founded by Yuandong Tian and seven other AI researchers, has a 25-person team, $650 million in funding, and a $4.65 billion valuation, with a stated goal to automate evaluation, data filtering, training, post-training, and research-direction selection.

Why it matters: All three HKR axes pass: a $650M raise at a $4.65B valuation for a 25-person recursive-improvement startup is not routine funding. The stated target spans evals, data selection, training, post-training, and research selection.

Take

Recursive Superintelligence’s valuation is loud, but the bet is not silly: automate evaluation, data selection, training, post-training, and research-direction choice as one loop. A 25-person team raising $650M at a $4.65B valuation with no product looks absurd. With Yuandong Tian, Richard Socher, Jeff Clune, and ViT first author Alexey Dosovitskiy, investors are paying for a shot at replacing parts of the frontier-lab workflow.

I don’t buy the “AI researchers lose their jobs” framing. The sharper threat is that expensive human judgment inside model iteration gets eaten by tooling. DeepMind’s AlphaEvolve and Darwin Gödel Machine already showed algorithm search and self-editing code can move benchmarks. Nathan Lambert’s lossy self-improvement critique is also fair: nobody sane lets agents burn multi-billion-dollar training budgets unsupervised. Recursive has to prove stable savings in elite researcher time, not science fiction.

Synced · WeChatMay 14, 12:10

China in Focus: PsiBot Uses 100,000 Hours of Human Data for Embodied AI

PsiBot says it uses 100,000 hours of human operation data to train robot policies, with the W0 world model acting only as a training-time transfer module while deployment runs R2 alone.

Why it matters: HKR-H/K/R all pass, but the facts come mainly from company framing and lack an artifact link, benchmark, or third-party replication. This fits a solid robotics research/product story, not the 78+ band.

Take

PsiBot’s bet is embodied AI’s version of buying data scale first, then paying the transfer tax. The concrete setup is clean: 100,000 hours of human operation data, W0 as an action-conditioned world model during training, and R2 alone at deployment. That avoids the latency and reliability mess of running a world model on the robot. Compared with tens of thousands of hours of teleoperation, human-centric capture can enter cashier, warehouse, and factory workflows.

I don’t buy the “similar effect” claim yet. The article gives about 14,600 Hugging Face downloads for SynData, but no task suite, success rate, repeated real-robot trials, or hardware-controlled comparison. Robotics companies have spent two years using demos to dodge metric debt; Figure, 1X, and Tesla all did versions of it. PsiBot’s architecture is smart. The evidence is still mostly company narration.

Synced · WeChatMay 14, 12:10

ACL 2026: Alibaba DAMO I²B-LPO Improves RLVR Exploration

Alibaba DAMO Academy introduced I²B-LPO, an RLVR post-training framework that branches rollouts at high-entropy nodes and filters them with an information-bottleneck self-reward, reporting up to 5.3% accuracy gains and 7.4% semantic-diversity gains on math benchmarks using Qwen2.5-7B and Qwen3-14B.

Why it matters: HKR-H/K/R all pass: the ACL 2026 DAMO paper has a clear RLVR exploration hook, concrete I²B-LPO mechanics, and benchmark gains. It is still a training-method paper, not a major model or product release, so 78 fits the lower good-quality band.

May 13Wednesday

AI HOT (Curated Pool)May 13, 14:19

SenseNova-U1 Technical Report Released: Guide to Native Multimodal Model Building

SenseTime released the SenseNova-U1 technical report, covering six-stage training, RL post-training, and distillation; the open-source SenseNova-U1-A3B-MoT uses an MoE architecture and activates only 3 billion parameters.

Why it matters: HKR-H/K/R all pass: A3B-MoT’s 3B active parameters and six-stage training recipe give concrete signal. The score stays near the featured floor because this is a vendor post with no benchmarks, license terms, or reproduction details disclosed.

Take

SenseTime’s useful move here is not the “native multimodal” branding. It is exposing the pipeline: six-stage training, RL post-training, distillation, and pixel-space flow matching. SenseNova-U1-A3B-MoT activates only 3B parameters, which gives practitioners a concrete cost claim to test rather than another giant-model slogan.

I don’t buy the “full guide” framing yet. The snippet says weights, code, demo, and the technical report are open, but gives no benchmark table, training-token count, vision resolution, total expert count, or routing details. Qwen-VL, InternVL, and LLaVA-style releases already trained the field to demand reproducible evals, not architecture poetry. SenseTime’s bar is simple: show that 3B active parameters survive real multimodal tasks without hiding behind selective demos.

Xinzhiyuan · WeChatMay 13, 12:06

Tsinghua-affiliated team open-sources MiniCPM-V 4.6, a 1.3B model tunable on one RTX 4090

ModelBest, Tsinghua University, and OpenBMB open-sourced MiniCPM-V 4.6, a 1.3B multimodal model that supports full fine-tuning on one RTX 4090 and offers 4x/16x visual token compression for accuracy or speed trade-offs.

Why it matters: HKR-H/K/R all pass: the story gives a concrete open-source multimodal release with size, hardware condition, and token-compression details. It lowers local fine-tuning cost, but it is not a frontier-lab flagship release, so 78–84 fits.

May 12Tuesday

AI HOT (Curated Pool)May 12, 23:54

How Open Model Ecosystems Compound

China’s open AI model community forms a self-reinforcing loop, with domestic open model downloads rising by more than 200% quarter over quarter.

Why it matters: HKR-H/K/R all pass: the flywheel framing is clickable, the article gives a >200% QoQ download claim, and the topic hits China open-model competition. It is strong commentary, not a model launch, so 78 featured.

Take

China’s open-model advantage is not free weights; it is cheaper failure. Lambert cites Ai2 and Epoch AI estimates that roughly 80% of frontier compute goes into R&D, not the final training run. If leading Chinese labs keep publishing technical reports, weights, and infra details, peers avoid rerunning the same MoE, RL, and data experiments.

I don’t buy the lazy “open is cheaper” framing. The piece says off-the-shelf open models are usually more expensive for product teams than closed hosted APIs, because inference scale still favors integrated providers. The weak link is the stack: at-scale RL for MoE models still lacks a truly open recipe, and semi-open tools like Thinking Machines’ Tinker or Prime Intellect Lab may not release enough surface area. The compounding only works if labs stop forking the valuable training stack back behind company walls.

Google DeepMindMay 12, 22:40

Google DeepMind publishes Co-Scientist multi-agent research system

Google DeepMind published Co-Scientist research in Nature, introducing a Gemini-based multi-agent AI system that iteratively generates, debates and evolves new hypotheses for complex scientific problems.

Why it matters: The post discloses the system's three-stage collaboration mechanism and deployment cases at several labs, showing how AI takes part in scientific hypothesis generation.

QbitAI · WeChatMay 12, 11:55

Shanghai AI Lab Study: SFT Generalizes Under Three Conditions

Shanghai AI Lab, Shanghai Jiao Tong University, and USTC tested Long-CoT SFT on Qwen3-14B-Base and found that cross-domain performance recovered and improved after 8 epochs, with generalization conditioned on optimization depth, data quality and structure, and base-model capability.

Why it matters: HKR-H/K/R all pass: the SFT-generalization claim has a clear hook, Qwen3-14B-Base plus an 8-epoch finding, and direct relevance to fine-tuning teams. It lacks deployment impact or full benchmark detail, so it stays in the mid-featured band.

r/LocalLLaMAMay 12, 05:01

Prompt caching for RL training: 7.5x speedup on long-prompt, short-response workloads

The author proposes prompt caching for RL training. On Qwen3.5-4B, it reports a 7.5x speedup with 16k-token prompts and 64-token outputs, and the G=8 example with 1000-token prompts and 100-token responses reduces 8800 processed tokens to 1800 unique tokens.

Why it matters: HKR-H/K/R all pass: the angle is novel, and the post gives 16k/64 plus G=8 token-dedup numbers. Kept at 78 because this is a single Reddit post without independent replication or a paper/code artifact disclosed.

May 10Sunday

Synced · WeChatMay 10, 14:03

Turing Award Winner Sutton Uses a 1967 Formula to Improve Streaming Reinforcement Learning

Richard Sutton and coauthors proposed Intentional Updates, which derive the step size from the desired output change; Intentional AC approached SAC on MuJoCo under batch=1 streaming training without replay, while each update used about 1/140 of SAC’s FLOPs.

Why it matters: HKR-H/K/R all pass: Sutton's name, Intentional Updates, MuJoCo conditions, and 1/140 SAC FLOPs give it substance. Strong research signal, but less market-moving than a major LLM product release, so it stays in the 78–84 band.

Take

Intentional Updates cuts at the right layer: streaming deep RL may not fail because batch=1 is starved, but because learning rates control parameter motion instead of output change. The paper ports the 1967 NLMS idea into deep RL, deriving step size from desired output change; Intentional AC gets near SAC on MuJoCo with batch=1 and no replay, while each update uses about 1/140 of SAC’s FLOPs.

I buy this more than most online-learning pitches because it measures the mechanism, not just returns. With eligibility traces disabled, the actual/target update ratio has a standard deviation of 0.016 to 0.029, and the 99th percentile stays within 1.07. The flaw is also concrete: on Ant-v4, cosine alignment for policy-update direction drops to a median 0.63, so action-dependent step sizes can bias the gradient. Sutton is handing streaming RL a reproducible lever, not another manifesto.

Xinzhiyuan · WeChatMay 10, 12:49

Next-ToBE Targets Short-Sighted Next-Token Prediction in LLMs at ICLR 2026

East China Normal University and Fudan University researchers proposed Next-ToBE, a training objective that keeps standard autoregressive inference while adding a soft target over future-token windows, and the article reports the method ranked best in 35 of 36 experiments across Qwen2.5-Math-1.5B, Qwen2.5-Math-7B, and Llama3.1-8B-Instruct.

Why it matters: HKR-H and HKR-K pass: the mechanism and 35/36 result are specific, and next-token training is a real debate. The item stays near the featured floor because no artifact, reproduction detail, or production claim is disclosed.

Take

Next-ToBE has a clean pitch: leave architecture and autoregressive inference alone, then replace the one-hot next-token target with a soft target over future-token windows. The summary gives one hard hook: across Qwen2.5-Math-1.5B, Qwen2.5-Math-7B, and Llama3.1-8B-Instruct, it ranks best in 35 of 36 experiments.

I cannot verify the full paper details here because the WeChat body is blocked by verification. That matters: task mix, window size, target construction, training budget, and statistical spread decide whether this is a durable objective or a narrow tuning win. I like this more than inference-time “think longer” hacks because the cost sits in training and serving stays unchanged. If the gains depend on math-heavy data or distilled labels, it stays a fine-tuning trick. If it transfers across general instruction tasks, it belongs in the pretraining-objective conversation.

May 9Saturday

Xinzhiyuan · WeChatMay 9, 12:05

NVIDIA, AMD, and Intel Back RadixArk’s $100M Seed Round

RadixArk announced a $100 million seed round on May 5 at a $400 million post-money valuation, led by Accel and co-led by Spark Capital, with participation from NVentures, AMD, MediaTek, Databricks, and other investors tied to AI infrastructure.

Why it matters: HKR-H/K/R all pass: a $100M seed round, $400M post-money valuation, and chip/data investors create an AI-infra rivalry angle. It remains a single-company funding item with no product benchmarks or customer data, so it sits near the featured floor.

Take

RadixArk turned an open-source inference stack into hardware politics with a $100 million seed round. The $400 million post-money valuation matters less than the cap table: NVentures, AMD, MediaTek, Databricks, and Intel CEO Lip-Bu Tan as an angel. That reads like every vendor buying an option on SGLang before inference routing hardens around a rival stack.

The concrete hooks are strong: SGLang has 27K+ GitHub stars and the article claims deployment across 400,000 GPUs; Miles also supported DeepSeek-V4 RL training on launch day. I’m not taking the “trillions of tokens” claim at face value, because the source gives no third-party measurement, revenue, hosted product, or enterprise contract detail. vLLM already showed that open-source adoption is only the first inning. The paid game is SLA, managed serving, and ruthless hardware-specific performance work.

May 8Friday

Synced · WeChatMay 8, 17:06

SGLang Team Launches RadixArk With $100M Seed Round

RadixArk announced a $100 million seed round on May 5 at a $400 million post-money valuation, while its SGLang inference project has 27K+ GitHub stars and deployments across 400K+ GPUs.

Why it matters: HKR-H/K/R all pass: the round size, valuation, and deployment numbers are concrete, and SGLang is a known inference stack. It is still a startup funding and infra-roadmap story, not a major model release, so it stays in the 78–84 featured band.

Take

RadixArk’s strongest asset is not the $100M seed round; it is SGLang already sitting inside 400K+ GPUs. Infra startups usually burn time teaching the market. SGLang starts with 27K+ GitHub stars, claimed trillions of daily tokens, and day-zero DeepSeek-V4 inference plus RL support. That is stronger evidence than the cap table.

I don’t buy the “AI infrastructure as a public good” framing yet. Once an open-source inference engine gets tied to a hosted platform, neutrality becomes a product problem. Does SGLang stay vendor-neutral, or does RadixArk Cloud get the fast path? vLLM is fighting for the same open inference slot, and NVIDIA Triton still owns a lot of default hardware gravity. The article gives a platform signup and free credits, but no pricing, SLA, or enterprise deployment terms; that is the gap behind the $400M post-money valuation.

QbitAI · WeChatMay 8, 12:05

All Labs Watch ByteDance, Everyone Praises DeepSeek: A U.S. Researcher’s 36-Hour China AI Trip

Ai2 researcher Nathan Lambert visited Zhipu, Moonshot AI, Tsinghua, Meituan, Xiaomi, and 01.AI within 36 hours, and said Chinese labs closely watch ByteDance and respect DeepSeek, while student participation in core work, open source habits, and in-house control of the technical stack mark key differences.

Why it matters: HKR-H/K/R all pass: the piece has a named US researcher’s dense China-lab tour plus concrete claims on ByteDance, DeepSeek, open source, and in-house stacks. It is strong industry field reporting, not a model launch or major deal, so it sits at featured rather than p1.

Take

The useful signal here is not “Chinese labs are humbler.” It is that Beijing’s AI density is now obvious to an outside researcher after one compressed trip. Nathan Lambert saw Zhipu, Moonshot, Tsinghua, Meituan, Xiaomi, and 01.AI in 36 hours, then came away with two repeated tells: everyone watches ByteDance, and everyone respects DeepSeek.

I don’t fully buy the “less ego, faster catch-up” frame. The harder mechanism is labor and control: students sit near core model work, companies build their own data and RL environments, and non-AI giants like Meituan and Xiaomi still train foundation models. OpenAI and Anthropic largely keep interns away from core frontier work; Chinese labs appear to use students as real engineering bandwidth. But the piece also says Nvidia compute is scarce and data suppliers are uneven, so culture should not become a fairy tale explanation for infrastructure constraints.

May 6Wednesday

QbitAI · WeChatMay 6, 17:46

Claude Team Tests New Training Method on Qwen

Anthropic proposed MSM training between pretraining and alignment fine-tuning. Tests on Qwen2.5-32B and Qwen3-32B cut misalignment from 68% and 54% to 5% and 7%. The key point is MSM complements AFT rather than replacing it.

Why it matters: HKR-H/K/R all pass: Anthropic offers a concrete MSM alignment method with Qwen2.5-32B and Qwen3-32B rate drops. It is strong safety research, not a model launch or major product update, so 82 fits.

Financial Times · TechnologyMay 6, 00:09

Meta and Zuckerberg Sued by Publishers Over ‘Massive’ Copyright Infringement

Five major publishing groups sued Meta and Zuckerberg over copyrighted works allegedly used to train Llama AI models. The RSS snippet does not disclose work counts, damages, court venue, or training-data mechanism.

Why it matters: HKR-H/K/R all pass: FT covers a Meta/Llama copyright suit with Zuckerberg named. Missing court, damages, work counts, and data mechanics keep it at the featured threshold.

Take

Five large publishing groups sued Meta and Mark Zuckerberg over copyrighted works allegedly used to train Llama models. The FT item is only an RSS snippet. It gives no court venue, no damages figure, no work count, no publisher names, and no training-data mechanism.

My read is simple: the article is thin, but the legal move is not. Naming Zuckerberg is the signal. Plaintiffs usually do that when they want to argue knowledge, control, approval chains, or direct involvement. If the complaint later contains emails, dataset reviews, model-card drafts, or internal warnings, Meta cannot hide behind a generic “open models help developers” line.

Meta’s Llama problem has never been only model quality. It is the ledger behind the training corpus. Llama 2, Llama 3, and later Llama releases turned open weights into a distribution weapon. Developers get weights, clouds sell inference, enterprises fine-tune privately, and Meta gets ecosystem gravity without selling the core model as a metered API. That strategy works only while the input side stays legally cheap.

OpenAI took a different reputational route. It signed content deals with Associated Press, Axel Springer, Financial Times, and others. The economics and coverage are not fully transparent, but OpenAI can tell courts and regulators that it has an authorization channel. Meta’s public posture has leaned harder on broad web use and openness. Publishers hear that as “you trained first and want to negotiate later.”

I’m being careful here because the body does not disclose the Llama version. The title says Llama AI models, but it does not say Llama 2, Llama 3, Llama 4, or a specific pretraining run. It also does not say whether the alleged data came from Books3, LibGen, filtered Common Crawl, licensed corpora, or Meta’s own data pipeline. Without the complaint, anyone claiming certainty is over-reading one sentence.

The outside pattern is familiar now. Authors Guild v. OpenAI, The New York Times v. OpenAI and Microsoft, and music-publisher cases around generative AI all shifted the fight away from single bad outputs. Plaintiffs want the court to examine training copies, ingestion pipelines, and whether model building needs a license. Output infringement is painful to prove one sample at a time. Training infringement scales better as a legal theory if plaintiffs can show copying and use.

Meta carries an extra liability shape because Llama is distributed as weights. OpenAI can say the output happens inside a controlled service, with safety layers, logging, and product limits. Meta ships weights into an ecosystem where users fine-tune, distill, quantize, wrap, and deploy in private. Publishers will frame that as distribution of an infringement-derived asset, not just an internal research act. I don’t know if that wins, but it is a more uncomfortable story for Meta than a narrow API-output dispute.

My pushback on the publisher narrative: this may be less about killing Llama than forcing Meta into the licensing market. Publishers have seen AI content deals become a price anchor. Litigation now functions as a rate card with subpoenas attached. If Meta settles, the likely outcome is not “Llama stops.” The more likely outcome is a mixed training stack: some licensed material, some public-web material, some excluded categories, and a lot of language that neither side wants to explain too clearly.

Three facts decide the seriousness here. First, who are the five publishing groups? Second, which court has the case? Third, does the complaint identify specific datasets or internal Meta records? If the complaint names Books3 or LibGen and ties them to Llama training decisions, Meta has a harder optics problem. If the complaint only says protected books were likely present in training data, this starts closer to a negotiation lawsuit.

I would file this under Llama’s structural cost, not a short-term model shutdown risk. Meta has cash, lawyers, and political reach. One FT snippet will not slow Llama distribution by itself. The pressure lands elsewhere: open-weight models are cheap to adopt because someone else absorbs the training cost. If copyrighted training data becomes a recurring licensing expense, Meta’s pitch changes. It stops being “free open AI for everyone” and becomes “Meta pays the input bill so the market standardizes around our weights.” Zuckerberg can probably defend that. He just may have to defend it in discovery first.

May 3Sunday

r/LocalLLaMAMay 3, 02:11

Built a C++17 transformer from scratch with 0.83M params and CPU training

Reddit user Suspicious_Gap1121 released Quadtrix.cpp, a C++17 GPT-style model with 0.83M parameters. It uses 4 layers, 4 heads, 200d width, and a 128-character context; one CPU core trained on 31.4M characters for 76.2 minutes to 1.6371 nats val loss. The key detail is handwritten backprop for LayerNorm, attention, Q/K/V, dropout, and AdamW without PyTorch, BLAS, or autograd.

Why it matters: HKR-H/K/R all pass: the no-framework C++17 build is clickable, the training setup is specific, and local-LLM builders care about dependency-free control. It stays in the 72–77 band because it is a small personal project.

May 2Saturday

MIT Technology Review · AIMay 2, 06:08

Musk v. Altman week 1: Musk says xAI distills OpenAI models

Elon Musk testified in week 1 of Musk v. Altman, saying he gave OpenAI $38 million in funding. He asks the court to remove Sam Altman and Greg Brockman and unwind OpenAI’s for-profit restructuring. The sharp detail: Musk said xAI partly distills OpenAI models, while OpenAI previously accused DeepSeek of similar conduct.

Why it matters: HKR-H/K/R all pass: the trial has conflict, concrete facts include $38M and xAI’s distillation admission, and OpenAI governance is a live nerve. No ruling or product-level change, so it stays below P1.

Take

Musk testified that he gave OpenAI $38 million and admitted xAI uses OpenAI models to train Grok. Honestly, the money claim is the courtroom hook; the distillation admission is the AI-industry problem sitting in plain sight.

The $38 million figure matters legally, not technically. Musk frames it as free funding for a nonprofit that later became, in his words, an $800 billion company. The article says OpenAI is racing toward an IPO near a $1 trillion valuation. At that scale, $38 million is evidence for governance intent, not economic authorship. His requested remedy is huge: remove Sam Altman and Greg Brockman, and unwind OpenAI’s for-profit restructuring. Courts will care about charters, fiduciary duties, donor conditions, and control rights. They will not simply relitigate a founder’s regret.

The sharper line is that xAI “partly distills” OpenAI models. The article does not disclose the share of training data, the API path, the number of generated samples, the exact wording from Musk, or whether the behavior violated OpenAI’s terms. Those missing facts matter. Distillation can mean many things: teacher-model completions, preference pairs, refusal-boundary data, synthetic reasoning traces, eval calibration, or large-scale supervised fine-tuning. Those are not legally or technically identical.

Still, practitioners know why this landed hard. Distillation is not a vague ethics issue. It is a concrete capability-transfer mechanism. You query a stronger model, collect outputs, filter them, and train a weaker or cheaper model on the result. The more capable the teacher, the more its outputs resemble subsidized expert labeling. If the teacher is a closed frontier model, its product becomes part dataset, part API, part competitor training substrate.

That is exactly why OpenAI’s earlier posture toward DeepSeek now looks awkward. OpenAI had accused DeepSeek of similar conduct, centered on whether DeepSeek used OpenAI outputs to train its own models. The commercial theory is straightforward: don’t use our paid model as a synthetic-data factory for a rival. The problem is that Musk’s admission suggests the norm is not confined to one Chinese lab or one suspicious competitor. It smells like a common frontier-model practice that companies prefer to describe differently depending on whether they are teacher or student.

I have always thought the industry moralizes distillation too much. Stanford’s Alpaca used 52,000 instruction-following examples generated from text-davinci-003 back in 2023. Vicuna, ShareGPT-derived data, and self-instruct pipelines pushed the same lesson: if a model is accessible through an interface, some of its behavior will leak into the ecosystem. The difference is scale, automation, contractual language, and lawyer count. OpenAI can ban training competitors on its outputs through terms of service. That is a real commercial boundary. But frontier labs also train on vast public, licensed, scraped, and synthetic mixtures. When model outputs become protected data assets, the line suddenly hardens.

I also do not buy Musk’s clean “mission restoration” framing. The article says he wants OpenAI restored to its original nonprofit structure. The same article says xAI is expected to go public as part of SpaceX as early as June, at a target valuation of $1.75 trillion. That is a massive number, larger than the IPO narrative attached to OpenAI. A founder pushing his own AI company toward public-market liquidity is also asking a court to freeze a rival’s corporate path. Safety can be part of the case. Competition is plainly part of it too.

The AI-doom testimony needs the same discipline. Musk warned that AI could destroy us all. The article does not disclose a technical risk model, a concrete failure path, or a governance mechanism he proposed from the stand. Without that, the statement functions as litigation rhetoric. OpenAI’s 2015 nonprofit mission really did revolve around AGI benefiting humanity. But by 2026, “safety” has become a strategic language layer. Anthropic uses it in product boundaries. OpenAI uses it in governance arguments. xAI uses “truth-seeking” as brand posture. Underneath, the companies are fighting over GPUs, talent, user traffic, model outputs, and feedback loops.

The poaching detail also matters, though the article gives too little to judge it. It says Musk sat through revelations that he had poached OpenAI employees for his own companies. It does not give headcount, dates, roles, compensation, or whether any restrictive covenants were involved. I would not overread it. But paired with the distillation admission, it shows the real shape of frontier competition. It is not just benchmarks, model cards, and parameter counts. It is employee movement, user conversations, synthetic data rights, API terms, and courtroom discovery.

That is where this case can become bigger than Musk versus Altman. Closed-model companies have spent years treating outputs as product. Now those outputs are also training fuel, eval material, and behavioral IP. If courts start drawing sharper lines around generated text as a protected competitive asset, the synthetic-data supply chain changes fast. Large labs can license data, log provenance, route through legal review, and train on their own user exhaust. Smaller labs often have an API key, a scraper, and a filtering script. Legal clarity may sound fair, but it will favor companies with distribution and counsel.

I have one complaint about the article itself. The headline correctly grabs the xAI admission, but the body does not provide the courtroom transcript or exact exchange. “Uses OpenAI’s models to train its own” can cover benign eval-adjacent usage or large-scale output harvesting. Those are different facts. MIT Tech Review may have the courtroom context, but readers need the precise quote before turning this into a clean hypocrisy verdict.

Even with that caveat, this first week put a quiet industry habit into the public record. Everyone has talked about synthetic data as if it were a neutral scaling trick. In litigation, it becomes provenance, contract compliance, and unfair competition. That is the part AI teams should care about. Not the founder drama. The training-data boundary around model outputs is becoming a legal surface.

May 1Friday

Synced · WeChatMay 1, 13:01

The Evolution of RL: From PPO to MaxRL in LLM Reasoning Training

Jiqizhixin translated Alexander Weers' article on RL algorithms for LLM reasoning from 2024 to 2026. It covers REINFORCE, PPO, GRPO, RLOO, Dr. GRPO, DAPO, CISPO, MaxRL, DPPO, and ScaleRL, comparing critic removal, clipping, normalization, and pass@k goals. The key signal is mechanism choice, not algorithm names.

Why it matters: A strong technical explainer, not a model or paper release. HKR-H comes from the PPO→MaxRL arc, HKR-K from concrete mechanism comparisons, and HKR-R from live RL-recipe choices; the higher technical bar keeps it in low featured.

The Verge · AIMay 1, 02:16

Elon Musk confirms xAI used OpenAI’s models to train Grok

Elon Musk testified Thursday in a California federal court that xAI used OpenAI models to improve Grok. The mechanism described is model distillation: a larger teacher model transfers knowledge to a smaller student model. The post does not disclose which OpenAI models, data volume, or training runs.

Why it matters: HKR-H/K/R all pass: Musk confirmed in court that xAI used OpenAI models to train Grok, with distillation as the mechanism. Missing model names, scale, and runs keeps it in 78–84, not P1.

Take

Elon Musk testified in California federal court that xAI used OpenAI models to improve Grok, with no model names, data volume, or training-run details disclosed. That is a small factual disclosure with a large blast radius. xAI has spent two years performing opposition to OpenAI: less captured, less censored, less corporate, more truth-seeking. Now its founder has acknowledged that Grok benefited from OpenAI as a teacher model. Technically, this is unsurprising. Politically, it is ugly. Legally, it is where the sharp edges start.

Distillation is normal. Big labs use stronger internal models to train smaller or cheaper ones all the time. GPT-4-class systems can generate synthetic instruction data. Claude-family models can provide preference data for smaller variants. Google has used Gemini-family outputs in synthetic-data loops. Open-source builders have also used strong hosted models to create instruction-tuning corpora. The mechanism is not exotic: teacher outputs, student training, filtering, evaluation, repeat. The issue is whose teacher model was used, under which terms, through which access path, and at what scale.

The Verge snippet gives only the headline fact and the mechanism. It does not disclose whether xAI used GPT-4, GPT-4o, an o-series reasoning model, or another OpenAI system. It does not say whether access came through the API, ChatGPT, an enterprise account, scraped front-end use, or some other route. It does not disclose whether this was a narrow experiment or a recurring part of Grok’s training pipeline. Those missing details matter. One million teacher responses for safety refusals and one billion reasoning traces for capability transfer are completely different events.

I am especially wary of the phrase “common industry practice” here. It is technically true and legally incomplete. Distilling your own frontier model into your own smaller model is one category. Using a direct competitor’s protected model outputs to improve a competing commercial model is another. OpenAI, Anthropic, and Google have all placed restrictions around using outputs to train competing models, though the exact wording varies by product and contract. I have not checked every 2026 terms-of-service revision line by line, but across 2024 and 2025, this restriction was standard in major model API agreements. If xAI obtained OpenAI outputs through ordinary product access and fed them into Grok training, that is not just “everyone does synthetic data.” That is a contract and unfair-competition fight.

The setting matters too. This surfaced through courtroom testimony, not through an xAI technical report. If the distillation were clean, authorized, or strategically harmless, a lab would usually frame it with process language: teacher model, synthetic data generation, filters, eval deltas, maybe a benchmark table. Here, the public record has none of that. The title gives the hard claim. The body snippet gives the general mechanism. The article does not disclose authorization status, dataset size, model identity, or training procedure. For practitioners, those four blanks are the story.

The broader industry context is uncomfortable for everyone. Model-output laundering has become a quiet substrate of AI development. When OpenAI previously alleged that DeepSeek-related actors may have used OpenAI outputs for distillation, a lot of people defended open competition in public while privately recognizing the obvious: frontier model outputs are already treated as shadow training data. Meta’s Llama license also restricts using Llama outputs to improve non-Llama models. Anthropic has been aggressive about automated access and competitive training use. Musk’s testimony gives OpenAI a cleaner narrative example than any blog post could: even its loudest critic apparently used its models as a capability source.

I do not fully buy the moral purity narrative OpenAI can build from this either. The model industry grew by absorbing public internet content at massive scale, and many copyright questions remain unresolved. Labs that were once scrapers now want enforceable rights over their own outputs. That does not excuse xAI if it violated terms. It does explain why this dispute will not stay confined to Musk. The next phase of frontier-model competition is partly about whether generated text is merely output, licensed content, confidential know-how, or evidence of model substitution. Courts, not benchmark leaderboards, will draw part of that boundary.

For Grok, the reputational damage lands faster than any technical consequence. Grok has been sold on three ideas: a looser speech posture, access to X’s real-time data stream, and distance from OpenAI’s worldview. If the capability baseline was boosted with OpenAI teacher outputs, the product story gets awkward: distribution from X, personality from Musk, and performance help from the rival it mocks. Fans will shrug. Enterprise buyers will not shrug as easily. A compliance team can ask a simple question: if my company blocks OpenAI exposure for internal data, why should I trust a vendor that admitted using OpenAI models in its own improvement loop?

I want the full transcript before assigning legal weight. A question about whether Musk understood distillation is not the same as a question about whether xAI systematically trained Grok on OpenAI outputs. The Verge headline says Musk confirmed xAI used OpenAI’s models to train Grok. The summary says xAI used OpenAI models to improve Grok. Both are serious, but the snippet does not provide the verbatim exchange. My read: the disclosure is already enough to dent xAI’s public posture. Damages, injunction risk, and discovery exposure depend on the access logs, contract terms, prompt-output datasets, and training lineage records.

TechCrunch · AIMay 1, 02:03

Elon Musk testifies that xAI trained Grok on OpenAI models

Elon Musk testified that xAI trained Grok on OpenAI models. The post only says distillation concerns frontier labs; it does not disclose scale, model versions, or case context.

Why it matters: All HKR axes pass: Musk’s testimony puts xAI, Grok, OpenAI, and distillation evidence in one story. Missing model versions, scale, and full litigation context keep it at the low end of the 85+ band.

Take

Elon Musk testified that xAI trained Grok on OpenAI models; the body gives no scale, versions, timing, or legal context.

This is a tiny article with a big reputational blast radius. xAI has spent its public life positioning Grok against OpenAI: less filtered, more plugged into X, more aligned with Musk’s anti-OpenAI story. The title cuts straight through that posture. Distillation itself is common. The problem is that xAI’s brand depends on the claim that it is building a different frontier path. If Grok’s training pipeline used OpenAI model outputs, even at one stage, then xAI’s independence story gets messier fast.

The snippet only says “distillation” is a hot topic as frontier labs try to stop smaller competitors from copying their models. That leaves out the facts that matter. We do not know whether xAI used GPT-4, GPT-4o, GPT-5, or an older OpenAI endpoint. We do not know whether the use was supervised fine-tuning, synthetic Q&A generation, preference data, evaluation bootstrapping, tool-use traces, or direct student-model training. We do not know whether the corpus was 50,000 examples, millions of completions, or a large synthetic-data pipeline. We do not know whether this touched Grok-1, Grok-2, Grok-3, or an internal unreleased model. The title says testimony exists; the RSS body does not give the transcript.

That distinction matters because “trained on OpenAI models” is a very wide phrase. Plenty of teams have used stronger models to generate synthetic data, especially for coding, math, instruction following, and safety evaluations. Alpaca did this openly in 2023 with 52,000 instruction-following examples generated from text-davinci-003. After that, WizardLM, OpenOrca, and a lot of open SFT datasets normalized teacher-model outputs as a bootstrap path. So if xAI used a small amount of OpenAI API output for labeling, evals, or early data generation, the technical fact is not shocking. The ugly part is the commercial and legal context. OpenAI, Anthropic, and Google have all put restrictions in their terms against using outputs to train competing models, though exact language has changed over time.

The obvious comparison is the OpenAI-DeepSeek fight earlier this year. OpenAI’s concern was not that one model can learn from another in the abstract. The concern was that a competitor used API access or generated outputs to bypass training cost, data scarcity, and contractual barriers. Microsoft was also reported to have looked into suspicious account behavior tied to high-volume OpenAI access. If xAI did anything similar, Musk’s litigation posture against OpenAI becomes awkward. He has accused OpenAI of betraying its founding mission, while his own AI company allegedly used OpenAI models inside Grok’s training path. That is not a technical inconsistency. It is a narrative self-own.

I do want to push back on the easy headline reading. Distillation is not a binary offense. It can mean legitimate API use for internal evaluations. It can mean a terms-violating attempt to train a competing model. It can mean a small data-cleaning assist. It can mean systematic extraction of a frontier model’s behavior. Without model version, call volume, account provenance, timeline, terms language, and the actual testimony, we cannot assign legal risk. The TechCrunch snippet also does not say which case produced the testimony. Was this from Musk’s dispute with OpenAI? Was it another deposition? Did Musk volunteer the point, or confirm it under questioning? The body does not disclose that, so the safe reading stays narrow.

The broader technical issue is that “clean” model lineage is becoming harder to defend. Frontier labs train on public web text, code repositories, forums, papers, synthetic data, user interactions, and model-generated artifacts that have already leaked back into the web. OpenAI wants to stop smaller competitors from distilling its systems. Anthropic wants to stop high-volume sampling of Claude outputs. Google has the same incentive around Gemini. Those concerns are legitimate, but proof gets hard fast. “The model sounds like mine” is not enough. A serious case needs API logs, batch prompt templates, account linkage, sampling rates, training-set placement, and reproducible behavioral overlap between the alleged student and teacher distribution.

My read: if the transcript shows xAI systematically used OpenAI outputs to train Grok, Musk loses the moral high ground before any court ruling lands. If the underlying fact is early bootstrapping or evaluation data, the headline is doing too much work. AI practitioners should not reduce this to “Grok copied ChatGPT.” The missing fields are the story: which OpenAI model, how many outputs, which training stage, and whether the use violated the terms in force at the time. Until those are disclosed, the strongest supported claim is that xAI touched OpenAI model outputs in Grok’s training pipeline. That is damaging for the posture, but not yet enough to prove Grok’s capability stack was copied.

Apr 30Thursday

MIT Technology Review · AIApr 30, 23:59

Goodfire releases Silico, a mechanistic interpretability tool for debugging LLMs

Goodfire released Silico, letting engineers inspect and adjust LLM parameters during training. It maps neurons and pathways; one Qwen 3 neuron triggered trolley-problem-style outputs. Pricing is case-by-case, and the post does not disclose rates.

Why it matters: HKR-H/K/R all pass: Silico offers a concrete interpretability-debugging mechanism. It stays at 76 because this is a startup product preview with no pricing or adoption scale disclosed.

Take

Goodfire picked the right wedge: mechanistic interpretability only matters commercially if it enters training, not post-hoc safety theater. Silico claims coverage from dataset building through training, with neuron and pathway mapping plus parameter edits. The Qwen 3 trolley-problem neuron is a concrete hook, and it is closer to an engineer’s workflow than another audit dashboard.

I don’t buy the “precision engineering” framing yet. The article gives Goodfire’s “off-the-shelf” claim, but not pricing, latency overhead, supported model sizes, named customers, or a reproducible hallucination-reduction benchmark. Anthropic already showed sparse features and the Golden Gate Bridge-style neuron demos; production control is a different bar. Silico’s test is not whether it can surface a neuron. It is whether a parameter edit preserves capability, safety, and out-of-distribution behavior after the next training run.