For background and context, see my related series of posts on an approach for AI Safety Movement Building. This is a quick and concise rewrite of the main points in the hope that it will attract better engagement and feedback.
Which of the following assumptions do you agree or disagree with? Follow the links to see some of the related content from my posts.
Assumptions about the needs of the AI Safety community
- A lack of people, inputs, and coordination is (one of several issues) holding back progress in AI Safety. Only a small portion of potential contributors are focused on AI Safety, and current contributors face issues such as limited support, resources, and guidance.
- We need more (effective) movement builders to accelerate progress in AI Safety. Utilising diverse professions and skills, effective movement builders can increase contributors, contributions, and coordination within the AI Safety community, by starting, sustaining, and scaling useful projects. They can do so while getting supervision and support from those doing direct work and/or doing direct work themselves.
- To increase the number of effective AI Safety movement builders we need to reduce movement building uncertainty. Presently, it's unclear who should do what to help the AI Safety Community or how to prioritise between options for movement building. There is considerable disagreement between knowledgeable individuals in our diverse community. Most people are occupied with urgent object-level work, leaving no one responsible for understanding and communicating the community's needs.
- To reduce movement building uncertainty we need more shared understanding. Potential and current movement builders need a sufficiently good grasp of key variables such as contexts, processes, outcomes, and priorities to be able to work confidently and effectively.
- To achieve more shared understanding we need shared language. Inconsistencies in vocabulary and conceptualisations hinder our ability to survey and understand the AI Safety community's goals and priorities.
Assumption about the contribution of my series of posts
I couldn't find any foundation of shared language or understanding in AI Safety Movement building to work from, so I created this series of posts to share and sense-check mine as it developed and evolved. Based on this, I now assume:
- My post series offers a basic foundation for shared language and understanding in AI Safety Movement building, which most readers agree with. I haven't received much feedback but what I have received has generally been supportive. I could be making a premature judgement here so please share any disagreements you have.
Assumption about career paths to explore
If the above assumptions are valid then I have a good understanding of i) the AI Safety Community and what it needs, and ii) a basic foundation for shared language and understanding in AI Safety Movement building that I can build on. Given my experience with entrepreneurship, community building, and research, I therefore assume:
- It seems reasonable for me to explore if I can provide value by using the shared language and understanding to initiate/run/collaborate on projects that help to increase shared understanding & coordination within the AI Safety Community. For instance, this could involve evaluating progress in AI Safety Movement building and/or surveying the community to determine priorities. I will do this while doing Fractional Movement Building (e.g., allocating some of my productive time to movement building and some of my time for direct work/self-education).
Feedback/Sense-checking
Do you agree or disagree with any of the above assumptions? If you disagree then please explain why.
Your feedback will be greatly valued and will help with my career plans.
To encourage feedback I am offering a bounty. I will pay up to 200USD in Amazon vouchers, shared via email, to up to 10 people who give helpful feedback on this post or my previous posts in the series by 15/4/2023. I will also consider rewarding anonymous feedback left here (but you will need to give me an email address). I will likely share anonymous feedback if it seems constructive, and I think other people will benefit from seeing it.
Are you aware of Alignment Ecosystem Development? They have a list of potentially high impact community building projects. If anyone want to volunteer some time to help with AI Safety community building, you can join their discord.
Regarding how to prioritise. I would be very worried if there where a consensus around how to rank what projects are highest priority, that would more likely be groupthink than wisdom. I think it's much healthier for everyone form their own opinion. The sort of coordination I would like to see is different community builders getting to know each other and knowing about each others projects.
Fractional Movement Building is a good idea. I'm doing this my self, and the same is true for about half of the AI Safety community builders I know. But I would not prescribe it as a one-size-fits-all solution. I am also not claiming that you are suggesting this, it's unclear to me how far you want to take this concept.
You write about the importance of a shared language. This sems useful. Although if you want to contribute to this, maybe create a vocabulary list? In the section about shared language in you previous post you wrote:
However, your posts are really long. I'm not going to read all of them. I only read a few bits of your previous post that seemed most interesting. Currently I don't know what vocabulary you are proposing.
Also regarding shared vocabulary, I'd be exited about that if and only if it doesn't become too normative. For example I think that the INT framework is really good as a starting point, but since then has become too influential. You can't make a singel framework that captures everything.
In your previous post you also write
I know you are just describing what other people are saying and thinking, so I'm not criticizing you. But other than the last question, these are the wrong questions to ask. I don't want community builders to ask what projects are generally considered good, I want them to ask what projects are good. Also, focus on evaluation early on seems backwards. Uncertainty about funding is a real issue though. It might be tempting to focus on the community building that is most ledigble good, in order to secure a career. But I think that is exactly the road that leads to potentially net negative community building.
Thanks for the thoughts, I really appreciate that you took the time to share them.