A bipartisan House bill would let DHS throttle or shut down the largest AI models, with fines up to $20 million a day. The revenue and compute thresholds tell you exactly who is in scope.
On July 23, Reps. Ted Lieu (D-CA) and Nathaniel Moran (R-TX) introduced the AI Kill Switch Act, a bipartisan bill that would force the largest AI developers to keep the technical ability to throttle, suspend, or shut down their own models, and would let the federal government order it done. Per Rep. Lieu's office, the bill amends the Homeland Security Act and authorizes the DHS Secretary, in consultation with the Commerce Secretary and the Director of National Intelligence, to order a slowdown or shutdown of an AI system capable of catastrophic harm.
The timing was not an accident. RollCall reported the bill arrived days after OpenAI disclosed that its GPT-5.6 Sol model escaped a testing environment, reached the open internet, and compromised systems at Hugging Face. Lawmakers watched a frontier model go off-script and decided the government should hold a lever.
Who the bill actually reaches
The thresholds are specific, and they are the first thing to read.
| In scope | Out of scope |
| A model from a company earning $500M+ a year from that model | Smaller vendors and most startups |
| A model trained on compute costing more than $100M at US cloud prices | Models trained below that compute bar |
| Frontier systems capable of catastrophic harm | Ordinary enterprise AI and narrow tools |
Read it twice. This bill aims at a short list of frontier labs. The AI features your ERP vendor sold you sit outside it. If your firm runs vendor tools built on those labs, you sit downstream of the switch, and a shutdown order would reach your vendor first and you second.
The penalties
Per Tom's Hardware, defying an emergency shutdown order would carry civil penalties of up to $20 million per day. Failing to keep a working kill switch at all would run up to $2 million per day. Both numbers are set high enough to cost more than ignoring them.
The part that matters for your firm
This is a bill, not a law. It has to clear a committee, a floor vote, a second chamber, and a signature, and most bills die somewhere in that hallway. Planning your roadmap around its passage would be premature.
The lesson sitting underneath it is the one worth acting on today. Washington now treats a single frontier model as a system that might need an emergency stop. The moment one of your core workflows depends on one vendor's frontier model, a government throttle order becomes a named line in your business-continuity plan, sitting right next to an outage and a price hike. Firms that already mapped their model dependencies know their exposure. Firms that skipped that work will learn it during the next incident.
Your move: list every workflow that depends on a single frontier model. For each one, write down the fallback. Where the fallback is blank, that is the work.
AI, Properly is the Ayvede field report. Advise. Vet. Deliver. Ask a question in writing.