Some hopefully-unnecessary background info for people attempting this task:
A description of corrigibility Eliezer wrote a few months ago: “‘corrigibility’ is meant to refer to the sort of putative hypothetical motivational properties that prevent a system from wanting to kill you after you didn’t build it exactly right”.
An older description of “task-directed AGI” he wrote in 2015-2016: “A task-based AGI is an AGI intended to follow a series of human-originated orders, with these orders each being of limited scope”, where the orders can be “accomplished using bounded amounts of effort and resources (as opposed to the goals being more and more fulfillable using more and more effort).”
Some hopefully-unnecessary background info for people attempting this task:
A description of corrigibility Eliezer wrote a few months ago: “‘corrigibility’ is meant to refer to the sort of putative hypothetical motivational properties that prevent a system from wanting to kill you after you didn’t build it exactly right”.
An older description of “task-directed AGI” he wrote in 2015-2016: “A task-based AGI is an AGI intended to follow a series of human-originated orders, with these orders each being of limited scope”, where the orders can be “accomplished using bounded amounts of effort and resources (as opposed to the goals being more and more fulfillable using more and more effort).”
Also:
Being able to change a system after you’ve built it.
(This also refers to something else—being able to change the code. Like, is it hard to understand? Are there modules? etc.)