AI Lab employee or leader
A lot of the key information about how frontier models are developed and deployed is housed within the AI labs; this makes them a natural place for AI verification work to take place.
Plan A Verification
Kick-start coordinated work on verification technologies and standards:
- Initiate industry conversations on Plan A verification techniques. One option would be to use the Frontier Model Forum as a place to start inter-lab conversations.
- Publicly announce the intention to work on AI Verification. Even simple public statements can encourage and accelerate other people’s AI verification work.
- Run an external grant or venture funding programme to accelerate the AI verification field. Less than $15M has been spent on AI Verification technologies; even small increases in the available funding will accelerate the field. AI labs have a lot more talent reach than some other funders, and such a funding round would be a call to action for top talent.
AI labs can directly support technical AI verification R&D, both by running internal projects and by working with outside research groups.
- Create an initial internal demo of inference verification (e.g. re-implement this demo on your stack with relevant frontier models)
- Start an AI verification research track inside your lab. Research projects could be pulled from the list of technologies described in Plan A.
- Give feedback on technical plans being developed by outside research groups.
- Support joint verification experiments, including AI verification red-teaming exercises.
Ultimately, Plan A will require the cooperation of AI model developers, and the engineers and researchers at AI labs are likely to be involved in implementation. Gaining familiarity with and accelerating the tech readiness of AI verification technologies will help Plan A succeed.
Further Verification projects
Any verification project should start with the question: what claim are we trying to verify? An initial exercise for any AI model developer could be to answer these questions internally:
- What existing commitments from AI developers (RSP, Frontier Safety Framework, Preparedness Framework) would be useful to verify?
- What would reassure one AI developer that another developer is following best safety practices1?
- What information can be unilaterally disclosed now that might support future high-stakes coordination?
- What training and deployment practices should be considered “unsafe”?
- What capability thresholds might be worth gating?
Working through these questions and, if appropriate, releasing the answers publicly would help start to give direction for technical AI verification projects and near-term verification goals.
If any of this is of interest, email us. We can help fill out these recommendations in more detail and make them more suitable to you.
- “But to the extent that other relevant AI developers … prioritize safety and invest in legible demonstrations that they are doing so—as we intend to—commitments like this may help avoid an inadvertent “race to the bottom” on safety.” Anthropic RSP — Appendix A ↩