РУКОВОДСТВО ПО ОБЩЕСТВУ

Закон о прозрачности данных для обучения в Калифорнии AB 2013

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

Прослушайте это руководствоОзвучено ИИ · ~3 min

На этой странице3 минуты чтения
  1. Обзор
  2. Глубокое погружение
  3. Реальная реализация
  4. The Future of California AB 2013 Training Data Transparency Law
  5. Применение на практике
  6. Продолжайте исследовать
  7. Часто задаваемые вопросы

Обзор

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.

Глубокое погружение

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.

Реальная реализация

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.

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.

Применение на практике

Почему это важно

  • Риски и безопасность. Катастрофический и повседневный вред ИИ зависит от того, кто понимает риски и может действовать.
  • Более четкие решения. Общественная и профессиональная грамотность определяет, возможна ли с политической точки зрения сильная политика безопасности.
  • Пробивая шумиху. Четкие объяснения уменьшают влияние шумихи, лабораторного пиара и расплывчатого этического театра.

Следите за

  • Относитесь к экзистенциальному риску как к научной фантастике, в то время как возможности растут.
  • Сбивает с толку безопасность поверхности продукта и выравнивание при высокой автономности.
  • Оставляя неанглоязычную и неспециалистскую аудиторию только с некачественными источниками.

Следующие шаги

  1. Отдельные риски повреждения продукта, неправильного использования и потери контроля/перекоса.
  2. Спросите, какие доказательства могут изменить ваше мнение о сроках и серьезности.
  3. Предпочитайте первоисточники и конкретные оценки маркетинговым заявлениям.
  4. Определите один путь действий: карьера, политика, финансирование или навыки, а не только осведомленность.

Продолжайте исследовать

Бесплатная рассылка

Получайте ежедневный AI-обзор

Три проверенных AI-истории каждое утро буднего дня, написанные простым английским. Бесплатно навсегда, без рекламы.

Одно электронное письмо каждый будний день. Отписаться в один клик. Мы никогда не продаем и не передаем ваш адрес.

Проверьте себя

Take the California AB 2013 Training Data Transparency Law quiz

Мгновенная обратная связь по каждому ответу и общий сертификат с проверяемым идентификатором после прохождения курса.

Начать тест

Поддержите бесплатное образование в области искусственного интеллекта. AI Understanding — это некоммерческая организация 501(c)(3). Никакой рекламы и платного доступа. Сделать пожертвование

Часто задаваемые вопросы

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.

Продолжайте учиться

Связанные руководства

Другие руководства, выбранные по этой теме

Получите бесплатный AI-сертификатКороткий бесплатный курс и экзамен. Без стоимости, без карты. Около 2,5 часов.Начать бесплатно →