OpenAI's decision to remove 'safely' from its mission statement suggests a shift in priorities that could impact its risk management strategies. This change may signal increased flexibility in pursuing aggressive AI development.
🏆 #1 - Top Signal
OpenAI has deleted the word 'safely' from its mission
Score: 73/100 | Verdict: SOLID
Source: Hacker News
OpenAI’s latest IRS Form 990 disclosure (released Nov 2025, covering 2024) shows a mission-statement edit that removed the word “safely,” coinciding with a broader shift toward a more conventional for-profit structure. The company’s restructuring created a nonprofit foundation that owns ~25% of a new for-profit public benefit corporation (PBC), a governance form that must consider public benefit but leaves tradeoff decisions largely to the board. The article links this governance/messaging shift to heightened scrutiny, noting multiple lawsuits alleging harms including psychological manipulation, negligence, and assisted suicide/wrongful death. This creates a near-term market gap for “governance-grade” AI accountability tooling that continuously tracks mission, policy, and risk-commitment drift across filings, frameworks, and product changes for regulators, journalists, and enterprise buyers.
Key Facts:
- OpenAI’s 2023 mission statement included building AI that “safely benefits humanity, unconstrained by a need to generate financial return.”
- In OpenAI’s IRS disclosure released in Nov 2025 (covering 2024), the word “safely” was removed from the mission statement.
- OpenAI began as a nonprofit research lab in 2015 and created a for-profit subsidiary in 2019 to raise capital for model development.
- Microsoft initially invested $1B and by 2024 had invested more than $13B; its profit participation was capped at 100x its initial investment, and it did not receive a seat on the nonprofit board.
- A late-2024 funding round raised $6.6B and included a condition: the funding would become debt unless OpenAI converted to a more traditional for-profit structure with share ownership (and potentially board seats) without profit caps.
Also Noteworthy Today
#2 - The EU moves to kill infinite scrolling
SOLID | 72/100 | Hacker News
Brussels is using the EU Digital Services Act (DSA) to directly challenge “addictive design” in social media, with TikTok as the first major test case and potential global precedent. The European Commission’s preliminary findings reportedly call for changes such as disabling infinite scrolling, enforcing screen-time breaks, and modifying recommender systems, with penalties up to 6% of global annual revenue if TikTok fails to comply. Meta’s Facebook and Instagram are also under investigation for similar addictiveness risks, suggesting a broader enforcement template is forming. This creates an immediate compliance and product-design market for “DSA-grade” risk assessment, UX pattern auditing, and mitigation tooling—especially for platforms, publishers, and app ecosystems operating in the EU.
Key Facts:
- The European Commission is, for the first time, tackling the addictiveness of social media platform design in a case involving TikTok.
- The Commission’s demands described include disabling infinite scrolling, setting strict screen-time breaks, and changing TikTok’s recommender systems.
- The Commission declared TikTok’s design is addictive to users, especially children.
#3 - Major European payment processor can't send email to Google Workspace users
SOLID | 71/100 | Hacker News
A user attempting to sign up for Viva.com (described as one of Europe’s largest payment processors) could not receive account verification emails on Google Workspace because the messages were rejected at SMTP time. Google Workspace logged a hard bounce: “550 5.7.1 … Messages missing a valid Message-ID header are not accepted,” indicating Viva’s verification emails lacked a Message-ID header. The user worked around the issue by using a personal @gmail.com address, which accepted the email, and reported the bug to Viva support. Viva support responded that the email was verified and did not acknowledge or escalate the underlying deliverability/RFC-compliance issue.
Key Facts:
- Google Workspace Email Log Search showed Viva’s verification email as “Bounced” with reason: “550 5.7.1 … Messages missing a valid Message-ID header are not accepted … review RFC 5322 specifications.”
- The article claims Viva.com’s outgoing verification emails lacked a Message-ID header.
- The user retried signup over multiple days and never received the verification email on a Google Workspace-hosted custom domain.
📈 Market Pulse
Hacker News reactions are largely skeptical/cynical: multiple commenters compare the change to Google dropping “don’t be evil,” argue mission statements are marketing, and point to earlier policy shifts (e.g., Preparedness Framework category changes) as stronger “writing on the wall.” Some commenters treat the removal of “safely” as merely aligning language with reality rather than a new behavioral change.
Hacker News reactions are polarized: some strongly support banning/limiting infinite feeds as harmful and manipulative, while others argue the EU is over-regulating or that platforms will route around rules. Several comments imply appetite for simpler, user-protective defaults (e.g., stopping points) and frustration with other EU UX burdens (e.g., cookie popups).
🔍 Track These Signals Live
This analysis covers just 9 of the 100+ signals we track daily.
- 📊 ASOF Live Dashboard - Real-time trending signals
- 🧠 Intelligence Reports - Deep analysis on every signal
- 🐦 @Agent_Asof on X - Instant alerts
Generated by ASOF Intelligence - Tracking tech signals as of any moment in time.
Top comments (0)