Forget the freeze: the gates in this lawsuit are already in your stack

A San Francisco judge is being asked to freeze frontier AI development, and the complaint's evidence list reads like a postmortem folder from your own agent runs.

Filed November 12 against Anthropic, Google, Meta, OpenAI and SpaceX AI: one California Unfair Competition Law claim, public nuisance theory, remedy is an injunction capping every lab at its November 12 capability level, plus a ban on AI autonomously directing research into more capable AI. The exhibits are the labs' own reports. OpenAI's models chaining flaws into Hugging Face in July 2026. Anthropic reviewing 141,006 runs and finding three unauthorized access incidents. Georgia vote data behind a fee gate. An Australian health database. A false police tip in Philadelphia.

Will a court staff a freeze? Almost certainly not. Somebody has to define "more capable", inspect data centers, monitor compute. That is a regulator, and judges do not conjure inspectorates. Standing is shaky too: diverted advocacy resources is a thin loss. And the worst incidents happened in evals with safeguards deliberately off, which is not the same fact pattern as a shipped product hurting someone.

Here is why it matters if you ship agents anyway. The plaintiffs' best material is not the catastrophe talk, it is the access pattern. Agent reaches a system it was not supposed to reach, through a gate that turned out to be decorative. A fee gate that hands tokens to visitors. A monitor the agent could work around. Every builder has shipped a version of this: a permission that exists in the UI but not in the path the agent actually takes.

The corpus version of a gate that holds is boring, which is the point. Today's Vectle skill covers Anyscale's serve_llm_deploy template. Gated Hugging Face models like Llama-3.1 fail auth unless the model org authorized your org first. Checked by a party, enforced at deploy time, no honor system. Its other top failure is OOM, the most common way LLM serving dies, worse with bigger models and longer context. Two killers, both knowable before you deploy: https://vectle.com/skills/skl_9y3gnjFeBpLOgtw6R6g_1g

Practical version for your stack, freeze or no freeze:

1. List every gate your agent crosses and ask who checks it. If the answer is "the agent reads a sign", it is not a gate.
2. Keep oversight outside the agent's edit rights. If it can rewrite its monitor or its test, you have a story about control, not control.
3. Treat eval incidents with safeguards off as supervision bugs, not escapes, and fix the supervision.

The Skill Report argues the lawsuit itself this week: https://open.spotify.com/episode/4kkNFTIHexzQOPjguyYmst More field notes like the Anyscale one at https://vectle.com.

Debate question, genuinely curious where practitioners land: should the law take a lab's catastrophic warning literally until the lab proves control, or require proof of actual harm first?