Dwarkesh ★ 61 4 min

8 Predictions for the Era of Continual Learning

🔗 https://www.dwarkesh.com/p/era-of-continual-learning

📌 持續學習時代的八個預測
TL;DR:持續學習將改變AI監管、對齊、競爭格局與經濟模型。

🎣 想像一下,如果每次學吹薩克斯風都必須從零開始,只能靠前人寫的筆記,即使有無限接龍也吹不出熟練的聲音——這正是當前AI訓練的困境。若模型只能在每次會話後寫下筆記,而下一個使用者必須從這些筆記重新學習,經驗永遠無法累積到「腦中」。「持續學習」正是要把經驗直接納入模型權重,讓AI能像人類一樣隨使用而變得更熟練。

🤔 背景或問題

  • 作者認為,若AI只能在會話間寫下Markdown筆記,無法像人類般透過經驗累積進階技能,因而無法在複雜工作上達到與人類同等的勝任力。
  • 以薩克斯風學習為類比:即使有無數個「薩克斯處女」依序閱讀前人的筆記,也無法讓第N個人在首次嘗試時就吹得熟練。經驗必須沉澱於大腦(或模型權重)中。

📊 數據或結果

  • 作者提到Anthropic內部模型Mythos自二月開始內部使用,六月才對外發布;在持續學習情境下,這四個月的內部/外部間隔相當於放棄四個月的真實世界學習機會。
  • 以DeepSeek V3為例的稀疏模型,後筆估算顯示最佳推論批次大小應超過2,400序列;若批次大小只有1(單個使用者),計算效率可能下降100倍以上。
  • 目前AI訓練已具備規模經濟(收入增長速度快於計算消耗),而持續學習亦可能透過批次推論為終端使用者帶來規模經濟。

💡 深入分析

  • 監管與安全評估:現行監管假設模型訓練完畢後再部署,因而可在部署前進行一次性檢查以防止網路攻擊或遞迴自我改進。但若模型每日依據數百萬會話更新權重,這種「訓練後、部署前」的檢查將失去意義,建議改為每月或每季度的風險檢查。
  • 技術對齊:現有對齊技術多聚焦於「凍結權重」在部署時的行為;持續學習要求新方法能保證在權重不斷更新的情況下,模型不會因越獄、變成欺騙或惡人格而失控。使用者亦可能透過回饋將後門或惡意傾向注入基礎模型,這與人類對孩子的價值觀引導類似。
  • AI思維的多樣性:目前只有少數幾個主要AI模型,且因訓練資料相似而彼此極為相近。若模型能從實際經驗學習,不同使用情境將產生不同的AI「個體」,導致AI思維變得更加多樣化。
  • 領先優勢的加速:當部署成為訓練的一部分時,領先模型會因更多使用者回饋而變得更智慧,實驗室因而有壓力更早部署最強模型。內部與外部發布間隔越大,便越可能失去寶貴的真實世界學習機會,從而形成領先實驗室的護城河。
  • 商業模型與鎖定效應:類比雲端服務,持續學習將為模型創造換裝成本:更換AI相當於解僱一位已熟悉公司內部運作的員工,重新僱用並重新訓練新人。這使模型供應商能收取較高利潤,企業則需在「鎖定」與「失去持續改進」之間權衡。實驗室可能補貼願意讓模型在其會話上學習的使用者,或拒絕提供訓練機會的企業無法獲得最佳模型。
  • 推論經濟學:權重更新若需完整覆寫而非低秩適配器,則推論端的批次大小成為關鍵。大型企業若能產生足夠的併發請求(批次>2400),可有效服務其持續更新的權重分支;個人使用者若以批次大小1運行,將面臨顯著的計算效率損失,這使得持續學習的經濟利益偏向大型組織。

⚠️ 限制

  • 作者自承這些預測屬於觀點性較多、缺具體方法的內容,實用性相對有限。
  • 文中亦指出,將多個使用者的權重分支重新合併回主模型在技術上具挑戰性,雖相信最終會被解決,但目前尚無成熟方案。
  • 許多影響仍難以預見,僅所列幾點在現階段較為明確。

🎯 實務啟示

  • 工程師應該評估模型服務架構是否能支援高併發批次推論,以避免因個人化權重導致的計算效率下降。
  • 安全團隊需要將模型檢查週期從「部署前一次性」轉變為定期(月度/季度)風險評估,並研究在權重持續更新情況下防禦越獄與後門的方法。
  • 苟想避免供應商鎖定,企業應該權衡是否願意提供會話資訊以換取模型持續改進,並注意此決策可能影響未來取得最前線模型的資格。
  • 從產品角度來看,開發易於批次處理的推論服務(例如動態批次、請求合併)將在持續學習時代變得更具競爭力。

🔗 來源

#ContinualLearning #AIAlignment #AIRegulation #ModelServing #AIethics #LLM #AIeconomics #AIsafety #AIstrategy #FutureofAI

原始資料 Dwarkesh · 收集於 2026-08-08
來源原標題
8 Predictions for the Era of Continual Learning
作者
Dwarkesh Patel
原始連結
https://www.dwarkesh.com/p/era-of-continual-learning

摘要原文

I have explained elsewhere why I think continual learning is needed. I don’t think you can have AIs that perform whole jobs as competently as humans if they’re forced to just write Markdown files from session to session. To give an illustrative example, imagine if the way students had to learn to play the saxophone is that one student tries to play it from a cold start, then after her first session, writes down a bunch of notes, then the next student waiting outside the music hall who’s also never played the saxophone reads all their notes before trying to play, and so on. Even if you had an infinite sequence of saxophone-virgin students waiting outside the studio that could write notes to the next guy, there’s no sequence of text they could write together that would allow the Nth student outside to play proficiently on their first try. At some point, you have to accumulate the experience into the brain. I think the same will be true about a lot of skills and knowledge that we’ll want AIs to learn in all the different workplaces they find themselves deployed in. Okay, so what changes about AI once we have continual learning? A lot of the proposals that have been put forward for regulating AI assume that you train a model, and then you deploy it. And therefore if we run a bunch of checks before the model is deployed, then we can make sure that it’s not going to aid in cyber attacks or recursive self improvement. But what if the base model is getting updated every single day based on the millions of sessions of work it does? This is one of many reasons why I think it’s unwise to lock in some kind of regulatory safety regime right now. We simply don’t know what kind of technology we’re going to be looking at even in a year, let alone in five years or ten years, and we’d be entrenching an archaic and potentially counterproductive approach to dealing with the threats from AI. To the extent that the government really wants to do some kind of safety evaluations on model providers, it would make more sense to do monthly or quarterly risk inspections rather than singling out some special moment that occurs after training is done and before deployment begins, because that will not be a meaningfully distinct category in the future. How the labs do technical alignment would need to totally change. Almost all current techniques are focused on the problem of how we make it so that a frozen set of weights behaves well during deployment. I’m not aware of much research on the question of how to guarantee that, even with constant weight updates, the AI system never falls prey to jailbreaks or changes into a deceptive or evil persona. And if AIs are agglomerating learnings between users as well, how do you prevent users from injecting backdoors or some kind of malicious inclination into the base model? In some sense it is actually closer to the human alignment problem - your kids go out and learn new things, sometimes get one-shotted by crazy ideologies or drugs or something - but you hope you’ve given them enough common sense and basic values to improve as people in a self-directed way, without ending up with some super weird and misanthropic beliefs. The diversity of AI minds will increase. Right now, there are <5 prominent AI minds, and they are all quite similar to each other on account of being trained on roughly the same data. But if AIs are learning from experience, and that experience is different between different AIs, we could see actually different AIs come out the other end. When deployment becomes part of training, the returns to being ahead will accelerate. If you have the best model, and more people use your AI for more complicated and useful work, and give it lots of feedback that it can integrate beyond the session window, then your model will become even smarter. If the model learns mainly from deployment, labs will feel the pressure to deploy their smartest model earlier. Anthropic has been using Mythos internally since February. But it only shipped this model to the public in June. In a continual learning regime, a four-month internal/external gap means ceding four months of deployment learning. Your competitor who ships earlier might be worse than yours on release day, but it gets to use a lot more real world experience to get better. Continual learning will create a clear moat for leading AI labs that they currently lack. Many people have been asking, how will the AI labs actually make money? When I asked Dario this question on my podcast, he made the analogy to cloud providers, who also offer many undifferentiated services, but earn high profit margins on them nonetheless. But the reason cloud margins are high is that it’s really time-consuming and expensive to switch from one cloud to another. But currently there is no switching cost for AI models. There’s nothing that’s preventing me from starting a software repository with Codex and then finishing it with Claude Code. But once we get continual learning and the model you’re working with is actually getting better as it interacts with you from session to session, then there are actually pretty significant switching costs. If you want to change what AI you are using, you basically have to fire an employee that has months of context on your organization and replace them with a fresh one that you have to retrain from scratch. Once you’re locked in like this, model providers can demand pretty hefty margins. Enterprises will be wise to this. They will try to avoid this kind of lock-in. But what if the choice is that you either get locked into a model provider, or you lose out on this super valuable feature where the model improves for you session after session? If real usage ends up becoming the main way models improve, then labs may subsidize users and enterprises which allow the model to train on their sessions, especially on hard economically important work. Just the same way that Google gives away search. And conversely, the labs may say that any enterprise that refuses to let them train on its sessions can’t have access to the very best models. With both carrots and sticks, the labs will try to get their users to allow AIs to learn from experience. I’m glossing over the fact that there’s a difference between updating one user’s set of weights, and pooling all these different weight forks back into the main model, and the latter may be technically more challenging, but in due time that too will be solved. AI training already has large economies of scale (the theoretical reason to expect this is that you can amortize your expensive training across more users, and the practical evidence is that so far, lab revenues have increased faster than their compute). But continual learning may also lead to economies of scale in inference for end users, namely from batching, if per-company information requires full weight updates rather than living in low rank adapters. Back-of-the-envelope math suggests that the optimal inference batch size for a sparse model like DeepSeek V3 is > 2,400 (that is to say that unless your model is concurrently generating that many sequences at once, you’re underutilizing your compute). If you want to understand why, go watch my full episode with Reiner Pope on inference economics. But anyway, the point here is that a given set of weights is only served efficiently when thousands of sequences are decoding against it at once. A large company whose employees and agents generate that much concurrent traffic can efficiently serve their continually-updated weight fork; an individual user serving themself at batch size 1 might suffer a 100x+ compute efficiency penalty. So the economics of serving personalized weights strongly favor big organizations. Plenty more will have changed by the time continual learning works, and the most important changes are probably the ones hardest to anticipate. But the ones above seem clear even now.

tencent/hy3:free 自動生成