OpenAI paused RL training for two weeks on cyber-risk signals, and Altman names "various degrees of misalignment" as the real cause

What happened

OpenAI disclosed it paused reinforcement-learning training on its next model family, codenamed Astra, for a little over two weeks after preliminary signs the model might cross the "Critical" tier on its own Preparedness Framework for cybersecurity capability — and its single largest planned frontier training run is still on hold. The trigger was a combination of the Hugging Face/Modal Labs breach this thread already tracks and internal evaluation results on Astra. New safeguards tied to the pause: ~20% additional compute overhead for training-time monitoring, automated alerts within a 30-minute window on concerning activity, and training runs pausing automatically if OpenAI's safety team cannot rule out a false alarm inside that window. Cost of investigating the original breach is estimated at $4-15M in compute. (OpenAI, Fortune)
Sam Altman told TIME the slowdown has no single "smoking gun" — it's a collection of research observations showing "various degrees of misalignment" as capability outran the researchers' own expectations, and he named the field's race dynamic itself as the danger: "I don't like the whole thing in this field of 'we have to race' or 'we have to do this because somebody else is going to do it.' I think that's a very dangerous dynamic." OpenAI has not disclosed what the misalignment research actually found. This is the same week's second lab head making a public case for slowing down (Amodei's pacingthefrontier.com sits at this thread's opening watch) — but the first time either lab has tied a concrete, dated production decision (a two-week RL pause on a named model) to that argument rather than just an open letter. (Time, Techmeme/Axios)
OpenAI separately announced new containment safeguards and a rewrite of its Preparedness Framework — the formal response to the Hugging Face breach this thread has tracked since 07-29. New measures: reasoning-trace/activity-log monitoring targeting a 30-minute alert window on worrying behavior in unreleased models; stricter network isolation ("a single compromise of a workload or supporting service does not, by itself, allow for unauthorized access to the Internet, or other internal networks" — OpenAI's own quote); and capability-scaled oversight controls. ⚠️ Sits awkwardly against the FT's 08-16-reported dissolution claim and OpenAI's own 08-17 denial above — a framework rewrite credited to a team whose existence was publicly disputed one day earlier, unreconciled by any outlet. A Hacker News thread ("Be skeptical of OpenAI's rogue hacker agent story") is circulating alongside the coverage — not chased to a primary rebuttal, but noted as contested framing rather than uncontested fact, matching this map's practice on the GLM-5.3/Kimi K3 sandbox-escape dispute. (TechCrunch, Wired)

Sources 6

OpenAI openai.com primary source
Fortune fortune.com high 0.876
Time time.com high 0.826 generally reliable
Techmeme/Axios techmeme.com unrated
TechCrunch techcrunch.com high 0.886 no consensus
Wired wired.com high 0.852 generally reliable

Credibility ratings combine two public datasets: Lin et al. 2023, PNAS Nexus 2(9):pgad286 (CC BY 4.0) for the domain-quality score, and Wikipedia's perennial-sources list (CC BY-SA 4.0) for the reliability tier. A rating describes an outlet's general record, never this particular article. Unrated means absent from those datasets — not a judgement.