OpenAI has created a new safety group as it works on the successor to GPT-4 while grappling with the recent departure of high-profile members who criticized its commercial intent.

Termed the Safety and Security Committee (SSC), the team's leadership includes OpenAI CEO Sam Altman, Bret Taylor (who is set to be the chair), Adam D'Angelo, and Nicole Seligman, all of whom also sit on the board of directors.

Other SSC members include various team leaders at OpenAI, including Jakub Pachocki, who has been chief scientist for just 13 days after he [1]replaced co-founder Ilya Sutskever .

[2]

OpenAI [3]says the safety team will advise the board of directors on "critical safety and security decisions" from now on. Those decisions will, presumably, impact the development of the successor to GPT-4, which OpenAI briefly mentions in its announcement as its "next frontier model."

[4]

[5]

"While we are proud to build and release models that are industry-leading on both capabilities and safety, we welcome a robust debate at this important moment," the company said, without specifying what it expects to be discussed.

First on the docket is a 90-day period of developing safety recommendations for the board's consideration, though the implication is that Altman and other directors have the final say as they get to review the recommendations. Naturally, the OpenAI CEO and the four other leads will also have their chance to influence the recommendations before they even reach the board of directors.

[6]

The formation of the new security board is likely wrapped up with two high-profile departures that happened earlier this month: that of Sutskever and Jan Leike. Their exits from OpenAI were immediately followed by the dissolution of the company's Superalignment group, which existed to evaluate AI safety concerns over the long term. Leike had been the leader of the Superalignment team up until his departure.

OpenAI also lost Daniel Kokotajlo, who worked on OpenAI's governance team, earlier this month, and in February co-founder Andrej Karpathy quit as well.

While Sutskever and Karpathy have declined to delve too deeply into the reasoning behind their departures, Leike and Kokotajlo have made it clear that they resigned over disagreements on AI safety.

[7]By 2030, software developers will be using AI to cut their workload 'in half'

[8]OpenAI tells employees it won't claw back their vested equity

[9]Top AI players pledge to pull the plug on models that present intolerable risk

[10]AI might be coming for your job, but Sam Altman can't go on dinner dates anymore

[11]Google thinks AI can Google better than you can

"Over the past years, safety culture and processes have taken a backseat to shiny products," Leike [12]said the day before the Superalignment team was abolished. "We are long overdue in getting incredibly serious about the implications of AGI… OpenAI must become a safety-first AGI company."

Similarly, Kokotajlo [13]said he "quit OpenAI due to losing confidence that it would behave responsibly around the time of AGI."

[14]

AI safety is undoubtedly a contentious issue at OpenAI, and that's probably a key reason why the new Safety and Security Committee was created. Although whether the new group will actually satisfy safety advocates is an open question. ®

Get our [15]Tech Resources



[1] https://www.theregister.com/2024/05/15/openai_cofounder_ilya_sutskever_leaves/

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZlZUA@XUke1LxC6MDK4XmwAAAMQ&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://openai.com/index/openai-board-forms-safety-and-security-committee/

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZlZUA@XUke1LxC6MDK4XmwAAAMQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZlZUA@XUke1LxC6MDK4XmwAAAMQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZlZUA@XUke1LxC6MDK4XmwAAAMQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://www.theregister.com/2024/05/28/software_development_2030/

[8] https://www.theregister.com/2024/05/24/openai_contract_staff/

[9] https://www.theregister.com/2024/05/22/ai_safety_seoul_declaration_signed/

[10] https://www.theregister.com/2024/05/20/openai_safety_culture/

[11] https://www.theregister.com/2024/05/15/google_ai_developer/

[12] https://x.com/janleike/status/1791498174659715494

[13] https://www.lesswrong.com/users/daniel-kokotajlo

[14] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZlZUA@XUke1LxC6MDK4XmwAAAMQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[15] https://whitepapers.theregister.com/