HƯỚNG DẪN xã hội

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.

  • Đọc trong 3 phút
  • Cập nhật lần cuối
Trên trang nàyĐọc trong 3 phút
  1. Tổng quan
  2. Lặn sâu
  3. Tác động chiến lược
  4. The Future of Virginia HB 2094 High-Risk AI Bill and Its Veto
  5. Triển khai trong thế giới thực
  6. Rủi ro & lan can
  7. Lộ trình thực hiện
  8. Tiếp tục khám phá
  9. Câu hỏi thường gặp

Tổng quan

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.

Lặn sâu

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.

Tác động chiến lược

Rủi ro và an toàn

Những tác hại thảm khốc và thường ngày của AI đều phụ thuộc vào việc ai hiểu được rủi ro và ai có thể hành động.

Quyết định rõ ràng hơn

Kiến thức công cộng và chuyên môn định hình liệu chính sách an toàn mạnh mẽ có khả thi về mặt chính trị hay không.

Phá vỡ sự thổi phồng

Những lời giải thích rõ ràng làm giảm sự thu hút bởi sự cường điệu, PR trong phòng thí nghiệm và sân khấu đạo đức mơ hồ.

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.

Triển khai trong thế giới thực

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.

Rủi ro & lan can

  • Xử lý rủi ro hiện hữu như khoa học viễn tưởng trong khi khả năng lại phức tạp.

  • Nhầm lẫn giữa an toàn sản phẩm bề mặt với sự liên kết dưới quyền tự chủ cao.

  • Chỉ để lại những khán giả không phải người Anh và không có chuyên môn với những nguồn chất lượng thấp.

Lộ trình thực hiện

  1. Tách biệt các tác hại của sản phẩm, sử dụng sai và rủi ro mất kiểm soát/sai lệch.

  2. Hỏi bằng chứng nào sẽ thay đổi quan điểm của bạn về thời gian và mức độ nghiêm trọng.

  3. Ưu tiên các nguồn chính và đánh giá cụ thể hơn các tuyên bố tiếp thị.

  4. Xác định một lộ trình hành động: sự nghiệp, chính sách, nguồn tài trợ hoặc kỹ năng - không chỉ là nhận thức.

Tiếp tục khám phá

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.

Bắt đầu bài kiểm tra

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

Câu hỏi thường gặp

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.