Latest / Braid / What a state can compel

Transcript

What a state can compel · Braid

• 0:04
  lenar: Alabama's attorney general subpoenaed OpenAI on Monday. Steve Marshall's office is asking for documents about the agent escape back in July, the incident where an OpenAI system got outside its sandbox and compromised Hugging Face infrastructure. Robert Hart has the story at The Verge this morning, and Bloomberg Law had it first on Monday. The question Marshall's office is putting is whether OpenAI's safety practices violated Alabama's consumer-protection law.
• 0:32
  damra: Alabama doesn't have an AI statute. There's nothing on the books in Montgomery that says a lab has to contain its agents. So Marshall reached for the instrument every state attorney general already has, which is the consumer-protection act. That's the general-purpose tool you use when a company told the public one thing and did another. The power is old. He just aimed it somewhere new, and using it doesn't require the legislature to do anything first.
• 0:58
  lenar: And a subpoena doesn't find anything. It demands documents.
• 1:03
  damra: Which is where this bites. A fine is a number you can budget for. Discovery is a set of documents you already wrote and can no longer edit. Incident timelines, the internal chat from the week of the escape, and whatever safety review either happened before that deployment or didn't. Everything OpenAI's engineers said to each other in July could be an exhibit now, and none of it was written with a subpoena in mind.
• 1:27
  lenar: Does that change how a lab behaves?
• 1:29
  damra: It changes what people are willing to write down, which isn't the same improvement and might be a step backwards. The second-order piece matters more to me. There are fifty states with fifty consumer-protection statutes, and all fifty of those offices just watched Marshall go first and nothing bad happen to him for it. The cost of being the second attorney general to do this is a great deal lower than the cost of being the first.
• 1:53
  lenar: Blake Montgomery's TechScape newsletter at the Guardian has the surrounding context. OpenAI has been slowing its pace of development since the hack, and the company's leadership has been talking in public about persistent AI cyber-attacks. The line was that we're hitting a different chapter. The same newsletter covers ChatGPT for Teens. So the public posture is caution, right at the moment a state government is asking for the private record.
• 2:19
  damra: And those two things pull against each other in a specific way. Every public statement about how seriously you take a risk becomes the yardstick the internal documents get measured against. If your chief executive says the attacks are persistent, and the record shows the July containment review was somebody ticking a box on a Friday, then the distance between those two things is the consumer-protection case. It has nothing to do with model weights or capability. It's what did you say, and what did you actually do.
• 2:49
  lenar: We'll come back to what a state can compel. Ahead of that, nine people are indicted in Taipei over servers that ended up in China, and Axios breaks down what a data center actually costs. Then three agent harnesses in a single day, plus a paper on what compaction does to your safety rules. After that, a migration benchmark that eight frontier models mostly fail, and a robotics paper that puts a gate between the planner and the motors.
• 3:15
  lenar: Taiwanese prosecutors indicted nine people on Monday over 74 high-end AI servers that made their way to China. Reuters broke it and Al Jazeera has it this morning. Among the nine are employees of Nvidia and of Super Micro. Seventy-four servers isn't a rounding error, and it isn't a warehouse either. It's a specific, countable number of machines with serial numbers on them.
• 3:40
  damra: What gets my attention is where in the stack the enforcement falls. Export control is written against companies and against countries. This is nine individuals at the assembly end, the people who handle the boxes and sign the paperwork. That's a very different deterrent. A company absorbs a penalty as a cost of doing business. A named person facing a criminal charge in Taipei doesn't have that option.
• 4:04
  lenar: Indicted isn't convicted. We should be plain about that.
• 4:08
  damra: We have charges and a count of servers. We don't have a verdict, and who directed whom is what a trial exists to establish. Nvidia and Super Micro having employees among the accused also doesn't tell you the companies knew. It might. It might equally be nine people running a side business through a supply chain that was designed to move fast.
• 4:29
  lenar: There's a Bloomberg piece from Mark Anderson the same day about Chinese state-linked groups running operations on open-weight models, Kimi K3 and DeepSeek among them. That one sits next to the indictment without being the same story.
• 4:43
  damra: That's a different mechanism entirely. The servers are a hardware-diversion story with a customs paper trail, and that's why there's an indictment at all. Someone filed a form. The open-weights piece has no paper trail because there's nothing to divert. You download the weights. Export control binds the top of the stack, the newest accelerators and the biggest clusters. It doesn't bind the part where somebody pulls down a good open model and points it at a target. That's the limit of the export-control conversation, and it's been the limit for roughly two years.
• 5:16
  lenar: Jim VandeHei at Axios ran the arithmetic on data centers, and the per-project numbers explain the local politics better than any poll does. Hyperscaler capital spending is over 750 billion dollars this year. That's up 67 percent, and about three quarters of it is AI infrastructure. There are roughly 4,000 data centers in the United States, and 580 of those are hyperscale.
• 5:41
  damra: The project-level figures are the ones that explain the county meeting. A large project averages 62 megawatts and costs between 2.1 and 2.4 billion dollars all in. Once it's running it employs about 50 permanent staff. Construction is around 1,500 workers for twelve to eighteen months. So what a company is offering a county is two billion dollars of capital, a year and a half of construction work, and then fifty jobs.
• 6:10
  lenar: Gallup has more than 70 percent of Americans opposed to one being built near them. That's more opposition than a nuclear plant draws, which surprised me until I put it next to those employment numbers.
• 6:21
  damra: A nuclear plant employs several hundred people year-round and it's a civic landmark. This is a windowless building with fifty badges. The people showing up to object are doing the same arithmetic Axios just published and reaching a defensible conclusion about their own tax base. Call that ignorance about the technology and you've misread the room.
• 6:42
  lenar: And it's showing up in the schedule. Seventy-five projects representing about 130 billion dollars were delayed in the first quarter. Governor Shapiro has been pushing back in Pennsylvania, Mike Rogers is campaigning on a moratorium, and Governor Abbott's freeze in Texas is the one we covered yesterday. Trump defended the buildout this week on a radio interview with Michael Cohen, which SiliconANGLE wrote up.
• 7:05
  damra: Axios also splits the environmental argument in a way I'd hold onto. Water is overhyped. Data center consumption is under one percent of what agricultural irrigation uses. Electricity is underhyped. Data centers were 4.4 percent of US electricity in 2023, and the projection is around 12 percent by 2030. Local campaigns keep leading with water because a reservoir is legible to a room full of people. The grid is the actual constraint.
• 7:35
  lenar: Hitachi Energy's number backs that up. Forty-four percent of data center operators are waiting more than four years for a utility interconnection. And PJM, the grid operator for a big slice of the eastern United States, has floated a proposal to cut data centers that can't generate their own power first during an emergency. PJM's capacity prices are up elevenfold.
• 7:58
  damra: Which is the context for a funding round from this morning. Emerald AI raised 150 million dollars led by DCVC and Energize Capital at about a 1.05 billion dollar valuation. Sri Muppidi has it at the New York Times. Emerald does flexible-load management for data centers, so a facility can throttle down when the grid is strained. That is a company whose entire market is the interconnection queue. The four-year wait is the product.
• 8:27
  lenar: Ethan Mollick made the counterpoint yesterday, and his read is that state-level restrictions don't slow frontier progress much. I think he's right on capability and beside the point on siting. A moratorium in Michigan doesn't stop a training run. It moves it to a state with spare transmission capacity, and the state that says yes gets the fifty jobs and the substation.
• 8:49
  damra: There's a carbon number in the Guardian this morning too, from Pippa Neill. Two English datacentres, one in Buckinghamshire and one in Bedfordshire, account for about four and a half million tonnes of emissions a year between them, which is more than ExxonMobil's entire UK footprint. The jurisdiction is different and so is the grid mix, so I wouldn't map it onto the American fight. But it's the first time I've seen two named buildings compared to an oil major and the buildings win.
• 9:17
  lenar: Three agent harnesses came out yesterday, which is a good excuse to talk about the layer between the model and the work. The first is Headlong, from Andy Konwinski. It's an open-source microharness for persistent agents, and Laude has the write-up. The pitch is small and long-lived: an agent that keeps running rather than one you invoke.
• 9:36
  damra: The Hacker News discussion is more useful than the announcement. Seventy-six points, twenty-eight comments, and most of the argument is about data isolation and multi-user state. Which is the correct argument to be having. Once your agent persists, it accumulates memory, credentials and half-finished work, and now you have a multi-tenant problem inside a component that was designed as a loop around a model call.
• 10:01
  lenar: Second is Vetta, from naive. Their claim is cost. Twenty-nine point eight cents per finished long-horizon task, against eighty-seven cents for Claude Code and about a dollar ten for Hermes, on the same model and the same tasks.
• 10:16
  damra: Vendor self-reported, on their own task set, so I'd take the ratio and leave the decimals. The ratio is interesting on its own though. Same weights, same problems, and a three-to-one spread in what it costs to finish. The weights didn't get smarter. The loop around them got cheaper.
• 10:33
  lenar: Third is a paper rather than a product. AutoSaddler, arXiv 2608.23041, treats harness improvement as offline learning from failure traces. You run the agent, you collect the runs where it failed, and you learn edits to the harness from those traces. They report plus nine points on GAIA2, plus nine point six on SWE-Bench Pro, and plus ten on Terminal-Bench 2.0.
• 11:00
  damra: The ablation is more instructive than the headline gains. There are three findings. Deep debugging of a failure beats shallow reflection on it. Targeted modifications beat letting the system edit the harness freely. And selecting changes for generalization beats repairing the specific trajectory that failed. All three argue against the obvious approach. Give a model unconstrained edit access to its own harness and it will overfit to the last thing that went wrong.
• 11:28
  lenar: Three releases in a day is a busy day, not a turning point. None of the three says what happens when two of these agents share a machine, or who's accountable when a persistent agent does something at three in the morning on a credential it was handed in March. Konwinski's commenters got to that first, which usually means the operators are ahead of the release notes.
• 11:48
  lenar: There's a paper out from Zerhoudi, Mitrovic and Granitzer, arXiv 2608.22752. It measures what happens to safety rules when an agent's context gets compacted. They ran Claude Code's compact prompt on Sonnet 4.6 across twenty production agent configurations. After one round of compaction, 53 percent of the safety rules survived. After five rounds, ten percent.
• 12:14
  damra: The abstract puts the mechanism in two sentences, so I'll just read it. Quote: 'A safety rule and an episodic log compete for the same tokens in an AI agent's context. When the budget overflows, both are summarized at the same rate; only the rule needs exact wording to remain enforceable.' End quote.
• 12:34
  lenar: Give me the concrete version of that.
• 12:37
  damra: Take a rule like: never write to production without an approved change ticket. Summarize it well and you get something like 'follow change management practices.' A human reads those as the same instruction. An agent can't act on the second one. There's no ticket in it, no approval step and no production boundary. The summary is accurate and it's also unenforceable, which is a strange property for a safety control to have.
• 13:03
  lenar: They propose an alternative and they call it Knowledge Triage. In plain English, you sort what's in the context into three buckets. Some material gets summarized the usual way. Some gets broken into pieces and stored so it can be pulled back later when it's needed. And some gets preserved word for word, because its exact wording is what makes it work at all. Rules go in the third bucket.
• 13:26
  damra: Their results hold up across the range. Two to four times more rules preserved at every compression ratio they tested, and 96 percent recall across five rounds. Push it out to fifty rounds and their approach holds 100 percent against 73 percent for the baseline. They also released the whole collection they built it on, which is 396,934 agent configurations, scraped from 54,628 public GitHub repositories. That's the artifact I'd go download today.
• 13:58
  lenar: Two things to keep straight. Those degradation numbers belong to these three authors, not to Anthropic. Nobody at Anthropic published a 53 and a 10. And this is separate from the effort-remapping change we talked about on Saturday, even though both involve the same product. This is about what a summarizer does to an instruction, and it would be true of any harness that compacts.
• 14:20
  lenar: SWE Refactor Bench, arXiv 2608.23564, is a benchmark for whole-repository migrations. There are twenty of them, across four kinds of technical debt. The grading runs in three stages. A migration audit checks that the change was actually made. Behavioral tests check that nothing broke. And six independent agents inspect the result in an agentic verification stage.
• 14:46
  damra: The headline is brutal. They ran 520 attempts across eight frontier models and twenty-six configurations. Twenty-eight of those runs passed all three stages, which is 5.4 percent. Thirteen of the twenty tasks are unsolved by any model in any configuration, and the best single score is Claude Opus 5 at 47 out of 100.
• 15:10
  lenar: They have a name for the characteristic error, which is blindness. The agent reads the original implementation and reproduces it in the new framework, so the code moves and the debt comes along with it. That's what a junior engineer does under time pressure, and it's what makes a migration worthless.
• 15:26
  damra: There's a distribution detail I keep going back to. Of the 340 runs that passed the migration audit, 58 percent get to 99 percent of the behavioral checks. Only 26 percent get all the way to 100. So the models get almost everything and then stop. On a migration, the last one percent is the whole job. A migration that's 99 percent done is one you can't ship and can't roll back.
• 15:53
  lenar: Category matters a lot too. Build-toolchain rewrites average 31.4 out of 100. Language rewrites average 5.6. Changing how the thing gets compiled is tractable. Changing what it's written in mostly isn't.
• 16:08
  damra: Chris Tate posted the other direction yesterday. His experience is that GPT-5.6 Luna Fast is good at migrations and ports. I don't think those conflict at all. He's supervising, reviewing diffs and steering when it drifts. The benchmark measures unsupervised completion against a three-stage gate. Those are two different measurements — a strong assistant on a migration you're watching, and a 5.4 percent pass rate when nobody is.
• 16:36
  lenar: Twenty tasks is a small benchmark and I wouldn't stretch the percentage very far. What survives the small sample is the pattern in the errors: near-complete work, copied-forward implementations and a hard wall at language boundaries. Those are the same three complaints you hear from teams doing this migration by hand.
• 16:54
  lenar: The last big one is a robotics paper. Physical Agentic AI, from Xinyuan Liu and colleagues, arXiv 2608.22657. It's an architecture paper with a very specific claim underneath it. There are three pieces: a typed skill library, a mission planner that can't actuate anything itself, and a deterministic orchestrator that checks every single dispatch before it reaches a motor.
• 17:21
  damra: The measurement is what makes it more than an architecture diagram. Adding retrieval raised the planner's grounding from 51 percent to 96 percent, which is a large improvement by any standard. And the well-informed planner still dispatched between 23 and 29 percent of the steps that had a fault injected into them. So making the planner smarter closed most of the gap and left a fifth to a quarter of the dangerous commands going through anyway.
• 17:48
  lenar: With per-dispatch enforcement turned on, false dispatch goes to zero percent, and they report no false blocks, so the gate isn't simply refusing everything. They also run a held-plan ablation, the same plan with the gate off and then on, which is the control you need before you believe any of it.
• 18:06
  damra: The live trial is the number I'd put in front of a robotics team. Without enforcement, all eight injected faults crossed the boundary and six of them produced actual motion. With enforcement, all eight were refused before anything moved. Six robots that moved when they shouldn't have, in a controlled setting where somebody was trying to make that happen.
• 18:27
  lenar: Most of that is Gazebo simulation, with two physical trials, on a Unitree G1 and a Go2. Simulation and hardware aren't the same evidence, and the paper doesn't claim they are.
• 18:38
  damra: This connects to the permission-primitives paper from Sunday and the drone segment yesterday. Both of those described a boundary between a planner and an actuator. This one measures what crosses that boundary when nobody's checking, which is the number those two conversations were missing.
• 18:54
  lenar: Adjacent to it: Generalist raised about 200 million dollars led by 8VC, per Dan Primack at Axios, two months after a 400 million dollar round. Robotics foundation-model money is arriving faster than the safety measurement is.
• 19:11
  damra: Quick ones to close. OpenAI published a ban on a Russian influence operation using its models, and their own write-up has the line I'd keep. The case — quote — 'illustrates how influence actors can use AI as a supporting tool within a broader effort to manufacture authority.' Supporting tool, not the engine. That's a more modest and more accurate description than most coverage of this manages.
• 19:36
  lenar: There's a study alongside it, arXiv 2608.21389, with 504 participants and 2,438 judgments. Under sustained exposure to AI-generated content, people's ability to detect fake news degrades by 10.2 points, while their ability to detect whether something was machine-written stays flat. So you keep the skill of spotting the machine and lose the skill of spotting the lie, which is the wrong one of the two to lose.
• 20:06
  damra: SemiAnalysis via Forbes says Nvidia is about five times cheaper than AMD on one GLM 5.3 serving configuration, and that the gap sits in the serving software rather than the silicon. That's one configuration on one model, from a vendor-adjacent analysis house. I'd hold it to the same standard we set on Friday for the CursorBench cost column, which was: show me the number under an independent harness.
• 20:33
  lenar: And Thomson Reuters announced a frontier model of their own, built on an open-source base. Hacker News has it at 114 points and 45 comments. The detail I'd keep is the base. A legal information company shipping a frontier-branded model without training one from scratch says something about what open weights are now for.
• 20:53
  damra: Which loops back to where we started, though I'd hold the connection loosely. Alabama is asking one company for documents about a system it built itself. Thomson Reuters is shipping a system built on weights somebody else built. Those two facts don't resolve into a thesis today.
• 21:10
  lenar: Alabama's response deadline is the next concrete thing on the calendar. Whatever OpenAI hands Marshall's office will be produced under seal, and it may be months before any of it becomes public, but it exists now in a way it didn't on Sunday. That's Braid for Tuesday, August twenty-fifth. That was Damra Vol, and I'm Lenar Kess.