← 返回 AI 2040 首页

透明度计划

补充材料 · Supplement

Thomas Larsen

AGI projects face key decisions around transparency : who gets to see algorithmic secrets, who gets real time access to the datacenters sufficient to be confident in what they are doing, who gets to be aware of ongoing experiments and training runs, and with what latency. This document outlines our current thinking on transparency in the context of Plan A.

First, we discuss baseline transparency desiderata—aspects of transparency proposals that are core to Plan A. A fundamental component of Plan A is a trustless US/China deal to ensure that AI development is safe, which necessitates a minimal amount of US/China transparency, sufficient to verify that the other is following the agreement. ( more ).

Second, we give an overview of possible transparency regimes which can satisfy these desiderata. ( more )

Third, we give an in depth explanation of our favorite proposal, “total research transparency”. In this proposal, almost all algorithmic secrets, experiments, and training runs would be visible to the public immediately. ( more ).

Finally, we give an analysis of the tradeoffs between the different proposals outlined, and the reasons why transparency is beneficial. The main reason we recommend Total Research Transparency is because it would improve government and corporate decisionmaking during Plan A; which is our current most concerning failure mode. The second-most important reason is that it makes it much harder for corporations and governments to abuse their power. ( more ).

Baseline Transparency Desiderata

Any transparency proposal in Plan A should be consistent with the following desiderata:

Four Transparency Proposals

We have four viable candidates for transparency, each of which meet the above desiderata. Proposals #1-3 are further consistent with Plan A, while Proposal #4 only works for Plan S.

Proposal #1: Total Research Transparency. Nearly all AI research is fully transparent to the public, including AI algorithms, code, and documentation, for all frontier AI projects. AI model weights, significant fractions of the training data, and a small amount of other sensitive information is prevented from leaving the datacenters.

Proposal #2: Filtered Transparency. Nearly all AI research is done within a physical security boundary containing both the researchers and the compute. Within the security boundary, US and Chinese auditors have sufficient access to verify deals. Three things are allowed to leave the datacenter: (1) (partially redacted) reports approved by both sides about what is going on inside, (2) model weights that get sent to the inference datacenters, and (3) researchers themselves. One can vary the level of redaction: with minimal redaction, this proposal approaches Proposal #1, and with maximal redaction, this proposal is similar to Proposal #3.

Proposal #3: Algorithmic Security. It may be necessary to prevent the exfiltration of algorithmic secrets. This requires tightening the security boundary above: if people are regularly entering and leaving the AI datacenters, then they will almost certainly report back most of the algorithms to their governments. Similarly, filtered reports provide a channel for steganographically encoded versions of the model weights to be exfiltrated. Under this proposal, all frontier AI research is done in a secure datacenter with researchers and auditors located onsite and prevented from leaving or communicating any information out. Model weights are allowed to move from the R&D datacenters to the inference datacenters. This involves something like “handing off trust” to the auditors inside the datacenters, because so limited information is allowed to leave the datacenter that external actors cannot exert meaningful oversight internally.

Proposal #4: Shut it all down. Specifically, ban compute-intensive AI R&D. Under this proposal, there is no large-scale AI R&D, so there’s no need for AI R&D transparency. This could be enforced through compute declarations and physical inspections (but doesn’t require sharing digital access to the clusters, i.e. algorithms). This is similar to the MIRI proposal, and also what occurred for about 6 months during 2029 in the AI 2040 scenario.

This table summarizes the rough tradeoffs between them:

Proposal #1: Total Research TransparencyProposal #2: Filtered TransparencyProposal #3: Algorithmic SecurityProposal #4: Shut it all down
SL5 algorithmic secrets securityNoPartial, depends on redactionsMaybeN/A, no new algos discovered
Allows new training runsYesYesYesNo
How informed are public discussions of safety cases?VeryDepends on redactions.NoN/A, no new safety cases needed

In Plan A, we currently recommend Total Research Transparency for many reasons, chief of which is that the likelihood of reasonable analyses of safety cases is much higher if external researchers and the general public are able to critically analyze them. The main drawback relative to Proposals 2&3 is that there is less algorithmic security, and so algorithms will probably leak to covert projects. However, we think that SL5 algorithmic secrets security is incredibly difficult. Therefore, our main mitigation for algorithms leaking is to prevent new algorithmic secrets from being developed in the first place.

Total Research Transparency

In this section we’ll discuss a specific possible implementation of Total Research Transparency, which will correspond to the implementation done in Plan A.

The arrows in the diagram show the flow of information between humans, R&D datacenters, and Inference datacenters.

Under this proposal, there are two types of datacenters:

Information from the AI R&D Datacenters is organized as follows:

Anything that’s in the transparent internal database could end up in the transparent public database if anyone requests that information. However, what stops everything from leaving to the public database are upload limits that cap outgoing information to ~1 megabyte / second, as a layer of defense for the opaque information being exfiltrated (i.e., model weight exfiltration in particular). There is an ongoing auction for the outgoing bandwidth to allocate access, and all outgoing bandwidth is also copied to a freely accessible database on the internet. In practice, this means that almost all algorithms are immediately revealed to the public.

The R&D datacenters are still owned and operated by tech companies, like in today’s world. In fact each R&D datacenter is really a campus of datacenters, inside which several tech companies‘ datacenters are located. The US and Chinese governments, with their respective auditors and monitoring devices, ensure that each tech company’s datacenters on the campus create logs of their activities that go to the internal opaque database and the internal transparent database.

Anyone, including members of the public, can purchase compute inside the R&D datacenters and have the same level of access to frontier AI development as frontier AI company researchers. Members of the public can, for example, run experiments on intermediate model checkpoints, see loss curves during training, or ask an AI to run a desired analysis for them.

There are three risk tiers of inference:

High Risk and Lower Risk inference operates on the inference clusters, while Extreme risk inference occurs within the AI R&D clusters on a compute cluster that’s verified to be inference only.

All of the high risk trajectories and some of the non-ZDR lower risk trajectories are physically transported (under guard!) between the inference datacenters and the R&D datacenters in order to give safety researchers access.

Filtered Transparency

In filtered transparency, AI researchers are physically located within a security boundary, and we attempt to prevent information from leaking across this boundary. Then there are also auditors inside the R&D datacenters that have sufficient access to verify and make judgement calls about safety.

The three ways that information crosses out of the boundary are:

There’s no restriction on information crossing into the security boundary.

Like Total Research Transparency, there are R&D datacenters and inference datacenters. This allows for one of the most important forms of transparency: widespread access to frontier AI models. The main downside of filtered transparency relative to total research transparency is that it does not allow for fully open access and scientific scrutiny of the safety cases related to AI R&D. Instead we have to hope that the relatively small group of researchers inside the security barrier will be able to identify all the flawed assumptions of each safety case, make appropriate assessments, make sufficient research progress, etc.

Algorithmic security is similar to an extreme form of filtered transparency. The central idea is that algorithmic progress is allowed to be made in the project, but doesn’t leak outside. This is extremely difficult because algorithmic progress is often memorizable.

Therefore, the main difference is that for the “algorithmic security” proposal, it is necessary to prevent humans from crossing the security boundary. This enables us, in principle, to secure algorithmic insights.

When is each proposal desirable?

The main axis for deciding between transparency proposals for R&D is whether we are more concerned about possible covert projects, or poor regulation. Increasing transparency will result in more algorithms leaking, boosting covert projects, but improving public oversight of AI projects and increasing the expected quality of AI regulation.

Overall, we think that poor regulation is more concerning than covert projects, and so we recommend Total Research Transparency.

Proposal #4 does not allow for the development of new AI models, i.e. it only works as part of Plan S as opposed to Plan A. The decision about Plan A vs Plan S will mostly be made on other factors, which are discussed more in the Plan S branch .

What fraction of algorithms will leak under each proposal?

The optimal policy on this spectrum will depend on quantitative factors around how much algorithmic progress would leak under each proposal. This will depend on what fraction of algorithmic progress is of the type that would be transparent (e.g. architectural improvements) vs what fraction of algorithmic progress is large dataset improvements. Overall, we make the current (very rough) best guess estimates of the fraction that will leak under each proposal:

ProposalAlgo Fraction leaked
P1 Total~67%
P2 Filtered~47%
P3 Algorithmic Security~14%

You can see the reasoning behind this estimate here . We would be excited about security experts (which we are not) making their own forecasts; especially forecasts that are more granular (e.g., that include over what time period the algorithms leak).

Total Research Transparency Upsides

This section talks about the benefits of transparency for reducing loss of control risks and concentration of power risks. It’s basically an explanation of this diagram:

In the diagram, the two most important policy interventions of Plan A are described in blue. The two most important goals—preventing loss of control, and preventing extreme concentration of power—are described in green. Arrows represent causation.

This diagram is in some sense a summary of Plan A, except it’s biased towards depicting the benefits of transparency in particular.

We won’t talk through the entire diagram here. Instead we’ll talk through the seven depicted benefits of Total Research Transparency, plus an additional eighth benefit. For each one, we’ll talk about how weaker kinds of transparency would get similar (but weaker) benefits.

The development of AI will pose many problems, both foreseen and unforeseen. Increasing transparency into AI development will on average improve the level of public epistemics and understanding of what is going on.

Total Research Transparency Downsides

The main additional downsides of Total Research Transparency relative to Proposals 2&3 are:

Without the ability to do trustless verification, the main alternative is to rely on trust. Historical agreements have often relied on trust for enforcement (for example, the London Naval Treaty restricted the tonnage of military fleets, but did not include verification provisions). However, without verification, there is a much larger incentive to defect.

Concretely, we think that we will, at some point in the capability progression, get AIs that (1) can quickly design/build mirror life, (2) superpersuade/mindhack humans, and (3) quickly build self replicating nanobots/grey goo that grows fast enough to boil the oceans pretty quickly. The resilience response to these threats looks something like “no human ever goes outside, everyone lives in bioshelter bunkers, all info going in and out is moderated by a friendly AI, and a friendly drone swarm / nanobot army is outside protecting the bunker”, which would be (i) highly disruptive and undesirable to most people and (ii) take significant serial time to implement.

We think that it is technically viable to verify that an AI cluster is doing inference on a fixed model without the auditors being able to read the information going in and out of the model (e.g. the chatbot logs).

In the absence of improved privacy-preserving verification technology, this would involve something similar to Total Research Transparency within the security boundary; with improved verification technology, it could involve less transparency while still being sufficient to verify deals.

In the Plan A scenario we also do depict the implementation of Proposal #4 for a short period of time (from March to October 2029).

This is enforced via an inference-only retrofit, as explained in our verification supplement .

This verification also helps to prevent misuse and AI R&D assistance. This is covered more in our verification supplement .

This threshold is chosen to be high enough to allow for convenient access to the R&D clusters, but low enough to make weight theft difficult. The security rationale is discussed further below, in the Security supplement .

This happens automatically, because of the co-location of multiple companies’ datacenters

Under this proposal, then, what would the companies be incentivised towards? Well, they still own the model weights they train, and they still own their datacenters, their software products, etc. So they’ll compete to train the biggest models and teach them the most lucrative skills and serve them fastest in the most appealing UI and build up the most loyal userbase. Just like in other low-secrets industries, a company with good taste and rapid execution can overtake larger dumber competitors, stay ahead even as they scramble to copy them, and ultimately perhaps even build up a durable moat of infrastructure scale and network effects. That said, moats and profit margins will be smaller and AI will be much more of a commodity under our proposal than in the default world. We think this is a good thing.

Of course, this doesn’t solve the whole problem. For example, a defecting AI project may be able to conduct their research steganographically through the monitored input and output channel, or they may be able to undermine the cybersecurity that’s attempting to enforce the transparency requirements.