
MTS
2.9K posts







A lot of my friends and/or people I admire signed “Pacing the Frontier.” I think this was a bad move. My disagreement isn’t with the forecast or the framing of the coordination challenge, but with the immense and illiberal power the letter implies. There is no object called “the pace.” Progress at the frontier comes from compute, algorithms, data, post-training, inference, unattended task length, the spread of model weights, how researchers organize, and other things we haven’t invented and don’t yet know about. Inquiry leads to progress along dimensions that can’t be exhaustively specified in advance. That’s the nature of the frontier. If you gate compute, the research effort moves to algorithms. Regulate releases? Labs start taking things in-house. And other 2nd order effects will be unpredictable. Any rule that must pace the frontier involves ever-shifting proxies. It requires that its administrator has standing authority to continually redefine what counts as dangerous progress. What else is required beyond adaptive scope? The pacing regime would also need speed. One can’t successfully intervene on recursive self-improvement only after six months of legislation and litigation. It will require executive discretion. The pacing regime would also need under-the-hood access. Frontier progress is a process. The regime would need to see internal model use, training activity, compute infrastructure, and perhaps code -- proprietary and strategically sensitive information. And the thresholds couldn’t be fully public, lest they invite firms to game them. So some standards and evidence would remain secret. Insofar as the regime had to verify a rival state’s compliance, that would be an intelligence function. Restrictions would be triggered partly by evidence an affected company or researcher, or the public, could not inspect. Because this contemplated power cannot be bounded by a stable regulatory object (in the way, say, nuclear weapons can be), it would depend heavily on discretion, speed, internal access, and secret evidence. This has a highly illiberal character. Coercive power should be specific, limited, reviewable, and governed by general and knowable rules. Its characteristics (e.g., trigger, scope, evidentiary standard, duration, exceptions, means of review) should be stated before the power is granted. And the burden is on those who would propose it. A defender might answer that the proposed tool need not be coercive at all. That it could be narrow and advisory, focused on evaluation and transparency and readiness. But that wouldn’t solve the letter’s stated problem: racing. With race dynamics, each actor is under pressure not to slow down because others may continue (and thus the frontier keeps advancing). You need a mechanism to bind defectors. Voluntary norms tend to be great for binding people and firms that interact repeatedly and care about reputation. But the letter says each company and _country_… and you can’t rely on informal solutions when dealing with an unwilling state. That’s why the audience for this letter is Washington and why it calls for an international effort. Its diagnosis implies a binding mechanism. @deanwball thinks it is sensible to have a break-glass plan. That plan must involve a binding instrument, because nothing weaker addresses the problem the letter describes. But that therefore carries the burden for the use of coercive power, mentioned earlier. @johnschulman2's suggestion that labs design voluntary mechanisms among themselves is a different notion and coherent one (I would have signed that letter), but the word “country” makes this direction incompatible with the pacing letter. @OpenAI recently argued that a federal evaluator shouldn’t be able to block deployments. A week after, @AnthropicAI proposed that the government should be able to block deployments. Both labs endorsed the same letter. Whether or not the state may stop a deployment is a central question. Yet the letter accommodates both positions. What then, does the letter really say? Like the “We Must Act Now” letter from @erikbryn, @ajay_bcv, @akorinek, and @testingham before it, the letter secures agreement at an altitude where the main disagreement disappears. Lastly, the benefit of pacing is not established. The kind of slowdown the signatories have in mind would seek to buy us time for things like alignment, cyber defense, biological countermeasures, or scientific understanding -- things that increasingly depend on technologies a pause would restrict. E.g., Anthropic's framework relies in part on AI-based biological countermeasures and its security program uses AI to give defenders an advantage. A researcher in the letter's own friendly commentary was astonished at how much agents accelerated the work of the best alignment people he knows, and gave that as his reason for wanting six more months. When danger and our capacity to respond to that danger are plausibly both accelerating, the relevant question is whether this relationship is asymmetric in a safety-improving direction at the level of real-world risk. A slowdown needs to differentially slow the production of danger vs. our capacity to understand and contain that danger. The letter doesn’t attempt to establish that. It treats slower and safer as though they are the same; they are not. The letter is a serious warning, but it is no good as a warrant for an undefined power over inquiry.


View of Starship in space from a Starlink V3 satellite on Flight 13. This composite is made of imagery from four separate cameras on a single satellite. Six of the satellites were equipped with cameras to scan Starship’s heat shield and transmit imagery down to operators to continue testing methods of analyzing Starship’s heat shield readiness for return to launch site on future missions

New blog post on what would be true about the world if trendline continues and leading lab hits $1T in revenue by the end of next year. In other words, why compute might get 10x+ more expensive in coming years dwarkesh.com/p/why-compute-…

@Jason @Dell @nvidia @Apple Over 90% of AI compute will be in server-side for the next few years. Long-term, 99.99…% of compute will be in space.



Prediction We will have Claude Code + Opus 4.5 quality (not nerfed) models running locally at home on a single RTX PRO 6000 before the end of the year

SITUATION EXPLAINED: Leopold Aschenbrenner lore. • Born and raised in Germany by two doctors, educated at the John F. Kennedy School in Berlin • At 14, he spoke at the German Green Party's national conference, in 2016 • He warned that nearly 2 million German drivers and truckers faced automation within years • His proposal, at 14, was universal basic income, years before Andrew Yang made it mainstream • Enrolled at Columbia at 15, graduated valedictorian at 19 in economics and mathematics-statistics • At 17, he co-authored "Existential Risk and Growth" with Philip Trammell, now head of economics at Epoch AI • Tyler Cowen publicly flagged the paper as remarkable at the time and gave him one of the first Emergent Ventures grants • In February 2022 he joined the founding team of the FTX Future Fund, alongside Will MacAskill • Also on that team: Avital Balwit, now his wife and Dario Amodei's chief of staff at Anthropic • FTX collapsed nine months later, after the fund had already made $100 million in grants • He joined OpenAI's Superalignment team as a founding member in July 2023, under Ilya Sutskever and Jan Leike • He was fired in April 2024 over an alleged leak, which he disputes, saying it followed warnings he raised about OpenAI's security practices • Weeks later he published the 165-page "Situational Awareness," dedicated to Ilya Sutskever • He founded Situational Awareness LP that same year, with anchor investments from Patrick and John Collison, Nat Friedman, and Daniel Gross @theojaffee: "Leopold Aschenbrenner went to Columbia at the age of 15 and got into effective altruism and longtermism. He founded Columbia's University EA chapter. I know some people who knew Leopold at Columbia, and he was always sort of on the ball. He was always, like, very smart and very goal-directed."


It's coming. @Hailuo_AI #MiniMaxH3

🚀 DeepSeek-V4-Flash Official API is now LIVE in public beta! 🔷 We’ve massively upgraded its Agent capabilities—benchmark scores are now far surpassing the V4-Pro-Preview. Check out the massive performance leap below! 👇 🔷 The official V4-Flash now natively supports the Responses API format and is fully adapted for Codex! Check out the configuration details in our official API docs: api-docs.deepseek.com/quick_start/ag…