Ryan Kidd

Technical governance, which is plenty of stuff, like compliance protocols, eval standards, how to actually enforce these kind of things.

If you have an off switch, how would you even make such a thing be viable in a governance framework?

And in compute infrastructure, which is stuff like tracking where chips are going, right?

Because if you're going to have international compliance with various types of treaties, you need to know where your chips are and what they're running as well, or at least have some zero knowledge proofs that guarantee they're not doing terribly dangerous things.

And of course, physical security for if you're going to prevent, if you build super intelligence or AGI or something, presumably you don't want everyone to have access to it and arbitrarily modify it, give it weird goals, because that would be bad.

Some people say that's good.

I say that's

We don't let everyone have nukes.

Why would we let everyone have super intelligence?

It seems kind of ridiculous.

So you gotta have physical security to prevent that from happening, to prevent diffusion.

So yeah, those are the main tracks now.

We're super excited.

I think we have somewhere over like 50, 60 research mentors lined up for our summer program, which applications are open right now.

And it's gonna be the largest program yet, 120 fellows across our Berkeley and London offices.

Anything else I should say?

Yeah, current program has something like 27% evals, 26% interp, 18% oversight control, 12% agency, 10% governance, and about 9% security.

I wish I had a figure I could show.

I do have a figure, but it might be hard to show in the podcast format.

But as you can see, like,