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

California AB 2013 Training Data Transparency Law

California AB 2013 requires developers of covered generative AI systems and services to publish training-data documentation.

  • Đọ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 California AB 2013 Training Data Transparency Law
  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 initial posting deadline was January 1, 2026; developers must also post before each later public release or substantial modification in scope. The law creates transparency duties but does not decide whether particular training uses are lawful.

Lặn sâu

AB 2013, the Generative Artificial Intelligence Training Data Transparency Act, was enacted in 2024. It requires a developer of a covered generative AI system or service made publicly available to Californians for use to post training-data documentation on its website. The initial posting deadline was January 1, 2026. For a covered system released on or after January 1, 2022, documentation must also be posted before each later public release or substantial modification. The documentation includes a high-level summary of training datasets and information about their sources or owners, purpose, approximate number and types of data points, and collection period. It must address whether datasets include copyrighted, trademarked, patented, personal, or aggregate consumer information; whether they were purchased or licensed; how the developer cleaned or processed them; when they were first used; and whether synthetic data generation was used. The definition of developer includes parties that substantially modify a system for public use. AB 2013 requires dataset-level information, not publication of the raw training corpus or source code. A disclosure does not grant copyright permission, decide fair use, or replace privacy obligations. The act includes exceptions, including systems used solely for security and integrity, systems whose sole purpose is aircraft operation in the national airspace, and systems developed for national-security, military, or defense purposes that are made available only to a federal entity. Read each exception against its exact statutory conditions. Maintain a training-data inventory linked to model versions, fine-tuning runs, synthetic-data generation, and release dates. Assign an owner to prepare and update the public documentation, review sensitive claims, and preserve evidence of what was posted for each covered release. Describe uncertainty rather than inventing dataset provenance. Check the enacted text and current California code for definitions, exceptions, and amendments.

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 California AB 2013 Training Data Transparency Law

AB 2013 is operative on a fixed timeline, and implementation choices may be clarified through amendments, enforcement, or litigation. Data pipelines and model versions continue to change, making stale disclosures a practical risk. Developers should monitor official California sources, preserve the dated disclosure in release records, and reassess coverage after substantial model changes. Training-data transparency should be coordinated with privacy, copyright, and contractual review. Retain dated copies of posted documentation and link them to model release records. Recheck the official code after amendments.

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

A developer lists the sources or owners of training datasets and explains how the data were collected, processed, and used.

A model maker describes whether training included copyrighted, trademarked, or patented material, without claiming that disclosure settles permission questions.

A developer identifies whether personal information was included and whether synthetic data generation was used.

A system developed for national-security, military, or defense purposes is checked against the statutory condition that it be made available only to a federal entity.

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 California AB 2013 Training Data Transparency Law 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 California AB 2013 Training Data Transparency Law?

California AB 2013 requires developers of covered generative AI systems and services to publish training-data documentation. The initial posting deadline was January 1, 2026; developers must also post before each later public release or substantial modification in scope. The law creates transparency duties but does not decide whether particular training uses are lawful.

Which developer activity can bring a system within AB 2013?

The statute defines developer broadly to include designing, coding, producing, or substantially modifying a system or service for public use.

Which public documentation deadline does AB 2013 set?

The statute sets January 1, 2026 as the deadline for the required posting.

Which information belongs in the required documentation?

AB 2013 calls for documentation about datasets used in development, including source, collection, processing, and use information.

Does AB 2013 disclosure itself authorize use of copyrighted training material?

The transparency requirement does not resolve copyright permission or fair-use questions.

Which system date can be relevant to coverage?

The statute’s scope includes systems released or substantially modified on or after January 1, 2022.