惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Forbes - Security
Forbes - Security
T
Troy Hunt's Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
H
Hacker News: Front Page
TaoSecurity Blog
TaoSecurity Blog
PCI Perspectives
PCI Perspectives
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
V
Vulnerabilities – Threatpost
博客园 - 【当耐特】
V
Visual Studio Blog
N
News and Events Feed by Topic
Security Archives - TechRepublic
Security Archives - TechRepublic
V
V2EX
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
WordPress大学
WordPress大学
T
Tor Project blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
美团技术团队
P
Proofpoint News Feed
A
Arctic Wolf
C
CERT Recently Published Vulnerability Notes
Last Week in AI
Last Week in AI
T
Tenable Blog
K
Kaspersky official blog
爱范儿
爱范儿
S
Security @ Cisco Blogs
Spread Privacy
Spread Privacy
大猫的无限游戏
大猫的无限游戏
Jina AI
Jina AI
博客园 - 三生石上(FineUI控件)
T
Tailwind CSS Blog
S
SegmentFault 最新的问题
Security Latest
Security Latest
T
The Exploit Database - CXSecurity.com
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Project Zero
Project Zero
W
WeLiveSecurity
L
LINUX DO - 最新话题
Hacker News: Ask HN
Hacker News: Ask HN
阮一峰的网络日志
阮一峰的网络日志
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
Cyber Attacks, Cyber Crime and Cyber Security
小众软件
小众软件
Webroot Blog
Webroot Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
Attack and Defense Labs
Attack and Defense Labs

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Two Hours of Deliberation
Arthur · 2026-06-26 · via DEV Community

Nine jurors. Two hours of deliberation. Twenty-six claims at the original federal complaint's peak. Three surviving claims at trial. Zero claims surviving the verdict. One hundred fifty billion dollars of maximum disgorgement exposure if the verdict had gone the other way. One hundred thirty billion dollars of OpenAI Foundation equity stake under the October 28, 2025 recapitalization. Thirty-eight million dollars of total Musk contributions per his sworn trial testimony. Forty-four million per the legal complaint. Eight years from the January 2, 2016 Sutskever-Musk "less open / Yup" email exchange to the August 2024 federal filing date. Three years of statute-of-limitations runway on the breach-of-charitable-trust claim; two years on the unjust-enrichment claim.

The verdict in Musk v. Altman came in this morning at the federal courthouse on Clay Street in Oakland, before Judge Yvonne Gonzalez Rogers in the Northern District of California. The companion piece, The Calendar Technicality, makes the doctrinal argument that the procedural dismissal is the substantive determination California charitable-trust law would have produced on the merits as well. This piece takes the same conclusion through the numbers. The dollar-and-time math closed the merits door before the doctrinal door even came into view.

Two hours, in context

Federal-court civil-trial deliberations on complex commercial cases typically run between one and five days. The Administrative Office of the U.S. Courts' annual judicial-business reports show median civil-jury deliberation in the multi-day range for cases with three or more issues to resolve and dollar exposure above one billion. The two-hour deliberation in Musk v. Altman is roughly one to two standard deviations below the median for cases of this complexity. The brevity is not a function of jury inattention. The trial ran three weeks. Roughly four hours of testimony came from Altman alone on May 12, with cross-examination opening with Musk's lead trial counsel Steven Molo asking "Are you completely trustworthy?" Live trial testimony also came from Greg Brockman, former chief scientist Ilya Sutskever, Microsoft CEO Satya Nadella, Microsoft CTO Kevin Scott, and former OpenAI board member Shivon Zilis.

What the two hours signals is that the legal question the jury was asked to resolve had a clean answer. The three surviving claims at trial — breach of charitable trust against OpenAI / Altman / Brockman, unjust enrichment against the same defendants, and aiding-and-abetting breach of charitable trust against Microsoft — all fell on a single question: when did Musk know or should have known of the conduct he eventually sued over. The candidate clock-start dates were knowable from the timeline and not seriously contested by the underlying evidence. The jury's role was to apply the applicable statutes (three years on the charitable-trust theories, two years on unjust enrichment) to the dates and confirm the count. Two hours is what that count takes when the dates do not require extensive re-litigation.

The 26-to-zero attrition, with dollar columns

The case began with a much larger surface area and shed it in stages. Pretrial motions disposed of roughly two-thirds of the original claims on substantive doctrinal grounds. Summary judgment in January 2026 cleared most of the Microsoft-specific theories. The two-hour verdict closed the remaining three.

Claim Dismissal stage Mechanism Maximum dollar exposure if prevailed
Breach of contract (vs OpenAI) Pretrial (March 2025) No written founding agreement pled $44M-$150B (specific-performance theory)
RICO racketeering Pretrial No pattern of predicate acts established Treble-damages, theory-dependent
Antitrust Pretrial No defined market and exclusionary act pled $30B+ (market-distortion theory)
False advertising Pretrial (May 2025) No specific reliance-inducing statement pled Restitution-based
Breach of fiduciary duty Pretrial (May 2025) No fiduciary relationship pled Disgorgement-based
Tortious interference (vs Microsoft) Summary judgment (January 2026) No actionable interfered-with contract $20B+ (contract-value-based)
Unjust enrichment (vs Microsoft) Summary judgment (January 2026) No direct benefit conferred by plaintiff $14B+ (Microsoft's pro-rata gain)
Breach of charitable trust Jury verdict (May 18, 2026) 3-year SOL (Cal. CCP §338(d)) $150B disgorgement to OpenAI Foundation
Unjust enrichment (vs OpenAI/Altman/Brockman) Jury verdict (May 18, 2026) 2-year SOL $30B+ (defendants' pro-rata gain)
Aiding-and-abetting (vs Microsoft) Jury verdict (May 18, 2026) 3-year SOL (Cal. CCP §338(d)) $14B+

The pattern the table makes visible is that the dollar-exposure rows fall at the verdict stage, not at the pretrial stage. The largest-exposure theory (charitable trust at $150B disgorgement) survived all the way to the jury because it presented the cleanest doctrinal anchor in California law — the Holt v. College of Osteopathic Physicians & Surgeons standard that a person with sufficient special interest may bring an action to enjoin breach of a charitable trust. Musk's case argued he had sufficient special interest as a founder and major donor. The case died on the timing question, not on the special-interest question; the special-interest question was not reached.

The dollar exposure

The numbers around the case form a stack that is worth flattening into a single column. From smallest to largest:

Number Source What it represents
$38 million Musk trial testimony (under oath) Total Musk contributions to OpenAI by his own sworn account
$44 million Musk's amended federal complaint Total Musk contributions per the complaint's pleading
$14 billion Industry estimates Microsoft's pro-rata gain attributable to the OpenAI position
$30 billion Plaintiff's expert testimony OpenAI's directors/officers' pro-rata gain attributable to the conversion
$130 billion OpenAI's October 28, 2025 disclosures OpenAI Foundation equity stake in OpenAI Group PBC at recap valuation
$150 billion Plaintiff's prayer for relief Maximum disgorgement to the OpenAI Foundation if all surviving claims prevailed
$500 billion OpenAI's October 28, 2025 disclosures Total OpenAI Group PBC valuation at recapitalization

The corporate-structure transition over the case's eleven-year window is the dollar pattern most worth tracking. From the December 2015 nonprofit founding (zero equity value) through the 2019 capped-profit conversion (private valuation in the single-digit billions) to the October 28, 2025 PBC recapitalization (500 billion enterprise value; 130 billion controlled by the Foundation; 27 percent held by Microsoft; the remainder by employees and outside investors), the curve is roughly six orders of magnitude across eleven years. The Foundation's controlled position carries an additional warrant: if OpenAI Group's per-share value increases tenfold over fifteen years, the Foundation receives a substantial further equity grant. The warrant is the contingent upside layer the recap left in place and is not included in the $130 billion figure. Musk's disgorgement theory asked the court to push approximately one hundred fifty billion of that value back into the Foundation's controlled column. The Foundation's controlled column already stood at approximately one hundred thirty billion at the time of trial.

The arithmetic the jury did not need to perform is worth doing externally. If Musk had prevailed on all surviving claims at their pleaded maxima, the Foundation's equity stake would have moved from approximately $130 billion to approximately $280 billion, the for-profit's effective controlled-by-Foundation share would have risen from 26% to a number closer to 56%, and Microsoft's 27% position would have been diluted by roughly the same factor required to honor the disgorgement transfer. The transfer is the operative remedy Musk's case proposed. The transfer did not happen because the case did not reach the transfer-considering merits stage. The transfer remained, throughout the case, conditional on the timing question that the jury answered against Musk in two hours.

The timing math

The three-year statute of limitations under California Code of Civil Procedure §338(d) (fraud SOL) was the load-bearing legal mechanic on the charitable-trust theories; the §343 four-year residual SOL was the alternative-theory framing and would have placed the filing window opening in August 2020 instead of August 2021. The unjust-enrichment claim ran on a separate two-year clock that placed its window opening even later, in August 2022. The August 2024 federal filing date created a window opening in August 2021. The candidate clock-start dates the trial record established were four:

Anchor event Date Span to August 2024 filing
Sutskever-Musk email "less open / Yup" exchange 2016-01-02 8 years 7 months
Musk's departure from OpenAI 2018-02 6 years 6 months
OpenAI capped-profit conversion announcement 2019-03 5 years 5 months
Musk's last monetary contribution 2020 4 years 8 months

Any of the four anchors places the filing outside the three-year window. Musk's rebuttal at trial was that he did not fully discover the true extent of the fraud until 2023, on which theory the filing would be within the window. The rebuttal required the jury to find that none of the four anchors triggered the limitations clock, and that the 2023 PBC-conversion announcement materially changed Musk's knowledge of the conduct. The jury rejected the rebuttal in two hours, which is what rejected the rebuttal looks like when the anchors are four and the jury believes each of them is independently sufficient.

The continuing-breach theory Musk's appellate counsel will need to advance at the Ninth Circuit is the theory that mission drift in a charitable trust does not reset the clock at each subsequent corporate restructuring, but that the cumulative drift constitutes a continuing breach the limitations clock cannot exhaust. The theory exists in the California case law, but the Holt anchor and subsequent cases have largely confined it to specific categories of trustee misconduct rather than to mission-drift claims by former donors. The Ninth Circuit's base rate for reversing district-court statute-of-limitations dismissals on continuing-breach theories in California charitable-trust cases is, on a quick survey of the published case law, low single digits.

The witness load

The three-week trial calendar contained roughly fifteen named witnesses, with the principal testimony falling on these dates:

  • April 27: Trial opens; opening statements
  • April 28-30: Musk testifies
  • May 5-7: Greg Brockman testifies
  • May 7: Shivon Zilis testifies on her 2020-2023 OpenAI board service and on conversations with Musk about OpenAI's corporate structure in 2017-2018
  • May 12: Sam Altman testifies (~4 hours, including Molo's cross-examination)
  • Week 3: Ilya Sutskever, Satya Nadella, Kevin Scott testify
  • May 14: Closing arguments
  • May 18: Verdict (<2 hours deliberation)

The full witness list and the substantive content of the testimony are discussed in the companion Calendar Technicality piece. The numerical observation worth carrying here is that fifteen witnesses across three weeks is the trial load California charitable-trust cases at this dollar exposure typically carry, and that the verdict was rendered on a single question that did not require the jury to resolve the substantive disputes most of those fifteen witnesses had been brought to address.

What the Ninth Circuit gets to review

The appellate-review standards for a statute-of-limitations dismissal split between de novo review on the legal question of whether the limitations period applies and clearly erroneous review on the underlying factual determinations. The legal question Musk's appeal would need to win is whether the trial court correctly identified the clock-start anchor. The factual question Musk's appeal cannot easily revisit is the jury's finding that the candidate anchors were each knowable to Musk at the relevant times.

The continuing-breach theory is the most plausible appellate path. The theory would need to argue that the October 28, 2025 PBC recapitalization was itself a discrete breach event that started a fresh three-year clock, regardless of whether the earlier anchors had triggered earlier clocks. The argument has a doctrinal foothold in California charitable-trust law and a factual foothold in the recap's actual date, which falls within the three years preceding the May 2026 verdict but after the August 2024 filing. The Ninth Circuit would need to find that the trial court erred as a matter of law in not treating each subsequent corporate-structure change as a fresh clock-start. The base rate for that kind of reversal is, on the available statistics, low.

The number that matters for what the verdict actually settles is the appellate-cycle count. A 9th Circuit ruling on the SOL question is likely in twelve to eighteen months. Any further appellate review (en banc; Supreme Court certiorari) would add another twelve to eighteen months. The Foundation-controlled $130B equity stake is, on the calendar, structurally settled beyond private-litigation reach by approximately late 2027 to mid-2028 even in the worst case. The numerical structure of the appellate process is the final block on the procedural-versus-substantive question; the dismissal Musk is calling a calendar technicality is, in calendar terms, durable.

Coda

The verdict's numerical content is the article in the article. Nine jurors took two hours to resolve a case with $150 billion at stake because the three-year clock had four candidate anchor dates and all four pre-dated the filing window by margins between five months and five years. Twenty-six original claims attritted to two surviving claims attritted to zero prevailing claims through a sequence of doctrinal and procedural gates that each narrowed the case's dollar exposure without ever needing to resolve the substantive question of whether the founding-mission promise had been breached. The Foundation's $130 billion equity stake remained, throughout, the structural fact the case was nominally asking the court to revisit. The case ended without the court revisiting it.

What the numbers show is that the verdict is durable in the dimension Musk's appellate framing is contesting. The clock will not move. The anchors will not change. The 9th Circuit's most plausible reversal path is the continuing-breach theory on the 2025 recap, and that path's base rate is low. The substantive question of whether the OpenAI Foundation's controlled position is adequate to the structural stakes of a $500 billion AI lab remains open. The numerical question of whether private donor litigation can reach that question is closed.