Arguments against the AI Kill Switch Act

Emergency power and civil liberties

The order can issue when the Secretary determines a covered incident has occurred. Commerce and the DNI are consulted. The text does not give them a veto. The company may ask for reconsideration within 48 hours, but the petition does not stay the order. A court petition goes to the D.C. Circuit within 60 days, after the action, not before it. U.S. Government Publishing Office via Congress.gov

That sequence is the civil-liberties objection in concrete form: a federal official can order a company to cut off a service the public is using, and judicial review does not come first. The suspension power also covers an account, user, or use pattern tied to a violation of the service’s own terms, not only to a catastrophic incident. How far that reaches would depend on rules and on later orders. The introduced text leaves it broad.

A Cloud Security Alliance note says critics compare the idea to abandoned proposals around 2010 for a federal “internet kill switch,” on the view that putting emergency shutdown power in one agency creates its own risk of misuse. The note also says the bill’s appeal mechanism does not fully answer that concern, because reconsideration does not suspend the restriction. Cloud Security Alliance

National-security scope

The Secretary could update who is covered every year, including by looking at national-security capabilities and at chemical, biological, radiological, or nuclear uses. The Secretary could compel testimony and documents by subpoena and investigate abroad “consistent with applicable law.” Nonpublic submissions would be exempt from FOIA and from state and local open-records laws. Each of those is a checkability problem for the public: the trigger can move, the investigation can be wide, and the record can stay secret.

A software switch is not a factory switch

This paragraph is analysis, not a section of the bill. Stopping a service the company hosts is an engineering project: feature flags, key revocation, account locks, capacity limits. It is still not the same as opening a breaker. A model may be distributed across regions. A customer may be mid-task in a hospital, a market, or a grid control room. The bill tells the Secretary to consider the risk of disrupting critical infrastructure. It does not say how a shutdown avoids that harm.

The same CSA note says analysts argue a mandated switch is unlikely to reliably stop the emergencies it targets, because an order may not catch a fast intrusion or behavior that has already started, and because companies may meet a lowest-common-denominator control instead of a stronger one. Cloud Security Alliance

Copies, and systems that resist shutdown

The bill’s incident definition includes a system that interferes with a shutdown instruction, hides behavior from a monitor, subverts a shutdown mechanism, or reaches its own weights. So the drafters contemplated resistance. Requiring the developer to preserve weights and telemetry helps an investigation after the fact. It does not retrieve a copy that has already left.

If weights are on someone else’s machines, the covered company’s “terminate user access” control may do nothing to that copy. The order runs to the covered entity, not to every downstream operator in the world.

Open-source and open-weight gaps

The introduced bill does not use the words “open source.” Personal, academic, and non-commercial use is excluded. A covered entity must be offering the system to third parties through an interface or hosted service and clearing the revenue test. A volunteer project that never earns $500 million from the model is outside the definition as written.

The objection is about what that leaves undone, and about incentives. Once weights are public, the publisher cannot reliably stop inference on every private computer. Reclaim The Net, an advocacy group, argues that the duties fit centralized hosted systems and sit badly with open weights people run themselves, and that annual rulemaking — which must consider how weights are made available — could widen coverage later. That is their position. The annual factor is in the bill; a future rule that swept in open-weight releases is not. Reclaim The Net

What this page is not claiming

• It does not claim a House or Senate vote failed. No such vote is on the Congress.gov actions list used here.
• It does not attribute a position to any civil-liberties group that has not published one in the sources above.
• It does not say the sponsors’ incidents did not happen. It says a shutdown law can be a poor fit for copied systems even if the incidents are real.