Sign up to save your podcasts
Or
Share “Attaching requirements to model releases has serious downsides (relative to a different deadline for these requirements)” by ryan_greenblatt
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
“Attaching requirements to model releases has serious downsides (relative to a different deadline for these requirements)” by ryan_greenblatt
Here's a relatively important question regarding transparency requirements for AI companies: At which points in time should AI companies be required to disclose information? (While I focus on transparency, this question is also applicable to other safety-relevant requirements, and is applicable to norms around voluntary actions rather than requirements.)
A natural option would be to attach transparency requirements to the existing processes of pre-deployment testing and releasing a model card when a new model is released. As in, companies would be required to include the relevant information whenever they release a new model (likely in the model card). This is convenient because pre-deployment testing and model cards are already established norms in the AI industry, which makes it easier to attach something new to these existing processes rather than creating a new process.
However, I think attaching requirements to model releases (such that the requirement must happen [...]
The original text contained 5 footnotes which were omitted from this narration.
---
First published:
August 27th, 2025
Source:
https://www.lesswrong.com/posts/Eh7WdKTrpLch5Kvkz/attaching-requirements-to-model-releases-has-serious
---
Narrated by TYPE III AUDIO.
View all episodes
By LessWrongHere's a relatively important question regarding transparency requirements for AI companies: At which points in time should AI companies be required to disclose information? (While I focus on transparency, this question is also applicable to other safety-relevant requirements, and is applicable to norms around voluntary actions rather than requirements.)
A natural option would be to attach transparency requirements to the existing processes of pre-deployment testing and releasing a model card when a new model is released. As in, companies would be required to include the relevant information whenever they release a new model (likely in the model card). This is convenient because pre-deployment testing and model cards are already established norms in the AI industry, which makes it easier to attach something new to these existing processes rather than creating a new process.
However, I think attaching requirements to model releases (such that the requirement must happen [...]
The original text contained 5 footnotes which were omitted from this narration.
---
First published:
August 27th, 2025
Source:
https://www.lesswrong.com/posts/Eh7WdKTrpLch5Kvkz/attaching-requirements-to-model-releases-has-serious
---
Narrated by TYPE III AUDIO.
More shows like LessWrong (30+ Karma)
View all
Making Sense with Sam Harris
26,388 Listeners
Conversations with Tyler
2,424 Listeners
The Peter Attia Drive
8,267 Listeners
Sean Carroll's Mindscape: Science, Society, Philosophy, Culture, Arts, and Ideas
4,145 Listeners
ManifoldOne
92 Listeners
Your Undivided Attention
1,565 Listeners
All-In with Chamath, Jason, Sacks & Friedberg
9,826 Listeners
Machine Learning Street Talk (MLST)
89 Listeners
Dwarkesh Podcast
488 Listeners
Hard Fork
5,475 Listeners
The Ezra Klein Show
16,083 Listeners
Moonshots with Peter Diamandis
534 Listeners
No Priors: Artificial Intelligence | Technology | Startups
133 Listeners
Latent Space: The AI Engineer Podcast
96 Listeners
BG2Pod with Brad Gerstner and Bill Gurley
509 Listeners