Giorgos Tsetis: no one is personally accountable for AI. This must change

The author, an AI investor and former Nutrafol leader, argues that senior AI executives should face personal legal accountability when they knowingly release systems with serious risks, underfund safety, ignore warnings or conceal problems. The piece notes that US AI rules are evolving and that major AI companies have made voluntary safety commitments, but says these measures do not currently impose personal legal responsibility. It acknowledges AI’s potential benefits while warning that failures could affect critical systems and the public.

Analysis

This is advocacy, not a regulatory event: absent proposed statutory text, enforcement authority, or a timetable, it should not move AI earnings estimates on its own. The investable mechanism is a shift from firm-level penalties toward named-executive exposure. If lawmakers adopt a negligence-based duty tied to documented warnings, safety budgets, and disclosure, frontier developers could face higher audit, legal, and safety costs—and a greater incentive to delay releases. That favors scaled incumbents able to absorb fixed compliance costs over smaller labs, potentially concentrating the market. Safety testing, cybersecurity, and independent audit providers could gain demand; compute providers face a two-sided effect, with more evaluation workloads but slower commercial deployment if release gates tighten.

Near term, the article is unlikely to change cash flows. Over 1–3 months, watch whether federal proposals define individual duties and safe harbors, and whether state rules conflict. Over 6–18 months, a patchwork or credible personal-liability regime could raise entry barriers and increase executive retention and insurance costs. The contrarian point: vague or outcome-based liability could discourage candid safety reporting and push development to less transparent jurisdictions, weakening safety rather than improving it. The thesis fails if proposals remain symbolic, carve out broad protections, or focus only on corporate process rather than executive decisions. No company-specific financial impact is established here.

Key Decisions for Investors

• No immediate directional AI trade on this commentary alone; treat it as a policy-risk signal, not a change in law or a verified operating-cost shock.
• Monitor federal bill language and state rulemaking for the liability trigger, individual scope, safe harbors, and enforcement timeline. Escalate to a relative-value view only if binding duties emerge: scaled AI platforms versus smaller frontier developers is the likely compliance-resilience expression, not a forecast of guaranteed outperformance.
• Track safety/audit spending, release cadence, and disclosure practices at frontier labs. A sustained rise in compliance budgets alongside delayed launches would support a long thesis in independent testing and cybersecurity services, but verify revenue exposure before positioning.
• Falsifiers: legislation stalls or grants broad executive protections; alternatively, evidence of slower model releases, higher safety-related costs, or executive departures after binding rules would confirm that the regime is affecting deployment economics.