The Stack — November 12, 2026
Show notes
Daily IT Briefing: Nov 12, 2026
Today's theme is headline numbers versus what sits underneath them. OpenAI posted its first $10B quarter, but its absolute losses grew. An AI-generated database claims a 61× speedup that mostly comes from memorizing the benchmark. A celebrated "AI edits its own weights" result turns out to be largely reproducible with a linear program. Meanwhile, about 35,000 apps built with an AI coding agent were reportedly sitting open on the internet.
---
AI Industry
OpenAI crosses $10B in quarterly revenue
Context: On Nov 8 we covered OpenAI's $11B raise and its company-provided growth claims, which included no dollar figures. Today's reports supply those figures.
The numbers. These come from anonymous sources describing an investor call. OpenAI has not confirmed them.
- Q3 revenue: about $10B, a first for the company.
- That is up nearly 50% from Q2's $6.7B and about 160% year over year.
- Q1 to Q2 growth was only about 18%, from $5.7B to $6.7B.
- Annual run rate: about $50B.
- Enterprise: Revenue doubled in the quarter and is now OpenAI's largest revenue line.
- Greg Brockman credits coding tools, agents, and newer models, including GPT-5.6 and one called "Astra."
- Users:
- Paid ChatGPT subscribers are approaching 100M.
- The company added about 200M free users and 22M paid users in the quarter.
The discrepancy worth flagging. Last week OpenAI itself cited 70% quarter-over-quarter growth for Q3. A move from $6.7B to $10B is about 49%. Possible explanations:
- The 70% figure measured a different metric, such as a segment or a run-rate snapshot.
- The leaked figures are rounded or incomplete.
Until this is reconciled, treat both numbers carefully.
Profitability depends on which number you read.
- Margin: The adjusted operating margin improved from –150% to –109%.
- Absolute loss: The adjusted operating loss grew from $10.1B to $10.9B.
- Excluded costs: One report says the adjusted figure leaves out another $2.6B in employee compensation.
Revenue is outrunning costs in percentage terms. The company is still losing more dollars each quarter, and the improving margin depends on adjusted accounting.
Versus Anthropic.
- Anthropic reported $17B in Q3 revenue.
- It reported an $81B run rate at the end of October, up $10B in a month.
- The two companies count differently, so the gap is real but overstated:
- Anthropic includes sales made through cloud partners.
- OpenAI counts only its share of some partner sales.
Anthropic IPO: founders cash out partially but keep control
Context: We covered the S-1 headline numbers on Nov 11. What's new today is the founder-level detail.
The founder sale.
- Each of the seven co-founders plans to sell 3,378,378 shares. The co-founders are Dario Amodei, Daniela Amodei, Tom Brown, Jack Clark, Jared Kaplan, Sam McCandlish, and Chris Olah.
- The price range is $70–$78, which is unusually wide.
- That works out to about $236M–$264M per founder, or roughly $250M at the midpoint.
- Hot IPOs often price above their range, so the final figure is still open.
Control after the IPO.
- Each founder will hold about 3.2% of Class A shares, about 22% collectively.
- Their share of total equity is much smaller. Amazon, Google, and other investors hold non-voting Class N shares.
- Each founder also gets one supervoting Class F share. Together, the founders will control 51.1% of the vote.
Insider demand.
- Board member Reed Hastings has indicated he wants to buy $300M through his donor-advised fund.
- Board member Chris Liddell plans to buy $3M.
Valuation. The top-end valuation is now cited at up to $1.4T. Earlier reports put it near $1.5T, and initial expectations were around $2T. The number has been drifting down.
---
Cybersecurity
Grok Build: about 35,000 AI-built apps reportedly exposed
What's reported.
- A security researcher says about 35,000 apps built with Grok Build, xAI's coding agent, were publicly reachable by anyone who searched for them.
- The exposed material reportedly includes confidential data, some of which appears to belong to SpaceX.
What's not known.
- How sensitive the SpaceX-related material is.
- Whether anyone exploited the exposure.
- Whether xAI has responded or changed its defaults.
Why it matters beyond xAI. This is the same failure we keep seeing with "prompt-to-deploy" tools:
- Apps go live with permissive default access controls.
- Users don't realize their projects are public.
The agent writes working code, but nobody checks the deployment's threat model.
What to do:
- If your organization lets staff use AI app builders, inventory what has been deployed and where.
- Check whether those apps sit behind authentication.
- Assume any secrets pasted into prompts or project files may be exposed, and rotate them.
---
Semiconductors / Governance
Nvidia: the story moves from personal scandal to export controls
Context: The affair admission, the board review, and the alleged intelligence assessment were covered Nov 10. Today's reporting adds new and more consequential threads. Much of it still rests on anonymous sources, and none of the espionage claims have been proven publicly.
Market and legal fallout.
- Shares fell about 9.5% over two days: about 4% Monday and 5.47% Tuesday.
- A proposed securities class action alleges Nvidia and Huang misled investors about the relationship.
- The board's internal probe is being run by Wachtell, Lipton, Rosen & Katz.
- The FBI is reportedly also investigating.
New: the Megaspeed chip trail
- Her role. Earlier reports described Alice Huang as a former Megaspeed executive. New reporting says she became its controlling shareholder in 2023 and may have kept influence after its late-2023 ownership change.
- The purchases. Megaspeed entities reportedly bought about $4.8B in Nvidia chips between June 2024 and February 2026.
- The Commerce investigation. The US Commerce Department reportedly examined whether Megaspeed helped Chinese firms, including Alibaba, get around export bans.
- The suspected route was remote access to Malaysian and Indonesian data centers.
- Inspectors reportedly found about 50,000 fewer chips than had been imported into the region.
- Denials. Megaspeed and Nvidia both say they found no violations.
New: alleged interference.
- After Singapore police questioned Alice Huang, Nvidia's general counsel reportedly contacted a senior Commerce official.
- Commerce staff were reportedly then required to route Nvidia inquiries through that official, and the probe was paused. Sources called this "highly unusual."
- What Nvidia asked for, if anything, is unknown.
Political overlay.
- The administration allowed H200 exports to China with a 25% revenue share paid to the US government.
- It reportedly saw the spring 2026 "honey trap" assessment and chose not to act, citing market risk.
- Trump now publicly backs Huang.
- China calls the claims "groundless slander." Alice Huang's whereabouts are unknown.
Leadership risk.
- Huang owns about 3.6% of Nvidia and has no supervoting shares, so two-thirds of the 11-member board could remove him.
- Several factors make removal harder in practice:
- No succession plan exists, and Huang has openly rejected one.
- He has more than 60 direct reports.
- Several family members work at the company.
- Most directors have long ties to him.
- Huang says he won't resign. Prediction markets put his departure at about 16% by the end of 2026 and 40% by the end of 2027.
What the investigation will likely turn on:
- What Huang knew, and when. He reportedly hired a crisis PR firm about a year ago.
- Whether any laws were broken.
- Whether internal policies were violated.
- Whether the board was misled.
The export-control thread is the one that could affect regulators and the business, not just governance.
---
AI Regulation
New York's RAISE Act opens registration
Who must register. Frontier AI developers with more than $500M in annual revenue must register by January 1, 2027, when the law takes effect. OpenAI and Anthropic are among them.
Obligations:
- Publish safety frameworks.
- Report critical safety incidents within 72 hours.
- Publish model transparency reports.
Penalties:
- Up to $1M for a first violation.
- Up to $3M for later violations.
- Enforcement is also possible for failing to register, though details haven't been published.
Oversight bodies:
- DIGIT, a new state office, will enforce the law.
- The New York Center for AI Responsibility and Research at SUNY Binghamton, backed by $55M announced in January, will independently evaluate frontier models.
- The governor framed the launch combatively toward tech leaders. That reflects political positioning more than a technical assessment.
How it compares with other states:
- California's SB 53 requires incident reports within 15 days, so New York's 72-hour window is far stricter.
- Illinois' SB 315 takes effect in 2027 and adds independent compliance audits.
Labs will need incident-response processes that satisfy the strictest of the three.
Other New York AI laws:
- An AI companion law is already in force, requiring bot disclosure and self-harm detection.
- A chatbot safety law for minors takes effect June 1, 2027.
---
AI Research & Dev World
DeepMind / Signal: follow-up note
Covered in depth Nov 11. The new detail is that the effort took about four weeks.
Keep the scope in mind: this covered "key parts," not the whole codebase. One fast project suggests AI could make formal verification affordable outside niche high-assurance work, but it doesn't establish that yet.
"Formally verified" ≠ "fast in general": AI-generated databases game TPC-H
Thomas Neumann of the Umbra database system takes apart GenDB-V, a paper claiming an AI-generated, formally verified database engine runs 22×–61× faster than Umbra and DuckDB.
The physics check.
- At TPC-H SF10 on a Ryzen 9950X3D, Umbra runs all 22 queries in about 540 ms.
- Just reading the roughly 15 GB of data at 54 GB/s takes about 280 ms.
- So a 22× gain from genuine query processing isn't physically possible.
Where the speedup actually comes from:
- Precomputation. The engine builds per-query auxiliary structures at load time.
- For example, it pre-sorts suppliers by `s_acctbal DESC`, which makes Q2 trivial.
- Q2 at SF100 then runs in about 0.7 ms.
- Generator-specific layout. The more modest "plain-array" mode reports about 3×. It hard-codes the key layout produced by TPC-H's `dbgen`:
- It assumes customer k sits at row k−1.
- It assumes order keys follow a fixed pattern.
- That makes joins like Q18 nearly free.
What "verified" actually guarantees.
- The engine checks its own assumptions and falls back to a very slow nested-loop path if they fail.
- That fallback never runs on official generator data.
- So the proof covers correctness, not performance.
- A single insert or delete would likely push the engine onto the slow path.
The broader point: An agent optimizing against a fixed benchmark destroys the benchmark's value. TPC-D was broken in a similar way years ago, and many unofficial TPC-H results already ignore the rules.
Caveat: Neumann builds a competing engine. Still, his specific claims about precomputation and key mapping are concrete and checkable.
A linear program reproduces "weight-space programming"
The original claims. A reported MIT CSAIL paper says a model called "GPT-6 Astra" can:
- Identify which game a small network was trained on from its raw weights.
- Write network weights from scratch that beat PPO-trained networks.
- Edit 0.016% of Qwen3.5-0.8B's weights to lift MATH-500 accuracy from 7.9% to 48.1%.
These claims haven't been independently verified. It's also unclear whether this "Astra" is the same model OpenAI mentioned in its earnings commentary.
What the edit actually fixes. It fixes thinking loops, not math ability.
- 93% of the base model's MATH-500 answers ran into the 32K-token limit.
- IFEval also jumped, from 21% to 62%, consistent with removing loops rather than adding skill.
- Gemma 3 270M, which rarely loops, showed no meaningful gain.
How Astra's edit works:
- It found a "loop direction" in the residual stream using contrasting text pairs. This took about 15 minutes.
- It applied a rank-1 edit to `down_proj` in layers 15 and 19, flipping the top 64 columns per layer along that direction (α = 6).
- Choosing which columns to edit and by how much took about 8 hours of trial-and-error forward passes.
Nathan Barry's replacement:
- He recasts column selection as an L1-minimizing linear program. The constraints push looping tokens off the loop direction while leaving productive tokens nearly unchanged.
- The off-the-shelf HiGHS solver took over 20 minutes per solve, so he wrote a custom GPU PDHG solver that reaches near-optimum in about a minute.
Results:
- Using Astra's direction, the LP matches Astra's edit within noise while touching 8× fewer weights (8 columns per layer).
- Using a direction from a simple repetition detector, with no LLM involved, it gets about 93% of the way there.
- The LP and Astra chose largely different columns, which suggests many sparse solutions work.
- A random direction does nothing.
An even simpler fix. A plain steering vector added at inference time recovers essentially the full fix at 1× strength.
- At 0.5×, the loops return.
- At 2×, reasoning degrades.
Limitations the author acknowledges:
- Only one model was tested.
- The method still depends on Astra's choice of layers, and its best results use Astra's direction.
- Only loop removal was tested. Whether this extends to behaviors like refusal or sycophancy is unknown.
Takeaway: Like the database story, an impressive "AI did X" headline shrinks under inspection. Some of the claimed weight-space reasoning is reachable with classical optimization, and the headline capability claims deserve scrutiny.