This post
follows from an interesting discussion I’ve been having with Eliezer
Yudkowsky. He also pointed me to a
couple of interesting threads on Strong / Friendly AI, and Global Brains on
Steve Jurvetson’s blog, here, and here. I’d been thinking about this for a while, so here’s a rather long post
with those thoughts. Essentially, I’m
suggesting that the evolution of strong AI needs to be seen, literally, as evolution
– with consideration of adaptive behaviors in a co-evolving environment. What’s more, this is potentially a big evolutionary
change – but not the first. Other,
previous major evolutionary transitions cast significant light, I think, on how
this will happen.
Strong AI,
believers would probably agree, represents a significant potential step change in
the capability and complexity of the biosphere and its artifacts. But that description could apply to several
previous changes. These include the
appearance of life, RNA to DNA, pro- to eukaryotic cells, single to multi-cellular
life... and more debatably, significant human changes such as language,
agriculture, the limited liability firm. The book “The Major Transitions in Evolution” explores this in
detail. These changes all share several significant
characteristics. An important
observation on evolution in general – none of these changes was designed with the
end in mind. Each gradual step conferred
incremental advantages. But the result
was that the primary basis of selection shifted to more complex entities at a
higher level, i.e. aggregates of the entities that existed before. Those new aggregated entities were fitter in
the new landscape, and came to predominate (though this didn’t usually mean the
complete disappearance of the lower level forms). The increased complexity of the new entities
came from one of several different mechanisms – symbiosis being perhaps the
most important in most of these transitions. Initially what we see is increased reproductive success of the symbiotic
entities. Over time, two other important
changes gradually occur – an increased division of labor, and changes in
heredity, i.e. how the system is described for replication.
In summary,
what you see is an increasingly tight symbiotic coupling of existing entities
which, gradually, but at an accelerating pace, becomes the basis or platform
for an explosion of new, more complex forms.
Re Strong
AI, there’s been much discussion about what “recursively self-improving machine
intelligence” will look like. Well, look
around – it already exists. Not of course,
in the form that Strong AI purists are thinking of. But the lesson of evolutionary history is
that the messy, evolving, symbiotic cycles of self-improvement early on are the
place to look for the origins of the tightly-encoded future entities. So what is this recursive machine
intelligence cycle I’m talking about? Essentially, it’s the computer software and hardware business. Here are
some of the steps in that cycle:
- Sophisticated design and development tools running on powerful computers enable (employ!?) humans to produce a new generation of processors and software.
- Those processors and software replicate by competing for people’s and companies’ attention and dollars. The successful ones are more widely manufactured / installed.
- Increased “fitness” of these “phenotypes”, i.e. software products and computers with improved feature/function performance and “user-friendliness”, drives reproductive success. Increased demand at this level also drives demand for better, more powerful design tools.
- New design and development tools are developed (using and extending the existing software design tools). Typically, each successive generation allows greater abstraction, modularity, speed and flexibility.
But there
are humans involved, I hear you protest. The machines aren’t self-improving. Well, look at it from the “point-of-view” of the software. As a replicator, it doesn’t “need” to develop
certain capabilities when a supply of sufficiently capable and willing humans
is readily available. The evolutionary
history of increased division of labor would indicate that there’s not a
reproductive advantage for the software in developing those design capabilities
itself.
So what
does this imply for “real” strong AI? First, I think it implies that the space to be looking in is “prosthetic
intelligence” rather than “artificial intelligence” – what you might call
“machine symbionts” or “software prostheses”. These are in some senses just fancy terms for consumer and enterprise
technology products. However, I think
this mindset implies certain things about the nature of those technologies. One is that they will be intensely, and
increasingly individual – and tailored to their particular user (person, and
company if applicable). But they’ll also
be tightly tied to other, distributed parts of this symbiotic system – notably
other people and companies, via their respective software prostheses (see this
previous post). We’ll still have commercial
software – though perhaps more as components designed for configuration and
customization. Think of the human genome. Over half is shared with most other
living species, 95%+ with all primates, 99% all humans, and the small remainder
defines group, family and individual characteristics.
A further
key implication is that the interfaces with such software prostheses will be
fundamental – two, in particular, I think. One is the interface with humans; one is the interface with other
software (whether networked, or other locally-assembled components). The evolution of these interfaces is what will
enable tighter coupling, increased division of labor, and probably changes in
heredity. This will lead to the
emergence of strong AI that looks rather closer to what’s usually meant by that
term.
First, the
interface with humans. Although the
human brain is a wonderful and flexible thing, it’s wired in certain ways. Most
of the interface change is likely to come from machines communicating more and
more the way humans like. Developing a natural
language voice – the way we communicate with other humans – is a key step along
the way. As technologies for directly
interfacing with the brain improve, it will become “the voice(s) in your head”
(like schizophrenia, but in a good way). Ultimately, it will be little different from the way “other parts” of
the brain talk to one another. (I’m
deliberately implying here that distinguishing the machine piece from the rest of
the brain will become ever less meaningful). Subjectively, I suspect this will feel like a new level of human
consciousness, as much beyond humans today as we are beyond apes. Intriguingly, this may parallel the way human
consciousness originally arose. For more
on that, see Julian Jaynes’ mind-blowingly counter-intuitive book, (“The
Origin of Consciousness in the Breakdown of the Bicameral Mind”).
On a side
note, re “friendliness” of AI, it should be obvious that this type of
prosthetic intelligence is by definition friendly. “Symbiosis is the ultimate friendliness”, as Carl
Carpenter put it in a comment on Steve Jurvetson’s blog. “User-friendliness” is already a key design
requirement for technology to be successful. More profoundly, I’d suggest that our intuitive understanding of
“friendliness” is much more useful than any algorithmic or architectural
constraint. We consider a person “friendly”
– or a technology product “user-friendly” – based on repeated, positive
individual interactions. Increasingly,
with technology too, that means two-way interaction. “Friendliness” means, inter alia, getting to
know me. Someone (or something) being
friendly does depend partly on design (genes)… but also socialization. So in general, we can expect AIs (other
people’s software prostheses) to be no less – or more – friendly than other humans. For each of us, our own software prosthesis
or symbiont, will of course be very friendly to us indeed.
Second, the
interface with other software prostheses. It’s already clear to everyone that we live in a very networked
world. Our software prostheses (and
those of our businesses) will interact on our behalf with other people and
companies’ prostheses to do all the things we want them to. They will act as managers, secretaries,
research assistants, and teachers, to pick a few roles. Increasingly, they will evolve their own
languages for this communication (with some human help). Again, the clues can be found in what’s real
today. EDI and other transactional
communication automates routine interactions between many, mostly larger
companies. It’s still pretty much at the
“grunts and squeals” stage in terms of richness of meaning. As this example shows though, machine-to-machine
(or prosthesis-to-prosthesis) communication will be about a very different set
of subjects from those in human-to-human communication. Data already account for the vast majority of
Internet traffic. I’m not sure how much of this is machine-to-machine versus,
say, music downloads. But eventually, I
suspect, this machine-to-machine chatter will dominate. Over time, it will also explode in richness,
encompassing and extending the richness of human language.
I further
suspect that the notion of the “global brain” continues to emerge through this
process. Arguably, it already exists – the sum total of humans communicating,
recently much accelerated via the Internet. But the interactions between software prostheses – at machine speed, and
planetary scale – promise to accelerate this significantly further. (Steve Jurvetson and others talked in a comment to this post about this notion of acceleration through agent-based systems). Jeff Hawkins’ ‘memory-prediction framework’, as
described in his book “On Intelligence” shows, I think, how this might
happen. It makes a good start at
describing the specific types of messages that neuronal subsystems exchange in
recognizing and recalling patterns at all levels, and (intelligently) making
predictions. I think it’s reasonable to
suppose that such types of messages would become part of the message set, or
language, that’s developed for software prostheses to communicate. He seems to be thinking, again, in terms of
pure software implementations. But a
system where the individual software components are prosthetic symbionts able
to leverage the intelligence of “their” human or company should perform
significantly better. Again, here, from
the “point-of-view” of the distributed system, each subsystem is a black box –
it doesn’t “care” how they’re built, still less if a human is part of the
functioning of that subsystem. (Chinese
room, anyone?). The "group minds" this constructs probably exist at multiple scales. Companies probably already, supply chains may be a new type of group, probably others I've not thought of. Also, to the extent that software prostheses start making software component selection decisions on your behalf, that can become an accelerator on the clock-speed at which selection pressures can operate.
Does it
mean anything here to talk about “prosthesis-to-prosthesis” communication, as
opposed to just talking in more traditional terms of, say, B2B or app-to-app
(A2A) integration? I think it does. First, at any point in time, most of the
value in technology is tied up or embodied in some form of legacy
software. Anyone in IT knows this – or
come to that, any consumer who’s grappled with migrating applications and data
to a new PC. That’s not easily discarded
or replaced. But for the most part, they’re
not designed for this kind of seamless, networked integration. They have the interfaces they have, and
that’s just life (at least until the developer, and user, have compelling
reasons to change). Today, you can have
integration that’s deep, but point-to-point, and very costly. Or you can have connections that are broad, relatively
inexpensive, but without machine-to-machine integration at all. There’s not much in between.
This is in
some ways similar to the challenges the early Internet (well, ARPANet)
designers faced. A – arguably the – key
architectural innovation, was realizing that none of the mainframe owners
wanted the hassle of installing and running extra stuff on their system. The key was to develop a separate, uniform
networking box – a platform that could talk a single standards-based language
to all the other boxes. The messiness of
interfacing natively to the various legacy systems was kept contained to a
local “adapter”. (See “When Wizards
Stay Up Late” for more of this history). That platform was focused on a relatively narrow problem, just the most
basic plumbing layer. Of course, its
evolution into the Internet and the Web, is now all history. But all its splendid complexity, in
particular via globally-used used Internet applications, formed as additional
layers, most of them also relatively simple, on top of the uniform platform
created by previous layers.
The point
here is that for “intelligent” software prostheses in the future to behave as
described here, there are certain architectural implications. In particular, there are architectural implications
for creating the unified interface for interacting with humans, on the one
hand, and with other software, on the other. For the global, seamless, any-to-any communication between software
applications, it implies the need for a unified, global platform, separate from
but increasingly integrated with those applications.
The
second, machine-to-machine problem is essentially what my company, Traxian, is
solving - though my colleagues would barely recognize it from this
description. What we’re building today
is hardly “intelligent” at all, certainly not in the AI sense. It’s focused on solving a very narrow,
immediate set of problems for real, mostly smaller businesses in connecting
them to their trading partners. Our
customers would find the concepts here even more foreign. But again, in all the historical examples of these
evolutionary changes, that’s the way they happened.
Recent Comments