Reuel et al. map open problems by capacity (assessment, access, verification, security, operationalisation and ecosystem monitoring) across data, compute, models and deployment. Choose one cell and scope a project.
It is the most cited map of where technical people can help governance. Starting from it means your project plugs into a real need.
Output: A scoped project plan, then a first result.
Write your question in one sentence.
Spend 30 minutes finding what has already been written about it.
Collect evidence in a simple table: claim, source, how strong.
Draft 1–2 pages: answer first, then reasons, then uncertainties.
Ask one person to poke holes in it, revise, and share.
All steps done
Share what you made, then try another project. The PDF version has room for notes.
Neel Nanda’s list of 200 open problems grades each one by difficulty, including problems marked as good for beginners. Pick one, scope it down and investigate with TransformerLens.
Export controls target data-centre chips. But consumer hardware keeps getting better, and frontier-level performance reaches it within about a year. Update the analysis with the latest hardware.
Pick one verification mechanism, such as network taps, trusted execution environments, chip telemetry or satellite monitoring, and write a short, clear analysis of how it works and how it could fail.
