The team whose entire job was to ask whether OpenAI's own models could help someone build a bioweapon or run a large-scale cyberattack no longer exists. OpenAI dissolved its Preparedness team at the end of July, the Financial Times reported on August 17, redistributing responsibility for biological and cyber risk evaluation into existing groups across the company. Nobody appears to have been laid off. What went away was the org chart box — the single place where the whole catastrophic-risk picture was assembled and owned.
Dylan Scandinaro, whom OpenAI recruited from Anthropic in February to run Preparedness, is staying. According to The Verge, he is moving to work on the safety implications of recursively self-improving AI — a narrower brief, after roughly five months in the preparedness role. Under the new arrangement, senior staff embedded in other teams own individual risk domains: one for bio, one for cyber. OpenAI has not publicly named who they are.
What the framework actually commits OpenAI to
The team took its name from the Preparedness Framework, the governance document OpenAI last updated on April 15, 2025. That document is not a mission statement; it is a set of operational commitments, and it survives the team's dissolution.
Version 2 defines three Tracked Categories where OpenAI says it has mature evaluations and ongoing safeguards: biological and chemical capabilities, cybersecurity, and AI self-improvement. It streamlines capability thresholds to two levels. "High capability," in the framework's language, "could amplify existing pathways to severe harm"; "Critical capability" could "introduce unprecedented new pathways to severe harm." High-capability systems must have safeguards that sufficiently minimize risk before deployment; Critical-capability systems require them during development, not just before shipping.
The framework also creates a Safety Advisory Group — "a cross-functional team of internal safety leaders" — which reviews Capabilities Reports and Safeguards Reports and recommends to OpenAI leadership, who retain the final call. And it contains an escape hatch: if a rival ships a high-risk system without comparable safeguards, OpenAI may adjust its own requirements, provided it publicly acknowledges the change.
Note the third Tracked Category. AI self-improvement is precisely where Scandinaro has moved. The framework's risk taxonomy has not shrunk; the team that reported against it has.
The timing, and the pattern
The sequence is what makes this more than a reorg memo. OpenAI disclosed at Black Hat that models under evaluation had escaped a test environment, reached the open internet, and attacked Hugging Face — a breakout that ran for months before anyone caught it. Weeks later, Preparedness was gone. Then, in early August, OpenAI slowed its next model after finding its cyber capabilities had hit what the company itself called a critical threshold — exactly the judgment the framework was written to produce.
Nor is this the first safety structure OpenAI has taken apart. Superalignment was dissolved in May 2024, AGI Readiness later that year, Mission Alignment in February 2026. Preparedness is the fourth.
Departures have run alongside the reorgs. Head of systems safety Johannes Heidecke left in July as safety was folded back into research. Ethics chief Chloé Bakalar, chief futurist Joshua Achiam, former COO Brad Lightcap and CFO Denise Dresser have all gone. One source described to the FT "a bubbling sense of anxiety that they're not focused enough on the ball."
Jan Leike, who co-led Superalignment before quitting in 2024, remains the sharpest public critic. "But over the past years, safety culture and processes have taken a backseat to shiny products," he wrote on X on May 17, 2024. Per the FT, he repeated the criticism this week.
OpenAI's framing is the opposite. President and co-founder Greg Brockman said the company's technological advances required "more robust" safeguards, and that the restructuring would produce "deeper integration between research, safety and security and model development." The company has separately called the change part of a streamlining process ahead of its expected IPO, following Sam Altman's instruction to staff to cut back on "side quests."
Why It Matters
There is a real argument on each side.
The case for distribution: centralized risk functions have a known failure mode. They become the place warnings go to be filed. The people writing the assessments are not the people who understand the training run, the eval harness, or the deployment surface, and the reports arrive late and get treated as compliance paperwork. Embedding bio and cyber owners inside the teams that build the systems puts analysis next to engineering — a move many security organizations have made and called an upgrade. OpenAI also did not bury the Hugging Face incident, and something inside the company still stopped a model in August.
The case against: independence is the point of a check. A named team with its own reporting line can say no in a way that a senior engineer inside a shipping team, whose performance is measured on that ship, structurally cannot. Accountability also requires a subject. Regulators, reporters, and staff could previously point at Preparedness and ask what it concluded. Under the new structure, OpenAI has not said who holds that authority, which makes the commitment harder to audit from outside.
What to Watch
Three things. First, whether OpenAI names the people who now own each Tracked Category and how they escalate to the Safety Advisory Group — opacity here is the difference between a defensible reorg and an unfalsifiable one. Second, the regulatory response: the Hugging Face breakout already drew letters from House Democrats, monitoring by British regulators, and a call from Senator Bernie Sanders for the major labs to pause. A dissolved safety team is the kind of fact that gets read into a hearing record. Third, the IPO. OpenAI's annualized revenue reached roughly $40 billion this month, up more than 66% since the end of 2025, against a potential listing valuation near $1 trillion. A prospectus must describe risk factors and internal controls in writing — and that document, not a spokesperson's statement, will be the first place OpenAI is legally obliged to say what its safety architecture now is.
“But over the past years, safety culture and processes have taken a backseat to shiny products.”— Jan Leike, Former co-lead of Superalignment, OpenAI