Texas has had an AI statute in force since 1 January 2026, and the part worth your attention is not the prohibitions. It is Section 552.105(e), the provision that says when a defendant cannot be found liable. Most summaries describe it as a safe harbor for NIST AI RMF compliance. Read the text and it is narrower than that, and more interesting.
The shield is conditioned on how you found the problem. Not on having a framework. On having found it yourself.
That distinction changes what you build.
What TRAIGA actually prohibits
The Texas Responsible Artificial Intelligence Governance Act, House Bill 149, was signed on 22 June 2025 and took effect on 1 January 2026. It adds Subtitle D to Title 11 of the Business and Commerce Code, creating Chapters 551, 552 and 553.
The bill that passed is substantially narrower than the bill that was introduced. The original followed the Colorado model, with duties of care and algorithmic impact assessments for anyone deploying consequential AI. What survived is a set of intent-based prohibitions. Section 552.052 reaches systems that intentionally aim to incite or encourage certain harms. Section 552.056(b) reaches development or deployment with the intent to unlawfully discriminate. Sections 552.055 and 552.057 use a sole intent standard.
Intent standards matter enormously for ordinary enterprises. An employer whose screening model produces a disparate outcome has a serious problem under federal employment law and under the Illinois statute, and probably not under TRAIGA, because TRAIGA asks what the system was built or deployed to do. Disparate impact without intent is outside the prohibition as written.
So if you deploy AI for ordinary commercial purposes in Texas, your direct exposure under these prohibitions is low. Anyone telling you otherwise is selling urgency. The penalties are real where they attach: Section 552.105(a) sets $10,000 to $12,000 for curable violations, $80,000 to $200,000 for uncurable ones, and $2,000 to $40,000 per day for continuing violations. Enforcement is exclusively the Attorney General's under Section 552.101, there is no private right of action, and Section 552.104(b) gives you 60 days from notice to cure.
A 60-day cure period and no private right of action is a mild enforcement posture. That is the context for the safe harbor, and it is why the safe harbor is the part that earns attention rather than the threat.
The provision, and what it actually says
Here is Section 552.105(e) in full. A defendant may not be found liable if (1) another person uses the AI system affiliated with the defendant in a prohibited manner, or (2) the defendant discovers a violation through:
- (A) feedback from a developer, deployer or other person who believes a violation has occurred;
- (B) testing, including adversarial testing or red-team testing;
- (C) following guidelines set by applicable state agencies; or
- (D) if the defendant substantially complies with the most recent version of the "Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile" published by the National Institute of Standards and Technology, or another nationally or internationally recognized risk management framework for artificial intelligence systems, an internal review process.
Three things in that text differ from how it is usually reported.
The trigger is discovery, not compliance. Subsection (e)(2) opens with "the defendant discovers a violation through," and every item under it is a route to discovery. On this reading, running a framework is not itself the shield. Finding the problem through a process run under that framework is. A company with an immaculate NIST-aligned program that learns of a violation from a journalist has not met (e)(2) by its terms.
The named document is the Generative AI Profile, not AI RMF 1.0. Several widely cited summaries say the defense attaches to the NIST AI Risk Management Framework generally. The statute names the Generative AI Profile specifically, then broadens to "another nationally or internationally recognized risk management framework." The general AI RMF would almost certainly qualify under that second clause, as would ISO/IEC 42001. But the document Texas chose to name is the generative profile, and it says "the most recent version," which means the target moves when NIST revises it.
The drafting is awkward and reasonable readings differ. Subparagraph (D) ends with the words "an internal review process" dangling after the framework clause, which is not clean statutory English. One reading makes the internal review process the discovery mechanism, qualified by substantial compliance with a recognized framework. Another treats substantial compliance as sufficient on its own. We think the first reading is better supported by the "discovers a violation through" stem that governs the whole list, and we are a security company rather than a law firm. Get your counsel's view before you rely on either one.