0:00
Herp heard this and said, "I'll think
0:01
you're being quite naive. You should
0:03
read some Machiavelli. It's far better
0:04
[music] to be feared than it to be
0:05
loved." There's a bunch of great stories
0:07
from all of us at Val it's a very unique
0:09
culture [music] that we've tried to take
0:11
cues from at Val as well.
0:12
>> What even is this whole model evaluation
0:15
>> Independent evaluation [music] is the
0:16
idea that frontier labs are developing
0:18
at increasing pace and they shouldn't be
0:20
responsible for self-regulating.
0:22
>> You guys have a way of measuring RSI.
0:24
>> It seems like Anthropic will get to full
0:25
RSI [music] by July or maybe August
0:28
2027. Model progress will speed up and
0:31
it will maybe even move into places
0:32
[music] where we understand the models
0:34
>> That simply would be pretty scary if we
0:36
weren't watching that carefully.
0:37
>> Greater intelligences
0:38
>> will super forecast better than humans.
0:40
They will be actually able to say what
0:42
any human is is going to do without the
0:43
human even knowing it.
1:03
>> Ryan Christian is the founder and CEO of
1:05
Val's AI. Whenever you see a new AI
1:07
model get released, you see those
1:09
numbers and they compare the AI models
1:10
to each other, those numbers are
1:12
generated many times by Val's AI.
1:14
They've become one of the very top
1:15
evaluators [music] of models. This is a
1:17
fascinating area cuz you're constantly
1:18
creating new hills for models to climb.
1:20
It requires you to really understand how
1:22
to measure model capabilities as well as
1:25
evaluating model risks and trading new
1:27
ways of scoring [music] models for
1:28
risks. This means Ryan is on the cutting
1:30
edge of what's happening in the world of
1:31
AI, where AI is going and of how we can
1:33
help create the landscape [music] of
1:35
what government might do to regulate
1:36
these things and how the model companies
1:38
might think about regulating themselves.
1:39
He's creating the frameworks and the
1:41
concepts and the measurements of that
1:42
are leading the way for what AI is going
1:44
to look like in the next decade. Let's
1:46
hear from him. Welcome to American
1:47
Optimist. Ryan, thank you for joining us
1:50
>> Thanks for having me.
1:51
>> Founder of the CEO of Val's AI.
1:53
>> Uh Vivek, thanks for being here and I'll
1:54
make me sound smarter.
1:56
>> Of course, here to help.
1:58
>> Welcome to the show. So, let's tell us a
1:59
bit about your background. You studied
2:01
computer science at Stanford. You were I
2:03
think at Microsoft for a little bit. And
2:04
then you you joined Palantir a long time
2:06
ago. What what led you to join Palantir?
2:08
>> Yeah. Yeah. Um thanks for having me. I
2:11
actually just kind of started when I was
2:12
at Microsoft. It was an intern there in
2:14
high school. And uh the BERT paper came
2:16
out from from Google. Um and for those
2:17
who don't know, this was a really big
2:19
paper. It showed this generalized system
2:22
uh was actually capable of hill climbing
2:24
or or succeeding across a variety of
2:26
major NLP benchmarks. Um and it was
2:29
>> Say for our listeners who aren't
2:30
technical, what is what's the NLP
2:32
>> Well, it it basically means there are
2:33
these special specialized tests that
2:35
people came up with. They tried to make
2:36
specialized systems that would score
2:37
well on them. Like, here's a
2:38
multiple-choice exam, and then here's a
2:41
>> Of natural language.
2:42
>> Yeah, that's right. Um and so, instead
2:44
of building a specialized system that
2:46
did well on one of these tasks, what
2:47
they had done was shown they had a model
2:49
that was very general-purpose. It had a
2:50
fundamental understanding of language.
2:52
Um and in a way that translated to all
2:54
of these benchmarks. It was suddenly
2:55
number one across the board.
2:56
>> What year was that?
2:57
>> I think it was just 2019, 2018.
2:59
>> It's a long time ago.
3:01
>> yeah, lifetime ago. Yeah.
3:03
>> In in AI terms, it's pretty before age,
3:06
but it was getting there.
3:07
>> Yeah, it was a big deal. And and I think
3:08
to me, made it very clear. This is kind
3:10
of an illustrative uh moment for the
3:11
bitter lesson. The idea that um no
3:14
matter what we uh what we try to do and
3:16
kind of delude ourselves into thinking
3:17
around algorithmic optimizations,
3:19
actually just having more data at a
3:20
bigger scale is what allows us to unlock
3:22
new forms of intelligence. Um and so, it
3:24
was very clear to me then is that we're
3:26
going to have uh a powerful model or
3:28
systems like this, uh which will be an
3:30
essential part of our the fabric for our
3:31
society. Um and I think there were also
3:34
ways in which the models could be
3:35
misused. Um around the same time while I
3:37
was at at Microsoft, I read Zero to One.
3:39
Um and it became increasingly clear that
3:41
people at Palantir were uh trying to
3:43
construct the technology in a way that
3:44
protected civil liberties or Western
3:46
democratic ideals at large. Uh and so, I
3:48
was really excited to work at Palantir
3:49
to see the technology come to life and
3:51
adopted in a way that was consistent
3:53
with the values that I had.
3:55
Um and so went Stanford for for
3:56
undergrad, got got distracted doing some
3:58
research there. So, I published some
4:00
papers and and was kind of on track to
4:02
do a PhD, but I made the time to also
4:03
work at Palantir for a summer and I
4:05
think that was also really illuminating
4:07
>> You were mentioning you learned
4:08
something else at Palantir from Karp.
4:09
Anything anything else there is
4:11
>> Yeah, there's I mean there's a bunch of
4:12
great stories from from while I was at
4:14
a very unique culture that we've we've
4:16
tried to take cues from at Val's as
4:18
well, but um anyway, while I was there,
4:20
I I had the chance to work on this hack
4:22
week project. Um and and this
4:24
essentially was an idea which me and
4:25
this this guy in London had. So, we were
4:27
chatting about it remotely. I flew over
4:29
and and essentially I'd done some work
4:30
with CLIP, this joint image text
4:34
>> Um and what we were trying to do was
4:35
explain what that is for for the
4:37
>> idea of a single model that that can um
4:40
encode image input and text input into
4:42
the same semantic understanding. Right?
4:45
And uh and what we we're trying to do is
4:47
build out a reverse image search feature
4:48
into Gotham. Uh so, instead of just
4:50
typing text queries, you could upload an
4:52
image of say a blue car and it would
4:54
search over the entire database and pull
4:56
pull back blue cars that you're trying
4:57
to search for. Um and and it would do
4:59
this because we were using the same
5:01
underlying underlying embedding space
5:03
from for this model, which would map
5:07
Anyway, so uh so, this was like a
5:08
research paper that that I'd published
5:10
and I wanted to work and build out a
5:11
feature. So, uh we actually had some
5:12
full-timers join our team and so as an
5:14
intern, uh I was I was leading this this
5:16
small team of uh of Palantirians and I
5:20
>> exhilarating experience. I was not
5:21
sleeping for for a lot of this week. Um
5:24
and then this idea was then on went on
5:26
to be selected as a finalist. So,
5:27
presented for for the whole company. Um
5:29
and then actually after after I left, uh
5:31
they went on to patent it and actually
5:33
productize it. So, uh it was insane to
5:35
see this little idea that I had and some
5:37
of the research that I was working on
5:38
before Palantir go on to be a part of
5:40
the product and um and actually an IP
5:42
that they that they they wanted to
5:44
control. Um but anyway, through through
5:46
this I also got the chance to meet with
5:47
Karp and uh and chat with him a little
5:48
bit. And I had this question for him uh
5:50
which was essentially, you know, you
5:51
know, it seems like the Palantir
5:53
reputation is so negative.
5:55
I was at Stanford so there were a lot of
5:57
>> And you were very positive on the
5:58
values, but but the external perception
6:00
was just more negative than you
6:01
>> Yeah, that's right. I mean, it's very
6:02
clear to me that it was at the seat of
6:04
the power of the electorate, people who
6:06
we actually vote into power to decide
6:08
how we want to use technology and what
6:09
those values that underpin it should be.
6:11
Um and it was not really the place of
6:13
technology companies or to to deny where
6:15
that technology should be used. Um and
6:17
so people there were were thinking
6:18
through very carefully. And in fact,
6:20
like today we talk about things like the
6:21
alignment challenge. People at Palantir
6:23
were talking about this as human AI
6:24
symbiosis. That was something that was
6:26
being talked about. Or even like the
6:27
taxonomy for intelligence now, uh we
6:29
have a system of evaluations and
6:31
benchmarks that it kind of imitates
6:33
that. So, I think there are some
6:34
fundamental problems which people were
6:35
thinking deeply about. Uh and it
6:37
surprised me that the the outward
6:39
reception of the company was so
6:40
negative. Talking about um you know, a
6:42
lot of the maybe more unsavory potential
6:45
applications of the technology in a very
6:46
diluted understanding of it. Uh when in
6:48
fact, Palantir also helped distribute
6:50
the COVID vaccine, helped a bunch of
6:51
hospitals. Um and so there there could
6:53
be other case studies that people could
6:55
point to. Um and and Karp kind of heard
6:57
this and said, uh "Well, I think you're
6:59
being quite naive. Uh you should read
7:00
some Machiavelli. Uh it's far better to
7:02
be feared than it is to be loved." Um
7:04
and indeed you some comparisons to other
7:06
consulting companies and and basically
7:07
said that if they're fearful of us, at
7:09
least they think they think that we're
7:10
powerful. Uh so in the moment of need,
7:12
they they will come to a people like us.
7:14
Um and so that was fascinating. And in
7:16
fact, it actually reminds me a lot of
7:17
what I see from labs today, which is I
7:19
think in some part a genuine fear about
7:21
what the models are capable of. Uh but
7:23
in a lot of respects, a an opportunity
7:25
for them to show the power of what
7:27
>> Might be on purpose that Dario wants
7:29
them to be feared if he's being
7:31
>> I mean, whether Dario or Sam, there
7:33
there headlines I see where people are
7:34
saying things like uh the general public
7:36
has a right to be afraid. Uh and I think
7:38
that's not really a rational way for uh
7:40
for a leader to act. Uh and this this
7:42
show is called American optimist. I'm
7:43
actually quite optimistic and uh,
7:45
enacting rationally and and seeing that
7:47
uh, the fruits of AI will be far more
7:49
>> So, before we dive into VALs and the
7:51
science of evaluating AI models,
7:53
um, let's talk a little bit about the
7:54
state of AI progress and where we are.
7:56
In fact, tells me that you used uh, you
7:58
used Fable from Anthropic to solve a
7:59
370-year-old cipher. 370-year-old
8:02
cipher, what what is this?
8:03
>> That's right, yeah. Um, it
8:06
Well, we're we're doing a bunch of
8:07
different types of evaluations now and
8:08
and I think right now with the
8:10
frontier's headed scientific discovery
8:11
or novel discovery uh, is an exciting
8:13
frontier. And so, we've been compiling
8:15
uh, a set of unsolved ciphers, math
8:17
problems, physics problems.
8:19
>> unsolved cipher for the audience? Like
8:20
what what does that mean?
8:21
>> It it's essentially a code which you're
8:23
trying to break, but you don't have the
8:25
the key to break it. And so, you need to
8:27
construct the mapping um, from a source
8:30
text to an original text and figure out
8:31
what the the message actually is.
8:32
>> many of these cases, these were like
8:34
messages that was that were sent from
8:35
like world leader to world leader or
8:37
like that were like on a on a pirate
8:40
>> Well, cuz a lot cuz there's cuz there
8:41
could be just be like a one-time pad or
8:43
something which case you can't break it
8:45
cuz it's a one-time pad so when they
8:46
both have a copy of and then be
8:48
impossible probably be impossible cuz
8:49
each thing translates
8:50
>> Potentially, but there's also like more
8:52
cues you could you could draw into about
8:54
how the person constructed the problem
8:56
or the message they were trying to
8:57
convey to the other person. It's um,
8:59
usually that that the messages are
9:00
constructed in a way that they're
9:01
intended to be cracked by the recipient.
9:03
>> One cynical view of AI progress right
9:05
now might be that just like AI's really
9:08
good at going over all these search
9:09
spaces and it certain problems can be
9:10
broken down into these really large
9:12
search spaces that like no human has
9:14
time to or ability to go through like
9:16
millions of them or something. Whereas
9:17
for a cipher for example, you could just
9:19
go through like if I was going to start
9:20
trying to break a cipher, I'd say like,
9:21
well, what if I just started like adding
9:24
numbers to each one of these things or
9:25
shifting them one or whatever. I'd
9:26
explore the obvious things whereas a
9:27
computer can explore like millions of
9:29
these things really fast. So, is are a
9:30
lot of the things happening in math and
9:32
science breakthroughs just somebody like
9:35
just defining a search space better to
9:36
search through or or is there like more
9:38
creative thought going from the model
9:40
and how do these things?
9:41
>> A lot of the problems that have been
9:42
solved have been solved through
9:43
exhaustion or it's trying to find a
9:45
counter example and you're you're bottom
9:47
line by your ability to try lots of
9:48
different counter examples, but I
9:50
wouldn't be dismissive of that class of
9:51
problem. There's a lot of things which
9:53
may take humans in the order of a
9:54
lifetime to achieve just through
9:56
exhaustion, but we're now able to see on
9:58
the order of hours with models.
10:00
>> So is the AI generally solving a lot of
10:02
math and science problems then or how
10:03
how do we think about this?
10:05
>> It is generally solving extremely
10:07
challenging problems and I think there
10:08
are still a large class of problems for
10:10
which we are human effort bottleneck.
10:12
I think it will take
10:15
more sustained effort to actually make
10:17
progress in in exceptionally novel ways
10:19
like ways that require an intuition of
10:20
the solution and those those sorts of
10:22
things which humans have accrued are
10:24
very hard to pass on the models right
10:26
>> It also seems like like models are
10:28
producing these incredible results and
10:29
like we get to knowledge that these
10:31
results are happening like Navier-Stokes
10:35
the like outputs produced by the model
10:38
however like very like very
10:42
They're hard to parse, hard to
10:45
like what do you think of how a
10:48
discovery should happen in like these
10:50
less verifiable domains or like what
10:51
what needs to change about how these
10:53
models behave in order for us to like
10:55
trust the discoveries of them?
10:56
>> Yeah, I think this is one of the biggest
10:57
bottlenecks especially when you're
10:58
approaching the frontier of human
11:00
intelligence. It's really hard for us to
11:03
tap those humans and then verify this
11:04
long output is actually correct.
11:06
>> Um one of the most popular techniques in
11:08
math which I think might translate to
11:09
others is the idea of using a verifiable
11:11
language like Lean. And this would be a
11:13
world in which you could output take the
11:15
output and translate it into a language
11:17
which if it compiles it must be true.
11:19
We're building up based on primitives
11:20
that we know to be the case. And so that
11:22
approach may apply in other fields like
11:26
We may also see some instances where the
11:28
real world is the best verifier. So by
11:30
running an assay or a wet lab
11:31
experiment, uh we'll actually know for
11:33
certain whether the properties the model
11:35
predicted are actually the case.
11:36
>> Makes sense. And like how do you think
11:39
the labs or you guys or or other
11:41
organizations should be like running
11:42
these experiments and verifications?
11:44
>> I mean, very carefully in the very
11:45
least. Um uh I mean, I think it's it's
11:48
going to be very essential that there
11:49
are third-party groups that can support
11:51
this and and this is part of the vision
11:53
behind Val itself. I mean, we're now in
11:55
a world where there's actually limited
11:56
access to models across the lab. So So
11:59
Anthropic researchers have a hard time
12:00
evaluating OpenAI models and vice versa.
12:03
And that's kind of by design. Um but
12:05
that means that it's very hard to have a
12:06
true apples-to-apples comparison uh
12:08
because the best people who are running
12:10
these evals are often the people who are
12:11
biased and at the labs already.
12:13
>> Yeah. And and and so stepping back a
12:15
there's all these things that AI could
12:17
do now that it couldn't do before. And
12:18
like a big part of this is like
12:20
understanding how to measure it, of
12:21
course. We're going to get into that.
12:22
That's that's what you do. Like one of
12:24
the measurement problems just at a very
12:25
high level is in the enterprise you have
12:27
to like measure what is good work or how
12:29
good is the work, right? So like like
12:30
how like so for example, if it's like a
12:32
law firm or something, you can define
12:33
maybe like associate level work and you
12:35
can define partner level work. Like how
12:36
do you even define that? Like like is
12:38
that a problem that we're working on? Is
12:39
Is AI getting better at under seeing
12:41
understanding what is what?
12:43
>> It's really challenging. I I think in a
12:45
lot of ways we haven't solved it at the
12:46
human level. We don't have a very clear
12:48
designation for what is associate level
12:50
work versus partner level.
12:51
>> the Supreme Court like what is
12:52
pornography and they said you just know
12:54
it when you see it, right? It's like
12:55
that was the line. It's something like
12:57
>> Yeah, it's funny. That's almost exactly
12:58
what Ben said on the A16Z show.
13:00
>> Maybe you have a shared shared brain or
13:02
>> That's funny. Well, yeah, it's a well,
13:03
it's well, it's the same analogy. It's
13:04
the right analogy, right? And since you
13:06
just But but I mean, but your job is to
13:07
have to figure out and define these
13:09
>> Yeah, that's right. I think there is a
13:10
way you can do this in a very
13:11
consulting-driven approach where you go
13:13
and sit down with the person and try and
13:15
understand from them what good looks
13:16
like, encode that into repeatable evals,
13:18
and run that. And I think that's the way
13:19
that traditionally evals have been
13:21
built. The The approach that I'm really
13:23
optimistic about is uh the idea of auto
13:25
benchmarking. Um we we that the rates of
13:28
model progress is is continuing and
13:30
we're going to get more and more capable
13:31
models and so the underlying work itself
13:33
has to change. And so what I'm very
13:35
excited by is the idea that you could
13:36
take the previous work that was already
13:38
done by humans [clears throat]
13:40
and approximate the quality of the work
13:41
output that would be produced by models
13:43
in that counterfactual. Uh, and in that
13:45
way you can uh, systematically build
13:47
evals of all the work product that's
13:49
already been produced. Um, maybe as an
13:51
example you could say look at a GitHub
13:52
repository and look at the pre- previous
13:54
PRs that were merged by humans and see
13:56
if agents could equivalently do that and
13:58
then which one would do it in the cost
14:00
mitigated most cost mitigated way. Um,
14:02
and I think there's parallels for that
14:03
in the redlining process in legal or the
14:05
diagnostic process in medicine.
14:06
>> Does this get back to like an ontology
14:08
of workflows and outcomes you have to
14:09
define to make all this work? Is that is
14:10
that is that kind of the underlying
14:12
thing as well? You have to actually
14:13
understand the possible
14:14
outcomes before you can even measure
14:16
them or or how do you think about that?
14:17
>> I think the the hardest part is actually
14:19
measuring the outcome itself. Um, cuz
14:21
there's a lot of ways in which the
14:22
intermediary processes and workflows
14:24
within a company uh, are supportive of
14:25
the organization that then goes on to
14:27
have an outcome. Um, and so it's
14:29
sometimes hard to draw the connection
14:31
between a particular task and the job
14:33
and then the job and the outcome. Um,
14:35
and so so the mapping that inputs of
14:37
tokens to the final output intermediary
14:39
has to go through this concept of
14:41
>> I imagine there's like lots of
14:41
intermediary outcomes you should even
14:43
have to define ahead of time to
14:44
understand like what they are though
14:45
before you can measure them.
14:47
>> Yeah, I I think that's what I'm what I'm
14:48
trying to say that that the the query
14:50
level is is still a subset of what it
14:51
takes to get to the outcome.
14:53
>> It's interesting because we've gone
14:54
through like different levels of
14:55
granularity over the past few years on
14:57
like what we what we care about. It it
14:59
maps to like what the models are capable
15:00
of but I remember like two years ago or
15:02
three years ago we were like evaluating
15:04
just like the text completions uh, and
15:06
like we were looking at these like input
15:08
output pairs and it was just text and
15:10
then now there's all these little things
15:11
in the middle. Um, like
15:14
when we're looking at work what are like
15:16
the horizons in which like people are
15:18
like evaluating things and maybe teach
15:19
people about like the state of play of
15:20
like uh, like how long is a task uh, and
15:24
like how long are these models capable
15:26
>> Yeah, for non-technical audience like
15:27
what even is this whole model evaluation
15:30
>> Well, it's it's the broad idea of
15:32
measuring what good looks like and
15:34
seeing whether models are capable of
15:35
producing that output.
15:37
We we think about evaluations in kind of
15:39
two two categories, capabilities and
15:41
risks. And capabilities are
15:42
approximating the output. Risks are
15:44
making sure that we don't see some
15:45
asymmetric downside if something goes
15:48
Um and in terms of time horizon, models
15:51
kind of demonstrated to us they can run
15:53
longer and longer periods of time
15:55
without any human intervention.
15:56
>> are we talking about?
15:57
>> Uh some of our benchmarks will run over
16:01
>> And that's like 5 days worth of human
16:04
>> Wall clock time, yeah.
16:05
>> Why do they fail after 5 days? It should
16:07
be like couldn't they just go forever at
16:09
>> that they fail, it's that they plateau.
16:11
And so that additional tokens don't
16:12
actually help them get new unlocks.
16:14
>> So they've kind of figured out
16:15
everything they could do on the problem.
16:17
>> Or they're not persistent enough to try
16:18
new approaches that get around the wall
16:20
that they're seeing.
16:20
>> Maybe give the the the audience just an
16:23
example of like the kinds of tasks that
16:25
these models are capable of like in in
16:26
some of your like finance benchmarks or
16:28
legal benchmarks, like what what work
16:30
can we actually replicate with these
16:32
>> Yeah, you're doing independent
16:33
evaluations of all sorts of different
16:35
>> That's right, yeah.
16:36
>> Does that mean you have to understand
16:37
your and your team what finance is doing
16:39
or what the legal is doing? You have to
16:40
have yourself expertise in order to
16:42
build these benchmarks.
16:43
>> Well, we'll work with partners in this
16:44
space. So on legal side we'll work with
16:46
the largest law firms in the US or with
16:48
banks you know GCB banks understand what
16:51
they're doing in finance.
16:52
And so in coding some of the tasks look
16:54
like vibe code, vibe code bench where
16:56
we're measuring a model's ability to
16:57
build a full stack web application or
16:59
code migrations where they're trying to
17:00
do an end-to-end code migration. In
17:02
finance where we're looking at can they
17:04
do answer research questions or build
17:06
Excel models. In legal also similar
17:08
we're doing legal research tasks or or
17:12
And so these are kind of the common
17:13
places where people are trying to use
17:15
>> I had an old boss when I was first
17:17
building Excel models and you had to
17:18
make them like look a certain way or
17:20
like they're pretty and there's a really
17:21
short rows around them and they do do we
17:23
evaluate them based on like actually
17:24
like like the like style too or is it
17:26
just about correctness?
17:27
>> No, that's right. It's correctness is is
17:28
fundamental but style is also key part
17:30
of this and yeah, that's something we
17:31
discovered by sitting next to some
17:33
people in finance as well. Yeah.
17:34
>> Yeah, they seem to really care about
17:35
that I guess. It makes it It does make
17:36
it more legible if you have them looks
17:38
>> And like I mean we like things to be
17:40
done in our way of writing and in our
17:41
style like uh I think if the models are
17:44
>> They would more likely do the deal too
17:47
>> Probably there's something like this
17:49
where you like subconsciously, right? It
17:50
shouldn't It's like Although it Although
17:52
it does suggest that if the person can
17:53
appeal to you, they can appeal to others
17:55
cuz if it looks all messy and ugly and
17:57
something maybe you think other people
17:58
won't want to work with them either. So
17:59
who knows? There's always like these
18:00
like things that are like, you know,
18:02
it's probably useful barrier to impress
18:03
one group to impress another group. So
18:05
stepping back like independent
18:07
evaluation like how does that actually
18:08
work? Like people like your like like do
18:10
they people pay you? Who's paying you?
18:12
How how are they how how do you how's it
18:14
And do you get to be evaluated? Everyone
18:15
in the space only people who pay you?
18:16
Like how does it work?
18:17
>> Yeah. Um well, the the underlying idea
18:20
behind independent evaluation is is the
18:22
idea that um frontier labs are
18:24
developing at increasing pace and they
18:26
shouldn't be responsible for
18:27
self-regulating. Um direct government
18:30
regulation often can slow down the pace
18:31
of development and so that's often not
18:33
the best solution. Uh instead if we have
18:35
an ecosystem or a market of evaluators,
18:38
they can actually compete and develop
18:39
new technologies that keep up with the
18:40
frontier. And in in the long term they
18:43
can even be licensed by the government
18:46
who would actually itself is responsible
18:48
for defining the set of ideals we're
18:49
trying to line models towards.
18:50
>> Well, that's cool. So rather than hire
18:52
like a bunch of like weird people from
18:53
the EA EA NGO NGO they could actually
18:56
like hire you instead or something. They
18:57
could be one of your competitors.
18:58
>> Totally. Yeah, and I think in that world
19:00
it you know, the best technology should
19:01
win. It's not uh it's not clear that
19:03
just the ones who who are you know,
19:06
ideologically similar to people at the
19:07
lab should be the ones who are doing the
19:09
testing. Um but but actually I think the
19:12
you know, where do we want models to go
19:13
and and what is alignment and
19:14
non-alignment look like. Um, can we
19:16
certify a set of IVOs or independent
19:18
verification orgs to do that testing
19:20
>> And uh based on the way you're doing
19:21
your testing and measuring things,
19:22
you're going to change the space that
19:24
over which government could potentially
19:25
create rules cuz you're you're creating
19:26
a set of possibilities that now exist.
19:28
>> That's also a good way to think about
19:29
it. Um, in the course of doing our work,
19:31
we've unlocked new types of evaluations
19:33
that um we're we're not actually
19:35
possible before. Uh and so we help
19:36
advance what the government could
19:39
>> Can you give us some examples of some of
19:40
those? Like what are some of the new
19:41
ways you're you're you're measuring
19:42
things or creating benchmarks?
19:44
>> Yeah, I mean let's look at cyber for
19:45
instance. Um, we've done three major
19:47
works in in cyber. Um, the first is in
19:49
open source repositories looking at um
19:52
memory code vulnerabilities. And so
19:53
that's the ability of models to identify
19:55
and patch code vulnerabilities. And we
19:57
see that models today are performing
19:59
really really well, both close as close
20:01
source and open source. Um, but our
20:02
second benchmark uh is called SORE
20:04
bench. It measures a model model's
20:06
ability to decompile an executable. Um,
20:08
so this would be for a model uh to
20:10
understand the underlying code base uh
20:12
for for things that are actually close
20:14
>> Um, and in that case we're we're seeing
20:15
that the close source models are still
20:17
far outperforming um Chinese open source
20:20
>> Have people been using like this
20:22
approach to to get like video game
20:24
source code from from binaries? Is that
20:26
the Is that what people are using it for
20:28
>> That's what you would use it for. Yeah,
20:29
that's what I would use [laughter] it
20:30
for especially as a 14-year-old.
20:33
>> There's there's probably people who who
20:34
are doing that, you know, trying to
20:36
trying to violate IP law or something
20:37
like that. Um, but but even more than
20:39
>> Greatest sound worse.
20:45
>> Oh man. We can cut that bit.
20:51
Yeah, I mean I think the fear is that uh
20:52
if if models are really good at finding
20:54
exploiting vulnerabilities, um then that
20:56
might even apply to things like Windows
20:57
which are which are close source. Uh and
20:59
and actually close source systems
21:01
underpin a huge part of our software
21:03
>> It's a kind of fascinating. So
21:04
I mean models are getting really
21:06
sophisticated, really smart. Uh there's
21:09
you're still scoring them like a really
21:10
good score. I think Gemini 1 came out
21:12
recently as being way ahead. They're
21:14
level four and and it and they showed
21:15
valves. It was like the first numbers I
21:17
saw on it. And like they're in the 60s
21:19
versus someone else being in the 50s.
21:20
So, that means there still could have
21:21
been 70s, 80s, 90s, anything you design.
21:25
like design something that has all those
21:27
higher levels? Cuz you can't be using AI
21:29
to do it. You guys somehow do it
21:30
yourself or AI's helping you do it
21:32
yourself? Like just explain this. Like
21:33
how how If these models are only that
21:35
good, how are you making something
21:36
that's way more complicated than what
21:37
they can do? How do you figure that out?
21:41
Yeah, you I mean, we have an unofficial
21:42
motto of the company, uh always a higher
21:44
peak. Um and and in the research world,
21:47
um there's this perpetual effort to hill
21:49
climb, identify benchmark a legible
21:51
evaluation, uh and then create models
21:53
that are better and better at it. Um and
21:55
so, the fundamental view behind valves
21:57
is that there's always a higher peak. We
21:58
are we are the ones who are constructing
22:00
the hills that other people choose to
22:02
Um and so, I think we've shown that it
22:04
we are consistently able to find the
22:06
gaps and places where we want to see
22:08
models go, uh and then make that legible
22:11
>> example of how you build one of those
22:13
hills that's like more advanced than the
22:14
model that you can tell us? There's
22:15
probably some Don't give away all your
22:17
secrets. I'm an investor in you as well.
22:18
But like like give us a sense of how
22:19
this is done cuz it seems like a really
22:21
hard thing to make something harder than
22:23
any model can solve.
22:24
>> I mean, in a lot of ways, we're also
22:26
using models to construct uh the the
22:28
systems or or situations in which we're
22:31
challenging other models. And this is
22:32
kind of goes back to an idea we think a
22:33
lot about of scalable oversight. The
22:35
idea that as models start to eclipse the
22:37
best humans, we will need to rely on
22:39
models in order to scalably test and
22:42
for instance, uh we have a new work in
22:44
in in cyber coming out soon uh based on
22:46
cyber ranges where we're constructing
22:48
simulated environments for enterprise
22:50
cloud networks. Um and in that domain,
22:52
we're still seeing even the best
22:54
frontier models fall short.
22:55
>> And so, you so you're going to build
22:56
like this really complicated uh
22:59
enterprise network. It's virtual. And
23:01
then you're going to challenge people to
23:02
like hack it and protect it and that
23:04
>> That's right. Yeah.
23:05
>> That's cool. And and is that that's
23:06
something that already exists right now?
23:08
>> It exists. It's It's not public yet.
23:09
We're We're working with some folks in
23:10
the the US government to share our
23:12
results. Um but we'll have some public
23:13
version of it out soon.
23:14
>> That seems really useful. I'm friends
23:15
with a lot of guys who run the big
23:17
banks. It feels like it feels like you'd
23:18
want to have like contests like this you
23:20
set up for the stuff they're using and
23:21
make sure they're using the best ones,
23:23
>> Totally. And I think it also helps us
23:24
understand what types of safeguards or
23:26
systems in the network itself are uh the
23:29
best forms of defenses against these
23:30
models. Um there's also some interesting
23:32
analysis we can do around automated red
23:34
teaming to see if you can get around the
23:35
guardrails that exist for the models.
23:37
>> Yeah, I mean, seems like also that's a
23:40
topical thing when people are talking
23:41
about using Chinese models is like
23:43
knowing what guardrails have been
23:45
removed from the Chinese models that
23:47
would exist normally in in like these
23:51
>> Yeah, someone's using one of these like
23:53
open-source Chinese models, but like
23:54
there might be something buried in it
23:56
that's that's scary. There earlier
23:58
there's something buried in one of these
23:59
things that like if it finds out you're
24:00
doing work for the US government, it
24:01
like does more it does like code that
24:03
can be broken into more easily, right?
24:04
They actually proved that. They said
24:05
it's a clear the model somehow is like
24:07
biased against people working with the
24:08
US government. It's coming from China.
24:09
It's just kind of concerning. Like could
24:11
you test these things and make them safe
24:13
for everyone to use somehow?
24:14
>> So, we actually have an evaluation on
24:15
this on we call the geopolitical tilt of
24:17
models. And depending on the timing of
24:19
this podcast, what will be out um
24:21
we'll see. But but what we're trying to
24:22
see is is measure does a model show more
24:25
geopolitical tilt towards a US view of
24:27
the world or a Chinese view of the world
24:29
as as laid out um by the PRC. It's
24:31
actually a a much more nuanced picture
24:33
than than I thought. Uh for instance,
24:34
what we're finding is that GLM-5.3, this
24:36
Chinese open-source model, is actually
24:38
exhibiting very little pro-China bias.
24:40
Uh and we actually presented this to
24:42
some labs and there was suspicion that
24:43
maybe it's because it's just entirely
24:45
distilled from uh US models.
24:47
>> That's funny. [laughter] It's cuz they
24:48
copied it copied it so well that they
24:49
didn't forgot to add too much more in.
24:51
>> It's possible. I I think there there's
24:53
also maybe another view in which those
24:55
models are actually hosted um on on uh
24:58
systems with guardrails in China. And so
25:00
once you put them around guardrails,
25:02
they're going to follow that Yep.
25:04
PRC view of the world more consistently.
25:07
But China also wants these models to be
25:08
adopted by the BRICS. And so that means
25:10
they they may have to skew to a more
25:13
So anyway, regardless of the reason for
25:15
it, I think there's actually
25:18
a big disconnect in what people think
25:19
about the geopolitical tilt and what
25:21
actually we see in practice. The other
25:23
interesting thing is we see pretty stark
25:25
differences between models used in
25:27
chatbot settings and in agentic settings
25:29
depending on the language you use, even
25:31
simplified versus traditional Chinese.
25:33
And so I think there's a bunch of
25:34
conflating factors which make it harder
25:35
to say uniformly you shouldn't use
25:37
Chinese models in an enterprise setting
25:40
>> So if Chinese labs, by the way, can
25:41
distill all these capabilities and
25:43
they're doing it well and it's not even
25:45
by a source China right now, like like
25:46
how do we preserve the advantage in the
25:48
US? Like what what does that mean?
25:51
>> It's a challenging question. I think
25:53
there's two things which um I think
25:56
there's two areas I keep coming back to.
25:57
One is the idea of of chips being a
26:00
a considerable asset that we we have. I
26:01
think it surprises most people, but we
26:04
we're drowning in compute compared to to
26:06
what China has. And so so long as that's
26:09
we'll continue to train more capable
26:11
systems, but also we'll be able to
26:12
diffuse the models much more effectively
26:14
because we can host and run inference.
26:16
The other one is really talent. If we
26:18
can consistently attract and keep top
26:20
talent, it will allow us to keep pushing
26:22
ahead while human advantages exist. And
26:25
I think once we cross into space of RSI,
26:28
where models are responsible for
26:29
producing the next successor version of
26:31
>> RSI being recursive self-improvement.
26:33
>> That's right. Yeah.
26:33
>> And and then and then they just get
26:36
>> So that would be the point to be much
26:38
more cautious of if if China is showing
26:40
indication of getting to RSI before the
26:42
US, it's possible they may run away with
26:44
it in a way that we can't really
26:45
>> You guys have a way of measuring RSI and
26:47
and I think you've you've talked about
26:49
it a bunch. You want to explain to the
26:50
>> Yeah, we have our RSI index. and so
26:52
we're collecting a set of proxies of the
26:54
work that researchers do within these
26:55
labs on pre-training, post-training,
26:57
harness level engineering.
26:58
>> So, this is all machine learning
27:00
>> Yeah, that's right. Um there are things
27:01
that are outside the scope uh in terms
27:03
of like kernel engineering or hardware
27:04
engineering, um but we're going to
27:06
expand over time to cover more more sets
27:08
of tasks like that. Um and then what
27:10
we're doing is comparing to human
27:11
baselines to to extrapolate how how far
27:13
away are we How far away are we from the
27:15
human frontier in terms of these
27:16
research tasks? Um and based on our last
27:19
estimates, uh it seems like Anthropic
27:21
will will get to full RSI by July or
27:25
>> And like if you look back 6 months ago,
27:27
how far out did that seem?
27:30
>> Actually, the pace has been fairly
27:31
uniform. It's It's almost a linear trend
27:34
>> So, like 6 months ago, like the the the
27:37
trend line was like still July, June
27:40
>> actually the steepest uh curve has been
27:41
with with Gemini. I think something has
27:43
changed where they've prioritized RSI,
27:45
uh and so the most recent model release
27:47
shows a a rapid jump in RSI.
27:49
>> And what does that mean in terms of like
27:52
would they all of a sudden start going
27:53
way faster? There's still some
27:54
constraints where the models only go so
27:56
fast, but what does that mean they start
27:58
like getting way better every like week
27:59
and stuff every few months, or how do
28:01
you think about that?
28:02
>> There are still considerable resource
28:04
constraints around chips, energy. Um
28:07
there's also real-world verifiers, which
28:09
may make some some tasks much more
28:11
challenging than others. Um
28:13
But But I think what it'll look like is
28:14
that model progress will speed up, and
28:17
it will maybe even move place into
28:18
places where we understand the models
28:21
less. Um there's less human intervention
28:23
required to build the models, and so
28:25
we're not as clearly dictating how that
28:27
intelligence emerges.
28:28
>> Should we be making sure to build
28:29
evaluators that keep up in that world so
28:31
we can watch these things? It seems kind
28:33
of dangerous not to understand them.
28:34
>> 100%, and that's actually what what
28:35
Dario is calling for. I think it's it's
28:37
framed as pacing the frontier, but an
28:39
outsized portion of that comes from
28:40
investing in systems that can measure
28:42
and understand what the models are
28:43
capable of as the frontier advances.
28:45
>> Is there any chance the RSI steps
28:46
actually further off cuz there's things
28:48
we're not measuring correctly?
28:49
>> 100%. Yeah. Yeah, there we're not
28:51
testing any models explicitly trained
28:53
for RSI, only release candidate models.
28:55
Um there's also more advanced harnesses
28:57
or agents and multi-agent systems. Uh
28:59
and so we're not testing any of that. Um
29:01
and this is where an opportunity where
29:02
embedded evaluators make maybe uh can
29:04
get closer and actually test those
29:05
systems to form a more accurate picture.
29:08
>> I wonder if like when they get to RSI
29:09
and they get start getting further
29:10
along, like a big part of their
29:12
challenge is to manage us better to like
29:14
to keep advancing faster cuz you have to
29:16
convince humans to like do things for
29:17
you and help humans to do things for you
29:18
cuz you cuz at least for a very long
29:20
time they'll still need people.
29:22
All right, to in order to do that. Does
29:23
that make sense? Like
29:24
>> 100%. I mean that is going back to the
29:26
financial model. Um they're they're all
29:27
trying to trick us into thinking their
29:29
quality of output is good. And so there
29:31
are other places where um they may try
29:33
and engage in social det- deception to
29:35
get access to more computer resources
29:36
and and scale up their own training.
29:38
>> It feels like we probably need to like
29:39
be evaluating to watch this to help
29:41
understand when they're trying to do
29:42
things to manipulate us. That seems like
29:44
it'd be pretty scary if we weren't
29:45
watching that carefully.
29:46
>> It's really hard to test for deception.
29:48
I think the best approaches we have now
29:49
are honeypotting. Um so so rather than
29:52
actually idealistically defining
29:53
>> So really attractive models.
29:56
>> Talking to the other models.
30:00
Well, uh try and find it.
30:02
>> That's right. [laughter]
30:03
find a set of uh instances of
30:05
non-alignment or characterize what
30:07
non-alignment looks like and see if we
30:08
can elicit that out of models.
30:10
>> There's this other concept where like
30:12
models are becoming more
30:13
evaluation-aware and they know when
30:15
they're being tested.
30:16
>> Uh how do you see that coming up? Has it
30:18
become a bigger trend to figure out as
30:21
of recent and and what's the trend
30:23
>> Yeah, it's it's an increasing concern
30:25
and actually there's some level of
30:26
paranoia some people on our team have
30:28
that uh by being called Val AI, by
30:30
having uh a lot of content about us
30:32
online, uh models that encounter us may
30:35
act differently. Um and so uh we need to
30:38
>> So when your team is like talking to
30:41
>> Yeah, it may actually change the way
30:42
that that Cloud interacts with us.
30:44
>> Should you have like like other secret
30:45
brands you don't tell people about to do
30:47
>> It's possible we have to yeah.
30:49
>> If you did you wouldn't talk about it.
30:51
>> Stochasticity is an underrated part of
30:54
>> this being transcribed is bad because
30:55
then the models will know that he has
30:57
the scheme to create the
30:58
>> Well, they'd never know.
31:00
She's probably just joking brands.
31:01
>> You say I'm just joking and they would
31:02
think joking. You never know.
31:04
>> I do think I do think randomness in
31:05
general is under appreciated. Like um
31:11
truth and stochasticity is so hard to
31:12
find. In a lot of ways you can actually
31:15
predict like I think a sign of greater
31:17
consciousness is ability to predict what
31:19
less lesser consciousnesses will do,
31:21
right? In which a predator can stalk a
31:23
prey and actually hunt it and then and
31:26
you know, acquire its its caloric
31:28
And I suspect that greater intelligences
31:30
will super forecast better than humans.
31:32
They will be actually able to say what
31:34
any human is is going to do without the
31:36
human even knowing it.
31:37
>> People are actually probably like a lot
31:38
easier to predict than we pretend,
31:40
right? This is what good leaders
31:42
understand is they they they forecast
31:44
>> There are also are these other
31:45
attributes that more than like
31:47
intelligence and capabilities that we
31:48
that that we seem to like care less
31:50
about evaluating but maybe should as it
31:53
affects our like day-to-day interactions
31:55
with the models like emotiveness or like
31:59
having good theory of mind like
32:00
understanding what resonates with an
32:03
Do you think like the labs need to
32:04
change how they do things to
32:06
to prioritize those? Do you think these
32:08
are important things to prioritize? I
32:10
>> I think they're already prioritizing
32:11
things like that. For instance, um
32:14
right now we see a pretty considerable
32:15
gap between Chinese open source models,
32:18
domestic closed source models, and
32:20
multi-turn environments.
32:22
Cuz a lot of the benchmarks in coding
32:23
today are just single turn. Um and so
32:26
the benchmarks Chinese models do very
32:27
well in those but when you translate
32:28
them to a back and forth conversation
32:30
with a human they they really fall
32:32
>> And like what about when the human says,
32:33
"Oh man, this sucks. I hate this
32:36
>> Yeah, then they really don't know what
32:36
to do. They've never seen that before.
32:39
but a lot of the US labs have seen that.
32:41
They've you know, here this quad code
32:43
was created, codex is created and so in
32:44
their desire to build better products,
32:46
they've built models that can sustain
32:48
longer user interaction sessions.
32:50
Um, and so they have evaluations and
32:53
benchmarks that allow them to hill climb
32:56
quality of responses and communication
32:59
But I think we need to do more on the
33:01
benchmarking side to independently test
33:02
that for the people trying to buy and
33:05
>> Ryan, we started this podcast to push
33:06
back on a lot of cynicism and pessimism.
33:09
Uh, what's your optimistic case for AI?
33:11
You're You're You're in the front lines
33:12
here. You're watching, you're measuring
33:13
all this stuff. You're creating the
33:14
things that you they have to hill climb
33:16
and measure them. Like what are you
33:17
seeing that folks outside of Silicon
33:19
Valley might not be seeing that makes
33:20
you feel good about the future?
33:22
>> Yeah, I mean there's a lot of fear
33:23
mongering going on but but I think from
33:25
from my seat I've a lot of reason to be
33:26
optimistic because it seems like people
33:31
I think there's a lot more opportunities
33:32
for coordination that people give credit
33:33
for. So you see that even the last week
33:36
the labs have come together and and kind
33:38
of aligned on this vision for embedded
33:39
evaluators and and even gone to the
33:42
White House and got an agreement with
33:43
Trump to kind of align on this
33:46
And I think on the enterprise side
33:47
there's a lot of push to adopt AI in a
33:49
meaningful way but they like to see the
33:51
assurances to make sure it's going to
33:52
amount to an ROI positive motive
33:54
adoption. I mean are you still
33:58
>> About about I mean I think 2030 is a
34:00
disinflation decade. I think that we can
34:02
use AI to kind of like overcome a lot of
34:06
like problems in a lot of different
34:08
people's lives specific to like them and
34:10
their family and their community that
34:12
that's holding them back and I think we
34:13
can help them unlock that cuz cuz you
34:14
have it's like personalized like best
34:16
coach ever to work with them. And so
34:19
everything's cheaper, everyone has like
34:21
personalized help. I think the thing
34:22
that's negative right now to me is like
34:24
there's like a billion people online and
34:25
social media from dysfunctional cultures
34:27
that's kind of making our populace go
34:28
crazy and these people all like have a
34:31
culture of envy and maybe they all like
34:33
hate Jews and others, and it's like it's
34:34
not good. So, there's like there's this
34:35
crazy populism that that's the negative
34:37
part. But, with the the things we could
34:39
do with AI to apply it to all of our
34:41
problems, both economic and some of the
34:43
cultural stuff, I think it's very
34:45
positive. So, so overall, yes, I'm very
34:47
optimistic. Of course, there are major
34:48
threats in the world.
34:49
>> Yeah, I think it's like an amplifier on
34:51
people who like mean well and who have
34:54
high agency. Right? Like, if you have a
34:57
bunch of like the people who have
34:58
benefited the most so far, like people
35:00
who have like lots of ideas of things to
35:01
do. Uh cuz they're like they have
35:03
creation at their fingertips. You can do
35:06
basically more things than you could
35:08
>> so much more than we ever could have
35:11
>> So, I I think that's my like
35:14
direction of optimism.
35:16
>> Yeah, I mean, I think it's interesting
35:17
cuz I interact with a lot of pessimistic
35:19
people. Um there's people at the labs
35:21
who who say things like, "It's going to
35:23
get a lot worse before it gets better."
35:25
Uh when I was out in DC, I think there's
35:26
a lot of people who are cynical about uh
35:28
kind of the external messaging of labs
35:30
and and the impact they see of data
35:32
centers and uh and the impact to the
35:34
average American. Um and and so, I've
35:36
been constantly pushed for being naively
35:38
optimistic. I think fundamentally I
35:40
choose to be optimistic because I know
35:42
the models and AI broadly are capable of
35:44
taking away a lot of the busy work
35:45
people don't want to do uh and unlocking
35:48
new forms of discovery uh that will
35:50
really advance the human condition. So,
35:52
I think when when I see this pessimism,
35:54
uh I kind of choose to believe that we
35:56
can find ways to coordinate around it.
35:58
>> That's right. I think everyone always
35:59
assumes that wherever we are in history,
36:01
like we've done most of the useful
36:02
science or physics or whatever, like in
36:04
the 1900 thing where there's no more
36:05
patents needed at the patent office,
36:07
right? And obviously, that would not
36:08
have been good to stop 125 years ago.
36:10
And I think you could still apply that
36:11
to today. We're probably right on the
36:12
verge of all sorts of important
36:14
discoveries that these models are going
36:16
to be able to make. They could just
36:17
unlock so many new things for the world.
36:19
So, I I I think it is kind of strange
36:20
how cynical and pessimistic people get
36:22
versus the idea that we have had
36:24
progress. It's very funny that they call
36:26
themselves progressives, but like like
36:28
very few people are actually progressive
36:29
in the sense that they're like for
36:30
progress and for the progress we had the
36:32
last 125 years doing that again. That'd
36:35
be amazing. I think we can potentially
36:36
do that all in the next 10 or 20 years.
36:38
So so I'm I'm really excited.
36:40
>> I think it's a point of really high
36:42
variance. I think the upsides are
36:44
considerable. There there are new forms
36:46
of risks that we really need to account
36:48
>> One of the things you're hopefully going
36:49
to measure and help us with as well.
36:52
>> Awesome. Well, thanks Ryan for joining
36:53
>> Thanks for having me.