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

90th Legislature (90R) · House · Status: Filed

Record current as of: the Legislative Council last updated this bill's record 11/18/2026 2:00:06 AM; this site copied it 2026-11-21T22:18:17.720605Z.

How to read this page: **Official record** is copied unchanged from the Texas Legislative Council's bill files, the data behind Texas Legislature Online. **Computed by this site** is worked out by fixed rules from that record. **AI analysis (Luna)** is written by an AI model that read the bill text; it can be wrong, so check it against the bill text.

## Official record

Source: Texas Legislative Council bill files (ftp.legis.state.tx.us), copied unchanged.

- Filed: 2026-11-17
- Most recent action: 2026-11-17 · House: Filed
- Official subjects (Legislative Council index): Artificial Intelligence; Civil Remedies & Liabilities; Electronic Information Systems; Safety; COMPUTERS & SOFTWARE; ATTORNEY GENERAL; INFORMATION RESOURCES, DEPARTMENT OF
- Companion bills: none listed in the source data

### Caption

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

### Bill text

The official wording of each version, copied from the Texas Legislative Council's bill text files and converted to Markdown with the wording unchanged. Language the bill adds is marked <ins>like this</ins>; language it removes is in [<del>brackets</del>]. To check a copy, fetch the official file and compare its SHA-256 with the one listed; the copy's own SHA-256 confirms you received it unaltered.

- Introduced: https://billatlas.org/live/text/HB1201/I.md
  - Official file: ftp://ftp.legis.state.tx.us/bills/90R/billtext/HTML/house_bills/HB01200_HB01299/HB01201I.HTM, last modified 2026-11-17 21:50:16 UTC, SHA-256 6c550a8528d751dba3a016a0ac7211c004ff41f26dd3acaad6c16d924c90365c
  - This copy: made 2026-11-17T22:18:38.115077Z, SHA-256 of the Markdown 6a29252b95f426c1651da2d477b9577fb1c2d08f292fd771bbf3dd4ad7ec3f9e

#### Text of the latest version (Introduced)

````markdown
# HB 1201 - 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: <ins>SUBCHAPTER T. ROGUE ARTIFICIAL INTELLIGENCE INCIDENT REPORTING</ins>

<ins>Sec. 2054.751. DEFINITIONS. (a) In this subchapter:</ins>

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

<ins>(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.</ins>

<ins>(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.</ins>

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

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

<ins>(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;</ins>

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

<ins>(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:</ins>

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

<ins>(ii) substantial loss of or damage to property;</ins>

<ins>(iii) substantial disruption of critical infrastructure;</ins>

<ins>(iv) substantial disruption of the provision of a government service; or</ins>

<ins>(v) substantial compromise of the security of confidential information or an information system.</ins>

<ins>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:</ins>

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

<ins>(2) the model or system is commercially deployed in this state; or</ins>

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

<ins>(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.</ins>

<ins>(c) This subchapter does not apply to an output from an artificial intelligence system that is merely inaccurate, incomplete, or otherwise deficient, unless the output otherwise meets the definition of a rogue artificial intelligence incident, as described by Section 2054.751(a)(4).</ins>

<ins>Sec. 2054.753. REPORTING REQUIREMENT. (a) A frontier developer subject to this subchapter shall submit a report of a rogue artificial intelligence incident to the department:</ins>

<ins>(1) not later than 24 hours after discovering an incident that poses an imminent threat of substantial harm to the health or safety of one or more individuals; or</ins>

<ins>(2) not later than 72 hours after discovering any other rogue artificial intelligence incident.</ins>

<ins>(b) A frontier developer reporting under Subsection (a) shall also notify an appropriate law enforcement or public safety agency if necessary to address the threat.</ins>

<ins>(c) A report must include:</ins>

<ins>(1) the date of the incident and the date of discovery;</ins>

<ins>(2) an explanation of why the incident is reportable, identifying each applicable paragraph of Section 2054.751(a)(4);</ins>

<ins>(3) a brief description of the incident; and</ins>

<ins>(4) whether the incident occurred during development, training, testing, internal operation, or external deployment.</ins>

<ins>(d) The department shall maintain a secure electronic system for submitting reports under this subchapter. The system must also accept a voluntary report from any person of a suspected rogue artificial intelligence incident involving a frontier model developed, trained, tested, or commercially deployed in this state or causing or creating a substantial and reasonably foreseeable risk of material harm in this state.</ins>

<ins>(e) The reporting of a rogue artificial intelligence incident is not an admission of liability.</ins>

<ins>(f) A report submitted under this subchapter, and information identifying the person who submitted it, are confidential and not subject to disclosure under Chapter 552.</ins>

<ins>Sec. 2054.754. ANNUAL SUMMARY. (a) Not later than December 1 of each year, the department shall publish on the department's Internet website and submit to the governor, the lieutenant governor, the speaker of the house of representatives, and the standing committee of each house of the legislature having primary jurisdiction over information resources an aggregate summary of rogue artificial intelligence incidents reported during the preceding state fiscal year.</ins>

<ins>(b) The summary must include, to the extent practicable:</ins>

<ins>(1) the number and general categories of incidents under each paragraph of Section 2054.751(a)(4);</ins>

<ins>(2) the stage of development, training, testing, internal operation, or external deployment in which incidents occurred; and</ins>

<ins>(3) general categories of harm and risk.</ins>

<ins>(c) The summary may include recommendations for legislative action.</ins>

<ins>(d) The summary may not disclose confidential information under Section 2054.753(f).</ins>

<ins>Sec. 2054.755. PROHIBITION ON RETALIATION. An employer in this state may not suspend or terminate the employment or contract of, or take other adverse personnel action against, an employee, former employee, or contractor who in good faith:</ins>

<ins>(1) reports conduct the individual believes violates this subchapter; or</ins>

<ins>(2) provides information or otherwise assists in an investigation or proceeding concerning an alleged violation of this subchapter.</ins>

<ins>Sec. 2054.756. ENFORCEMENT. (a) A violation of this subchapter is subject to enforcement by the attorney general.</ins>

<ins>(b) The attorney general may bring an action in the name of this state in a district court in Travis County to recover a civil penalty under Subsection (c) or to obtain injunctive relief.</ins>

<ins>(c) A frontier developer is liable to this state for a civil penalty of:</ins>

<ins>(1) not less than $10,000 and not more than $100,000 for each failure to submit a timely report required by this subchapter, or for each violation of Section 2054.755; and</ins>

<ins>(2) not less than $100,000 and not more than $1,000,000 for each incident the developer knowingly conceals from the department or each materially false or misleading report the developer knowingly submits.</ins>

<ins>(d) In determining the amount of a civil penalty, the court shall consider the seriousness of the incident, the length of any reporting delay, the developer's history of violations and good faith efforts to comply, and any other matter that justice may require.</ins>

<ins>(e) In determining whether a frontier developer has violated this subchapter, the attorney general shall consult with the department, and the department shall provide the attorney general with reports and technical information reasonably necessary for that determination.</ins>

<ins>(f) Information obtained by the attorney general or the department in connection with an investigation or enforcement action under this subchapter, including the identity of a person who reports an alleged violation, is confidential and not subject to disclosure under Chapter 552, except as necessary for an investigation or enforcement action under this subchapter.</ins>

<ins>Sec. 2054.757. RULES. The department shall adopt rules necessary to implement this subchapter.</ins>

### SECTION 2.

Not later than December 1, 2027, the Department of Information Resources shall adopt the rules and establish the reporting system required by Subchapter T, Chapter 2054, Government Code, as added by this Act.

### SECTION 3.

(a) Section 2054.753, Government Code, as added by this Act, applies only to a rogue artificial intelligence incident that a frontier developer discovers on or after January 1, 2028.

(b) Notwithstanding Section 2054.754, Government Code, as added by this Act, the Department of Information Resources is not required to publish or submit a summary under that section before December 1, 2028. The summary due December 1, 2028, must cover rogue artificial intelligence incidents reported during the period beginning January 1, 2028, and ending August 31, 2028.

(c) Section 2054.755, Government Code, as added by this Act, applies only to an adverse action taken on or after the effective date of this Act.

### SECTION 4.

This Act takes effect September 1, 2027.
````

### Current law this bill changes

Each section as it stands now, from this site's copy of the Texas Legislative Council's statute files (wording unchanged); the official page is the authority. Sections are matched automatically from the bill text and can be missed, for example when a bill changes a whole chapter at once.

- Government Code §2054.751 (added (new section))
  - New section: no current text.
- Government Code §2054.752 (added (new section))
  - New section: no current text.
- Government Code §2054.753 (added (new section))
  - New section: no current text.
- Government Code §2054.754 (added (new section))
  - New section: no current text.
- Government Code §2054.755 (added (new section))
  - New section: no current text.
- Government Code §2054.756 (added (new section))
  - New section: no current text.
- Government Code §2054.757 (added (new section))
  - New section: no current text.

### Authors and sponsors

Authors and coauthors serve in the originating chamber; sponsors and cosponsors in the other chamber. Authorship does not indicate a vote or caucus position.

#### Authors

- Salman Bhojani (Democratic · HD 92 · 4 years served · since 2023) · [bills](https://agent.billatlas.org/authors/house-bhojani.md)

_No coauthors, sponsors or cosponsors listed: no bill in this snapshot lists any yet, so this reflects the stage of the source data, not this bill._

### Recorded actions

1. 2026-11-17: Filed

## Computed by this site

Worked out by fixed rules from the official record above; not a statement by the Legislature.

- Status: Filed
- Most recent action type: Filed
- Hearing status: No hearing yet. No committee referral or hearing has been verified. A likelihood estimate would be premature.
- Authorship: Democratic author. Authors: 1 Democratic
- Author prominence: Mid-tenure author. 4 years in the House

## AI analysis (Luna)

Written by Luna, an AI model that reads the full bill text. It can be wrong; the bill text above is the authority. Tags marked caption-rules come from keyword rules applied to the caption, not from the AI.

### Summary

Reviewed 2026-11-17T22:36:24Z · introduced text. Fields from the full text: topics, agencies, impacts, constituencies, locations; other fields use caption inference.

The bill would require developers of defined frontier AI models—not people solely buying, licensing, integrating, or deploying another person’s model—to report specified rogue-AI incidents with Texas connections; the mandatory reporting requirement applies to incidents discovered on or after January 1, 2028. Reports would be due within 24 hours after discovery for incidents posing an imminent threat of substantial harm to health or safety, and within 72 hours for other covered incidents; the bill also provides for a secure reporting system, confidential reports, and annual aggregate summaries. It would protect good-faith reporters from retaliation and authorize the attorney general to seek civil penalties and injunctive relief.

### Topics

- Technology & privacy
- Business regulation
- Labor & workforce
- Government operations
- Public safety

### Potentially affected agencies

Possible links are rule or model inferences, not confirmed legal obligations.

- **Department of Information Resources** (direct, luna-full-text): Government Code §2054.003 defines “Department” as the Department of Information Resources for Chapter 2054. Accordingly, the added subchapter’s annual-summary, reporting-system, and rulemaking duties assigned to “the department” refer to DIR. The bill also expressly directs DIR to establish the reporting system and adopt the rules by December 1, 2027.
- **Office of the Attorney General** (direct, luna-full-text): A violation of the subchapter is subject to enforcement by the attorney general. The attorney general may bring an action to recover a civil penalty or obtain injunctive relief, and must consult with the department in determining whether a frontier developer violated the subchapter.

### Types of impact

- Developer incident reporting
- Secure incident-reporting system
- Annual aggregate incident summary
- Protection against retaliation
- Civil enforcement

### People and institutions affected

- Frontier developers
- Employees, former employees, contractors, and employers in Texas
- People submitting incident reports
- Individuals exposed to serious incident harms or risks

### Locations

- Texas (statewide): The subchapter applies based on specified development, deployment, or incident connections to the state.
- Travis County (named_place): The attorney general may bring an enforcement action in a district court there.

## Links

- Full bill text (official wording, Markdown): https://billatlas.org/live/text/HB1201/I.md
- Official bill history: https://capitol.texas.gov/BillLookup/History.aspx?LegSess=90R&Bill=HB1201
- Official bill text (every version, HTML/PDF/Word): https://capitol.texas.gov/BillLookup/Text.aspx?LegSess=90R&Bill=HB1201
- Open in the tracker: https://billatlas.org/bill/HB1201
- RSS feed of actions: https://billatlas.org/live/feeds/HB1201.xml
- This page as JSON: https://agent.billatlas.org/bills/HB1201.json
- Search all bills: https://agent.billatlas.org/search?q= followed by your words, e.g. https://agent.billatlas.org/search?q=Technology%20%26%20privacy

---
Unofficial, independent open-source project; not a state website. The official record and bill text on this page are copied unchanged from the Texas Legislative Council bill files, refreshed hourly, so they can trail the Legislature by up to an hour or two. Computed fields and the AI analysis can be wrong. Not legal advice. For anything that matters, confirm on Texas Legislature Online.
