Who is the intended audience for this document?
Every smart person who is fairly persuaded to care about AI risk and then asks us, "Okay, so what's the technical research agenda?" This is a lot of people.
what's the community in which you hope to publish this?
It doesn't matter much. It's something we would email to particular humans who are already interested.
Why is Eliezer-time measured in months, and Luke-time in hours?
See here.
Do you expect to involve folks who haven't previously been involved with SIAI? If so, when?
Possibly, e.g. domain experts in micro-econ. When we need them.
How large a research team / author list would you expect the final version to have? Is fairly large "5" or "15"?
My guess is 10-ish.
Series: How to Purchase AI Risk Reduction
When I was hired as an intern for SI in April 2011, one of my first proposals was that SI create a technical document called Open Problems in Friendly Artificial Intelligence. (Here is a preview of what the document would be like.)
When someone becomes persuaded that Friendly AI is important, their first question is often: "Okay, so what's the technical research agenda?"
So You Want to Save the World maps out some broad categories of research questions, but it doesn't explain what the technical research agenda is. In fact, SI hasn't yet explained much of the technical research agenda yet.
Much of the technical research agenda should be kept secret for the same reasons you might want to keep secret the DNA for a synthesized supervirus. But some of the Friendly AI technical research agenda is safe to explain so that a broad research community can contribute to it.
This research agenda includes:
The goal would be to define the open problems as formally and precisely as possible. Some will be more formalizable than others, at this stage. (As a model for this kind of document, see Marcus Hutter's Open Problems in Universal Induction and Intelligence.)
Nobody knows the open problems in Friendly AI research better than Eliezer, so it would probably be best to approach the project this way:
Estimated cost: