Congressional AI Governance Watch

Pending federal legislation — proposed, not binding.

Last updated: September 9, 2026

Pending federal legislation affecting AI assurance, documentation, testing, accountability, and human oversight.

Legal status: Proposed — not binding. Every congressional item on this page remains subject to amendment, delay, consolidation, or failure to enact. Introduction, sponsorship, a hearing, or committee approval does not make a bill law.

Congress is developing federal approaches to AI standards, testing infrastructure, system documentation, incident reporting, professional competence, product liability, consumer protection, and human-centered oversight. Even before enactment, measures with bipartisan sponsorship or committee approval can reveal the evidence, capabilities, and institutional expectations likely to shape future procurement, standards, and regulation.

AI Govern Consulting LLC helps organizations monitor these signals without treating proposals as current obligations. Our readiness work is grounded in Governance Beta™, a proprietary AI decision-intelligence and governance framework derived from Dr. Damon Dade's doctoral research. Governance Beta™ emphasizes human-in-the-loop decision assurance, stakeholder values, fairness, transparency, accountability, trust, documentation, and defensible human judgment.

What qualifies for this watch

We include congressional activity only when it is materially relevant to AI governance and has a meaningful signal such as:

  • bipartisan introduction or reintroduction;
  • committee or subcommittee markup;
  • favorable committee reporting;
  • passage by either chamber;
  • incorporation into an authorization, appropriations, or other moving legislative vehicle; or
  • a proposal that would materially change liability, documentation, audit, testing, human-review, or evidence expectations.

We do not treat routine statements, hearings without legislative text, duplicative proposals, or sponsorship changes as stand-alone material developments.

How to read legislative status

How to read legislative status
StatusWhat it meansWhat it does not mean
IntroducedA bill has been formally submitted and referredIt has not been approved by a committee or chamber
Committee-approvedA committee favorably reported or advanced a billIt has not passed the House or Senate
Chamber-passedOne chamber approved the measureIt is not law unless both chambers pass identical text and the President signs it or a veto is overridden
EnactedThe measure completed the constitutional processOnly enacted text creates statutory obligations
Proposed — not binding

Priority congressional developments

Proposed — committee-approved, not law

House Science Committee advances an AI trust-and-assurance package

Status:
Proposed legislation; favorably reported by the House Committee on Science, Space, and Technology
Committee action:
June 25, 2026
Next procedural threshold:
House floor consideration; Senate action would also be required

The committee advanced a bipartisan group of bills that, taken together, would strengthen the federal infrastructure around AI documentation, evaluation, security, incident learning, workforce competence, data quality, and content provenance. They do not currently impose private-sector compliance duties, and several would establish voluntary programs or federal research functions.

H.R. 6461 — READ AI Models Act

Proposed — not binding

The Resources for Evaluating and Documenting AI Models Act would direct NIST to create a pilot program for voluntary model-documentation resources, including standardized templates and technical guidance.

Governance significance: Standardized documentation can influence vendor due diligence, procurement, assessment criteria, and the minimum evidence expected to support claims about model development, evaluation, deployment, capabilities, and limits.

Readiness actions: Compare present model cards, system cards, technical files, data statements, and change records with a common evidence architecture. Ensure documentation reflects the deployed context and does not stop at the base model.

H.R. 9333 — AI Flaw Reporting and Security Enhancement Act

Proposed — not binding

The bill would direct NIST, with the Cybersecurity and Infrastructure Security Agency, to establish a voluntary program for reporting and tracking AI vulnerabilities, failures, and other flaws, supported by common definitions, reporting frameworks, technical standards, and a national database.

Governance significance: The proposal signals movement toward a shared AI-incident vocabulary and a stronger expectation that organizations detect, classify, retain, analyze, and learn from failures.

Readiness actions: Define reportable AI events; integrate AI incidents with security, privacy, safety, compliance, and enterprise-risk processes; protect evidence; assign external-reporting authority; and test escalation timelines.

H.R. 9334 — Workforce for AI Trust Act

Proposed — not binding

The bill would support interdisciplinary fellowships and skills-based training for people who build, evaluate, and govern trustworthy AI. It would also direct NIST to develop a national framework identifying AI-related tasks, knowledge, and skills. The committee adopted language supporting independent AI testing and evaluation.

Governance significance: Effective assurance depends on demonstrable competence, not job titles alone. A national skills framework could become an important reference for audit teams, procurement qualifications, training programs, and future conformity-assessment capacity.

Readiness actions: Create role-specific competence profiles; maintain education and experience records; evaluate technical and domain expertise; establish continuing-development requirements; and document when specialist support is required.

H.R. 9363 — AI Security and Innovation Act

Proposed — not binding

The bill would strengthen federal coordination around AI risk, security, resilience, and innovation. Committee amendments added work on agentic-AI standards, explainability and interpretability research, and assessment of autonomous-AI research trends.

Governance significance: Agentic and autonomous systems challenge conventional approval boundaries because systems may plan, call tools, act, and adapt. Assurance must examine permissions, delegation limits, monitoring, intervention, and the attribution of responsibility.

Readiness actions: Inventory agentic functionality; define bounded authority; implement approval gates and least privilege; log actions and tool calls; establish human intervention points; and test containment and recovery.

H.R. 8893 — Protecting Consumers from Deceptive AI Act

Proposed — not binding

The bill would direct NIST to support research, testing, and standards for detecting, authenticating, and disclosing the origin of AI-generated or manipulated digital content.

Governance significance: Provenance and authenticity controls affect public trust, marketing claims, records integrity, fraud prevention, and the reliability of evidence used in organizational decisions.

Readiness actions: Establish content-origin policies, provenance metadata, disclosure rules, authentication processes, exception handling, and controls over synthetic evidence used in consequential decisions.

Other committee-approved infrastructure bills

The committee also advanced the AI-Ready Federal Data Guidelines Act, CREATE AI Act, and Data Center Energy Measurement and Standards Act. These proposals focus on federal data preparation, access to AI research resources, and standardized infrastructure metrics. They are less likely to create near-term private-sector governance duties but may shape public datasets, evaluation capacity, environmental metrics, and federal procurement expectations.

Governance Beta™ integration

This legislative package addresses much of the technical and institutional infrastructure surrounding assurance. Governance Beta™ provides the complementary decision layer: why a use was approved, whose interests were considered, what evidence decision-makers relied on, who can challenge or override the system, and how leadership accepts and monitors residual risk.

Proposed — bipartisan reintroduction, not law

Senate reintroduces the Future of AI Innovation Act

Status:
Proposed legislation; bipartisan reintroduction
Announcement:
February 26, 2026
Sponsors identified by the Senate Commerce Committee:
Senators Maria Cantwell, Todd Young, John Hickenlooper, and Marsha Blackburn

What the bill would do

The Future of AI Innovation Act would authorize the Center for AI Standards and Innovation at NIST, support voluntary AI standards, benchmarks, evaluations, transparency documentation, national-laboratory testbeds, public datasets, research partnerships, and international standards cooperation.

Who may be affected if enacted

The immediate duties would principally concern federal agencies and programs. AI developers, evaluators, research institutions, national laboratories, government vendors, and organizations using NIST resources could be affected through participation, procurement, funding, and evolving market expectations.

Assurance and market implications

  • NIST-backed benchmarks and testbeds could become reference points for product claims and purchaser due diligence.
  • Transparency-documentation work could increase expectations for complete, comparable, and technically supportable system records.
  • Public-private testbeds may create opportunities for evaluation-method development and specialized assurance services.
  • International standards coordination could influence future conformity-assessment and market-access expectations.

Governance Beta™ integration

Governance Beta™ can connect benchmark and evaluation results to human decisions: whether the evidence is relevant to the intended context, which stakeholders bear residual risk, who has authority to accept that risk, and what monitoring or intervention is required after deployment.

Recommended near-term actions: Monitor committee action; map products to emerging NIST documentation and testing concepts; document benchmark relevance and limits; and develop clear boundaries between consulting, management decision-making, testing, and independent assurance.
Proposed — not binding

AI LEAD Act proposes federal liability rules for AI developers and deployers

Status:
Proposed legislation; not binding
Sponsors identified in Senate Judiciary materials:
Senators Dick Durbin and Josh Hawley

What the bill would do

The Aligning Incentives for Leadership, Excellence, and Advancement in Development Act would establish potential developer liability for defective design, failure to warn, express-warranty violations, and unreasonably dangerous or defective AI products. A deployer could be treated as a developer when it substantially modifies or intentionally misuses a system. The proposal would also restrict certain contractual liability limitations, create federal enforcement and civil-action mechanisms, and require foreign AI developers to designate a U.S. agent for service of process.

Who may be affected if enacted

AI developers, deployers, vendors, enterprise purchasers, insurers, foreign developers serving the U.S. market, and consumers could be affected. Allocation of developer and deployer roles — and evidence of modification, intended use, warning, and misuse — would become especially important.

Assurance and governance implications

  • Preserve design choices, known-risk analyses, test results, limitations, warnings, version history, and post-market monitoring.
  • Define intended use and foreseeable misuse with enough specificity to support training, configuration, and contracting.
  • Establish change-control evidence that distinguishes vendor updates from deployer modifications.
  • Align warranties and performance claims with validated evidence.
  • Review indemnification, audit rights, incident cooperation, document access, and insurance with counsel.

Governance Beta™ integration

Governance Beta™ supports an evidence trail showing how organizational decision-makers evaluated warnings, limitations, stakeholder risks, modifications, and residual risk before approving use. It does not determine legal liability, but it can strengthen the defensibility of the underlying human decision process.

Recommended near-term actions: Conduct a developer/deployer role analysis; strengthen technical-file retention; link product claims to test evidence; review modification controls; and identify liability-related evidence that must be obtainable from vendors.
Proposed — not binding

GUARD Act proposal targets chatbot and AI-companion risks to minors

Status:
Proposed legislation; Senate substitute text for S. 3062; not binding
Current text:
119th Congress, second session (2026)

What the proposal would do

The Guidelines for User Age-verification and Responsible Dialogue Act of 2026 would establish age-verification, disclosure, data-security, and minor-access restrictions for covered AI chatbots and AI companions. The proposal includes civil and criminal enforcement provisions, disclosure that a chatbot is not human, restrictions on professional-status representations, safeguards for age-verification data, and limits on minors' access to AI companions.

Who may be affected if enacted

Entities making covered AI chatbots or companions publicly available to consumers, their age-verification vendors, product teams, safety teams, and governance leaders could be affected. Coverage would depend on the final definitions and enacted text.

Assurance and governance implications

  • Validate age-assurance processes and minimize collection and retention of identity data.
  • Test non-human and non-professional disclosures for clarity, timing, consistency, and accessibility.
  • Define safety metrics for harmful content, self-harm escalation, evasion, and repeated interactions.
  • Evaluate third-party age-verification controls and prohibit unsupported reliance on vendor assurances.
  • Preserve test protocols, red-team results, incidents, mitigation decisions, and management approvals.

Governance Beta™ integration

The proposal makes the quality of human governance around conversational systems especially important: stakeholder vulnerability, safety thresholds, escalation authority, evidence for risk acceptance, and the point at which leaders must restrict or discontinue a feature.

Recommended near-term actions: Inventory public conversational systems; identify companion-like features; conduct a minors-and-vulnerable-users risk assessment; test disclosures and safety controls; and establish evidence-ready escalation and shutdown processes.
Proposed — bipartisan introduction, not law

Human Dignity and Emerging Technologies Act proposes a congressional advisory commission

Status:
Proposed legislation; bipartisan introduction
Announcement:
July 23, 2026
Sponsors identified by the Senate Commerce Committee:
Senators Ted Cruz and Raphael Warnock

What the bill would do

The bill would create a non-regulatory U.S. Commission on Human Dignity within the legislative branch to study the ethical and policy implications of emerging technologies, hold hearings, issue reports, and provide advisory opinions, with particular attention to AI and bioethics.

Why it matters

The proposal would not itself impose audit or compliance requirements. If enacted, however, the commission's work could influence later legislation and increase attention to stakeholder values, human autonomy, vulnerable populations, and the limits of technology-mediated judgment.

Governance Beta™ integration

The proposal aligns with Governance Beta™'s premise that AI governance cannot be reduced to technical performance. Defensible decisions require explicit consideration of human values, affected stakeholders, fairness, autonomy, accountability, and the quality of human judgment.

Recommended near-term actions: Add human-dignity and autonomy questions to impact assessments; document vulnerable-stakeholder considerations; and monitor any commission mandate, membership, reports, or advisory opinions if the bill advances.
Watchlist

Next signals that matter

The following events warrant an update to this page:

  1. 1A committee files a report or advances amended text.
  2. 2The House or Senate schedules floor consideration or passes a measure.
  3. 3Related bills are consolidated into a larger AI package.
  4. 4AI provisions enter an authorization, appropriations, reconciliation, or other must-pass vehicle.
  5. 5The chambers adopt different approaches to federal preemption of state AI laws.
  6. 6Final text introduces mandatory audits, impact assessments, incident reporting, documentation, human review, licensing, certification, or independent-evaluator requirements.
  7. 7A measure is enacted, at which point it should move from this proposed-legislation page to the main Regulatory Watch.
Readiness

What organizations should prepare now

The proposals differ, but their recurring signals support a common readiness program:

Congressional signals and the capabilities they imply
Congressional signalPractical capability to build nowGovernance Beta™ contribution
Model and system documentationControlled technical files, versioning, provenance, limitations, approvalsLinks evidence to accountable decisions
Testing and benchmarksContext-relevant evaluation, subgroup analysis, test independence, monitoringTests whether results support a defensible judgment
Flaw and incident reportingTaxonomy, detection, retention, escalation, corrective actionClarifies decision authority and stakeholder response
Workforce competenceRole profiles, training, experience, specialist support, quality reviewDefines competence for meaningful human oversight
Developer/deployer liabilityIntended-use controls, warnings, modification evidence, vendor rightsDocuments reasoned acceptance and accountability
Child and chatbot safetyAge assurance, disclosures, safeguards, red teaming, shutdown criteriaCenters vulnerable stakeholders and human responsibility
Standards and testbedsCriteria mapping, evidence reuse, participation strategyConnects technical standards to organizational values and decisions
Engagements

How AI Govern Consulting can help

Congressional AI Readiness Briefing

Executive analysis of material proposals, likely operational impacts, uncertainty, and decision points.

Governance Beta™ Decision-Assurance Review

Evaluation of human authority, stakeholder considerations, evidence, override, escalation, and defensibility for a consequential AI use.

Evidence Architecture and Documentation Readiness

Preparation for emerging model-documentation, incident-reporting, testing, and procurement expectations.

AI Assurance Workforce and Independence Roadmap

Role competencies, qualification records, assessor independence, conflict management, and quality-review design.

Legislative Scenario Assessment

A requirements crosswalk showing how priority proposals could affect products, services, contracts, controls, and certification strategy if enacted.

Prepare for the direction of travel without treating proposals as law.

Contact AI Govern Consulting LLC for a Congressional AI Readiness Briefing or Governance Beta™ decision-assurance consultation.

Important notice

This Congressional AI Governance Watch is provided for general educational and informational purposes. It is not legal advice, lobbying advice, or a prediction that any bill will become law. Legislative text and status can change quickly. Organizations should verify current status through official congressional sources and consult qualified legal counsel before making legal or compliance decisions.

AI Govern Consulting LLC does not represent that it is government approved, certified, accredited, or designated as an auditor, Independent Verification Organization, certification body, or conformity-assessment body. No assessment or consulting engagement guarantees legal compliance, prevents enforcement, eliminates liability, or assures any particular business outcome.

Governance Beta™ and related methodology, intellectual property, licensing rights, and future certification rights are owned by The Dade Companies LLC. AI Govern Consulting LLC is the commercial subsidiary delivering consulting, training, readiness assessments, independent-assurance preparation, and related services.

Editorial note: This page tracks material congressional developments separately from binding requirements. An item is removed, reclassified, or transferred to the main Regulatory Watch when its status materially changes.