外部施压见效，OpenAI承诺非营利机构“掌舵权”

Core Viewpoint - OpenAI announced a restructuring to become a Public Benefit Corporation while retaining control by its non-profit parent organization, amid pressure from various stakeholders and former employees [1][3] Group 1: Company Restructuring - OpenAI will transform its limited liability company, currently a subsidiary of a non-profit, into a Public Benefit Corporation, allowing employees, investors, and the non-profit to hold equity [1] - The decision to restructure was made after discussions with the attorneys general of California and Delaware [1] - OpenAI's board chair, Brett Taylor, indicated that the non-profit will maintain majority ownership, although specific ownership percentages were not disclosed [1] Group 2: Legal Disputes - OpenAI is currently involved in a legal dispute with Elon Musk, a co-founder, who is attempting to block the company's transition to a for-profit model [2] - Musk's team previously made a $97.4 billion offer to acquire OpenAI, which was rejected [2] - OpenAI's CEO, Sam Altman, emphasized the company's focus on its mission despite the ongoing legal challenges [2] Group 3: Stakeholder Concerns - A group of former employees and academics expressed concerns about the restructuring, arguing it could undermine OpenAI's charitable mission and governance safeguards [3] - The letter sent to the attorneys general and OpenAI's board raised questions about the legal alignment of OpenAI's commercial goals with its charitable mission [3] - Taylor mentioned that the new board structure will include independent directors appointed by the non-profit, ensuring that the mission remains a priority [3] Group 4: Future Funding and Goals - OpenAI aims to ensure that artificial general intelligence (AGI) benefits all of humanity, but acknowledges the need for substantial funding, potentially in the trillions, to achieve this goal [4] - Altman noted that the landscape has changed significantly since OpenAI's founding, with unforeseen costs associated with AI development and deployment [4]