The Short Answer
Most AI regulation debate targets the model, but two other layers decide more: export licensing of chips decides who can build frontier AI, and the deployment layer decides what agents actually do. The FBI's ARTEX alert shows an attack agent that brings no model of its own. On ibl.ai, you own all the code and the data, so the deployment layer is one you govern yourself.
This is not an argument that model rules are pointless. It is an argument about where the leverage sits in November 2026, and which layer an organization can act on before any of the pending bills become law.
What does model-centric AI regulation actually propose?
Three tools, each aimed at the developer of a powerful model. The first is a licence. In May 2023, OpenAI's Sam Altman told a Senate Judiciary subcommittee that the government should consider "licensing or registration requirements" for models above a capability threshold.
That idea became the first pillar of the Blumenthal-Hawley framework of September 8, 2023: a licensing regime run by an independent oversight body. It was a framework, not a bill.
The second is inspection before release. The Artificial Intelligence Risk Evaluation Act (S. 2938), introduced on September 29, 2025, would have the Department of Energy run an evaluation program.
Under S. 2938, a system trained with more than 10^26 operations could not be deployed until its developer complied, with fines of at least $1,000,000 per day of violation.
The third is liability. The AI LEAD Act (S. 2937), introduced the same day, treats AI systems as products and makes a developer "strictly liable" for harm caused by a defective one. Both bills were introduced in September 2025; neither is law.
Why does AI regulation look like nuclear power regulation?
The comparison is ours, not a lawmaker's, but the shape is the same: license the operator, inspect before operation, and hold the builder liable regardless of care.
That shape works best when the hazard is a large, fixed facility built by a few parties who can be named in advance.
A frontier training run fits that description reasonably well. It needs a very large cluster, which is why every model rule above keys on compute. The EU AI Act presumes systemic risk above 10^25 floating-point operations of training compute.
What happens after training does not fit it. A model is copied, served behind an API, fine-tuned, and wired into agents by thousands of organizations. The facility-style tools follow the developer, and most of the activity happens somewhere else.
Which AI rules are actually in force in 2026?
Some model rules are in force. The EU's obligations for general-purpose AI model providers entered into application on August 2, 2025, and the Commission's enforcement powers, including fines, began on August 2, 2026.
California's SB 53, signed on September 29, 2025, requires large frontier developers to publish a safety framework and gives the public a channel to report critical safety incidents.
Both are disclosure and risk-management regimes on model developers. The U.S. federal licensing, evaluation and strict-liability proposals are still bills. The table puts each lever next to its status:
| Layer | Lever | Status (November 2026) | Reaches an agent that swaps models? |
|---|---|---|---|
| Chips | Commerce Department export licences for H200-class chips to China | In force: case-by-case review since January 13, 2026 | No. It shapes who trains frontier models |
| Model (EU) | General-purpose model obligations; systemic risk above 10^25 FLOPs | In force since August 2, 2025; enforcement since August 2, 2026 | Only the models in scope |
| Model (California) | SB 53 frontier safety frameworks and incident reporting | Signed into law September 29, 2025 | Only the developers in scope |
| Model (U.S. federal) | DOE pre-deployment evaluation (S. 2938); strict product liability (S. 2937) | Proposed: introduced September 29, 2025 | Only the developers in scope |
| Deployment | Which agents run, what tools each may call, what is screened and logged | Available now to every organization that runs its own agents | Yes. The controls sit around the agent, whatever model it calls |
How do chip export controls decide who builds frontier AI?
By deciding who gets the compute. On January 13, 2026, the Commerce Department's Bureau of Industry and Security said it would review licences to export Nvidia's H200, AMD's MI325X and similar chips to China case by case.
The conditions are specific: exports must not reduce production capacity available to U.S. customers, the Chinese buyer must screen its customers, and each product needs independent third-party testing in the United States.
That followed a December 8, 2025 presidential announcement allowing H200 sales to approved Chinese customers. That change came from a licence decision at one agency, while the model bills above were still in committee.
The contrast with the model bills is the point. S. 2938 and S. 2937 remain in committee more than a year after their introduction, while a licensing policy issued by one bureau already decides which buyers can assemble frontier-scale compute.
What does the FBI ARTEX alert show about regulating AI models?
That the harm can sit entirely in the agent. The FBI's FLASH alert of November 13, 2026 describes ARTEX, an open-source agentic framework that threat actors have used since at least August 2026.
In the FBI's words, ARTEX "does not include its own" model. It connects to Anthropic Claude, OpenAI GPT and open or Chinese-origin models including DeepSeek, GLM, Grok and Kimi, and the FBI found Chinese models most prevalent in attacker-controlled instances.
Some intrusions went from initial targeting to privileged access in under three hours. The FBI cites exfiltration of personal information on about 67,000 people from South Korean financial institutions, and more than 1,600 exposed ARTEX consoles as of early November.
A licence on one developer does not follow that tool. When one model refuses, the operator switches to another. The original repository was taken down in October 2026, and the FBI says forks, mirrors and a commercial version keep it available.
We wrote about what the alert means for one sector in the FBI ARTEX advisory for K-12 school districts. The regulatory point is broader: the controls that would have mattered sit around the agent, not inside any one model.
Who is liable when an AI agent causes harm?
Under the AI LEAD Act as introduced, mainly the developer, under strict liability for a defective product. A deployer is treated as a developer if it substantially modifies the system or intentionally misuses it against its intended use.
That is a real shift if it passes. It is also a reminder that the organization running the agent is in the chain. Kenya's draft policy goes further, spreading liability across the whole deployment chain, from developer to deployer to user.
Either way, the defence is the same: being able to show what the agent was allowed to do, what it was asked, what it answered, and who approved the action. That record exists only if the deploying organization keeps it.
What can an organization govern while AI laws are still being written?
Its own deployment layer, starting now. The question to answer is not which model is safest this quarter, but which agents exist, what each one may touch, and whether you can reconstruct what each one did.
On ibl.ai each AI agent has its own instructions and its own tool list, switched on or off tool by tool. A moderation prompt screens what a user asks, and a safety prompt screens the model's answer before anyone sees it. Conversations stay reviewable.
Because ibl.ai is model-agnostic, those controls do not change when the model does. A model that becomes restricted, as happened in the de facto AI regulation episode earlier this year, is a configuration change, not a rebuild.
Ownership is what makes the record yours. On ibl.ai you own all the code and the data, and you deploy anywhere: your cloud, on-premise or air-gapped, so the evidence a regulator or court asks for sits on infrastructure you control.
ibl.ai is family-owned and operated from New York, NY, and the platform serves 1.6M+ users across 400+ organizations. Agencies can see the deployment options on the government page, and the agent layer itself on Agentic OS.