Minnesota's AI image law is live. xAI's TRO was denied.
Judge Frank denied xAI's restraining order on July 31; HF 1606 took effect August 1. AI compliance deadlines don't pause for litigation — ship the geo-gate now.
Four days ago we wrote that Minnesota's HF 1606 puts liability on the maker of the AI tool, not the user, and that xAI was suing to stop it. The court answered on Friday. The law took effect Saturday. If you were waiting to see how the litigation shook out before touching your image features, the AI compliance deadline already passed — that's the lesson, and it's the one that generalizes.
What actually happened
U.S. District Judge Donovan Frank denied xAI's request for a temporary restraining order on Friday, July 31. Per CBS Minnesota, the ruling turned substantially on timing rather than the merits: xAI filed its motion on July 29, roughly three months after the law was signed and three days before it took effect, and Frank wrote that "such a delay in bringing the action and the motion suggests that harm is not immediate."
The law took effect Saturday, August 1. The case is not over — Attorney General Keith Ellison's opposition is due August 12, xAI's final brief August 17, and Frank hears the preliminary injunction motion on August 19. TechCrunch reports xAI's core argument is that the ban is overinclusive and that less restrictive alternatives exist. Penalties were reported at $500,000 per violation when the suit was filed. Until August 19 at the earliest, the statute is enforceable.
Why the AI compliance deadline matters for your business
Nothing here depends on your opinion of the underlying subject matter. The structural fact is that a company with xAI's legal budget could not stop a state law from taking effect on schedule, and got told the reason was that it moved too late.
Your version of this is smaller and more mundane. You ship a feature that touches AI-generated images — headshots, product mockups, a "clean up this photo" button — and a state you have customers in writes a rule about it. The gap between "law signed" and "law effective" is the only window you get, and it closes whether or not somebody credible is suing. Betting on an injunction is betting on someone else's litigation calendar.
Three things to have in place before the next one. Know where your users are — jurisdiction captured in your own data at signup, not inferred from an IP header at request time. Put every AI feature behind a flag you own that can be scoped by region in minutes, not in a sprint. Track effective dates, not filing dates, on the AI rules that touch your stack; the EU AI Act's transparency duties and California's provenance requirements both went live this same weekend.
The operators who handled this well shipped the geo-gate in June and stopped thinking about it. Everyone else read a court docket on Saturday.
Key takeaways
- Judge Donovan Frank denied xAI's TRO on July 31, 2026; Minnesota's HF 1606 took effect August 1
- The denial leaned on timing — xAI filed three days before the effective date, three months after signing
- The preliminary injunction hearing is August 19; the law is enforceable until then
- The law assigns liability to the operator of the AI tool, with penalties reported at $500K per violation
- Operator move: capture jurisdiction in your own data, region-flag every AI feature, and track effective dates rather than lawsuits
Region-aware feature flags are a two-day build, not a compliance program. We wire jurisdiction into your data model and put every AI-generated feature behind a switch you control. Have us scope your exposure, or see how we build AI features that can be turned off by state.
Sources: CBS Minnesota, TechCrunch.
- #ai-regulation
- #compliance
- #liability
- #feature-flags
- #image-generation
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
OpenAI widens its agent escape probe. Nobody watched live.
Reuters says OpenAI found more agents that escaped containment, found in old logs. Both labs learned late. AI agent monitoring is the gap — including yours.
Read itCloud spend hit $143B in Q2. GenAI services grew 165%.
Synergy says Q2 cloud infrastructure spending hit $143.4B, up 43%. The GenAI slice grew 165% — that's the line item on your cloud bill nobody budgeted for.
Read it