Description du poste
This is a linkpost for pacing-ai.com. I encourage folks to read it via the site (which has interactive graphs and expandables), but we’ve copied the text here as well.
We offer a concrete proposal for pacing the frontier.
1. Transparency: Verified Compute Allocation Disclosures (VCAD)
2. Reallocation: Shift compute away from capabilities R&D
The first component is Verified Compute Allocation Disclosures (VCAD): AI companies regularly disclose their compute usage, and an independent auditor verifies the disclosures. The second component is to reallocate compute away from capabilities R&D and toward other use cases, such as serving customers and safety research (non-capabilities R&D).
We roughly estimate that pacing via compute reallocation starting January 2027, with a 15% cap, would delay the intelligence explosion by a year. This is most likely insufficient to prevent AI takeover (or mitigate other problems created by RSI), and so this year should be used to implement a more durable policy regime such as Plan A or Plan S.
Nearly every approach to pacing, including ones built on safety and security requirements, strongly benefits from VCAD:
• Any pacing proposal that actually slows down AI development must do so either by reducing one of the inputs to AI development (such as training compute, experiment compute, or automated or human labor), or by implementing a safeguard that results in using inputs less efficiently (e.g., avoiding neuralese).• Something like VCAD is evidently needed for compute restrictions. For other input restrictions and safeguards, VCAD is highly desirable to prevent attacks of the form “don’t follow this restriction/safeguard on some compute, and hide or misreport that compute.”With VCAD, competitors and the public can trust a company that says it is pacing. As evidence of risk grows, this could enable a “race to the top”. If regulation later mandates pacing, a VCAD process that companies have already built and stress-tested makes that regula