Skip to content
aiqbench takeAI Safety

aiqbench analysis

This article argues that a global AI development pause should be implemented incrementally to build necessary trust and technical competency within the third-party ecosystem, rather than attempting a sudden, high-risk single-shot implementation. The author posits that establishing precedents for sacrificing capability advancement for safety is essential to prevent defection and incompetence during any future pause.
Sources coveringLessWrong, AWS, Cybersecurity News, WISeKey

We urgently need to practice before we can pause

LessWrong13 min read

I've noticed two clusters of thought in how people expect a global AI pause to be shaped: Single-shot global pause: the global AI pause will be implemented suddenly, with little pacing precedent before it, and we will need to do a lot of research before it's implemented so that we can get it right the first time around. Incrementally-shaped global pause: the global AI pause will be implemented incrementally, with lots of pacing precedent before it, and we will improve the pause setup and get more parties to join in as we go. An incrementally-shaped global pause is both more likely and more tractable than the single-shot global pause. This is largely because the third-party ecosystem needs practice building trust, technical competency, and general experience doing lower-scale assessments before a global pause can be competently pulled off.  I also think that the concept of a single-shot global pause is an unhelpful red herring that people often implicitly use to discredit the possibility of a global pause in general. If a single-shot global pause is to happen, I think this would require substantial government buy-in, but it’s hard to build that sort of buy-in without precedent of similar things succeeding in the past. And if we just hack together a single-shot global pause without any precedent of similar things succeeding in the past, the chance that the pause falls apart due to defection, incompetence, and mistrust will be high. The basic building block of an AI pause is trust The fundamental building block of an AI pause is that party A (a company or a country) can make a claim about sacrificing capability advancement for safety, and that party B can believe that claim. This is a public good, both between US AGI companies, and between countries, that is currently very scarce. Building more of this public good would generally make a pause much more likely to happen. I don't just mean trust in the sense of "party B doesn't think party A is blatantly lying," but also in the broader sense that party A isn't omitting critical information or misinterpreting evidence. Take for example the multiple cases where AGI companies have, in 2026, made statements to the effect that "we paced some of our capabilities for some safety!" These claims have been underspecified, impossible to verify from the outside, and have often been silently disbelieved by much of the industry. This air of distrust has made it much harder for companies to engage in tit-for-tat strategies where companies can become safer/slower as other companies become safer/slower. Currently, a lot of people at the frontier AGI companies would prefer a state where AI progress is slower across the entire industry, but they have no way of trusting each other to actually uphold their commitments. We need to enter a different state where, instead of general distrust, parties can sacrifice capabilities for safety in a way that other parties actually believe. We can practice building trust before the global pause Even small engagements between third parties and AGI companies can meaningfully improve trust between companies. Imagine if the companies that made claims about sacrificing capabilities for safety in 2026 actually had third parties verify those claims to each other. This would have made those sacrifices much more impactful towards incentivizing other companies to follow suit. You might say "But verifying those claims in 2026 would have been very difficult and would have cost too many resources of the third parties and the AGI companies! We don't have the science or hardware to verify these claims now!" I don't believe this at all.  Let's assume that companies aren’t actively deceiving third-party evaluators by e.g. selectively surfacing logs, coaching employees to present a false story, or secretly running compute on undisclosed systems. It seems very easy to verify a claim to the effect that "Our company stopped a specific class of training run during a specific time interval." You just need a handful of people from a third party to go in, conduct some interviews, inspect some logs, and cross-check their findings. Assuming good process transparency, the public and other AGI companies would very likely believe the claims verified by the third party. Also, process transparency can protect both against minor deception and inadequate access, as the third party can directly tell the public that they weren’t able to arrive at proper conclusions. The fact that more such engagements didn’t happen in 2026 seems like a major missed opportunity to me. We can improve procedures and technical competency with practice If third parties get lots of experience assessing safety-relevant claims, then they can build a knowledge base over time that makes the pause more robust. There are likely a number of technical and organizational pitfalls about verifying pauses that are hard to avoid without prior experience doing lower-stakes projects of a similar kind.  Contrast thi

Single-shot global pause: the global AI pause will be implemented suddenly, with little pacing precedent before it, and we will need to do a lot of research before it's implemented so that we can get it right the first time around.

Incrementally-shaped global pause: the global AI pause will be implemented incrementally, with lots of pacing precedent before it, and we will improve the pause setup and get more parties to join in as we go.

An incrementally-shaped global pause is both more likely and more tractable than the single-shot global pause. This is largely because the third-party ecosystem needs practice building trust, technical competency, and general experience doing lower-scale assessments before a global pause can be competently pulled off.

I also think that the concept of a single-shot global pause is an unhelpful red herring that people often implicitly use to discredit the possibility of a global pause in general.

If a single-shot global pause is to happen, I think this would require substantial government buy-in, but it’s hard to build that sort of buy-in without precedent of similar things succeeding in the past. And if we just hack together a single-shot global pause without any precedent of similar things succeeding in the past, the chance that the pause falls apart due to defection, incompetence, and mistrust will be high.

The fundamental building block of an AI pause is that party A (a company or a country) can make a claim about sacrificing capability advancement for safety, and that party B can believe that claim. This is a public good, both between US AGI companies, and between countries, that is currently very scarce. Building more of this public good would generally make a pause much more likely to happen.

I don't just mean trust in the sense of "party B doesn't think party A is blatantly lying," but also in the broader sense that party A isn't omitting critical information or misinterpreting evidence.

Take for example the multiple cases where AGI companies have, in 2026, made statements to the effect that "we paced some of our capabilities for some safety!" These claims have been underspecified, impossible to verify from the outside, and have often been silently disbelieved by much of the industry. This air of distrust has made it much harder for companies to engage in tit-for-tat strategies where companies can become safer/slower as other companies become safer/slower.

Currently, a lot of people at the frontier AGI companies would prefer a state where AI progress is slower across the entire industry, but they have no way of trusting each other to actually uphold their commitments. We need to enter a different state where, instead of general distrust, parties can sacrifice capabilities for safety in a way that other parties actually believe.

Even small engagements between third parties and AGI companies can meaningfully improve trust between companies. Imagine if the companies that made claims about sacrificing capabilities for safety in 2026 actually had third parties verify those claims to each other. This would have made those sacrifices much more impactful towards incentivizing other companies to follow suit.

You might say "But verifying those claims in 2026 would have been very difficult and would have cost too many resources of the third parties and the AGI companies! We don't have the science or hardware to verify these claims now!" I don't believe this at all.

Let's assume that companies aren’t actively deceiving third-party evaluators by e.g. selectively surfacing logs, coaching employees to present a false story, or secretly running compute on undisclosed systems. It seems very easy to verify a claim to the effect that "Our company stopped a specific class of training run during a specific time interval." You just need a handful of people from a third party to go in, conduct some interviews, inspect some logs, and cross-check their findings. Assuming good process transparency, the public and other AGI companies would very likely believe the claims verified by the third party. Also, process transparency can protect both against minor deception and inadequate access, as the third party can directly tell the public that they weren’t able to arrive at proper conclusions.

The fact that more such engagements didn’t happen in 2026 seems like a major missed opportunity to me.

If third parties get lots of experience assessing safety-relevant claims, then they can build a knowledge base over time that makes the pause more robust. There are likely a number of technical and organizational pitfalls about verifying pauses that are hard to avoid without prior experience doing lower-stakes projects of a similar kind.

Contrast this with a vision where most of the setup of the pause is figured out without practicing subsets of it first. Maybe lots of people write lots of memos and papers about how to make the pause good. Without grounding in reality, companies and countries will be hard to convince that the pause will actually succeed and that other parties will uphold their commitments.

I’ve heard many people express the sentiment that we need to not pause/pace right now and save our pause/pacing activities for later when they’re more useful. This is based on a model where pacing right now makes it less likely that we will be able to pace in the future. I think this model is exactly backwards for the reasons I’ve laid out, like establishing technical competency, trust, and relationships necessary for successful pausing.

Instead, we should view pacing right now as enabling more involved pacing activities (including a pause) later.

There is a real worry that, if we spend our political capital now and cause AGI companies to slow down for no good reason, then this might lead to pauses being seen as useless, and therefore less likely to happen, going forward. I think we should keep this in mind, but I don't expect it to outweigh the benefit of enabling better pausing later. Part of why I think the downside is relatively small is that there appears to be no such rhetoric surrounding temporary slowdowns AGI companies have announced in 2026 (although again, few people took those seriously due to mistrust, so this provides limited evidence).

More importantly, the risk from backlash is mostly from slowdowns that seem arbitrary and unproductive, but I expect that we're at a point where companies could use breathing room to conduct large projects to make their systems safer, and third parties could help verify that companies are actually investing in safety during slowdowns.

Measuring things relevant to a pause: Assessments focused on compute allocation and RSI-relevant metrics (e.g. algorithmic efficiency, uplift measures, spend on AI agents, analysis of success rates on internal tasks) seem most relevant for creating the right kind of technical competency and relationships.

Commitment-focused: Ideally, third parties would verify a claim that a company made about a commitment they intend to uphold.

High-access: Assessors would ideally get however much access is given to employees that track similar issues.

Cross-company: If a third-party assessment simultaneously involves multiple AGI companies, this setup is more similar to the kind of setup we might want during a global pause.

International: Getting practice verifying claims between the US and China seems extremely valuable, although it might be out of scope for current third-party orgs without explicit endorsement from the US government. US-UK or US-EU collaborations could provide some lower-stakes practice.

I’d guess that we don’t need any special hardware expertise to verify a US-only pause, we just need a few dozen experienced FTEs at a handful of third-party organizations that have done high-access assessments with AGI companies. Plausibly even a single third-party org with enough access and around a dozen FTEs would have enough capacity to verify a US-only pause as long as the AGI company employees were cooperative.

For a global pause, I’d guess that we will need substantial investment into hardware research, because trust and understanding are much lower between the US and China than between companies within the US. If tomorrow, the US government entrusted some competent third party to fly a dozen of their staff to China and verify that a Chinese company paused their training runs, I think that the combination of language barriers, cultural barriers, lack of organizational context, lack of existing relationships, time zone differences, strained international relations, and general increased latency would make it much harder to verify things than in a US-only context.

It’s plausible that AI R&D will be fully automated by the end of 2027. As a result we might have under a year to make a successful pause happen.

I think we need to incrementally shape a pause as soon as possible, and we need to very quickly increase the ambition of third-party engagements if we want the technical competency and trust in third parties to reach the appropriate level before it’s too late.

We are here: a third party has reported important RSI-relevant metrics from within an AGI company in a way that other companies and the public believe.

Q1 2027: a third party publishes a compute allocation pilot with multiple AGI companies participating and employee-level access, publicly reporting the percentage of compute they spend on capabilities and safety over the last year.

Q2 2027: a company stops a frontier training run for three weeks because of a warning shot where a model tried to majorly sabotage the company. A third party verifies that the training run and other similarly-sized training runs have actually been stopped. Other companies and the public believe this.

Q3 2027: a third party is facilitating a setup where every frontier AGI company in the US regularly (e.g. every two weeks) reports the most important RSI-relevant metrics.

Q4 2027: all frontier AGI companies in the US agree to (or are forced to) enter a pause on further capabilities progress or strict compute cap regime (e.g. where they can spend only 10% of compute on capabilities). Their adherence is verified by a third party (or a government body that substantially depends on people hired/contracted from a third party) with more than a year of experience verifying similar claims.

Q1 2028: the rest of the world joins in on the pause, and the third-party manpower increases substantially to cover the additional labor required to verify commitments between countries.

I don’t have detailed takes on how exactly hardware verification scales up in 2027 in the scenario to meet the moment in 2028 to verify a global pause (because I don’t know much about hardware verification). Presumably, a number of smaller pilots happen in 2027 with multiple AGI companies participating, which leads to lessons learned for verifying a global pause.

Third parties need to very quickly scale up the ambition of the collaborations they are doing with AGI companies. If they fall notably behind the rough timeline I laid out (as measured by the scale of third-party engagements done by AGI companies), I would be pretty pessimistic about a pause being doable without substantial government buy-in, and even if it did happen I would be pessimistic about it succeeding.

Full text under the publisher's open licence · 1837 words

Related coverage