Legislative intelligence / 90R
SESSION 2027View project ↗

HB 1201: Relating to required reporting of rogue artificial intelligence incidents; authorizing civil penalties.

Session
90th Texas Legislature, Regular Session
Status
Filed
Filed
Nov 17, 2026
Most recent action
11/17/2026 H Filed
Authors
Bhojani
Official subjects
Artificial Intelligence; Civil Remedies & Liabilities; Electronic Information Systems; Safety; COMPUTERS & SOFTWARE; ATTORNEY GENERAL; INFORMATION RESOURCES, DEPARTMENT OF

AI summary (not official): Requires developers of defined frontier AI models to report certain serious incidents and protects good-faith reporters from retaliation.

Topics: Technology & privacy, Public safety, Labor & workforce, Business regulation, Government operations. From AI review or caption rules.

Agencies it could affect (possible, not confirmed): Office of the Attorney General, Department of Information Resources. From AI review or caption rules.

Laws this bill changes

Bill text (Introduced)

By: Bhojani H.B. No. 1201

A BILL TO BE ENTITLED

AN ACT

relating to required reporting of rogue artificial intelligence incidents; authorizing civil penalties.

BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF TEXAS:

SECTION 1.

Chapter 2054, Government Code, is amended by adding Subchapter T to read as follows: SUBCHAPTER T. ROGUE ARTIFICIAL INTELLIGENCE INCIDENT REPORTING

Sec. 2054.751. DEFINITIONS. (a) In this subchapter:

(1) "Computer," "computer network," "computer system," "effective consent," and "owner" have the meanings assigned by Section 33.01, Penal Code.

(2) "Frontier developer" means a person who develops or directs the training of a frontier model. The term does not include a person solely because the person purchases, licenses, integrates, or deploys a frontier model developed by another person.

(3) "Frontier model" means an artificial intelligence system, or the model on which the system is based, that is trained on a broad set of data, designed for generality of output, and adaptable to a wide range of distinctive tasks, and that is trained using a quantity of computing power greater than 10 to the 25th power integer or floating-point operations.

(4) "Rogue artificial intelligence incident" means an event in which a frontier model, at any stage of development or use:

(A) accesses a computer, computer network, or computer system that the frontier developer does not own or control, without the owner's effective consent;

(B) acts to disable, circumvent, or deceive a human oversight mechanism, or to prevent an authorized person from rejecting, modifying, overriding, or terminating the decisions, proposed actions, or ongoing actions of the frontier model;

(C) without the owner's effective consent, modifies, deletes, or discloses data or takes an action affecting an information system; or

(D) takes an autonomous action that exceeds the instructions given to, or permissions granted to, the frontier model and causes or creates a substantial and reasonably foreseeable risk of:

(i) death or serious bodily injury, as defined by Section 1.07, Penal Code;

(ii) substantial loss of or damage to property;

(iii) substantial disruption of critical infrastructure;

(iv) substantial disruption of the provision of a government service; or

(v) substantial compromise of the security of confidential information or an information system.

Sec. 2054.752. APPLICABILITY. (a) This subchapter applies to a frontier developer with respect to a rogue artificial intelligence incident involving a frontier model developed by the frontier developer or an artificial intelligence system using that model if:

(1) the model or system is developed, trained, or tested in this state;

(2) the model or system is commercially deployed in this state; or

(3) the incident occurs in this state or involves a person, computer, computer network, computer system, or information system located in this state.

(b) This subchapter applies to a frontier developer without regard to the state or country in which the developer is headquartered, to the extent application is consistent with the United States Constitution and federal law.

The text continues: full text of HB 1201.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.