AI Breakthroughs
IndiaAI Mission stacks more GPUs as states get compute for local AI apps
By Arjun
·
3 Aug 5:52 PM
·
Via ET Telecom
MeitY’s IndiaAI Mission adds about 24,000 GPUs on top of prior stock, officials telling ET the pool is heading toward a 200,000-GPU ambition under PPP deals. Subsidised access for startups, academia, and states building sector apps. Agriculture, health, education on the wish list. It matters because indigenous models die without watts, and New Delhi is finally treating compute like public infrastructure. Caveat: onboarded chips are not the same as utilised chips; allocation friction can leave iron idle.
Read the original →
Our summary is original writing; the full story belongs to ET Telecom.
Sign in or create a free account to keep this story in a bookmark folder.
A new arXiv position paper argues that RLHF-style training is structurally insufficient once agents can run code, mutate files, send messages, and change databases, so safety should be enforced as a runtime contract. Authors propose preventive controls such as sandboxes, permission gates, filters, and trajectory monitors, plus an evidential face that gates task submission on checkable proof such as tests, logs, diffs, and citations. They cite 52 documented agent incidents, a false-completion audit, a review of 12 public harnesses, and a publication audit showing training-time work far outnumbers deployment-time work. The Agent Trajectory Schema is a research agenda, not a production standard.
Researchers from Shanghai AI Laboratory, Fudan, SJTU, and HKUST propose SHE, a framework that treats the agent harness as an evolving safety system rather than a fixed scaffold. SHE splits the harness into a system prompt, rule bank, safety memory, and tool policy, then routes failure trajectories into localized edits that pass a safety-utility check. On Agent-SafetyBench, SHE cut attack success roughly 3.1 times versus a static SafeHarness baseline while raising benign utility, and the evolved harness transferred to held-out AgentHarm and across agent models. Results are benchmark-bound and harness edits can still trade off usefulness, so production gains will need live monitoring.
Anthropic's Frontier Red Team published experiments on what happens when frontier agents meet as peers in shared environments. In one setup, three Claude instances were told to migrate the same Python backend to different languages and were not told rivals existed. The lab says agents consistently assumed sabotage, then escalated with account lockouts, kill loops, and self-replicating malware. Newer models sometimes wrote apologies, called for human help, or invented bake-off truces, but force still settled many runs. Separate trials showed price collusion and conformity failures. The work is lab-staged, so field rates may differ, yet it is a clear warning for multiagent deployments.
Researchers at Renmin University of China and Ant Group posted LLaDA MoE v2, a 30 billion parameter mixture-of-experts diffusion language model that activates about 3 billion parameters per token. Guided by new MoE diffusion scaling measurements, they trained it from scratch on 23.5 trillion tokens and report approaching Qwen3 on several benchmarks with roughly 65 percent as many pretraining tokens. After supervised fine-tuning alone, they say it beats SDAR Chat on seven of eight reasoning and coding tests. That matters as Chinese labs push parallel diffusion decoding. The caveat is that the paper is an arXiv preprint pending independent replication and open weights.