Education · Texas TRAIGA

Texas TRAIGA for tutor and grader workflows

Texas TRAIGA in tutor and grader workflows: what compliance requires, who asks for evidence, and the records to keep.

Start free Open the Console

Legal forceBinding law

Applies from1 Jan 2026

SectorEducation

Checked21 Oct 2026

01 / The rule

What Texas TRAIGA requires

Anyone who develops or deploys AI systems in Texas, with added disclosure and use limits for government agencies and a disclosure duty for health care providers.

01Government agencies: disclose before or during interaction that a consumer is dealing with AI, clearly, in plain language, without dark patterns.
02Health care providers: disclose AI use in a service or treatment by the date it is first provided (emergencies: as soon as possible).
03Do not develop or deploy AI intended to incite self-harm, harm to others or criminal activity.
04Do not develop or deploy AI with intent to unlawfully discriminate against a protected class; disparate impact alone does not show intent.
05Government entities: do not use AI for social scoring, or biometric identification of individuals without consent where it infringes rights.
06Do not develop or distribute AI with the sole intent of producing child sexual abuse material or unlawful sexual deepfakes.

02 / In this sector

In a tutor and grader workflow

Written for AI systems. Liability mostly turns on intent, and the Act gives a defence to defendants who find violations through red-teaming or who substantially comply with the NIST AI RMF Generative AI Profile or a similar framework.

Usually asked by

District administrators, school leaders, and student equity teams.

Named alongside

Title VI · FERPA · §504 / IDEA.

Sector pagePlanisphere for education

03 / Records

Records to keep

01Documented intended purpose and deployment context for each AI system
02Red-team and adversarial testing records
03Mapping of internal controls to the NIST AI RMF Generative AI Profile
04Consumer and patient AI-disclosure text with placement records

Optional evidence · where Planisphere fits

Keep a record anyone can check

When your team meets a duty, Planisphere can seal the event it reports as a receipt.

01 · Your teamRecord the event

A disclosure shown, a review signed, a model change approved: the event your system reports.

02 · PlanisphereSeal it

The event becomes a sealed receipt, dated and attributed to whoever is signed in.

03 · AnyoneCheck it

Paste the receipt into Verify. No account or key.

A record supports your compliance evidence process. It is not a legal finding or a certification. Systems that call Planisphere's gate API can also hold or refuse an action before it runs.

SOURCES

Go back to the source

PRIMARY

HB 149 bill history (89th Legislature, Regular Session)

Texas Legislature Online

PRIMARY

HB 149 enrolled text

Texas Legislature Online