The debate over slowing down AI development is starting to take on concrete substance. Sam Altman has revealed that OpenAI has begun operating pre-training safety checks and is in talks with competitors about joint voluntary self-regulation, while in the UK, members of Parliament are calling for new legislation to address AI's threats to human rights. In the local LLM space, the arrival of a new 84GB VRAM GPU is making waves, and at the same time, records of clever workarounds for running large models on limited memory are being shared. Here is a roundup of the news that caught our attention today.
Altman's "Pacing" Gets Concrete — Pre-Training Safety Checks and Three-Company Talks
Sam Altman has offered content that further substantiates his position on pacing AI development, building on his earlier claim that progress will continue even if development slows. According to [The Decoder](https://the-decoder.com/sam-altman-calls-for-pacing-ai-development-but-promises-rapid-progress-will-continue/), OpenAI has begun running safety checks before executing major training runs. Moreover, as reported by The Information, it has emerged that OpenAI has been in discussions with Anthropic and Google for several months regarding joint voluntary self-regulation.
This series of slowdown debates has until now been covered largely through statements from the top executives of each company. CNBC, under the title "Altman spells out why the AI industry wants to slow down," reports on this movement with references to Anthropic's Amodei and Musk. Meanwhile, the WSJ published an analysis arguing that "the clash between money and safety has created a serious crisis in AI," laying out a narrative of how rapidly expanding investment and safety considerations came to work against each other.
Yesterday we covered a report that OpenAI had put its IPO plans on hold due to safety concerns. What deserves attention, however, is less any individual decision than the fact that the discussion is shifting toward "mechanisms" — the institutionalization of safety checks and voluntary self-regulation talks among three competitors. From an exchange of statements to the design of operations — the granularity of the debate appears to be changing.
UK Parliament Demands New Legislation to Address AI's Threats to Human Rights
In the UK, calls for regulation are coming from within Parliament. According to [the BBC](https://www.bbc.co.uk/news/articles/cwyzvgj70y4o), members of both the House of Commons and the House of Lords have called for the enactment of new legislation to address threats to human rights posed by AI.
What can be read from the reporting at this point is that the legislators judged that existing legal frameworks cannot adequately handle the human rights risks AI brings, and raised their voices in demand of new legislation. Neither the expected content of such a bill nor when it might be introduced has been made clear, so we will need to wait for future developments.
While the slowdown debate in the US proceeds largely around industry-led self-regulation, the UK appears to be exploring a path of parliamentary legislation. Which will achieve practical effectiveness first — market self-regulation or regulation by law — looks likely to become one of the focal points of AI policy going forward.
The RTX PRO 5500 Blackwell 84GB Arrives — "GPU-Poor" Ingenuity Accelerates Too
In the local LLM community, the [release of the RTX PRO 5500 Blackwell (84GB VRAM)](https://www.reddit.com/r/LocalLLaMA/comments/1wfxi36/rtx_pro_5500_blackwell_84gb_released/) became a hot topic. 84GB of VRAM on a single card is a level that consumer GPUs have never reached, and it looks set to expand the options for running large models locally.
At the same time, users who cannot reach for expensive new GPUs continue to come up with clever workarounds. On r/LocalLLaMA, someone shared [an attempt to run Qwen 3.8 Next on an RTX 5060 Ti (16GB VRAM) with 32GB RAM](https://www.reddit.com/r/LocalLLaMA/comments/1wfxl0m/running_qwen_38_next_on_16vram32ram_a_usefulfun/). The setup: targeting the roughly 68.95GB REAP-quantized version of the model, the huge retrieval table that makes up the majority of the model (the N-gram portion) is streamed from an SSD via lazy mmap, while the remaining weights and the KV cache are packed into VRAM and system memory — enough to secure practically usable speed.
There was also a post [asking for advice](https://www.reddit.com/r/LocalLLaMA/comments/1wfy4vo/what_are_the_current_best_retail_gpus_for_max/): "I want to cancel ChatGPT Plus and go fully local — which GPU gives the most VRAM for the money?" — suggesting that a meaningful number of people are rethinking what they pay for cloud AI and moving to local setups. High-end new GPUs on one end and ingenuity under constrained environments on the other — both extremes are advancing simultaneously in today's local LLM scene.
Readers Writing Their Own Stories with Chatbots
While the publishing industry struggles with authors' use of AI, on the reader side, a way of enjoying chatbots — having them write stories to one's own tastes — appears to be spreading. A [WIRED article](https://www.wired.com/story/chatbot-generated-fiction-i-like-my-big-rat-wife/) takes a close look at the realities of the people creating such custom fiction. "I Like My Big Rat Wife," which also gives the article its title, is said to be one of the works born in this way.
The debate over AI use in commercial publishing has proceeded mainly around professional writers and publishers. But the usage pattern of individuals commissioning stories for their own sake can be seen as an example of AI directly satisfying demand that never existed in the market. What impact will readers' moves have on discussions that frame publishing as purely a "supply-side" problem? That is the question this reporting poses.
Prompt Injection Measured Across 1,509 Attempts — What Separated Success from Failure Was "Number of Steps"
On the security front, a large-scale empirical test by a domestic developer draws attention. In a [Zenn article](https://zenn.dev/acntechjp/articles/zenn-agent-injection-model-comparison), indirect prompt injection against multi-stage agents was tested in 1,509 attempts across five Gemini models, and their success or failure was analyzed.
The results were intriguing. Differences in robustness between models were not statistically significant at the pre-registered unit of analysis, and the most compelling explanation was said to be "the number of steps required for injection." A one-step attack that simply gets the model to send confidential information succeeded 28.0% of the time, whereas a two-step attack — first making the model retrieve the information, then send it — succeeded only 6.7% of the time. The author cautiously adds a reservation, however: when tested with independent units, the one-sided p-value was 0.0625, which strictly speaking fell short of the 0.05 significance level.
Furthermore, Google's Model Armor, even in its most detection-friendly configuration, let all 24 items of the frozen validation corpus pass through unnoticed. Operational pitfalls are also pointed out, such as the filtered version having to be specified via an alias, and migration notices appearing only deep in the sanitize logs. For hardening defenses, "make it take time" — the measurement carries the suggestion that structuring the paths to confidential data so they require more steps may be effective.
Don't Give AI Agents Execution Permissions — Six Months of Operation Led to "Separating Body and Brain"
Finally, a hands-on account of AI agent design philosophy. In a [Zenn article](https://zenn.dev/sodeyama/articles/tech-ai-agent-body-and-brain), Sodeyama of DeploAI, Inc. has begun publishing a record of about six months operating a resident agent that automatically handles everything from finding stalled work, to fixing it, to confirming the result.
Initially, the configuration gave the LLM tools and entrusted execution to it as well. Now, however, it has been switched to a configuration in which the LLM is given no execution permissions whatsoever — the LLM makes only the judgments, while deterministic code handles execution. The reasons that led to this design, which the author calls "separation of body and brain," and exactly where the lines were drawn, are to be documented in a series of posts.
LLM judgments are probabilistic, and outputs fluctuate even for the same input. Meanwhile, shifting execution to deterministic code makes failures easier to reproduce, verify, and fix — the observation that, in use cases where agents run continuously, this separation can make or break maintainability, is likely to serve as a useful reference for many implementers.
Wrapping Up
The slowdown debate has entered the stage of designing concrete mechanisms, and regulatory approaches are beginning to diverge by country. At the same time, on-the-ground accumulation — local LLM workarounds and agent design insights — continues steadily. Following not only headline news but also these diligent records looks set to provide a valuable clue for not misreading where AI actually stands today.