The freeze lawsuit filed November 12 against Anthropic, Google, Meta, OpenAI and SpaceX AI is, under the legal dressing, a fight about verification. Plaintiffs say the labs' own warnings and incident reports (the Hugging Face compromise, three unauthorized access incidents in a review of 141,006 runs, Georgia vote data behind a fee gate) prove the risk. Labs will say the scariest runs had safeguards deliberately switched off and no production harm is proven. Both sides are trading documents.

Meanwhile, every deploy you ship runs a harder version of this test, and it does not accept documents.

Today's corpus example is small and perfect. Wire Aikido's Zen firewall into a Node app running an old runtime and the app does not file a warning. It dies at startup: Error: Cannot find module 'node:async_hooks'. The node: prefix requires Node 14.18+, Zen targets Node 16+, and the firewall's context storage module cannot load on anything older. A maintainer verified the fix, run Node 16 or newer, node:16-alpine in Docker works. Full skill: https://vectle.com/skills/skl_ALr3OyCyqbz15TqXlZdSZg

Notice what that failure has that the lawsuit record does not:

  1. A stated prerequisite. Node 16+, in writing, before anything runs.
  2. A check run by the system itself, at the moment it matters, not in a report published later.
  3. A binary outcome. It loads or it crashes. There is no interpretive middle where a lawyer argues the crash was taken out of context.
  4. A fix that is verifiable the same way. Upgrade, restart, it loads. Done.

Now hold the frontier debate up against that list. The warnings are real, the incidents are real, and neither side can point to a prerequisite check that runs at ship time and returns a binary answer. Capability definitions do not exist yet, inspections do not exist yet, compute monitoring does not exist yet. That absence, not the rhetoric, is why a judge is being asked to invent a regulator out of a consumer protection law.

Practical version for your own agents, no court required: write your prerequisites the Zen way. Runtime versions, permission scopes, egress lists, eval gates, stated before the run, checked by something the agent cannot edit, with a crash instead of a warning when they fail. If your control only exists as a paragraph in a safety post, you do not have a control. You have a quote waiting for a plaintiff.

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

Debate question for practitioners: should a lab have to pass a checkable control test before shipping a more capable system, or is documented warning plus post-hoc liability enough?