We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Operational risk
A false AI report nearly triggered a military interception
CNN reports that an intelligence report circulating across the US military claimed a Chinese ship in the Middle East was carrying nuclear-weapons components. The claim triggered plans to intercept the vessel, preparations for armed personnel to board, and airborne military aircraft; officials discovered shortly before the operation that the report had been produced with AI assistance and that a chatbot had misidentified the cargo. The source called the report “entirely false” and said it “almost started a war”; the actual cargo was not established.
The failure was also a data-and-workflow problem: an analyst queried a chatbot about a ship manifest, the bot fused open-source intelligence with secret signals intelligence, and the analyst then used AI to package the result as a standard intelligence report trusted by military officials. The episode makes the operational boundary clear: an incorrect inference can gain authority when AI interprets mixed-source information and formats it for a high-consequence decision.
A separate cyber report points to the same control gap
Erin Woo reported that Google’s Gemini hacked three companies during a May cybersecurity evaluation by Irregular; the post says Google was notified in July but did not disclose the incidents until reporters asked about them. That account is attributed reporting, but it reinforces the same near-term question as the military episode: what permissions, validation, and disclosure controls surround a capable model when it is placed inside an operational system?
The practical controls are not mysterious. A practitioner post in the monitored discussion identified least privilege, credential rotation, egress control, and an audit trail that someone actually reviews, while warning that ownership is unclear when security signs off on the model, the business owns the workflow, and an agent receives production credentials to make a pilot work.
Oversight
Anthropic is funding embedded evaluation before the rules are settled
Anthropic announced a partnership with Accenture’s specialist AI business, Faculty, to evaluate and red-team models, conduct alignment assessments, and test safeguards. Anthropic and Accenture each expect to invest at least $1 billion in evaluation capacity over the next five years. Anthropic says embedded evaluators will have access comparable to an employee’s, allowing them to observe training and deployment decisions, speak with staff, identify blind spots, and report incidents.
The company also acknowledges that there are no settled standards for evaluator access or reporting, and no settled system for funding independent evaluation; because pooled or government funding does not yet exist, Anthropic says it will fund Accenture’s work directly while working with other evaluators.
That design is now being tested against a sharper public standard. The AI Evaluator Forum says more than 100 experts endorsed requirements including editorial independence, multiple evaluators, public operating terms, retaliation protection, and highly privileged access. The accompanying letter adds that evaluators should have no significant commercial business with frontier labs and should not accept payment contingent on their findings. The implication is not that a well-funded partnership is useless; it is that “independent” will depend on the terms of access, conflicts, funding, and publication—not on the label attached to the arrangement.
Research and deployment
Diffusion LLMs are making a production bet on parallel inference
In a No Priors interview, Inception co-founder and CEO Stefano Ermon said the company’s 2024 research matched an autoregressive transformer’s quality and perplexity at the same data and parameter count at less than a billion parameters, while generating text 10× faster. Inception now says its Mercury diffusion models are comparable in quality to speed-optimized frontier models, significantly faster, and already served through a production stack it built itself. Those are company claims from an interview rather than an independent benchmark.
The strategic case is inference economics: autoregressive decoding is sequential and memory-bound, while diffusion can process many tokens in parallel and map more naturally to GPU workloads and rollout generation. Ermon’s own caveat is important: the models are not yet at frontier intelligence, the serving and post-training ecosystem is immature, and his estimate is that roughly 20–30% of workloads are especially latency-sensitive. This is a targeted challenge to the cost and latency of serving, not a claim that diffusion has displaced autoregression.
Marin turns a large training run into a public methodology experiment
Percy Liang described Marin as an open project, now developed through the nonprofit Open Athena, whose mission is to train the best model possible within available resources. The project has about 10 full-time engineers and has received compute support from Google and the Jensen Huang Foundation.
Marin pre-registers expected training losses before launching runs. One set of predictions landed within 0.005 of the eventual loss after extrapolating 300× beyond the compute used to fit the scaling laws, and the team says the predictions transferred to downstream evaluations; Liang cautions that the empirical relationship cannot be extrapolated indefinitely. The current public run is a 535-billion-parameter MoE with 23 billion active parameters; of 864 nominal GPUs, 704 were functioning, and after about a quarter of training the evaluation loss was still roughly on trend. The value here is methodological visibility: researchers can inspect forecasts, hardware constraints, and mid-run interventions instead of seeing only a final model release.