Skip to main content
SIGNAL FEED
Loading signal feed…
AI Policy · Explainer

The Great American AI Act, explained

A plain-English, section-by-section guide to the Great American Artificial Intelligence Act (GAAIA) discussion draft (June 2, 2026) — covering frontier-AI governance, workforce, cybersecurity, and R&D. Ask Insta anything below and get an answer grounded in the actual bill text, with the section cited.

Informational only — not legal advice. This is a discussion draft that can change; it isn’t a compliance determination. For your situation, consult qualified legal counsel.

Ask Insta about the bill
Grounded in the GAAIA discussion draft · cited · refuses without support

I can answer questions about the Great American AI Act using only the bill text — with a section citation for every answer, and a clear “I don’t know” when the draft doesn’t cover it. What would you like to know?

Key terms defined in this bill

Plain-English definitions in the Insta Glossary.

Frontier modelFrontier developerLarge frontier developerCAISIIndependent Verification Organization (IVO)Frontier AI frameworkCritical safety incidentCatastrophic riskModel weights

In the news

House unveils the 269-page Great American AI ActTrump signs AI executive orderAnthropic calls for a global pause on frontier AIUS government eyes equity stakes in AI firms

Common questions about the bill

Answered from the bill text, with the section cited. Ask your own above.

Who does the Great American AI Act regulate?

Based on the discussion draft sections provided, the Act targets several distinct groups:

Frontier Developers

  • Entities that have trained a frontier model (a foundation model trained using more than 10²⁶ computing operations) AND had more than $50 million in gross revenue in the prior year (Sec. 101)
  • A subset called "large frontier developers" must have had more than $500 million in gross revenue (Sec. 101)
  • AI Developers More Broadly

  • Any person or entity that determines training objectives and performs or directs training, fine-tuning, or substantial modification of an AI model prior to deployment (Sec. 121)
  • State-level regulation of these developers' pre-deployment activities is preempted by federal law — at least for 3 years after enactment (Sec. 121)
  • Employers and Workers

  • Employers (including companies, contractors, and agents) who pay workers are covered under the whistleblower protection provisions (Sec. 113)
  • "Covered individuals" include current and former employees and independent contractors (Sec. 113)
  • AI Platforms

  • Computational systems or services that generate, curate, rank, recommend, or moderate content using machine learning or automated techniques fall under the free speech study provisions (Sec. 141)
  • Federal Agencies

  • The Comptroller General is directed to evaluate how federal agencies adopt and use AI (Sec. 122)
  • Federal agency interactions with AI platforms regarding content and speech are subject to study (Sec. 141)
  • ---

    Keep in mind this is a discussion draft dated 2026-06-02, and the scope of who is regulated may change. For questions about a specific organization's obligations, consult qualified legal counsel.

    What must large frontier developers disclose before deploying a new model?

    Before deploying a new frontier model (or one with a substantial modification), here is what the draft requires to be published on a publicly available website:

    From Sec. 111(c), a transparency report must include:

  • A mechanism for individuals to contact the developer
  • The model's release date
  • Each language the model supports (if any)
  • Each output modality (e.g., text, image, audio)
  • The intended use of the model
  • Any restrictions or conditions on use
  • Each catastrophic risk assessment conducted under the developer's frontier AI framework
  • The results of each such assessment
  • The extent to which a third party was involved in the risk assessment
  • Any other steps taken under the framework with respect to that model
  • Additionally, under Sec. 111(a), large frontier developers (those with over $500 million in gross revenue — see Sec. 101(15)) must already have a frontier AI framework published that covers how they identify risk thresholds, assess catastrophic risk, use third-party evaluators, handle cybersecurity of model weights, and more.

    A few things to keep in mind:

  • Developers may redact certain information to protect trade secrets, cybersecurity, public safety, or national security — but must include a note explaining the character of any redaction (Sec. 111(e)).
  • Knowingly making inaccurate or misleading statements in the transparency report is prohibited, with a good-faith exception (Sec. 111(d)).
  • This is a discussion draft dated 2026-06-02, so these provisions may change.
  • For questions about how these requirements apply to a specific organization, consulting qualified legal counsel is advisable.

    What is a large frontier developer under the bill?

    Under the draft bill, a "large frontier developer" is defined in Sec. 101 as a frontier developer that, in the calendar year immediately before the year at issue, had more than $500,000,000 in gross revenue — counting revenue collectively with every affiliate of that developer.

    To break that down, it builds on two earlier definitions:

  • A "frontier developer" is an entity that has trained (or initiated the training of) a frontier model AND had more than $50,000,000 in gross revenue (with affiliates) in the preceding calendar year. (Sec. 101)
  • A "frontier model" is a foundation model trained using more than 10²⁶ integer or floating-point operations, including the original training run and any subsequent fine-tuning, reinforcement learning, or other substantial modification the developer applies to it. (Sec. 101)
  • So, in plain terms, a large frontier developer is a company (or similar entity) that:

    1. Has trained a very large AI model (above the 10²⁶ compute threshold), and

    2. Brought in more than $500 million in gross revenue in the prior year, counting affiliated entities together.

    This distinction matters because the draft imposes the most significant obligations — such as publishing a frontier AI framework (Sec. 111) and undergoing semi-annual independent audits (Sec. 112) — specifically on large frontier developers.

    This is a discussion draft dated 2026-06-02, so these definitions may change. For questions about how these definitions apply to a specific company, consult qualified legal counsel.

    What is CAISI and what does it do?

    CAISI stands for the Center for AI Standards and Innovation. It is an existing body at the National Institute of Standards and Technology (NIST) that plays a significant role under this draft bill. Here is a summary of its key functions based on Sec. 102:

    Standards and Best Practices

  • Develops guidelines, best practices, and voluntary standards for evaluating and improving security of AI systems (Sec. 102)
  • Supports development of standards for AI hardware and software reliability, interpretability, and data center security (Sec. 102)
  • Develops best practices for detecting synthetic content, watermarking, and content provenance (Sec. 102)
  • Evaluation and Assessment

  • Conducts evaluations of AI systems developed in the US and by foreign competitors (Sec. 102)
  • Monitors trends in AI progress domestically and among foreign competitors (Sec. 102)
  • Produces resources to help federal agencies evaluate AI systems (Sec. 102)
  • Oversight of AI Auditors

  • Administers the Independent Verification Organization (IVO) regime, including licensing auditors, reviewing audit results, and disciplining non-compliant auditors (Sec. 102)
  • Can refer enforcement matters to the Attorney General (Sec. 102)
  • International and Interagency Coordination

  • Coordinates US participation in international AI standards forums (Sec. 102)
  • Convenes semiannual meetings with agencies, private sector, and other stakeholders (Sec. 102)
  • Support for Open-Source Security

  • Consults with CISA on grants and programs for critical open-source software maintainers (Sec. 311)
  • CAISI is also authorized up to $100 million per year for fiscal years 2027–2029 to carry out its work (Sec. 102).

    Note: This is a discussion draft dated 2026-06-02, so these provisions may change. For questions about specific obligations, consult qualified legal counsel.

    Does the bill preempt state AI laws?

    Yes, but only partially and temporarily. Here is what the draft says:

    Sec. 121 — Federal Preemption of State AI Development Laws

    The bill preempts state laws that specifically target the development of AI models — meaning activities before a model is deployed (e.g., training, fine-tuning, setting training objectives, pre-deployment safety evaluations). (Sec. 121(b))

    What is NOT preempted:

  • State laws of general applicability (laws that apply broadly, not just to AI) (Sec. 121(c)(1))
  • State common law remedies (Sec. 121(c)(1))
  • State laws covering activities after a model is deployed — including laws on AI systems, products, or services that use or incorporate an AI model (Sec. 121(c)(2))
  • State authority granted under this Act itself, including State Attorneys General powers (Sec. 121(c)(3))
  • Time Limit:

    The preemption provision has a sunset clause — it automatically expires 3 years after enactment unless Congress reauthorizes it. (Sec. 121(d))

    In short, this draft focuses preemption narrowly on the pre-deployment development phase, and it is not permanent.

    For questions about how these provisions apply to a specific state law or a particular company's situation, consulting qualified legal counsel is advisable.

    What must a developer report after a critical safety incident, and how quickly?

    Based on Sec. 111 of the draft, here is what the reporting requirements look like after a critical safety incident:

    Standard timeline — 15 days

    If a frontier developer discovers a critical safety incident, it must submit a report to the Director's reporting mechanism within 15 days of that discovery. (Sec. 111(g) and (f)(1))

    That report must include:

  • The date of the incident
  • Why the incident qualifies as a critical safety incident
  • Whether the incident is connected to the developer's internal use of a frontier model
  • Urgent timeline — 24 hours

    If the critical safety incident poses an imminent risk of death or serious physical injury, the developer must report it to a law enforcement agency with jurisdiction within 24 hours of discovery. (Sec. 111(g)(2))

    Who receives the reports

  • The Director receives reports through the confidential mechanism established under Sec. 111(f)(1).
  • State Attorneys General who have opted in under Sec. 111(h) may also receive these reports, pursuant to regulations from the Secretary of Commerce.
  • Penalties for non-compliance

    Failing to meet these requirements can result in a civil penalty of up to $1,000,000 per violation, with each day of continued non-compliance counting as a separate violation. (Sec. 111(i)(1))

    ---

    This is a discussion draft dated 2026-06-02 and provisions may change. For questions about how these requirements apply to a specific organization, consult qualified legal counsel.

    What are the penalties for violating the transparency requirements?

    Under Sec. 111, a frontier developer that violates the transparency requirements can face significant civil penalties:

  • Up to $1,000,000 per violation
  • Each day a violation continues counts as a separate violation, meaning penalties can accumulate quickly
  • Who can bring an enforcement action:

  • The Attorney General can sue to collect civil penalties and seek an injunction to force compliance (Sec. 111).
  • State Attorneys General who have opted in under the State AG opt-in provision can also bring their own enforcement actions for the same penalties and injunctive relief (Sec. 111).
  • A few coordination rules apply when both federal and state actions are involved:

  • A State AG must give written notice to the Attorney General and the Director before filing, unless it's not feasible to do so (Sec. 111).
  • The Attorney General has the right to intervene in a State AG action after receiving notice (Sec. 111).
  • If the Attorney General has already filed an action, a State AG cannot file a separate action against the same defendants for the same violations while that action is pending (Sec. 111).
  • Similarly, under Sec. 112, large frontier developers that violate the audit and assessment requirements face the same $1,000,000-per-violation-per-day structure, with enforcement available through both the Attorney General and opted-in State Attorneys General.

    This is a discussion draft dated 2026-06-02 and provisions may change. For questions about how these penalties might apply to a specific situation, consult qualified legal counsel.

    What protections does the bill provide for AI whistleblowers?

    Section 113 of the discussion draft covers anti-retaliation protections for AI whistleblowers. Here is a plain-English summary of the key provisions:

    Who is protected

  • "Covered individuals" include current and former employees, as well as current and former independent contractors (Sec. 113(d)(5)).
  • What conduct is protected

    Employers cannot retaliate against a covered individual for:

  • Reporting an "AI violation" (any violation of federal law related to AI development, deployment, or operation) to a regulator, the Attorney General, law enforcement, or Congress (Sec. 113(a)(1))
  • Participating in or assisting an investigation or legal/administrative action related to such a report (Sec. 113(a)(2))
  • Reporting concerns internally to a supervisor or someone the individual reasonably believes can investigate or address misconduct (Sec. 113(a)(3))
  • What retaliation is prohibited

    Employers may not discharge, demote, suspend, threaten, blacklist, harass, or otherwise discriminate against a covered individual in their terms of employment or work (Sec. 113(a)).

    How someone can seek relief

    A covered individual can:

  • File a complaint with the Secretary of Labor, or
  • If the Secretary has not issued a final decision within 180 days (and the delay is not the individual's fault), bring a lawsuit in federal district court, with the right to a jury trial (Sec. 113(b)(1)-(2))
  • Time limits for lawsuits:

  • No more than 6 years after the violation occurred, or
  • No more than 3 years after the individual knew or reasonably should have known the material facts
  • In all cases, no more than 10 years after the violation (Sec. 113(b)(2)(B)(ii))
  • Remedies available if successful

  • Reinstatement with the same seniority
  • Two times back pay, with interest
  • Compensatory damages, litigation costs, expert witness fees, and reasonable attorneys' fees
  • Any other appropriate remedy (Sec. 113(b)(3))
  • Waivers are not allowed

    These rights cannot be signed away by any contract, employment agreement, or arbitration/mediation clause (Sec. 113(c)).

    ---

    This is a discussion draft dated 2026-06-02, so these provisions may change. For questions about how these rules might apply to a specific situation, consult qualified legal counsel.

    Does the Act regulate businesses that only use AI tools rather than develop them?

    This is a good question that touches on several parts of the draft. Here is what the relevant provisions say:

    Deployers are recognized and included in some programs

    The draft distinguishes between developers and deployers. Under Sec. 246, an "artificial intelligence deployer" is defined as "an entity (including a cloud service provider) that operates artificial intelligence for internal use or for use by a third party." This covers businesses that simply use AI tools without building them.

    Deployers are explicitly included in the voluntary data-sharing program under Sec. 246 — they can participate alongside developers in sharing anonymized workforce adoption data.

    Preemption focuses on development, not use

    Sec. 121 preempts state laws that specifically regulate AI *development*, but it explicitly carves out state laws "applicable to activities occurring upon or after the deployment" of an AI model — including laws governing "implementation, deployment, distribution, offering, or use." So state-level regulation of businesses that *use* AI tools is not preempted by this provision.

    Whistleblower protections are broad

    Sec. 113 defines "AI violation" as any violation of federal law related to the "development, deployment, or operation" of AI. The whistleblower protections would therefore potentially apply in contexts involving deployers and users of AI, not just developers.

    What the draft does not clearly do

    The context provided does not show a broad compliance framework (like mandatory reporting requirements or conduct rules) specifically imposed on businesses that only use AI tools. The Sec. 246 program is voluntary.

    ---

    Because whether any specific business has obligations under this draft depends heavily on its particular circumstances, consulting qualified legal counsel would be the appropriate next step for any compliance assessment.

    What does the bill do on AI and the workforce?

    Here is an overview of what the discussion draft does on AI and the workforce, based on the sections provided:

    Workforce Research Hub (Sec. 243)

  • The Department of Labor must establish an AI Workforce Research Hub within 90 days of enactment.
  • The Hub collaborates with the Bureau of the Census, Bureau of Economic Analysis, and Bureau of Labor Statistics.
  • It conducts research on how AI affects workers, produces recurring analyses, and does scenario planning to inform policy on training and unemployment.
  • Federal, private sector, and state/local employees can be detailed to the Hub.
  • The Hub sunsets 4 years after enactment.
  • Expert Hiring (Sec. 242)

  • The Secretary of Labor can appoint up to 20 highly qualified experts to work on AI labor market measurement, forecasting, and policymaking.
  • This appointment authority also expires 4 years after enactment unless extended by law.
  • Up to $6 million is authorized for fiscal years 2026–2030.
  • Federal Survey Updates (Sec. 247)

  • Within 1 year, the Census Bureau and Bureau of Labor Statistics must update key surveys (such as the Annual Business Survey and the American Time Use Survey) to add or improve questions about AI adoption and use.
  • The questions aim to capture things like which occupations are most affected, skill changes, and the intensity of AI use.
  • Data Standards (Sec. 248)

  • The Secretary of Labor leads a voluntary, consensus-driven effort to develop federal standards for collecting and reporting AI-related workforce data.
  • A report to Congress on data elements is due within 12 months.
  • Up to $3 million is authorized for fiscal years 2026–2030.
  • Policy Options Report (Sec. 257)

  • Within 18 months, the Hub must publish a public report assessing existing federal tools for handling workforce disruption, identifying gaps, and laying out policy options such as modernized unemployment insurance, portable benefits, wage insurance, and retraining support.
  • Adjustment Assistance Study (Sec. 255)

  • Within 12 months, the Secretary must fund a study on how a "Rapid AI Adjustment Assistance Program" could work for workers displaced by AI.
  • The study looks at eligibility criteria, program costs, compatibility with existing law, and collaboration with labor organizations and educational institutions.
  • Results must be published publicly within 2 years.
  • Up to $1 million is authorized for fiscal years 2026–2030.
  • Important note: This is a discussion draft dated 2026-06-02 and provisions may change. For questions about how these provisions apply to a specific situation, consult qualified legal counsel.

    What’s in the bill

    Title I — Frontier Artificial Intelligence Governance11 sec.Title II — Workforce22 sec.Title III — Cybersecurity3 sec.Title IV — Research, Development, And International9 sec.
    Section 1

    Short title; table of contents

    Establishes the short title of the bill as the Great American Artificial Intelligence Act and provides the table of contents.

    Title I — Frontier Artificial Intelligence Governance

    Sec. 101

    Definitions

    Subtitle A — Definitions and the Center for AI Standards and Innovation

    Defines key terms used throughout the Act, including acceptable levels of catastrophic risk mitigation, artificial intelligence, artificial intelligence models, catastrophic risk, critical safety incident, foundation model, frontier AI framework, frontier developer, frontier model, independent verification organization (IVO), large frontier developer, material modification, model weight, and substantial modification.

    Sec. 102

    Center for AI Standards and Innovation (CAISI)

    Subtitle A — Definitions and the Center for AI Standards and Innovation

    Formally establishes CAISI within the Department of Commerce, directed by a Secretary appointed Director. CAISI will develop voluntary guidelines, best practices, and standards for AI security (adversarial robustness, interpretability, supply chain threats, model tampering, etc.), evaluate AI systems and monitor AI progress, support synthetic content detection tools, and administer the IVO licensing regime. $100 million per year authorized for 2027-2029, with additional fee authority from IVOs and large frontier developers. Grants special authorities for CAISI to hire critical technical experts and fix their pay at levels above the GS scale.

    Sec. 111

    Transparency in Frontier Artificial Intelligence

    Subtitle B — Transparency, Independent Verification, and Whistleblower Protections

    Large frontier developers (>$500M in revenue) must write, implement, comply with, and publicly post a frontier AI framework covering risk thresholds and assessment procedures for catastrophic risk, model weight cybersecurity, and both internal and external deployment decisions. Before, or concurrently with, deploying any new frontier model, frontier developers must publish a report disclosing the release date, supported languages, output modalities, intended use, restrictions, risk assessments, and mitigation steps. Redactions are permitted to protect trade secrets, cybersecurity, public safety, or national security. Additionally, developers must file a report with CAISI within 15 days of a critical safety incident or within 24 hours if the incident poses an imminent risk of death or serious injury. State attorneys general may also opt to receive such reports. Violations can result in fines of up to $1M per day, and the federal and state AGs can seek injunctions.

    Sec. 112

    Independent Verification Organization (IVO) Audits and Assessments

    Subtitle B — Transparency, Independent Verification, and Whistleblower Protections

    CAISI licenses IVOs to audit large frontier developers' compliance with Secs. 111 and to assess whether developers' AI frameworks achieve acceptable levels of catastrophic risk mitigation. Licenses may be revoked for material failures of independence, obsolete methods, or non- compliance. Large frontier developers must retain a licensed IVO to verify compliance with their framework and to ensure the adequacy of the framework and procedures. These IVOs must be granted sufficient access to company materials, and report their audits to CAISI. IVOs are immune from claims of loss from an AI model they have audited. State AGs may opt into receiving all audit and assessment reports from IVOs. IVOs may refer violations of this section to the AG, or to state AGs who have opted into receiving such referrals.

    Sec. 113

    Anti-Retaliation Protection for AI Whistleblowers

    Subtitle B — Transparency, Independent Verification, and Whistleblower Protections

    Prohibits AI companies from discriminating or retaliating in any way against employees or independent contractors for lawfully reporting a violation of federal AI law. If violated, employees are entitled to reinstatement, two times back pay with interest, compensatory damages, litigation costs, and attorney's fees.

    Sec. 121

    Federalization of State Laws Regulating AI Model Development

    Subtitle C — Federalization and Federal Resources

    Preempts any state or local law or regulation specifically targeting the development of AI models. Expressly does not preempt laws of general applicability, common law remedies, or laws regulating AI use or deployment. Sunsets three years post-enactment.

    Sec. 122

    GAO Report on Regulatory Impediments to AI Innovation

    Subtitle C — Federalization and Federal Resources

    Requires the Comptroller General to submit a report identifying federal statutes and regulations that directly affect AI innovation or unduly burden AI infrastructure (including energy), evaluating federal AI adoption progress, and providing legislative and administrative recommendations.

    Sec. 123

    Resources for AI Model Documentation

    Subtitle C — Federalization and Federal Resources

    NIST must establish a pilot program to create a template for documenting AI models and associated data (covering model name, developer identity, release date, training data cutoff, supported languages, terms of service, etc.), with technical guidelines and objective performance metrics.

    Sec. 131

    Financial Crimes and Artificial Intelligence

    Subtitle D — AI Fraud Deterrence

    Amends the federal mail fraud, wire fraud, bank fraud, and money laundering statutes to increase maximum fines from $1 million to $2 million and increase penalties when AI is used.

    Sec. 132

    AI Impersonation of Federal Officials

    Subtitle D — AI Fraud Deterrence

    Adds penalties when AI is used to impersonate government officials.

    Sec. 141

    Preventing Censorship and Protecting Free Speech

    Subtitle E — Free Speech

    Directs the Secretary of Commerce to conduct a study examining how the government encourages or pressures AI companies with respect to content moderation or limiting of expression. The report must include recommendations for legislation providing individuals redress against unlawful government censorship of AI platforms, including transparency requirements and oversight mechanisms.

    Title II — Workforce

    Sec. 201

    AI Literacy Efforts of the AI Task Force

    Subtitle A — AI Education and Capacity Building

    Directs the NSF Director to support the National STEM Teacher Corps pilot and Computer Science for All programs, consistent with recommendations of the House AI Task Force.

    Sec. 211

    Preparing K-12 Educators and Students for an AI-Literate Future

    Subtitle A — AI Education and Capacity Building

    Authorizes NSF to make competitive grants to universities and nonprofits for research on AI literacy curriculum, educator professional development, and evaluation tools for K-12 AI literacy.

    Sec. 221

    Expanding Capacity in Artificial Intelligence Science

    Subtitle A — AI Education and Capacity Building

    Directs NSF to establish a grant program for institutions not among the top 100 in federal R&D expenditures to broaden participation in AI research, education, and workforce development.

    Sec. 231

    Scholarships and Fellowships in Artificial Intelligence

    Subtitle A — AI Education and Capacity Building

    Authorizes the NSF to award scholarships and fellowships for students in AI-related programs.

    Sec. 232

    Community College and Area Career and Technical Education Centers of AI

    Subtitle A — AI Education and Capacity Building

    Excellence. Directs NSF to designate up to 8 regionally diverse "Centers of AI Excellence" at community colleges and career technical education schools. Centers must integrate AI into teaching and workforce development, develop best practices, identify career pathways, and facilitate private sector partnerships.

    Sec. 233

    Awards for Research on Artificial Intelligence in Education

    Subtitle A — AI Education and Capacity Building

    Authorizes NSF to award grants to research AI teaching tools, materials, and integration into K-12 classrooms, with emphasis on low-income, rural, and Tribal student populations. Also establishes a Rural and Low-Income Areas AI Collaborative to create regional peer-support networks for educators.

    Sec. 234

    National STEM Teacher Corps

    Subtitle A — AI Education and Capacity Building

    Adds AI skills development to the National STEM Teacher Corps pilot program and directs consideration of developing AI best practices for high school teachers.

    Sec. 241

    Information Collection and Discussion

    Subtitle B — Labor Market Data and AI Workforce Research

    The Secretary of Labor must publish a request for public comment on implementing the Act's data collection, forecasting, and workforce tools. Additionally, the Secretary must convene an initial expert workshop; subsequent annual workshops are required. The workshop must include economists, AI technical experts, industry representatives, labor organizations, and government officials with diverse viewpoints, and must critically evaluate BLS assumptions about AI's workforce impact.

    Sec. 242

    Attracting Highly Qualified AI Experts

    Subtitle B — Labor Market Data and AI Workforce Research

    Authorizes the Secretary of Labor to appoint up to 20 AI experts to excepted service positions with GS-15 pay.

    Sec. 243

    Artificial Intelligence Workforce Research Hub

    Subtitle B — Labor Market Data and AI Workforce Research

    Requires the Secretary of Labor to establish an AI Workforce Research Hub, in collaboration with the Census Bureau, Bureau of Economic Analysis, and Bureau of Labor Statistics. The Hub conducts recurring analyses of AI's workforce impact, conducts scenario planning, and generates actionable policy insights.

    Sec. 244

    Modernizing Access to AI-Related Labor Market Data

    Subtitle B — Labor Market Data and AI Workforce Research

    Establishes a pilot program producing statistics on job-to-job worker flows for at least 15 AI-sensitive occupations designated by the Secretary of Labor.

    Sec. 245

    Support for Evaluation of AI Automation

    Subtitle B — Labor Market Data and AI Workforce Research

    NIST must launch at least one prize competition to develop reproducible benchmarks for measuring AI's ability to automate or augment tasks/occupations. NIST may also award companion grants for benchmark design and validation.

    Sec. 246

    Voluntary AI Adoption and Use Reporting

    Subtitle B — Labor Market Data and AI Workforce Research

    Requires BLS to establish a voluntary program for AI developers and deployers to share anonymized data on AI adoption in the workforce.

    Sec. 247

    AI Questions in Federal Surveys

    Subtitle B — Labor Market Data and AI Workforce Research

    Within one year, the Census Bureau and BLS must revise specified federal surveys (including the Annual Business Survey, Current Population Survey, Occupational Requirements Survey, and American Time Use Survey) to incorporate or improve questions on AI adoption and use, focusing on types of AI, occupational impacts, skill changes, and work outcomes.

    Sec. 248

    Data Elements and Production

    Subtitle B — Labor Market Data and AI Workforce Research

    Directs the Secretary of Labor to identify standardized data elements for workforce reporting under the Act, report to Congress within 12 months, and lead a voluntary consensus effort to develop federal (and state/local) standards for producing trusted AI-related data.

    Sec. 251

    WARN Act Disclosures for AI-Related Layoffs

    Subtitle C — Worker Protections and Adjustment Assistance

    Amends the Worker Adjustment and Retraining Notification (WARN) Act to require that whenever AI is a "substantial factor" in a qualifying mass layoff, employers' 60-day advance notices must include a statement specifying that AI contributed to the layoff, describing the type and usage of AI involved, estimating the percentage of job losses attributable to AI, and detailing any pre-layoff upskilling or retraining efforts.

    Sec. 252

    Detailed Employment Forecasts for AI-Sensitive Occupations

    Subtitle C — Worker Protections and Adjustment Assistance

    Requires the Secretary of Labor to designate at least 15 AI-sensitive occupations every two years and publish annual prediction-interval employment forecasts (2-, 4-, and 8-year horizons) for those occupations, covering the 20th-80th percentile range of projected employment. Forecasts must be accompanied by benchmark comparisons, transparency on methods and data gaps, and periodic accuracy evaluations. A public, machine-readable archive of all forecasts and scores must be maintained.

    Sec. 253

    Forecasting Prize Competition

    Subtitle C — Worker Protections and Adjustment Assistance

    Directs NSF to establish a recurring prize competition (every 6 months) for accurate short-horizon forecasts and informative rationales on AI labor-market questions (e.g., model benchmark performance, AI adoption rates, occupation- level employment changes).

    Sec. 254

    Report on Use of Research Tools in Grant Recipient Selection

    Subtitle C — Worker Protections and Adjustment Assistance

    Within 2 years, the Secretary of Labor must report to Congress on how AI-related data, benchmarks, and forecasts developed under the Act will be incorporated into selection and performance measurement criteria for WIOA grants, apprenticeship programs, and other Labor Department grant programs.

    Sec. 255

    Study on Rapid AI Adjustment Assistance Program

    Subtitle C — Worker Protections and Adjustment Assistance

    Within 12 months, the Secretary of Labor must complete a study (directly or by grant) examining design options for a Rapid AI Adjustment Assistance Program for workers displaced by AI, drawing on trade adjustment assistance precedents. The study must address eligibility determination, types of assistance, program costs, evidence collection, and interoperability with existing law.

    Sec. 256

    Update of State In-Demand Occupation Lists

    Subtitle C — Worker Protections and Adjustment Assistance

    For five years after enactment, states and local workforce boards receiving WIOA Title I-B funds must consider AI-related forecasts and data produced under Subtitle B when updating their in-demand industry and occupation lists. The Secretary must provide technical assistance.

    Sec. 257

    AI Workforce Policy Options Report

    Subtitle C — Worker Protections and Adjustment Assistance

    The AI Workforce Research Hub, in consultation with BLS, must publish a public report inventorying existing federal authorities for technology-driven workforce disruption, identifying gaps relative to AI disruption's pace, assessing economic and tax policy mechanisms (unemployment insurance, portable benefits, tax code provisions), and presenting a range of policy options drawn from domestic and international precedents.

    Title III — Cybersecurity

    Sec. 301

    Reauthorization of the Cybersecurity Act of 2015

    Extends the Cybersecurity Act of 2015 from 2025 to 2035, allowing cybersecurity information to be shared between companies without anti-trust concerns.

    Sec. 311

    Support for Designated Critical Open-Source Software Maintainers

    Authorizes CISA (in consultation with CAISI) to award grants to eligible maintainers of widely used, critical open-source software for security improvements (patching, maintenance, security audits). Large frontier developers must also provide AI model access to eligible maintainers for cybersecurity purposes.

    Sec. 321

    Report on Model Weight, Data Center, and Open-Source Security

    Requires GAO to report on: security protocols protecting AI model weights, whether existing protections are sufficient, and the security situation of the open-source software ecosystem (resource adequacy of maintainers, infrastructure stability, and supply chain vulnerability).

    Title IV — Research, Development, And International

    Sec. 401

    AI Testbed Program

    Subtitle A — Testbeds and Interagency Coordination

    The Secretary of Energy and the NIST Under Secretary, in coordination with NSF, must establish a testbed program to facilitate collaboration between National Labs, federal labs, NIST, NAIRR, and public and private sector entities for testing, evaluating, and assessing AI systems. Activities include developing automated and reproducible evaluations, prioritizing security vulnerability assessments, and organizing hackathons.

    Sec. 402

    Coordination, Reimbursement, and Savings Provisions

    Subtitle A — Testbeds and Interagency Coordination

    Requires the Secretary of Commerce to prevent duplication between Subtitle A activities and existing DOE and private sector work. National Lab resources used under the program must be provided on a reimbursable basis, unless waived by the Secretary of Commerce.

    Sec. 411

    International AI Standards Coalitions

    Subtitle B — International Cooperation

    Requires the Secretary of Energy and NIST Under Secretary to jointly lead federal engagement in international AI technical standards development and form coalitions with like-minded governments to promote private sector-led standards adoption, advocate for U.S.-developed AI standards internationally, counter foreign adversary influence, facilitate cross-border AI R&D collaboration, and share cybersecurity best practices. Criteria for coalition membership include high scientific and technological advancement and adherence to WTO-compatible standards principles. China is expressly excluded from coalition eligibility unless USTR certifies WTO compliance.

    Sec. 421

    Public Data for AI Systems

    Subtitle C — AI Research and Development

    Amends the NAII Act to direct OSTP to develop a prioritized list of federal data and datasets for public release to support AI training and evaluation, with a focus on publicly funded research data, data advancing novel AI systems in the public interest, and datasets unlikely to be created without federal investment.

    Sec. 422

    Federal Grand Challenges in Artificial Intelligence

    Subtitle C — AI Research and Development

    Amends the NAII Act to establish a prize competition program administered by OSTP for AI research and development challenges across priority areas, including chip design, AI interpretability and explainability, advanced manufacturing, border security, AI for science, cybersecurity, energy efficiency, and modernizing federal legacy code..

    Sec. 423

    National Artificial Intelligence Research Resource (NAIRR)

    Subtitle C — AI Research and Development

    Formally establishes the NAIRR in statute. NAIRR would procure and provide resources such as datasets, training programs, and computational resources for AI development. These would be available to researchers, institutions, government entities, and small private sector entities.

    Sec. 424

    Liquid Cooling Development and Scalability

    Subtitle C — AI Research and Development

    Requires GAO to conduct a comprehensive review of liquid cooling for AI data centers with input from an advisory committee of industry, national labs, and academic experts.

    Sec. 431

    Research Security

    Subtitle D — Research Security

    All activities under the Act must comply with the research security requirements of the Research and Development, Competition, and Innovation Act and the NDAA.

    Sec. 432

    Certifications and Audits of Temporary Fellows

    Subtitle D — Research Security

    Before any non-federal temporary fellow (contractor, consultant, or fellow) performs AI-related work for an agency, both the fellow and the agency head must sign a certification that the fellow will not perform inherently governmental functions.

    Source: Great American Artificial Intelligence Act, discussion draft (June 2, 2026), summarised section by section. Want to go deeper? Ask Insta about any provision →

    Operated by Site Factory LLC · ContentOS. Informational only, not legal advice.