GUIA DA SOCIEDADE

Virginia HB 2094 High-Risk AI Bill and Its Veto

Virginia HB 2094 proposed obligations for certain developers and deployers of high-risk artificial intelligence systems, but it did not become law.

  • 3 minutos de leitura
  • Última atualização
Nesta página3 minutos de leitura
  1. Visão geral
  2. Mergulho profundo
  3. Impacto Estratégico
  4. The Future of Virginia HB 2094 High-Risk AI Bill and Its Veto
  5. Implementação no mundo real
  6. Riscos e guarda-corpos
  7. Roteiro de implementação
  8. Continue explorando
  9. Perguntas frequentes

Visão geral

The governor vetoed the enrolled bill in March 2025, and the House sustained the veto in April, so its proposed July 2026 effective date never took effect.

Mergulho profundo

House Bill 2094 was introduced in Virginia’s 2025 Regular Session as a proposed risk-based framework for certain high-risk artificial intelligence systems. Its enrolled text would have defined covered developers and deployers and imposed responsibilities including risk management, impact assessment, notice and documentation, with civil enforcement by the Attorney General. Those provisions describe a proposal, not a present duty. The bill passed both chambers in amended form. The House concurred in the Senate substitute on February 20, 2025. Governor Glenn Youngkin vetoed it on March 24, 2025. The House voted to sustain the veto on April 2, 2025; the constitutionally required override therefore did not occur. Virginia’s Constitution requires a two-thirds vote of members present in each chamber to pass a vetoed bill over the governor’s objections. The bill did not become an act. The enrolled text listed July 1, 2026 as its proposed effective date, but that date has no operative effect because the bill was vetoed and the veto sustained. The governor’s veto statement described the bill as a burdensome framework that could impede growth, stifle industry and burden smaller businesses. That is the executive’s policy explanation, not a judicial interpretation or a finding that every proposed requirement was unlawful. As of September 26, 2026, organizations should not cite HB 2094 as enacted law. They should distinguish this failed proposal from any separately enacted Virginia laws or generally applicable federal requirements.

Impacto Estratégico

Risco e segurança

Os danos catastróficos e diários da IA ​​dependem de quem entende os riscos e de quem pode agir.

Decisões mais claras

A literacia pública e profissional determina se uma política de segurança forte é politicamente possível.

Cortando o hype

Explicações claras reduzem a captura por exageros, relações públicas de laboratório e teatro de ética vaga.

The Future of Virginia HB 2094 High-Risk AI Bill and Its Veto

The 2025 veto is final for this bill. Future Virginia legislation could adopt similar or different provisions, so teams monitoring state AI policy should check new session bills and enacted chapter records rather than reusing HB 2094 summaries as current law. Maintain a dated record of the official source checked, the relevant section and any operational interpretation. When facts change, update policies and training materials together so staff do not rely on a stale summary or treat a proposed measure as an effective legal requirement.

Implementação no mundo real

A Virginia deployer should not treat HB 2094’s proposed impact-assessment duties as current law solely because they appeared in an enrolled bill.

A legislative analyst records the House and Senate passage separately from the later gubernatorial veto and failed override.

A compliance team continues to apply other current privacy, civil-rights and sector rules that independently govern its system.

A policy memo labels the governor’s concerns as a stated policy rationale, not a court finding about the bill’s legal validity.

Riscos e guarda-corpos

  • Tratar o risco existencial como ficção científica enquanto aumenta a capacidade.

  • Confundir segurança do produto de superfície com alinhamento sob alta autonomia.

  • Deixando o público não-inglês e não especializado com apenas fontes de baixa qualidade.

Roteiro de implementação

  1. Separe os riscos de danos ao produto, uso indevido e perda de controle/desalinhamento.

  2. Pergunte quais evidências mudariam sua visão sobre prazos e gravidade.

  3. Prefira fontes primárias e avaliações concretas em vez de afirmações de marketing.

  4. Identifique um caminho de ação: carreira, política, financiamento ou habilidades – não apenas conscientização.

Continue explorando

Free newsletter

Get the daily AI briefing

Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.

One email each weekday. Unsubscribe in one click. We never sell or share your address.

Test yourself

Take the Virginia HB 2094 High-Risk AI Bill and Its Veto quiz

Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.

Iniciar teste

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

Perguntas frequentes

What is Virginia HB 2094 High-Risk AI Bill and Its Veto?

Virginia HB 2094 proposed obligations for certain developers and deployers of high-risk artificial intelligence systems, but it did not become law. The governor vetoed the enrolled bill in March 2025, and the House sustained the veto in April, so its proposed July 2026 effective date never took effect.

Which final action determined HB 2094’s legal status?

The governor vetoed HB2094 and the House sustained that veto, so it was not enacted.

What happened to the bill on March 24, 2025?

The official veto report records the governor’s veto on March 24, 2025.

What did the House do on April 2, 2025?

The House voted to sustain the veto, meaning the bill did not pass over the governor’s objections.

How should HB 2094’s listed July 1, 2026 date be treated?

Because the veto was sustained, the bill’s proposed effective date never became operative.

Which description best captures the bill’s proposed coverage?

The enrolled proposal set duties for certain developers and deployers of high-risk systems.