MUTUNGAMIRIRO weSosaiti

Virginia HB 2094 Yakakwira-Risk AI Bhiri uye Veto Yayo

Virginia HB 2094 yakakurudzira zvisungo kune vamwe vagadziri nevashandisi vemahurongwa eAI ane ngozi huru, asi haana kuva mutemo.

Teerera kugwaro iriAI-yakarondedzerwa · ~3 min

Pa peji ino3 min verenga
  1. Pfupiso
  2. Kudzika Kwakadzika
  3. Kuitwa muNyika yeChokwadi
  4. The Future of Virginia HB 2094 High-Risk AI Bill and Its Veto
  5. Kuzvishandisa
  6. Ramba Uchiongorora
  7. Mibvunzo inowanzo bvunzwa

Pfupiso

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.

Kudzika Kwakadzika

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.

Kuitwa muNyika yeChokwadi

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.

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.

Kuzvishandisa

Nei zvichikosha

  • Ngozi uye kuchengeteka. Njodzi uye yemazuva ese AI kukuvadza zvese zvinoenderana nekuti ndiani anonzwisisa njodzi uye ndiani anogona kuita.
  • Sarudzo dzakajeka. Ruzhinji nehunyanzvi kuverenga nekunyora kunoumba kana mutemo wakasimba wekuchengetedza uchigoneka mune zvematongerwo enyika.
  • Kucheka kuburikidza nehype. Tsananguro dzakajeka dzinoderedza kubatwa nehype, lab PR, uye isina kujeka tsika theatre.

Chenjera

  • Kurapa njodzi iripo seSci-fi nepo kugona kunobatanidza.
  • Kuvhiringidza kuchengetedzwa kwechigadzirwa chepamusoro nekuenderana pasi pekuzvimiririra kwepamusoro.
  • Kusiya vateereri vasiri veChirungu uye vasiri nyanzvi vaine zvinyorwa zvemhando yakaderera chete.

Matanho anotevera

  1. Kuparadzana kwechigadzirwa kukuvadza, kushandisa zvisizvo, uye kurasikirwa-kwe-kudzora / kusarongeka njodzi.
  2. Bvunza kuti ndeupi humbowo hunogona kushandura maonero ako panguva uye kuomarara.
  3. Sarudzo yekutanga masosi uye kongiri evals pamusoro pezvikumbiro zvekushambadzira.
  4. Ziva imwe nzira yekuita: basa, mutemo, mari, kana hunyanzvi - kwete kuziva chete.

Ramba Uchiongorora

Tsamba yemahara

Tora iyo yemazuva ese AI pfupiso

Nhatu dzakasimbiswa dzeAI nyaya mangwanani ega ega pakati pevhiki, dzakanyorwa neChirungu chakajeka. Yemahara zvachose, hapana ads.

Imwe email zuva rega rega revhiki. Bvisa kunyoresa kamwe chete. Hatimbotengese kana kugovera kero yako.

Zviedze iwe pachako

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

Mhinduro yepakarepo pamhinduro yega yega, uye chitupa chinogovaniswa chine ID inobatika kana wapedza kosi.

Tanga mibvunzo

Tsigira dzidzo yemahara yeAI. AI Understanding ndeye 501(c)(3) isingabatsiri - hapana ads, hapana paywall, zvachose. Ita chipo

Mibvunzo inowanzo bvunzwa

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.