PRZEWODNIK Społeczny

Kalifornijska SB 53 i przejrzystość Frontier AI

California SB 53, the Transparency in Frontier Artificial Intelligence Act signed in September 2025, applies to developers of the most computationally intensive AI models.

Posłuchaj tego przewodnikaOpowiadane przez sztuczną inteligencję · ~3 min

Na tej stronie4 minuty czytania
  1. Przegląd
  2. Głębokie nurkowanie
  3. Implementacja w świecie rzeczywistym
  4. The Future of California SB 53 and Frontier AI Transparency
  5. Wdrażanie tego w praktykę
  6. Odkrywaj dalej
  7. Często zadawane pytania

Przegląd

It requires them to publish safety frameworks and transparency reports, report critical safety incidents to the state, and protects whistleblowers who raise catastrophic risk concerns. It matters because it is one of the first US laws aimed specifically at frontier model developers, and it replaced the liability-focused approach of the vetoed SB 1047 with required disclosure.

Głębokie nurkowanie

SB 53 defines a frontier model as a foundation model trained with more than 10^26 integer or floating-point operations, including compute from later fine-tuning or modification. Any developer that has trained such a model is a frontier developer and must publish a transparency report when it deploys a new or substantially modified frontier model. A large frontier developer, one with more than $500 million in annual revenue, must also publish and annually review a frontier AI framework, include summaries of catastrophic risk assessments in its transparency reports, and periodically send the Office of Emergency Services (OES) summaries of assessments of catastrophic risk from internal use of its models. Catastrophic risk means a foreseeable and material risk that a model contributes to the death or serious injury of more than 50 people, or more than $1 billion in damage, in a single incident. The risk must arise through expert-level help with chemical, biological, radiological or nuclear weapons; a cyberattack or serious crime carried out without meaningful human oversight; or the model evading its developer's control. Critical safety incidents include unauthorized access to model weights, harm from a materialized catastrophic risk, and loss of control. Developers may not make materially false or misleading statements about catastrophic risk. The Attorney General enforces the law with civil penalties of up to $1 million per violation. SB 53 also creates a consortium to design CalCompute, a public computing cluster. The law followed SB 1047, also by Senator Scott Wiener, which would have required pre-deployment safety testing, shutdown capability and liability for critical harms. Governor Newsom vetoed it in September 2024 and convened an expert group whose June 2025 report favored transparency with verification. SB 53 does not require licensing, pre-approval or a kill switch.

Implementacja w świecie rzeczywistym

A large frontier developer with more than $500 million in annual revenue must publish a frontier AI framework on its website. The framework explains how the company assesses and mitigates catastrophic risks, including whether it uses third-party evaluators.

When a developer releases a new frontier model, it must publish a transparency report covering the model's intended uses and restrictions. Large developers must also summarize their catastrophic risk assessments in that report.

A developer that discovers its unreleased model weights were stolen must report the critical safety incident to California's Office of Emergency Services within 15 days. If the incident poses an imminent risk of death or serious injury, the deadline is 24 hours.

An employee who believes their company is misrepresenting catastrophic risk can report it to the Attorney General or other authorities and is protected from retaliation. Large developers must also provide an anonymous internal reporting channel.

The Future of California SB 53 and Frontier AI Transparency

Most obligations took effect on January 1, 2026, so there is little enforcement history yet. Open questions include how OES will handle incident reports and how actively the Attorney General will pursue penalties. The law directs state officials to review its definitions and thresholds over time, because a fixed compute threshold may become outdated as training becomes more efficient. The biggest uncertainty is federal policy: efforts in Congress and from the White House to preempt or challenge state AI laws have left the relationship unsettled. Other states, including New York, have pursued similar frontier-model transparency legislation.

Wdrażanie tego w praktykę

Dlaczego to ma znaczenie

  • Ryzyko i bezpieczeństwo. Zarówno katastrofalne, jak i codzienne szkody spowodowane sztuczną inteligencją zależą od tego, kto rozumie ryzyko i kto może podjąć działania.
  • Jaśniejsze decyzje. Umiejętność korzystania z usług publicznych i zawodowych wpływa na to, czy silna polityka bezpieczeństwa jest politycznie możliwa.
  • Przebijanie się przez szum. Jasne wyjaśnienia ograniczają wpływ szumu, PR laboratoryjnego i niejasnego teatru etycznego.

Uważaj na

  • Traktowanie ryzyka egzystencjalnego jako science-fiction, choć łączy w sobie możliwości.
  • Mylenie bezpieczeństwa produktów powierzchniowych z wyrównaniem przy dużej autonomii.
  • Pozostawienie odbiorcom nieanglojęzycznym i nieeksperckim jedynie źródeł o niskiej jakości.

Kolejne kroki

  1. Oddziel ryzyko szkód, niewłaściwego użycia i utraty kontroli/niewspółosiowości produktu.
  2. Zapytaj, jakie dowody zmieniłyby Twój pogląd na temat terminów i dotkliwości.
  3. Przedkładaj źródła pierwotne i konkretne oceny nad twierdzenia marketingowe.
  4. Zidentyfikuj jedną ścieżkę działania: karierę, politykę, finansowanie lub umiejętności – nie tylko świadomość.

Odkrywaj dalej

Darmowy newsletter

Otrzymuj codzienne podsumowanie AI

Trzy zweryfikowane historie AI każdego poranka w dni robocze, napisane prostym angielskim. Bezpłatne na zawsze, bez reklam.

Jedno e‑mail każdego dnia roboczego. Wypisz się jednym kliknięciem. Nigdy nie sprzedajemy ani nie udostępniamy Twojego adresu.

Sprawdź się

Take the California SB 53 and Frontier AI Transparency quiz

Natychmiastowa informacja zwrotna na każde pytanie oraz udostępnialny certyfikat z weryfikowalnym ID po zaliczeniu kursu.

Rozpocznij quiz

Wspieraj darmową edukację AI. AI Understanding jest organizacją non-profit 501(c)(3) — bez reklam, bez płatnej ściany, zawsze. Przekaż darowiznę

Często zadawane pytania

What is California SB 53 and Frontier AI Transparency?

California SB 53, the Transparency in Frontier Artificial Intelligence Act signed in September 2025, applies to developers of the most computationally intensive AI models. It requires them to publish safety frameworks and transparency reports, report critical safety incidents to the state, and protects whistleblowers who raise catastrophic risk concerns. It matters because it is one of the first US laws aimed specifically at frontier model developers, and it replaced the liability-focused approach of the vetoed SB 1047 with required disclosure.

What training compute threshold defines a frontier model under SB 53?

SB 53 defines a frontier model as one trained with more than 10^26 integer or floating-point operations, counting compute used in later fine-tuning or modification.

What annual revenue makes a frontier developer a large frontier developer?

Developers with more than $500 million in annual revenue count as large frontier developers. They must publish a frontier AI framework and meet additional reporting duties.

What is the standard deadline for reporting a critical safety incident to the state?

Developers generally must report critical safety incidents to the Office of Emergency Services within 15 days. A shorter deadline applies when there is imminent danger.

How quickly must an incident be reported if it poses an imminent risk of death or serious injury?

If an incident poses an imminent risk of death or serious injury, the developer must notify an appropriate authority within 24 hours.

Which of these does SB 53 NOT require?

SB 53 relies on disclosure, incident reporting and whistleblower protection. It does not require licensing, pre-approval or a kill switch. Shutdown capability was part of the vetoed SB 1047.