Societate GHID

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 minute de citit
  • Ultima actualizare
Pe această pagină3 minute de citit
  1. Prezentare generală
  2. Scufundare în profunzime
  3. Impact strategic
  4. The Future of Virginia HB 2094 High-Risk AI Bill and Its Veto
  5. Implementare în lumea reală
  6. Riscuri și balustrade
  7. Foaia de parcurs de implementare
  8. Continuați să explorați
  9. Întrebări frecvente

Prezentare generală

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.

Scufundare în profunzime

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.

Impact strategic

Risc și siguranță

Daunele catastrofale și cotidiene ale IA depind de cine înțelege riscurile și cine poate acționa.

Decizii mai clare

Educația publică și profesională influențează dacă o politică puternică de siguranță este posibilă din punct de vedere politic.

Tăierea hype-ului

Explicațiile clare reduc captarea de hype, PR de laborator și teatrul vag de etică.

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.

Implementare în lumea 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.

Riscuri și balustrade

  • Tratarea riscului existențial ca SF în timp ce capacitatea se agravează.

  • Confuză siguranța produsului de suprafață cu alinierea sub autonomie ridicată.

  • Lăsând audiențe non-engleze și neexperte doar surse de calitate scăzută.

Foaia de parcurs de implementare

  1. Separați riscurile de deteriorare a produsului, utilizare greșită și pierderea controlului / dezaliniere.

  2. Întrebați ce dovezi v-ar schimba punctul de vedere cu privire la termene și severitate.

  3. Preferați sursele primare și evaluările concrete față de afirmațiile de marketing.

  4. Identificați o singură cale de acțiune: carieră, politică, finanțare sau abilități - nu numai conștientizare.

Continuați să explorați

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.

Quiz Start

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

Întrebări frecvente

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.