CalCompute research Suggest reading Search ⌘K

↑ ↓ choose a page · Enter searches everything, with exact title matches first · kind:source and other filters work there · Esc closes

← wiki/sources
source

SB-53 Assembly Privacy analysis 2025-07-08

Online ↗

type
source
created
2026-10-15
updated
2026-10-20
tags
A, B, C, D, E, F, G, legislative, analysis
elements
A, B, C, D, E, F, G
origin
legislative
tier
primary
citable
yes
url
https://apcp.assembly.ca.gov/system/files/2025-07/sb-53-wiener-apcp-analysis_0.pdf
rehost
yes

Links to 1 · Referenced by 15

SB-53 Assembly Privacy analysis 2025-07-08

Citation

California State Assembly, Committee on Privacy and Consumer Protection (Rebecca Bauer-Kahan, Chair), analysis of SB 53 (Wiener) as amended July 8, 2025, for the hearing of July 16, 2025. Prepared by John Bennett. https://apcp.assembly.ca.gov/system/files/2025-07/sb-53-wiener-apcp-analysis_0.pdf. Wiki copy: raw/legislative/SB-53 Assembly Privacy analysis 2025-07-08.md. Read 2026-10-15.

They are lines 10-31, 105-132, 177, 180, 190, 194, 244-248, 288, 290, 506-507, 565-567 and 607 of a full transcription. [...] marks the cuts.

Bottom line

  • The committee’s summary of the bill (items 17 to 28) already matches the enacted § 11546.8 almost item for item.
  • The University of California is a registered supporter of SB 53.
  • Item 28 shortens subd. (k). It drops the words “or other measure”.

Background

The Assembly Committee on Privacy and Consumer Protection heard SB 53 on July 16, 2025. The bill’s subject then was “CalCompute: foundation models: whistleblowers”. The analysis compares the bill with SB 1047 (2024), which also had a CalCompute consortium.

Key claims

  • Items 17 to 27 restate § 11546.8 (a) to (j). The analysis calls the Government Operations Agency “GovOps”. The items cover the mission, University of California (UC) placement, the three parts of CalCompute and labor laws.
  • Item 28.

    28) Requires that CalCompute become operative only upon an appropriation.

  • SB 1047 comparison.

    The bill also would have established, within GovOps, a consortium tasked with developing a framework for a public cloud computing cluster, CalCompute, to support the safe development and deployment of AI.

  • Why CalCompute.

    This initiative responds to the fact that academic institutions currently lack sufficient computing power to conduct research at the scale of large developers. This creates a resource and research gap, where the academic institutions, typically responsible for studying the safe and effective use of new technologies, are unable to keep pace with advancements at the AI frontier.

  • International AI Safety Report. “The recently released International AI Safety Report, developed by nearly 100 internationally recognized experts from 30 countries led by Turing Award winner Yoshua Bengio, sets forth three general risk categories associated with frontier models: malicious use, malfunctions, and systemic risk.”
  • Systemic risks, from that report. “Such risks include labor market disruption, global AI research and development concentration, market concentration, single points of failure, environmental risks, privacy risks, and copyright infringement.”
  • Systemic risk. “Due to the high costs of developing AI systems, a small number of large technology companies dominate the frontier model market”.
  • Evaluator access (quoted in the analysis). The feedback highlighted “the immature third-party evaluation ecosystem, the lack of evaluation standards and broader measurement science, and the current barriers for evaluators to acquire access to the AI models and systems they evaluate.”
  • Industrial policy.

    Moreover, a core function of government, is to craft sound industrial policy that encourages the growth of new markets serving the public good when economic forces do not support that market.

  • UC placement. The committee writes: “The consortium must prioritize locating CalCompute within the University of California system.”
  • Support letter (quoted in the analysis). CalCompute is “a public cloud computing cluster for use by academics and startups in California”, which “mirrors a similar computing cluster that is already being established in New York state.” The letter says SB 53 “thoughtfully implements the recommendations of the Report”, meaning the Governor’s working group report.
  • Registered Support: University of California. The list of supporters under “REGISTERED SUPPORT / OPPOSITION” includes “University of California”. UC is a registered supporter of SB 53.

Evidence and method

The analysis summarizes the bill and gives the committee staff’s comments. The “resource and research gap” claim has no cited data in the excerpt. Footnote 33 and note 34 support the systemic risk paragraph, but the excerpt does not give them.

Limits

  • The excerpt does not show the “Proposed Amendments” the heading names.
  • “Must prioritize” is the committee’s paraphrase. Subd. (c) says “make reasonable efforts to ensure […] to the extent possible”.
  • The industrial policy passage is about AI auditing.
  • The excerpt shows “University of California” in the support list but not the rest of the list.
  • The file’s header says “Hearing Date: July 8, 2025”. The analysis itself says “Date of Hearing: July 16, 2025” and “As Amended July 8, 2025”.

⚠️ Contradiction: Item 28 says “Requires that CalCompute become operative only upon an appropriation.” Subd.

July 8 is the amendment date.

Source file: wiki/sources/SB-53 Assembly Privacy analysis 2025-07-08.md, updated 2026-10-20.

Suggest reading

Know a report, dataset or law that belongs here? Have a question the sources could answer? Send it to the consortium. A member reads every suggestion, and the Suggestions page shows what happened to it. Your name is never shown.

Send opens your own email program with the message filled in, to team@californiacompute.org. Nothing is sent until you send it there.