Back to ‘This Is Nuts.’ An OpenAI Insider Explains Why He Quit.
Why Do Faster Model Changes Need a Live Safety Dashboard?
Changes come more and more frequently so at the limit safety transparency requires a live dashboard. The dashboard shows latest safety properties and performance after deployment rather than relying on system cards or long reports written every few months.
‘This Is Nuts.’ An OpenAI Insider Explains Why He Quit. ·
From the transcript
One of the long-term projects that was on my plate when I left and that the frontier firms are all going to need to figure out is the idea of a system card really dates from that older model where we were doing this every few months. And we're burying people in PDFs or, you know, these like long reports, but the changes are coming more and more frequently, as you said.
At the limit, I think what we would ideally have by way of safety transparency is some kind of live dashboard that says like, here's our latest thing, here's what its safety properties are, and that's also looking not only at the testing we did before we deployed, but also at the
performance. How confident should I be in safety testing when you guys are having to do it at the speed? I mean, given how quickly models are coming out, and these system cards are long, it takes time to write a complex report. So, at this speed, is effective safety testing and monitoring reliable?