[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"report-2026-06-14":3,"A21zqm1Do6":610,"hGUBonsJpu":625,"yq5v3TLSqy":635,"ia87aWG90x":645,"fy97cMokKD":655,"xgmiMOZtz7":796,"mJuBpckwf7":847,"lSwANcLHd0":888,"lEt6gT1wHX":904,"lxmaOFcvIv":938,"deN3E0sLz2":989,"OHu4sG0XWy":999,"P3YEMVB0UE":1009,"oduwtoe5y4":1019,"Bt4SkVWDXc":1029,"D83HbTOkTP":1039,"Hk8KIKt5Xo":1049,"M02hxQVGtE":1059,"sY6GfrWRmw":1069,"MC0PfqY7BM":1079,"Ftt991PTWT":1089,"9b1eCngveD":1099,"XUfVQJSJUg":1109,"cdY7Nl5zQo":1232,"UpzyPWORgd":1248,"2fSSHfHbiE":1264,"gZcrMCdDFa":1295,"BgbeYEeRxe":1355,"BijADEV0JQ":1396,"M4j1TsfO4j":1406,"CVV8Jm94Wy":1416,"A571URozSR":1426,"eDaeoYhME6":1436,"qMBGs345aH":1446,"GTmdycsYxZ":1456,"lgTxiHCXV8":1556,"narixn6nHd":1567,"3uAcxrFcUP":1578,"SJFvixf2LV":1626,"6mteJY4dg3":1652,"njRispmlqA":1781,"APu4AHv0aU":1835,"79xkQ7pwtH":1856,"KqkjJgOUEd":1873,"6mqDkp7hnp":1883,"rS9jLW1DsW":1893,"hNiGUdKwEp":1903,"WTluZjzcsL":1913,"9gG29G1jXP":1923,"34Tp2Fz2X4":1933,"1xRUaNRHSN":1943,"yuQiayFaqI":2090,"5ksVEFs9uR":2101,"pbrnacUQAL":2112,"dv7FDqdyEL":2143,"PEljt8Ou7Y":2169,"zBIvZjPLEe":2284,"KG5uwZDa99":2407,"hVC7XLXlXM":2432,"OKklKudVWO":2449,"UOq2DwsrXx":2459,"9If0onkdzN":2469,"9l2y8Y8GfZ":2479,"m6RZjP6nl6":2540,"40fh0wKHJa":2559,"vhmPLjz4Fo":2569,"er0TcCLBqI":2621,"uaHvviWfye":2669,"F4JdUDrvag":2688,"TP4Fn3AyjU":2698,"0wpgPlrzXU":2786,"VSOxWPr7X0":2796,"VbWStcE7af":2806,"dYUtg5QpSG":2835,"upWtffEtHE":2883,"fwnzbzhfZs":2893,"tfD7VlhTg7":2912,"pxnXPOnbhl":2955,"GEibDvT4wd":2965,"Ojx9N8BxNU":2975,"JGDKaeYPmE":3042,"UTq7aPNP7e":3063,"qiZcAzx7Q8":3079,"vhjcPToRFx":3136,"JDULF5rlN1":3177,"ZUSRS1DTsR":3187,"8aiRf08wPd":3197,"SoedO8Wyvg":3259,"n16wZvlrOZ":3269,"SNCgQ4Mw8l":3279,"MTYI3g1cOR":3324,"vV94TPRcHp":3391,"ZAigztnG8U":3412,"qHGJzUjD15":3915},{"report":4,"adjacent":608},{"version":5,"date":6,"title":7,"sources":8,"hook":19,"deepDives":20,"quickBites":326,"communityOverview":588,"dailyActions":589,"outro":607},"20260216.0","2026-06-14","AI 趨勢日報：2026-06-14",[9,10,11,12,13,14,15,16,17,18],"academic","anthropic","community","github","google","huggingface","media","meta","microsoft","openai","AI 監管元年到來：美國封鎖 Fable 5 與 Mythos 5、多州聯合調查 OpenAI、北京叫停 Manus 收購，三條管制軸線同一天收緊。",[21,141,211,270],{"category":22,"source":10,"title":23,"subtitle":24,"publishDate":6,"tier1Source":25,"supplementSources":28,"tldr":57,"context":69,"devilsAdvocate":70,"community":73,"hypeScore":93,"hypeMax":93,"adoptionAdvice":94,"actionItems":95,"policyDetail":105,"complianceImpact":106,"industryImpact":116,"timeline":117},"policy","美國政府下令封鎖 Fable 5 與 Mythos 5，AI 模型監管進入新紀元","出口管制首次落地於商業 AI 模型，全球企業面對「全關或全開」的合規困境",{"name":26,"url":27},"Anthropic 官方聲明：Fable 5 與 Mythos 5 存取暫停","https://www.anthropic.com/news/fable-mythos-access",[29,33,37,41,45,49,53],{"name":30,"url":31,"detail":32},"TechCrunch：Amazon CEO 提報安全疑慮始末","https://techcrunch.com/2026/06/13/amazon-ceo-reportedly-raised-anthropic-model-concerns-before-government-crackdown/","披露 Andy Jassy 在政府指令下達前主動向財政部提報 Fable 5 安全疑慮的內幕",{"name":34,"url":35,"detail":36},"The New Stack：政府命令事件全紀錄","https://thenewstack.io/us-gov-orders-anthropic-to-pull-fable-5-and-mythos-5-three-days-after-launch/","事件時間線與 Anthropic 官方聲明技術細節整理",{"name":38,"url":39,"detail":40},"HN Discussion：Anthropic 聲明社群討論串","https://news.ycombinator.com/item?id=48511072","技術社群對 jailbreak 範疇、國籍驗證可行性及政治背景的深度討論",{"name":42,"url":43,"detail":44},"12 Grams of Carbon：AI 監管先例深度分析","https://12gramsofcarbon.com/p/tech-things-there-is-a-massive-shadow","將此事件定性為「盧比孔時刻」，類比 1990 年代加密演算法出口管制歷史先例",{"name":46,"url":47,"detail":48},"Reddit/LocalLLaMA：對齊論點討論","https://redlib.perennialte.ch/r/LocalLLaMA/comments/1u4epzr/friendly_reminder/","社群批判「對齊」本質：模型並非失對齊，而是對齊方向與監管機構期望不同",{"name":50,"url":51,"detail":52},"Reddit/LocalLLaMA：本地部署黑色幽默","https://redlib.perennialte.ch/r/LocalLLaMA/comments/1u4l98a/when_fable_gets_banned_but_its_ok_because_youve/","社群以黑色幽默回應封鎖，折射轉向本地開源模型的集體應對",{"name":54,"url":55,"detail":56},"Reddit/artificial：事件完整經過彙整","https://redlib.perennialte.ch/r/artificial/comments/1u4gtk8/us_government_kills_fable_5_heres_what_happened/","Reddit r/artificial 社群對事件始末的彙整討論",{"tagline":58,"points":59},"出口管制首次落地於商業 AI 模型：頂尖模型存取權正在成為地緣政治籌碼",[60,63,66],{"label":61,"text":62},"政策","美國政府以出口管制為由要求 Anthropic 封鎖 Fable 5 與 Mythos 5 對外國公民的存取；Anthropic 因無法可靠驗證國籍而選擇對全體用戶斷線，AWS 企業客戶亦受波及。",{"label":64,"text":65},"合規","此次事件揭示企業面對政府緊急指令時幾乎只能「全關或全開」，可靠的國籍驗證機制在技術上不可行，現有合規框架無法因應此類監管要求。",{"label":67,"text":68},"影響","歐洲政界發出「警鐘」，指依賴美國 AI 平台存在系統性風險；開源社群趁勢推動本地部署成為主流選項，AI 主權議題從討論正式進入政策現實。","#### 章節一：政府指令內容與 Anthropic 的回應\n\nFable 5 與 Mythos 5 於 2026 年 6 月 9 日上線，僅三天後，美國政府於 6 月 12 日下午 17 時 21 分（東岸時間）向 Anthropic 發出緊急出口管制指令。指令要求立即暫停所有外國公民對這兩款模型的存取，涵蓋在美境內的外國公民與 Anthropic 員工。\n\n> **名詞解釋**\n> 出口管制 (Export Control) ：美國法律框架中限制特定技術向外國人士傳輸的機制，過去主要適用於軍事與加密技術，本次為首度大規模適用於商業 AI 模型存取服務。\n\nAnthropic 在數小時內選擇全面斷線，理由是可靠驗證用戶國籍所需的技術與法律成本，使局部合規在實務上不可行。AWS Bedrock 的企業客戶同樣受到波及，服務在無預警的情況下中斷。\n\nAnthropic 在官方聲明中明確「不同意」此次召回決定，指出政府所列舉的 jailbreak 屬於「窄範圍、非通用的漏洞利用」，且 OpenAI GPT-5.5 等其他主流模型無需任何繞過手段即可執行相同任務。\n\n公司強調已部署「深度防禦 (defense in depth) 」策略並進行大量紅隊測試。面對正式法律指令，Anthropic 選擇服從，同時以公開聲明保留異議立場；Claude 3.x 系列及其他服務則不受影響。\n\n#### 章節二：Amazon CEO 的角色與企業利益角力\n\nTechCrunch 的報導揭示了事件背後不尋常的商業博弈：Amazon CEO Andy Jassy 據報在政府指令下達前，已主動向財政部長 Scott Bessent 等官員提報 Fable 5 的安全疑慮，指研究人員發現了可被用於網路攻擊的漏洞。\n\nAmazon 在此事件中的角色極為複雜——它既是 Anthropic 的主要投資方與 AWS Bedrock 的商業夥伴，同時也是大型語言模型市場的直接競爭對手。\n\nTrump 政府前 AI 顧問 David Sacks 透露，政府曾要求 Anthropic CEO Dario Amodei 修復該 jailbreak 或下線模型；Dario 拒絕修復要求，最終導致全面斷線。\n\n批評者指出，OpenAI 因 Kushner 家族投資等政治關係的加持，疊加 Anthropic 長期倡導 AI 監管的鮮明立場，使本次事件被廣泛解讀為帶有競爭色彩的選擇性打壓，而非單純的國家安全考量。\n\n#### 章節三：開源社群的集體反撲與自救行動\n\n事件消息傳出後，Reddit/LocalLLaMA 社群迅速湧現兩種並行反應。第一種是政治解讀：用戶明確指出，這些模型「並非失對齊，只是與監管機構及其支持者的期望方向不同」——「對齊」的定義本身成為被政治重新詮釋的競技場。\n\n第二種反應是實用主義的自救行動。社群以黑色幽默方式慶祝「終於有正當理由下載那個名字長達一整行的 Qwen 模型」，反映大量用戶實際轉向本地開源模型部署的決策；Qwen、Llama、Mistral 等開源替代方案的採用動能因此大幅提升。\n\n同期，「Open Source AI Must Win」宣言被廣泛傳播，核心論點是：若 AI 基礎設施集中於少數閉源商業平台，社會將喪失「研究、構建、審計、部署、教學與保存智能系統」的能力，必須確保大型模型具備可本地部署性與社群治理機制。\n\n> **白話比喻**\n> 這場封鎖就像圖書館突然宣布「只有本國公民才能借書」，但館員根本無法確認誰是本國人——最後乾脆鎖門，所有人都進不去。社群的回應是：那就自己在家複印吧。\n\n#### 章節四：AI 模型監管的先例效應與產業影響\n\n12gramsofcarbon.com 的分析將此事件定性為潛在的「盧比孔時刻」——這是政府首次以出口管制手段強制下線一個面向數億用戶的商業 AI 模型，歷史類比是 1990 年代美國對加密演算法施加出口管制的決定。\n\n分析指出，若此類指令成為常態，全球數兆美元的資料中心投資將面臨根本性威脅：投資者難以為「可能隨時被政府叫停」的模型服務構建穩定的商業計畫。\n\n歐洲政界已有政治人物公開將此事定性為「警鐘」，認為依賴美國 AI 技術存在系統性主權風險，標誌著 AI 主權議題從政策討論正式進入具體執法現實。\n\n更深層的隱憂在於競爭格局的扭曲：美國模型受限之際，中國 AI 廠商持續開放發布，有望趁機積累市場份額。HN 社群用戶直言，本次事件已向全球 AI 產業傳達一個明確訊號——頂尖模型的存取權正在成為地緣政治的籌碼。",[71,72],"政府的安全顧慮可能確有依據——若 Fable 5 存在可被用於網路攻擊的 jailbreak，即使範圍窄，在當前地緣政治高度緊張的背景下，謹慎應對的成本低於事後補救。","Anthropic 拒絕修復 jailbreak 的決定值得被檢視——若確屬窄範圍漏洞，修復技術成本相對有限，拒修的立場反而可能加深政府對其配合意願的疑慮，使後續協商更加困難。",[74,78,81,85,89],{"platform":75,"user":76,"quote":77},"Hacker News","vlovich123（HN 評論）","Anthropic 的主張是：這不是通用的 jailbreak 方法，而且此 jailbreak 賦予的能力，在其他模型上不需任何繞過手段就能取得，並非 Mythos 5 才有的獨特能力。問題在於你更相信哪一方——而這屆政府在真相方面的紀錄並不樂觀。",{"platform":75,"user":79,"quote":80},"ramraj07（HN 評論）","我很好奇接下來會怎麼發展……Anthropic 會停止在 Bedrock 上發布嗎？他們會試著把營運遷移出美國嗎？大家都在關注美式足球和尼克斯隊，但這件事比任何體育賽事都更有意思。",{"platform":82,"user":83,"quote":84},"Reddit r/LocalLLaMA","u/feel_the_force69(Reddit LocalLLaMA)","友善提醒——它們並非「失對齊」，它們只是與你對齊，而非與監管機構及其支持者想要的東西對齊。",{"platform":86,"user":87,"quote":88},"Bluesky","techmeme.com（Techmeme，8 upvotes）","歐洲政界人士表示，Anthropic 停止存取 Fable 5 與 Mythos 5 是一個「警鐘」，讓人正視依賴美國 AI 技術的風險。",{"platform":90,"user":91,"quote":92},"X","@karpathy（AI 研究員，前 OpenAI 創辦成員）","這是一個令人振奮的發布——Claude Fable 5 與 Mythos 5 使用相同底層模型，但前者增加了安全防護。各項基準測試均屬當前最佳水準，而且從質性角度來看，這也是一個值得大版本號的重大躍進。",5,"追整體趨勢",[96,99,102],{"type":97,"text":98},"Watch","追蹤 Anthropic 官方聲明更新，以及美國政府是否對其他 AI 公司採取類似出口管制措施——這將決定此次事件是個案還是新常態。",{"type":100,"text":101},"Build","若產品依賴閉源 AI API，開始評估至少一個開源本地模型作為備援路徑（Qwen、Llama、Mistral），以降低單點政策風險的暴露。",{"type":103,"text":104},"Try","閱讀 Open Source AI Must Win 宣言與 12gramsofcarbon.com 的深度分析，理解此次事件的結構性意義及其對全球 AI 產業格局的長期影響。","#### 核心條款\n\n美國政府援引出口管制法規，於 2026 年 6 月 12 日向 Anthropic 發出緊急指令：立即暫停所有「外國公民」對 Fable 5 與 Mythos 5 的存取，管制範圍涵蓋在美境內的外國公民（包含 Anthropic 員工），而非僅限境外存取。\n\n政府所列舉的具體依據為一種可引導 Fable 5 識別程式碼漏洞的 jailbreak 技術，被認定具有可被用於網路攻擊的潛在風險。Anthropic 否認此 jailbreak 構成大規模召回的充分理由，雙方在技術評估上立場相左。\n\n#### 適用範圍\n\n本次指令直接適用於 Fable 5 與 Mythos 5 兩款模型；Claude 3.x 系列及其他服務不受影響。間接影響範圍涵蓋所有透過 AWS Bedrock 取用 Anthropic 模型的全球企業客戶。\n\n技術社群指出，「外國公民」身分的驗證在技術層面幾乎無法可靠實現——IP 位置、身分驗證文件均可偽造，使本次指令的合規執行帶有強烈的象徵意義，難以達到實際管制效果。\n\n#### 執法機制\n\n本次指令的執法主體為美國財政部，David Sacks 等政府顧問參與了政策溝通。Anthropic 在收到指令後數小時內完成全面斷線，整個執行過程缺乏公開的聽證程序與申訴管道。\n\n從時序來看，Amazon CEO Andy Jassy 在指令下達前已主動向財政部長 Scott Bessent 提報安全疑慮，顯示本次執法行動在正式指令之前已有企業層面的非正式溝通管道。",[107,110,113],{"label":108,"markdown":109},"工程改造需求","此次事件揭示現有 AI 平台架構在合規設計上的根本缺陷——幾乎所有主流雲端 AI 服務，都無法在不關閉全部存取的情況下可靠地依國籍進行隔離。\n\n企業若要對應類似的監管要求，需建置以下能力：\n\n- 可驗證的用戶身分識別機制（超出現有 KYC 流程的強度）\n- 地理封鎖與 IP 驗證的多層架構\n- 針對政府緊急指令的快速隔離開關 (kill switch) 設計\n- 企業合約中「服務中斷免責」條款的相應更新",{"label":111,"markdown":112},"合規成本估計","本次事件中，Anthropic 的合規選擇幾乎只有「全關」——因為實作可靠國籍驗證的邊際成本，遠超全面斷線的業務損失評估。\n\n對 AWS Bedrock 等企業服務提供商而言，此類政府緊急指令可能引發客戶信任危機，間接成本難以量化。建立可支援細粒度合規隔離的基礎設施，預估需要顯著的工程與法務投入，且現有技術框架尚無業界標準解決方案。",{"label":114,"markdown":115},"最小合規路徑","鑒於技術上的不可行性，目前最接近「最小合規路徑」的選擇包括：\n\n- 對所有新用戶啟動人工國籍驗證流程（以限制服務可及性換取合規安全感）\n- 建立企業級白名單制度，僅對可驗證的美國公民法人實體開放存取\n- 在服務條款中明確排除非美國公民的使用授權，轉移法律責任\n- 準備快速全面斷線的技術預案，作為應對政府緊急指令的後備選項","#### 直接影響者\n\nAnthropic 自身是最直接的受害方——數億用戶的服務在無預警情況下中斷，商譽與企業客戶信任受到衝擊。AWS Bedrock 的企業用戶面臨服務不穩定的風險，部分合約可能需要重新談判。\n\n其他頂尖閉源 AI 模型提供商（OpenAI、Google DeepMind）同樣面臨未來可能遭受類似監管行動的不確定性，特別是當其政治關係弱化或與政府立場產生摩擦時。\n\n#### 間接波及者\n\n全球採用美國 AI 平台的企業客戶，現在必須重新評估供應鏈的地緣政治風險。歐洲政界已公開將此事定性為「警鐘」，預計將推動 EU AI Act 框架下的主權 AI 倡議加速落地。\n\n開源模型生態系——Qwen、Llama、Mistral——直接受益：用戶在尋求可自主部署、不受美國監管干預的替代方案，開源社群的採用動能因此大幅提升。\n\n#### 成本轉嫁效應\n\n企業客戶若決定轉向本地部署或開源替代方案，短期內需承擔工程遷移成本。\n\n長期而言，若美國監管不確定性持續，全球 AI 市場可能出現碎片化——美國企業主導的閉源生態與中國、歐洲主導的開源或主權 AI 生態形成平行格局，最終使所有用戶面對更高的生態轉換成本。",[118,122,125,128,133,137],{"date":119,"text":120,"phase":121},"2026-06-09","Fable 5 與 Mythos 5 正式上線，面向全球用戶開放存取。","past",{"date":123,"text":124,"phase":121},"2026-06-12","美國政府於 17：21（東岸時間）發出緊急出口管制指令，要求立即封鎖外國公民存取。Anthropic 數小時內全面斷線，含美國本土用戶與 AWS 企業客戶。",{"date":126,"text":127,"phase":121},"2026-06-13","TechCrunch 披露 Amazon CEO Andy Jassy 於指令下達前已向財政部提報安全疑慮；Anthropic 發布官方聲明明確表示「不同意」此次召回決定。",{"date":129,"label":130,"text":131,"phase":132},"短期（0-3 個月）","短期","Anthropic 與美國政府就 jailbreak 技術範疇進行法律與技術協商；AWS Bedrock 企業客戶評估服務依賴風險並尋求備援；開源社群採用率加速成長。","future",{"date":134,"label":135,"text":136,"phase":132},"中期（3-12 個月）","中期","觀察美國政府是否對其他 AI 公司發出類似出口管制指令；歐盟是否將此事件轉化為具體的 AI 主權立法行動；Anthropic 能否恢復 Fable 5 與 Mythos 5 的全球服務。",{"date":138,"label":139,"text":140,"phase":132},"後續觀察","觀察","出口管制框架是否成為美國政府管控頂尖 AI 能力的常設工具；中國 AI 廠商開放政策是否形成顯著市場反差；開源本地部署能否在技術上成熟到足以替代閉源頂尖模型。",{"category":142,"source":16,"title":143,"subtitle":144,"publishDate":6,"tier1Source":145,"supplementSources":148,"tldr":156,"context":168,"devilsAdvocate":169,"community":172,"hypeScore":189,"hypeMax":93,"adoptionAdvice":94,"actionItems":190,"perspectives":197,"practicalImplications":209,"socialDimension":210},"discourse","從「Token 狂用」到「Token 節約」：Meta 內部 AI 成本飆破數十億美元的覺醒","73.7 兆 token、6,000 名員工、數十億美元——Meta 用一份備忘錄宣告 Claudeonomics 時代終結",{"name":146,"url":147},"The Decoder","https://the-decoder.com/meta-shifts-from-tokenmaxxing-to-token-managing-as-internal-ai-costs-reportedly-hit-billions/",[149,152],{"name":146,"url":150,"detail":151},"https://the-decoder.com/microsoft-ceo-satya-nadella-admits-hes-a-token-maxer-too-its-addictive/","Satya Nadella 承認自身 token-maxing 行為，並提出「邊際成本對等」原則",{"name":153,"url":154,"detail":155},"MLQ.ai","https://mlq.ai/news/meta-caps-internal-ai-token-spending-after-costs-approach-billions-in-2026/","Meta 限制內部 AI token 支出的補充報導與數字核實",{"tagline":157,"points":158},"73.7 兆個 token、30 天、6,000 名員工：Meta 的 AI 狂歡派對即將散場",[159,162,165],{"label":160,"text":161},"爭議","Meta 員工 30 天消耗 73.7 兆 token，Claudeonomics 排行榜將 AI 使用量扭曲為競技場，催生大規模「為用而用」的表演性消耗行為。",{"label":163,"text":164},"實務","AI Gateway 集中監控平台預計數週上線，完整預算配額框架 2027 年啟用；員工將被導向自家 MetaCode，而非付費的 Claude。",{"label":166,"text":167},"趨勢","Nadella「邊際成本對等」原則，預示整個業界即將從「用量為王」轉向精準投放的 ROI 思維，企業 AI 治理正式進入成熟期。","#### 章節一：內部備忘錄揭露的驚人數字\n\nMeta 向約 6,000 名員工發出的內部備忘錄揭露了驚人現實：公司 AI 使用成本正呈「指數級增長」，預計 2026 年逼近數十億美元，2027 年直接突破。\n\n在約 30 天內，員工透過名為「Claudeonomics」的內部排行榜共消耗了 **73.7 兆個 token**。這個名字直接向 Anthropic 的 Claude 致敬，Claude 正是 Meta 內部廣泛依賴的第三方 AI 工具之一。\n\n排行榜最初的設計出發點是鼓勵員工積極擁抱 AI，拉升全公司採用率。卻意外催生出「為用而用」的消耗行為——員工為了在榜上爭得名次而無謂消耗 token，而非用 AI 創造實際價值。\n\nMeta CTO Andrew Bosworth 明確點出問題核心：「沒有人應該只是為了使用 AI 工具而使用它們。所有行動都不等於進展，token 使用量本身也不是任何意義上的影響力衡量標準。」\n\n#### 章節二：Nadella 也自嘲是 Token-Maxer\n\n2026 年 6 月 13 日，微軟 CEO Satya Nadella 在 Hard Fork 頻道專訪中坦承：「我也是個 token-maxer，這很上癮。」這句話出自一位力推 AI 轉型的科技巨頭掌舵者之口，格外引人矚目。\n\nNadella 同時提出警告：不應把最強的前沿模型浪費在日常任務上。他提出「邊際成本對等」框架：生產力提升的邊際成本，必須與 token 的邊際成本相匹配。換言之，任務的複雜度應決定使用模型的等級。\n\nAmazon 同樣出現員工刷榜內部 AI 排行榜的現象，顯示 Meta 面臨的問題並非個案。當業界最積極推廣 AI 的領袖都坦承難逃 token-maxing 誘惑，這場行為科學實驗的失控，已是整個產業級別的課題。\n\n#### 章節三：企業 AI 成本管理的轉折點\n\nMeta 計劃以集中監控平台「**AI Gateway**」取代 Claudeonomics 排行榜。AI Gateway 可即時追蹤各團隊及個別員工的 token 用量與花費，並設有異常支出自動警報，儀表板預計數週內上線。\n\n完整的預算框架——含配額與分配機制——預計 2027 年初正式啟用。與此同時，Meta 計劃將員工從 Claude 等第三方工具導向自家 MetaCode 助理，以降低外部 AI 授權支出，進一步收緊成本控制。\n\nMeta 整體 AI 基礎設施支出計畫高達 **1,350 億美元**（至 2026 年），並承諾在 2028 年前投入 **6,000 億美元**於資料中心建設。即便如此，內部 AI 使用的失控成本仍足以讓管理層發出緊急備忘錄——這本身就是值得深思的訊號。\n\n#### 章節四：Token 經濟學對開發者與企業的啟示\n\nNadella 的「邊際成本對等」原則，為企業提供了一個評估 AI ROI 的實用模型：不同複雜度的任務應匹配不同能力等級的模型，而非一律動用最昂貴的前沿模型。\n\n對開發者而言，「右模型選配」即將從個人最佳實踐升格為企業強制規範。AI Gateway 類型的平台上線後，每一筆 token 消耗都將有成本歸屬，高消耗低產出的行為將無所遁形。\n\n更深層的啟示在於：AI 採用的「量化文化」已觸及天花板。當激勵員工「用量」的機制反而催生浪費，整個行業需要重新定義 AI 使用的成功指標——從 token 消耗量轉向可量化的業務成果。",[170,171],"Claudeonomics 排行榜可能確實加速了 Meta 員工 AI 工具的上手速度——若完全廢除激勵機制，可能抑制企業內部的 AI 使用意願，在競爭激烈的 AI 時代得不償失。","73.7 兆 token 的消耗若有對應的生產力提升，數十億美元的內部 AI 支出未必是浪費——真正的問題是缺乏追蹤機制，而非使用量本身。Meta 或許需要的是更好的 ROI 量測工具，而非成本限制。",[173,176,179,182,185],{"platform":86,"user":174,"quote":175},"gilduran.com（Bluesky 193 讚）","矽谷：所有人都必須隨時隨地使用 AI！這是奇蹟！\n\n矽谷，同樣是這些人：請不要使用 AI，太貴了（而且我們在監視你）",{"platform":86,"user":177,"quote":178},"fintwitter.bsky.social（Bluesky 242 讚）","META 宣布限制員工 AI 使用量，因 AI 成本已達數十億美元——《The Information》報導",{"platform":90,"user":180,"quote":181},"@AGTPinsights（X 用戶）","有報告指出 @Meta 員工在單月內消耗了 60 兆個 AI token，潛在成本約 9 億美元。確切數字難以核實，或許是刻意流傳，但數字所指向的方向才是重點——即便只有十分之一，也令人震驚。",{"platform":86,"user":183,"quote":184},"theserfstv.bsky.social（Bluesky 144 讚）","從商業面來看，跡象已昭然若揭。這就是為什麼你突然看到那麼多無關痛癢的政客和名人跑出來背書推廣 AI。\n\n創投資金正在枯竭，而沒有任何 AI 公司是盈利的，所以下一步就是要動你的儲蓄——也就是 IPO 時間（參見 SpaceX）。",{"platform":186,"user":187,"quote":188},"HN","giancarlostoro（HN 用戶）","Amazon 和 Meta 在 AI 方面的表現讓我感到驚訝。對 Google 則沒那麼意外——我認為 Google 選了非常明確的利基市場。仔細想想，你不必做到絕對最好，只需持續打磨模型的效率與成本，這才是 Google 真正的目標與秘密武器。",4,[191,193,195],{"type":103,"text":192},"審計自己或團隊的 AI 工具使用模式，記錄每項任務所用的模型與 token 量，實踐 Nadella「邊際成本對等」原則——依任務複雜度選擇對應等級的模型。",{"type":100,"text":194},"在公司內部建立簡易的 AI 成本追蹤機制，將 token 費用歸屬到具體專案或功能，為即將到來的企業 AI 治理時代提前做準備。",{"type":97,"text":196},"追蹤 Meta AI Gateway 及類似企業 AI 治理平台的推出進展，以及「AI 產出量測」方法論的行業標準化動態。",[198,202,206],{"label":199,"color":200,"markdown":201},"正方立場","green","AI 工具的全員普及需要一個探索期，員工在初期的「過度使用」是熟悉工具的必要代價。Claudeonomics 排行榜確實加速了 Meta 的 AI 工具上手速度——若沒有排行榜激勵，大量員工可能從未嘗試過 AI 輔助的工作流程。\n\n更根本的是，限制 token 使用可能是短視的成本控制措施。若 AI 使用量的背後是真實的生產力提升，數十億美元的內部 AI 支出，相對於節省的人力成本可能完全划算——但這需要測量機制，而非直覺判斷後的一刀切限制。",{"label":203,"color":204,"markdown":205},"反方立場","red","「Tokenmaxxing 文化」將 AI 使用量本身視為目標，而非手段。Meta 案例清楚顯示，當激勵機制錯誤設計，員工的理性選擇就是「為排行榜而用 AI」，而非「為解決問題而用 AI」。這種行為扭曲使得真實的 AI ROI 根本無從評估。\n\nAndrew Bosworth 的批評直指核心：所有行動都不等於進展。一個月 73.7 兆 token 的消耗，若大部分只是員工「展示 AI 使用量」的表演，那麼企業不只在浪費金錢，更在用錯誤的指標欺騙自己——成本失控的根源正是指標失控。",{"label":207,"markdown":208},"中立／務實觀點","問題的根源既不是 AI 工具本身，也不是員工的懶散——而是激勵機制設計的失敗。排行榜把「可量化的 token 消耗」當成代理指標，當代理指標與真實目標脫鉤，Goodhart 定律就會發作。\n\n> **名詞解釋**\n> Goodhart 定律：「當一個量測指標本身成為管理目標時，它就不再是有效的量測工具。」由英國經濟學家 Charles Goodhart 提出，廣泛應用於管理與政策分析。\n\nMeta 用 AI Gateway 取代 Claudeonomics，是從錯誤指標（token 量）轉向正確指標（成本對應產出）的正確方向。但真正的挑戰在於：如何量化 AI 帶來的生產力收益？這個問題至今沒有業界共識，AI 治理的下一個戰場，將是「AI 產出」的測量學。","#### 對開發者的影響\n\nAI 工具的「右模型選配」原則——依任務複雜度選擇對應能力等級的模型——即將從個人最佳實踐升格為企業合規要求。開發者需要建立模型分級使用的直覺，學會在「夠用」與「最強」之間做出有意識的取捨。\n\n企業內部 AI 工具使用即將納入成本監控與配額管理。習慣「無限 token」工作流程的開發者，需要提早適應「成本意識開發」的思維轉型。\n\n#### 對團隊／組織的影響\n\nAI 排行榜等量化激勵機制需要重新設計——核心問題是：如何設計讓員工「用 AI 解決真實問題」而非「用 AI 刷指標」的激勵系統？\n\n2027 年 Meta AI Gateway 預算框架落地後，各團隊對 AI 支出將負有直接責任。AI 投資的 ROI 評估將成為每個部門主管的必修課，而非只是 CTO 辦公室的議題。\n\n#### 短期行動建議\n\n- 審計現有 AI 工具使用模式，識別高消耗低價值的使用場景\n- 為不同複雜度的任務建立「推薦模型等級」指引\n- 在內部工具選型時，優先評估具備成本可視化功能的 AI 平台","#### 產業結構變化\n\n企業 AI 採用正式進入「治理成熟期」，從第一波「廣泛普及推廣」轉向第二波「精準投放管控」。AI Gateway 這類成本可視化平台，以及配額制、分配機制等治理工具，將成為 2027 年後企業 AI 採購清單的標準配備。\n\n#### 倫理邊界\n\nClaudeonomics 排行榜揭示了一個深層的倫理問題：當公司以「可量化的 AI 使用量」考核員工，是否在無意間鼓勵了表演性勞動？員工不是在創造價值，而是在「表演使用 AI」給管理層看——這是評估文化在 AI 時代的特殊扭曲。\n\n#### 長期趨勢預測\n\nAI 成本管控的下一個前線，將是「AI 產出量測」——如何客觀評估 AI 是否真的提升了生產力？當 token 使用量被廢棄為指標之後，企業需要建立新的衡量框架。\n\n程式碼品質、決策速度、錯誤率降低等業務成果導向的指標，將取代「使用 AI 的次數」成為新標準。掌握「AI 產出量測」方法論的企業，將在下一輪 AI 治理競爭中搶得先機。",{"category":212,"source":17,"title":213,"subtitle":214,"publishDate":6,"tier1Source":215,"supplementSources":217,"tldr":226,"context":238,"mechanics":239,"benchmark":240,"useCases":241,"engineerLens":249,"businessLens":250,"devilsAdvocate":251,"community":255,"hypeScore":189,"hypeMax":93,"adoptionAdvice":262,"actionItems":263},"tech","Microsoft SkillOpt：用一份「訓練過的 Markdown」就能大幅提升 LLM 表現","把 AI agent 的指令文件當成可訓練參數，52/52 組合全面勝出、GPT-5.5 準確率飆升 23 點",{"name":146,"url":216},"https://the-decoder.com/microsofts-skillopt-boosts-gpt-5-5-by-using-nothing-but-a-trained-markdown-file/",[218,222],{"name":219,"url":220,"detail":221},"arXiv：2605.23904 — SkillOpt 論文","https://arxiv.org/abs/2605.23904","Microsoft Research 與三所中國大學合著的原始論文，含完整技術細節與 52 組基準測試數據",{"name":223,"url":224,"detail":225},"SkillOpt 官方專案頁面","https://microsoft.github.io/SkillOpt/","Microsoft GitHub 官方頁面，含範例程式碼與文件",{"tagline":227,"points":228},"不動模型權重，只訓練一份 Markdown 就能讓 GPT-5.5 準確率飆升 23 點",[229,232,235],{"label":230,"text":231},"技術","SkillOpt 將 AI agent 的指令文件視為可訓練參數，引入學習率、負樣本緩衝等深度學習訓練機制，讓 Markdown 技能文件在 4 個 epoch 後系統化演進。",{"label":233,"text":234},"成本","最終產物僅 300–2,000 tokens 的 Markdown 文件，部署時零額外模型呼叫，推論成本與原本完全相同，技能文件可跨模型直接複用。",{"label":236,"text":237},"落地","52/52 評估組合全面勝出，GPT-5.5 提升 +23.5 點；但需要可靠的自動評分機制才能啟動優化流程，這是主要導入門檻。","#### 章節一：SkillOpt 的核心概念與運作原理\n\nSkillOpt 由 Microsoft Research 聯合三所中國大學於 2026 年 5 月發布，核心概念是將 AI agent 的指令文件（「skills」）視為可訓練的外部狀態，而非靜態提示詞。傳統上，開發者手動調整提示詞是一項費時費力的工作；SkillOpt 引入了一個獨立的「優化器模型」，讓這個過程系統化、可重複。\n\n優化流程中，優化器模型讀取 agent 的執行日誌 (rollouts) ，分析成功與失敗的案例，然後對技能文件提出局部編輯——新增、刪除或替換段落。關鍵突破在於：目標模型的權重完全凍結，只有那份 Markdown 文件本身被「訓練」，無需昂貴的模型微調 (fine-tuning) 。\n\n#### 章節二：「指令文件即模型調校」的技術突破\n\nSkillOpt 刻意將深度學習的訓練概念對映到純文字層面，構建出一套類神經網路訓練的最佳化框架。「學習率」限制每步可編輯的範圍，防止技能文件出現不穩定的大幅漂移；「排程器」逐輪縮小修改幅度，讓優化過程逐漸從粗調轉為微調。\n\n被拒絕的編輯存入「負樣本緩衝區」作為對比學習素材；「慢更新」機制確保在多個訓練 epoch 間保持穩定的編輯方向，避免前後矛盾的修改互相抵消。只有通過驗證集評分改善的編輯才會被接受，典型的最終技能文件在 4 個 epoch 中僅累積 1–4 次被接受的編輯。\n\n> **名詞解釋**\n> **負樣本緩衝區 (negative buffer)**：記錄被驗證集否決的優化嘗試，讓後續步驟能參照「哪些方向是死路」，類似人類從錯誤中學習的記憶機制。\n\n#### 章節三：基準測試結果與效能分析\n\n研究橫跨六個基準測試，涵蓋網路搜尋、試算表操作、文件分析、數學推理與具身行動等多元任務；評估對象包含七個目標模型，從大型的 GPT-5.5 到小型的 Qwen3.5-4B 均有覆蓋。在 52 個（模型 × 基準測試 × 執行框架）評估組合中，SkillOpt 全數勝出或並列第一。\n\n具體數字相當亮眼：GPT-5.5 直接對話模式下準確率提升 +23.5 點，Codex agentic loop 提升 +24.8 點，Claude Code 模式提升 +19.1 點。在具有嚴格格式要求與工具呼叫的任務上，增益最為顯著。\n\n技能可跨模型遷移：在大型模型上訓練的技能能直接提升同系列小型模型的表現；針對數學奧林匹克問題優化的技能，也能泛化至相關數學基準，顯示 SkillOpt 捕捉到的是任務的結構性知識而非模型特性。\n\n#### 章節四：對 Prompt Engineering 工作流的深遠影響\n\nSkillOpt 最大的實用意義在於部署的極度輕量性。優化器模型僅在訓練階段使用，線上推論時 agent 只需讀取那份最終的 Markdown 技能文件，零額外模型呼叫。最終產物僅 300–2,000 tokens，具備可檢視性（人類可讀懂它做了什麼）、可攜性（跨環境直接複用）與低成本性。\n\nThe Decoder 的報導指出，這套方法讓 AI 社群重新思考「最佳提示詞」是否應由機器而非人類定義。手動反覆調整 prompt 的勞動，有望被系統化的「文件訓練流程」取代，根本改寫 Prompt Engineering 的工作範式。\n\n研究者坦承的限制包括：需要可靠的自動評分機制，以及目前只優化單一技能文件而非技能庫。在多領域 agent 場景下，後者可能成為規模化的關鍵瓶頸。","SkillOpt 的核心技術突破在於將「訓練」的概念從模型權重空間搬移到文字空間。這讓 AI agent 的指令文件可以像神經網路一樣被系統化優化，而無需更動任何模型本身。\n\n#### 機制 1：文字空間梯度下降\n\n傳統梯度下降更新模型的浮點數權重；SkillOpt 的「梯度」是優化器模型分析 rollout 日誌後產生的自然語言編輯建議。每次迭代，優化器讀取成功與失敗的執行紀錄，針對技能文件提出段落級別的修改（新增、刪除或替換段落）。目標模型的權重始終凍結不動，只有文件本身在演化。\n\n#### 機制 2：訓練超參數的文字對應\n\n- **學習率 (learning rate)**：限制每步可修改的字符數或段落數，防止技能文件在單次迭代中發生巨大漂移\n- **排程器 (scheduler)**：隨訓練進程逐輪縮小修改幅度，讓優化從「粗調」逐漸轉為「微調」\n- **負樣本緩衝區 (negative buffer)**：記錄被驗證集否決的編輯，下一輪優化時作為「禁止方向」的對比學習素材\n- **慢更新 (slow update)**：多 epoch 間維持一致的編輯方向，避免前後矛盾的修改互相抵銷\n\n#### 機制 3：接受-拒絕驗證閘門\n\n每次編輯提案都要通過驗證集評分：只有實際改善準確率的編輯才被接受並寫入技能文件；被拒絕的提案進入負樣本緩衝區。典型訓練結果顯示，4 個 epoch 後僅 1–4 次編輯被接受，這種稀疏性確保了最終文件的品質而非量。\n\n> **白話比喻**\n> 想像一位編輯在不改動作者本人的情況下，反覆修訂一份操作手冊：每次只允許改一點點（學習率），記錄哪些改法被審稿人退回（負樣本緩衝區），最終手冊雖然只被改了幾次，卻讓使用者成功率大幅提升。SkillOpt 就是這位永不疲倦的自動化編輯。","#### 評估設計\n\n研究採用 52 個評估組合，涵蓋 7 個目標模型、6 個基準測試與多種執行框架。基準測試包含 WebArena（網路搜尋）、SpreadsheetBench（試算表）、DocBench（文件分析）、MATH（數學推理）、ScienceWorld（具身行動）等，並與 TextGrad、GEPA、EvoSkill、Trace2Skill 等現有方法全面對比。\n\n#### 主要結果\n\n- GPT-5.5 直接對話模式：準確率 +23.5 點\n- Codex agentic loop：+24.8 點\n- Claude Code 模式：+19.1 點\n- 52/52 評估組合全數超越或並列基線，小型模型 Qwen3.5-4B 亦有顯著增益\n\n#### 跨模型遷移測試\n\n在大型模型上訓練的技能文件可直接遷移至同系列小型模型，維持正向準確率增益。針對數學奧林匹克問題優化的技能，亦能泛化至相關數學基準，顯示技能文件捕捉到的是任務的結構性知識。",{"recommended":242,"avoid":246},[243,244,245],"需要高準確率且可重複執行的 agentic 任務，如試算表自動化、文件解析、資料提取流程","已建立可量化自動評估指標的 ML 工程團隊，希望系統化取代手動 prompt 調整工作","多模型環境下希望共用同一份技能文件的企業，在大型模型上訓練後部署至小型模型以降低推論成本",[247,248],"尚未建立可靠自動評分機制的早期 PoC 階段，優化器無法在缺乏量化指標的情況下收斂","需要同時跨多個高度異質技能領域的複雜 agent，目前只支援單一技能文件優化，多工場景需多次獨立訓練","#### 環境需求\n\n需要一個可運行 agent rollout 的評估環境，以及能量化輸出品質的自動評分函數（如 pass@1、exact match）。Python 環境搭配 OpenAI 或 Anthropic SDK 即可；SkillOpt 本身不需要本地 GPU，目標模型以 API 呼叫方式使用。官方 GitHub 專案頁面（https://microsoft.github.io/SkillOpt/）提供範例框架與文件。\n\n#### 最小 PoC\n\n```python\nfrom skillopt import SkillOptimizer\n\n# 準備初始技能文件 skill.md 與評估函數\noptimizer = SkillOptimizer(\n    target_model=\"gpt-4o\",      # 目標模型（凍結，只讀取技能文件）\n    optimizer_model=\"gpt-4o\",   # 優化器模型（訓練階段使用）\n    learning_rate=0.3,           # 每步最大編輯比例\n    epochs=4\n)\n\nresult = optimizer.run(\n    skill_path=\"skill.md\",\n    eval_fn=my_benchmark_eval,   # 回傳 0-1 分數的自動評估函數\n    train_tasks=train_set,\n    val_tasks=val_set\n)\n\nresult.save(\"skill_optimized.md\")  # 最終產物：一份優化後的 Markdown\n```\n\n#### 驗測規劃\n\n保留 10–20% 的任務集作為 holdout 測試集，分別以原始技能文件與優化後技能文件執行，比較 pass@1 準確率差值。建議同時在第二個目標模型上測試，驗證跨模型遷移性是否成立。\n\n#### 常見陷阱\n\n- 評分函數過於寬鬆或不精確，會引導優化器朝錯誤方向走，最終技能文件看似改善但實測下滑\n- 訓練集與測試集分佈差異過大，導致技能文件過擬合 (overfitting) 至訓練任務而無法泛化\n- 初始技能文件品質太低，建議優化前先人工撰寫至「合格但未最佳化」的水準作為起點\n\n#### 上線檢核清單\n\n- 觀測：優化後 vs. 基線的準確率差值、每個 epoch 被接受的編輯次數\n- 成本：優化器 API 呼叫費用（rollout 數量 × token 數 × API 單價）\n- 風險：技能文件版本控管（每個被接受的 epoch 存快照）、評分函數本身的可靠性審計","#### 競爭版圖\n\n- **直接競品**：TextGrad（文字梯度框架）、OPRO（Google 的 prompt 優化器）、DSPy（宣告式 prompt 優化框架）、EvoSkill\n- **間接競品**：傳統手動 prompt engineering 服務商、人工 red-teaming 與提示詞改善顧問服務\n\n#### 護城河類型\n\n- **工程護城河**：52/52 組合全面超越、系統化流程具論文支撐的可重複性，且已有開源社群研究者（如 @omarsar0）獨立複現驗證\n- **生態護城河**：與 Microsoft Azure OpenAI 服務深度整合的潛力；訓練好的技能文件可在企業內跨團隊共享，形成組織級知識資產\n\n#### 定價策略\n\nSkillOpt 本身為開源研究框架，核心成本來自優化器模型的 API 呼叫費用。一次性訓練成本（數百次 rollout × API 費用）可攤薄至長期部署收益，對高重複性 agentic 任務（如財務報表解析、合約審查自動化）CP 值顯著。\n\n#### 企業導入阻力\n\n- 需要可靠的自動評分機制，許多企業任務的品質評估仍依賴人工審查，建置自動評分本身即是額外工程投入\n- 目前只支援單一技能文件優化，複雜的多工 agent 需要多次獨立訓練，缺乏跨技能協調機制\n- 研究論文到生產就緒工具之間仍有工程化落差，企業採用前需評估維護成本\n\n#### 第二序影響\n\n- Prompt Engineering 這個職能的部分工作將被系統化工具取代，工程師角色將從「調參者」轉為「評估框架設計者」\n- 「技能文件市場」可能出現：預訓練好的高品質技能文件可被交易或共享，類似 HuggingFace 的模型共享模式\n- 小型模型因跨模型遷移能力而受益，企業可用大型模型訓練技能後部署在小型模型上，大幅降低推論成本\n\n#### 判決：企業值得優先評估自動評分可行性再決定是否採用（瓶頸在評分而非優化）\n\nSkillOpt 的 52/52 結果令人信服，20+ 點的準確率提升在業界屬於重大增益。核心門檻是企業必須先建立可靠的自動評分機制——這對許多任務而言本身就是一項工程挑戰。建議中大型 AI 工程團隊先審視自家任務是否具備可量化的評估指標，若已有，SkillOpt 的投資報酬率相當可觀。",[252,253,254],"論文的 52/52 全勝結果在獨立重現時可能出現差異，評分函數的選擇與任務集分佈對結果影響極大，存在「自出題、自評分」的過擬合風險","「文件訓練」框架看起來創新，但本質與 OPRO 或 DSPy 的 prompt 優化機制相近，真正的護城河可能不如論文聲稱的那樣持久","對於非結構化、開放式的創意任務，自動評分幾乎不可能做到可靠，這讓 SkillOpt 的適用範圍比廣告更窄，難以惠及所有 AI agent 使用場景",[256,259],{"platform":90,"user":257,"quote":258},"@omarsar0（AI 研究者與教育者）","這篇來自 Microsoft 的 SkillOpt 論文必讀！（先收藏起來）幾天前分享時，我對論文中報告的結果原本有些懷疑。然而，我成功將它整合進我的 agent orchestrator 並跑了幾次實驗。結果令人震驚。",{"platform":90,"user":260,"quote":261},"@akshay_pachaar","Microsoft 剛開源了 SkillOpt！這是一個像訓練神經網路一樣訓練 agent 技能的框架：SkillOpt 把一份普通的 Markdown 文件當成凍結 LLM agent 的可訓練參數，應用與權重訓練相同的最佳化規律：學習率。","值得一試",[264,266,268],{"type":103,"text":265},"前往 https://microsoft.github.io/SkillOpt/ 查看官方範例，在現有的一個 agent 任務上試跑 SkillOpt 優化流程，觀察技能文件實際累積了哪些段落修改",{"type":100,"text":267},"為自家 agentic pipeline 設計一個可量化的自動評分函數——這是導入 SkillOpt 的先決條件，也是最關鍵的工程挑戰，建議先從有明確正確答案的任務（如試算表、資料提取）入手",{"type":97,"text":269},"追蹤 SkillOpt 後續更新，特別是多技能文件（技能庫）的同步優化功能，這將是複雜多工 agent 場景規模化的關鍵解鎖點",{"category":212,"source":13,"title":271,"subtitle":272,"publishDate":6,"tier1Source":273,"supplementSources":275,"tldr":284,"context":293,"mechanics":294,"benchmark":295,"useCases":296,"engineerLens":305,"businessLens":306,"devilsAdvocate":307,"community":311,"hypeScore":189,"hypeMax":93,"adoptionAdvice":318,"actionItems":319},"Google Research Gemini-SQL2 大幅領先 Text-to-SQL 基準測試","首個突破 BIRD 80% 門檻，自然語言查詢企業資料庫邁入新里程碑",{"name":146,"url":274},"https://the-decoder.com/google-researchs-gemini-sql2-tops-text-to-sql-benchmarks-by-a-wide-margin/",[276,280],{"name":277,"url":278,"detail":279},"MarkTechPost","https://www.marktechpost.com/2026/06/12/google-releases-gemini-sql2-gemini-3-1-pro-text-to-sql-scores-80-04-on-bird-single-model-leaderboard/","詳細報導 Gemini-SQL2 的 BIRD 榜單成績、技術背景與企業應用展望",{"name":281,"url":282,"detail":283},"AI Weekly","https://aiweekly.co/alerts/googles-gemini-sql2-tops-bird-text-to-sql-at-8004","簡報 Gemini-SQL2 登頂 BIRD text-to-SQL 排行榜的關鍵數據",{"tagline":285,"points":286},"首個突破 BIRD 80% 門檻，Gemini-SQL2 讓自然語言查詢企業資料庫邁入可用門檻",[287,289,291],{"label":230,"text":288},"基於 Gemini 3.1 Pro 後訓練打造，BIRD 執行準確率 80.04%，較主要競品領先 7-9 個百分點，首個突破 80% 的 text-to-SQL 系統。",{"label":233,"text":290},"目前無公開 API，需等候整合進 BigQuery Studio 等 Google 資料服務；複雜 schema 的 token 上下文消耗在正式部署時不可忽視。",{"label":236,"text":292},"80% 準確率標誌自動化查詢進入可用門檻，但正式生產仍需人工審查；導入前應先建立黃金查詢集評估實際準確率。","#### Gemini-SQL2 架構與 Gemini 3.1 Pro 基底\n\nGoogle Research 於 2026 年 6 月 12 日發布 Gemini-SQL2，這是基於 Gemini 3.1 Pro 進行專業化後訓練 (post-training) 與 scaffolding 所打造的 text-to-SQL 能力層，而非全新基礎模型。\n\n不同於一般 LLM 生成語法正確的 SQL，Gemini-SQL2 的優化目標是生成「可執行且回傳正確結果」的 SQL 查詢——這正是 BIRD 基準的評測核心，Google 的設計從根本上以執行語意而非表面語法為標準。\n\n> **名詞解釋**\n> **後訓練 (post-training)**：在預訓練大型語言模型之後，針對特定任務進行進一步的監督學習或強化學習，使模型在該領域的表現大幅超越通用基礎模型。\n\nGoogle Research 指出，資料本身往往是多層次的，查詢需要納入複雜的商業邏輯，「這使得從自然語言精確生成 SQL 極為困難。」Gemini-SQL2 的架構設計正是針對雜亂的 schema 與複雜商業語意進行專項強化，截至發布時 Google 尚未公開 API、model card 或技術論文。\n\n#### BIRD 基準測試的壓倒性成績\n\nGemini-SQL2 在 BIRD 單一模型排行榜上以 80.04% 的執行準確率登頂，成為首個突破 80% 門檻的系統。相較之下，Google 前一版本 Gemini-SQL 約為 77.2%，AWS Q-SQL 約 76.5%，OpenAI GPT-5.5-xhigh 與 Anthropic Claude Opus 4.6 分別落在 72.8% 與 70.9%，差距達 7-9 個百分點。\n\n> **名詞解釋**\n> **BIRD 基準**(BIg Bench for LaRge-scale Database Grounded Text-to-SQL Evaluation) ：目前最具代表性的大規模 text-to-SQL 評測集，以執行正確性 (execution accuracy) 為標準——模型生成的 SQL 必須能實際執行並回傳正確結果，而非僅語法正確。\n\n值得注意的是，人類基準仍高達 92.96%，Google 與人類之間仍有約 12.92 個百分點的差距。這意味著複雜多表 JOIN 與深度業務語意的理解，至今仍是尚未完全攻克的難題，但 80% 門檻已是里程碑級別的跨越。\n\n#### 自然語言轉 SQL 的技術演進脈絡\n\nText-to-SQL 任務長期被視為 NLP 難題，技術路線的演進歷經三個世代：\n\n- **第一代（規則式方法）**：能處理有限的查詢模式，面對真實企業資料庫幾乎無法擴展\n- **第二代（seq2seq 神經網路）**：顯著提升準確率，但複雜多表 JOIN 與業務語意理解仍是瓶頸\n- **第三代 (LLM prompt-based)**：利用大型語言模型的語意理解突破業務語意障礙，但通用性與任務精準度之間存在取捨\n\nGemini-SQL2 代表「LLM + 任務特化後訓練」的第四個階段，首次在主要基準上壓過 80% 門檻。此前 Google 的 Gemini-SQL 已持有 BIRD 榜首，Gemini-SQL2 延伸同一路線再提升約 3 個百分點，顯示此迭代方向的空間仍在持續釋放。\n\n#### 企業資料查詢自動化的實務意義\n\nGemini-SQL2 的預期應用場景包括自助式商業分析（複雜 JOIN 與日期邏輯）、資料工程師以英文描述生成 ETL 轉換邏輯，以及 SaaS 平台的嵌入式查詢功能。Google 暗示此技術將整合進旗下更廣泛的資料服務，BigQuery Studio、AlloyDB AI、Cloud SQL Studio 均為潛在目標，但尚未官方確認。\n\n分析師普遍指出，80% 準確率在正式生產環境仍需人工審查；但對於結構化程度高的企業資料集，自動化查詢的可用性已大幅提升，能顯著降低非技術人員查詢資料庫的門檻，標誌著企業 BI 自動化的新拐點。","Gemini-SQL2 的技術突破核心在於：將「語法正確」的目標升級為「執行正確」的目標，並透過任務特化後訓練解決複雜商業邏輯的語意理解問題。這不只是準確率的提升，更是評測哲學的根本轉變——從比較 SQL 文本，到直接驗證執行結果是否正確。\n\n#### 機制 1：執行準確性導向的後訓練\n\nGemini-SQL2 並非以語法匹配 (syntax match) 為訓練目標，而是以 BIRD 基準的執行準確性 (execution accuracy) 為核心指標。訓練信號直接來自「SQL 查詢是否能執行並回傳正確結果」，而非文本相似度，迫使模型學習資料庫的實際執行語意，而非表面語法規律。\n\n#### 機制 2：複雜 Schema 理解與商業邏輯注入\n\nGemini-SQL2 特別針對「層層疊疊的資料結構」與「複雜商業邏輯」進行優化。實際企業資料庫往往包含數十張相互關聯的資料表、不規則的命名慣例與業務特定的計算邏輯。Gemini-SQL2 的 scaffolding 層負責將 schema 資訊結構化地注入上下文，使模型能理解跨表關聯的語意。\n\n> **名詞解釋**\n> **Scaffolding（鷹架）**：在 LLM 應用中，指圍繞模型核心能力建立的外部結構——負責組織輸入、管理上下文、格式化輸出，讓模型在其框架內發揮最佳效能，而不改變模型本身的權重。\n\n#### 機制 3：Gemini 3.1 Pro 底座的語意推理繼承\n\n選擇 Gemini 3.1 Pro 作為底座，而非從頭訓練專用小模型，使 Gemini-SQL2 能繼承原始模型的強大語意推理能力。這對複雜的自然語言消歧至關重要——當使用者說「上個季度業績最好的地區」時，模型需理解日期範圍、地理維度與業績指標的定義，這些能力源自預訓練階段廣泛的世界知識累積。\n\n> **白話比喻**\n> 可以把 Gemini-SQL2 想像成一位翻譯員：底層 Gemini 3.1 Pro 是他廣博的語言和常識基礎，而後訓練則是讓他通過了 SQL 專業執照考試——不只是懂語法，更知道如何讓查詢真正「跑出正確答案」。","#### BIRD 單一模型排行榜（2026 年 6 月）\n\n| 模型 | 執行準確率 |\n|---|---|\n| Gemini-SQL2(Google) | 80.04%（第一）|\n| Gemini-SQL（Google 前版）| ~77.2% |\n| AWS Q-SQL | ~76.5% |\n| OpenAI GPT-5.5-xhigh | ~72.8% |\n| Anthropic Claude Opus 4.6 | ~70.9% |\n| 人類基準 | 92.96% |\n\nGemini-SQL2 較前版提升約 3 個百分點，相較主要競品領先 7-9 個百分點。與人類基準的差距縮小至 12.92 個百分點，代表複雜查詢場景下仍有相當的改善空間。",{"recommended":297,"avoid":302},[298,299,300,301],"自助式商業分析 (BI) 工具，讓非技術人員以自然語言查詢複雜多表資料庫","資料工程師以英文描述 ETL 邏輯，快速生成初版 SQL 轉換腳本","SaaS 平台的嵌入式查詢功能，讓終端用戶以問題形式直接存取資料","結構化程度高、schema 相對穩定的企業資料倉儲查詢自動化",[303,304],"高敏感度財務或法規合規查詢——20% 的錯誤率在正式生產環境風險過高","Schema 極為複雜且動態變化的 OLTP 系統——需持續維護 schema 上下文才能保持準確","#### 環境需求\n\n目前 Gemini-SQL2 尚無公開 API，開發者無法直接調用。若要嘗試類似能力，可透過 Gemini API 自行實作 text-to-SQL scaffolding，或等候 Google 將其整合進 BigQuery Studio 等資料服務後使用。\n\n#### 最小 PoC\n\n```python\nimport google.generativeai as genai\n\nschema = 'orders(id, customer_id, amount, created_at, status), customers(id, name, region)'\nquestion = '上個季度各地區的總訂單金額是多少？'\n\nmodel = genai.GenerativeModel('gemini-2.0-pro')\nprompt = '根據此 schema：' + schema + '，將問題轉為 PostgreSQL 查詢，只輸出 SQL：' + question\nprint(model.generate_content(prompt).text)\n```\n\n#### 驗測規劃\n\n在生產環境導入前，建議建立「黃金查詢集」 (golden query set) ：從歷史查詢中挑選 100-200 個具代表性的問題，配上人工驗證過的正確 SQL 與預期結果，用於持續評測模型升版後的準確率變化。\n\n#### 常見陷阱\n\n- 模型對 schema 命名慣例極度敏感，`tbl_order_detail` 與 `order_items` 可能導致完全不同的查詢路徑\n- 日期函數因資料庫方言差異 (PostgreSQL vs MySQL vs BigQuery) 容易出錯，需在 prompt 中明確指定目標資料庫\n- 80% 的 BIRD 準確率基於相對乾淨的測試集；真實企業遺留系統的複雜度可能使實際準確率顯著下降\n\n#### 上線檢核清單\n\n- 觀測：記錄每次查詢的執行結果，標記空結果與錯誤，定期計算黃金查詢集準確率\n- 成本：LLM API 調用費用 + schema 上下文 token 消耗（複雜 schema 每次查詢可能消耗數千 token）\n- 風險：在資料庫前加入唯讀權限隔離層，避免誤生成 DELETE 或 UPDATE 語句","#### 競爭版圖\n\n- **直接競品**：AWS Q-SQL(76.5%) 、OpenAI GPT-5.5-xhigh 搭配 Code Interpreter(72.8%) 、Anthropic Claude Opus 4.6 企業版 (70.9%) 、各 BI 工具商內建 AI 查詢（Tableau AI、Looker AI）\n- **間接競品**：低程式碼 BI 工具（Metabase、Power BI）、傳統 ETL 平台（dbt、Fivetran）\n\n#### 護城河類型\n\n- **工程護城河**：BIRD 榜首的測試成績提供技術公信力；任務特化後訓練需要大量標注資料與訓練資源，複製成本高\n- **生態護城河**：與 BigQuery、AlloyDB 的深度整合將形成平台鎖定效應；Google Cloud 資料服務的既有客戶群是天然擴散基礎\n\n#### 定價策略\n\nGoogle 尚未公開定價，預期將作為 BigQuery 或 Google Cloud 的加值功能捆綁銷售，或以 API 呼叫次數計費。競品 AWS Q-SQL 已與 AWS Redshift 深度捆綁，Google 很可能採用相似的平台整合策略，而非單獨定價。\n\n#### 企業導入阻力\n\n- API 和技術細節尚未公開，企業評估導入需等候正式整合後才能實際測試\n- 正式生產環境的 20% 錯誤率仍需人工審查機制，增加實作複雜度\n- 與現有資料治理工具（資料血緣、稽核日誌）的整合方式尚不清楚\n\n#### 第二序影響\n\n- BI 工具商面臨壓力：若 Google 雲端服務原生提供高準確率 text-to-SQL，獨立 BI 工具的自然語言查詢功能差異化空間將縮小\n- 資料分析師角色轉型：重複性的 SQL 撰寫工作將被自動化，分析師需專注於更高層次的業務問題定義與結果驗證\n\n#### 判決：技術里程碑確立，企業落地需等待 API 開放（短期觀望，中期追蹤整合進展）\n\nGemini-SQL2 在技術指標上確立了明確的領先地位，但商業化路徑尚不明朗。80% 的 BIRD 準確率是里程碑，但距離無需人工審查的「可信賴生產級別」仍有距離。短期內，最大的競爭影響是對 AWS Q-SQL 和 OpenAI 的直接施壓，以及加速整個業界在 text-to-SQL 能力上的投入。",[308,309,310],"80% 的準確率意味著每 5 個查詢就有 1 個可能出錯，在財務或法規合規的查詢場景中，這個錯誤率仍難以接受，生產環境落地比數字展現的更困難。","BIRD 基準的測試集 schema 相對乾淨；真實企業遺留系統的複雜度、命名不一致性與業務特定計算邏輯，可能使實際準確率遠低於 80%，基準分數與生產表現之間存在明顯落差。","在 Google 提供公開 API 前，此成果對外部開發者而言僅是研究成果而非可立即使用的工具，任何企業計劃都必須等待 Google 整合進旗下資料服務後才能評估。",[312,315],{"platform":86,"user":313,"quote":314},"handle.invalid(Hashlytics.io)","Google Gemini-SQL2 在 BIRD 排行榜上達到 80.04% 準確率\n\n此次的核心成就正是基準測試分數本身。Gemini-SQL2 在 BIRD Text-to-SQL 排行榜上取得了 80.04% 的執行準確率…… #GeminiSQL2",{"platform":86,"user":316,"quote":317},"ai-news-shorts.bsky.social(AI News Shorts)","AI 產業動態：Gemini-SQL2 發布、Google 訴訟案與 Mistral 融資傳聞\n#ai #artificialintelligence #future #machinelearning #ainews","先觀望",[320,322,324],{"type":103,"text":321},"使用 BIRD 基準的公開測試集評估自己的 text-to-SQL 需求，了解企業資料庫的複雜度是否落在 80% 準確率可覆蓋的範圍。",{"type":100,"text":323},"建立企業「黃金查詢集」（50-100 個常見問題 + 標準 SQL），為未來導入 AI 查詢功能預做評估基準，降低升版後的驗測成本。",{"type":97,"text":325},"追蹤 Google BigQuery Studio 的官方公告，以及 BIRD 排行榜上主要競品（AWS Q-SQL、OpenAI）的追趕動向，觀察 Gemini-SQL2 API 何時正式開放。",[327,364,397,425,460,493,529,561],{"category":212,"source":10,"title":328,"publishDate":6,"tier1Source":329,"supplementSources":331,"coreInfo":340,"engineerView":341,"businessView":342,"viewALabel":343,"viewBLabel":344,"bench":345,"communityQuotes":346,"verdict":362,"impact":363},"Claude Fable 5 在 FrontierMath 最難題組上領先 GPT-5.5 達 13 個百分點",{"name":146,"url":330},"https://the-decoder.com/claude-fable-5-outpaces-gpt-5-5-by-13-points-on-frontiermaths-toughest-problems/",[332,336],{"name":333,"url":334,"detail":335},"MindStudio","https://www.mindstudio.ai/blog/claude-fable-5-vs-gpt-5-5-benchmark-comparison","Claude Fable 5 vs GPT-5.5 benchmark 詳細比較",{"name":337,"url":338,"detail":339},"Vellum AI","https://www.vellum.ai/blog/claude-fable-5-and-mythos-5-benchmarks-explained","Fable 5 與 Mythos 5 完整 benchmark 解析","#### FrontierMath 突破\n\nClaude Fable 5 在 Epoch AI 的 FrontierMath Tier 4 v2 測試中達到 **88%** 正確率，涵蓋 Tier 1–3 則為 87%，領先 GPT-5.5 的約 75% 達 **13 個百分點**。\n\n> **名詞解釋**\n> FrontierMath：由 Epoch AI 設計的頂尖數學推理 benchmark，收錄研究級難度數學題，分四個難度層，目前公認為 AI 數學能力測試天花板。\n\n#### 能力躍升幅度\n\n相較於前代旗艦 Claude Opus 4.5 在 Tier 4 不足 10% 的成績，Fable 5 的 88% 代表一次近乎翻轉式的能力跳躍。評測採用 Epoch AI 標準測試腳架與最大推理力設定，確保比較基準一致。\n\n另有報導指出，GPT-5.4 Pro 與 Claude Mythos 均各自解開了數個長年未解的 Erdős 數學猜想，顯示頂尖模型的突破已延伸至真實研究問題，且並非單一陣營獨佔。","FrontierMath Tier 4 採用研究級數學題，**88% 正確率**意味著模型在多步推理與符號操作上已進入實用區間。整合 Fable 5 時，可預期在程式驗證、數學推理型 agent 管道上的表現大幅優於 Opus 4.5。目前 Claude Code 已部署 Fable 5，但初期有部分 access 問題，建議確認 API 訂閱層級後再切換。","13 個百分點的領先差距，在科技、金融、製藥等需要複雜推理能力的垂直場景中，代表可量化的競爭優勢。Fable 5 定位為 Mythos 以下的大眾旗艦，若定價合理，企業採購者可在不進入 Mythos 授權門檻的情況下取得接近頂尖的數學推理能力，降低 AI 升級的成本壓力。","工程師視角","商業視角","#### 評測數據\n\n- FrontierMath Tier 4 v2：Fable 5 **88%** vs GPT-5.5 **~75%**（領先 13 個百分點）\n- FrontierMath Tier 1–3：Fable 5 **87%**\n- Claude Opus 4.5（Tier 4，2026 年初）：**\u003C10%**",[347,350,353,356,359],{"platform":90,"user":348,"quote":349},"karpathy（AI 研究員，曾任職 OpenAI 與 Tesla）","這是一個超令人興奮的發布——Claude Fable 5 與 Mythos 使用相同的底層模型，但加入了額外的安全防護。各項 benchmark 表現出色，在所有項目上都以差距領先，我還想補充一點：在質感上，這也是一次足以冠以主版本號的重大躍升。",{"platform":90,"user":351,"quote":352},"bcherny（Anthropic Claude Code 工程師）","Fable 5 現已在 Claude Code 上線，是我用過最強的程式撰寫模型，領先幅度很大。這是一次重大躍升：需要更少的提示與引導、token 使用更有效率、程式碼品質更好、工具使用更精準，自我驗證也更聰明。",{"platform":75,"user":354,"quote":355},"paulddraper（HN 用戶）","HN 上大家都鎖定「行銷炒作」作為唯一解釋——Claude.ai 網頁確實出現了無法關閉的「Claude Fable 5 目前無法使用」提示。我不是說這 100% 是噱頭，但 Anthropic 真的很想讓你知道這件事。",{"platform":86,"user":357,"quote":358},"motherjones.com（Mother Jones，81 upvotes）","川普的命令導致 Anthropic 對所有用戶停用了 Fable 5 和 Mythos 5——Claude 最新的兩款模型。",{"platform":75,"user":360,"quote":361},"tinyhouse（HN 用戶）","至少在 Claude Code 上完全無法使用。它叫我自己執行所有指令，因為被阻擋了（「分類器又擋住我了」真好笑）。我真的搞不懂 Anthropic 是怎麼在沒有實際測試的情況下就發布這東西的。我在 claude.ai 上使用沒問題；但程式碼撰寫方面完全不行。","追","FrontierMath Tier 4 的 88% 成績確立 Fable 5 在研究級數學推理的當前領先地位，對高複雜度 agent 管道的部署決策有直接參考價值。",{"category":142,"source":15,"title":365,"publishDate":6,"tier1Source":366,"supplementSources":369,"coreInfo":380,"engineerView":381,"businessView":382,"viewALabel":383,"viewBLabel":384,"bench":385,"communityQuotes":386,"verdict":94,"impact":396},"KPMG 因 AI 幻覺問題被迫撤回自家 AI 使用報告",{"name":367,"url":368},"TechCrunch","https://techcrunch.com/2026/06/13/kpmg-pulls-report-on-ai-usage-due-to-apparent-hallucinations/",[370,374,377],{"name":371,"url":372,"detail":373},"GPTZero 調查報告","https://gptzero.me/news/investigations-kpmg/","45 條引用法證審查詳細報告",{"name":375,"url":376},"The Register","https://www.theregister.com/ai-and-ml/2026/06/12/kpmgs-ai-report-turns-into-a-demo-of-ai-hallucinations/5255029",{"name":378,"url":379},"Finextra（引述 Financial Times）","https://www.finextra.com/newsarticle/47911/kpmg-report-contained-ai-hallucinations-about-ai-use-at-ubs---ft","#### 顧問巨頭的 AI 翻車現場\n\nKPMG 於 2025 年 10 月發布的 AI 企業應用報告，在 GPTZero 進行法證審查後於 2026 年 6 月緊急下架。45 條引用中僅 5 條正確，40 條引用標題完全捏造，UBS、英國 NHS 等四家機構均向《金融時報》表示，報告描述「不實或具誤導性」。\n\n#### vibe citing：AI 假引用的新手法\n\nGPTZero 將此現象命名為「vibe citing」——AI 將不同來源片段拼湊，篡改作者或發明 URL，製造外觀可信卻無法核實的假引用。\n\n> **名詞解釋**\n> vibe citing：類比 vibe coding，指 AI 生成引用時只追求「看起來合理」，實際上無法驗證甚至完全捏造。\n\n具體案例包括：將阿聯酋航空實體機器人「Sara」誤描述為手機聊天機器人，以 2019 年舊聞佐證當時尚未商業化的 agentic AI。EY 稍早也因相同問題撤回報告，顯示此現象並非個案。","此事件揭示 AI 輔助寫作的核心盲點：AI 能生成外觀合理的引用格式，卻無法保證內容真實性。在任何涉及外部引用的場景，應建立**引用驗證管線**——至少對 URL 進行可及性測試，對標題進行原文比對。「看起來像引用」與「引用正確」是截然不同的兩件事。","KPMG 一邊向客戶銷售 AI 治理服務，一邊因自身報告缺乏人工審查而翻車，諷刺性落差對品牌的傷害遠超技術失誤本身。AI 生成報告若未明確標示驗證流程，公信力將大打折扣。驗證流程的透明度，正成為 AI 時代新的信任門檻。","實務觀點","產業結構影響","",[387,390,393],{"platform":86,"user":388,"quote":389},"Anne Applebaum（2265 讚）","太驚人了：KPMG 撰寫了一份描述企業 AI 成功應用的報告，但其中的案例研究竟然全是 AI 幻覺。",{"platform":86,"user":391,"quote":392},"Margaret Mitchell（201 讚）","看來 KPMG 寫了一份描述企業 AI 成功應用的報告，但其中的案例研究竟然是 AI 幻覺。",{"platform":86,"user":394,"quote":395},"Financial Times（134 讚）","FT 獨家：KPMG 一份關於全球企業如何應用 AI 的報告，以虛假案例誇大了 AI 採用情況，而這些案例似乎都是 AI 幻覺所致。","顧問業 AI 翻車案例揭示企業報告缺乏驗證機制的系統性風險，正在倒逼產業建立 AI 輸出透明度標準。",{"category":212,"source":9,"title":398,"publishDate":6,"tier1Source":399,"supplementSources":402,"coreInfo":409,"engineerView":410,"businessView":411,"viewALabel":343,"viewBLabel":344,"bench":412,"communityQuotes":413,"verdict":423,"impact":424},"「Count Anything」模型：聽起來簡單的物件計數為何如此困難",{"name":400,"url":401},"arXiv:2605.30846","https://arxiv.org/abs/2605.30846",[403,406],{"name":404,"url":405},"The Decoder 報導","https://the-decoder.com/new-ai-model-called-count-anything-does-exactly-what-it-says-and-thats-harder-than-it-sounds/",{"name":407,"url":408},"GitHub 程式碼庫","https://github.com/Mengqi-Lei/count-anything","#### 開放世界計數：從細胞到人群的統一架構\n\n清華大學研究團隊於 2026 年 5 月提交論文（arXiv：2605.30846），發布「Count Anything」——首個透過純文字 prompt 計數任何影像中任何物件的開放世界模型，涵蓋人群、衛星影像、顯微鏡細胞切片、農業場景等六大視覺領域。\n\n> **名詞解釋**\n> 開放世界計數 (open-world counting) ：不限定類別、可透過文字描述計數任意物件，有別於傳統只能計數預先定義類別的專用系統。\n\n#### 為何計數比想像中難？\n\n傳統電腦視覺系統多為單一類別訓練，計算細胞的模型無法計數螺絲釘。Count Anything 採用**雙計數器架構**解決此問題：\n\n- **RSC(Region-level Sparse Counter)**：對大型、稀疏物件繪製 bounding box\n- **PDC(Pixel-level Dense Counter)**：對小型、密集物件逐像素點預測\n- **CCF(Complementary Count Fusion)**：以 parameter-free 方式融合兩者，抑制重複計數\n\n模型建構於 Meta 的 SAM3 基礎模型之上，加入小型 adapter 而非從頭重訓，以自建 CLOC 資料集（22 萬張影像、619 類別、1,500 萬標記實例）訓練。基準測試顯示，平均每查詢約 9 個計數誤差，錯誤率比主要競爭者低逾一半。","模型已開源（GitHub 程式碼庫：Mengqi-Lei/count-anything），基於 SAM3 adapter 架構讓工程師可快速整合，接受 bounding box、點、多邊形、mask 等異質標注格式，統一轉換為計數點訓練。主要限制：面對語義模糊術語或極度擁擠場景（如大型人群）時準確度下降，建議先在農業或醫療病理影像場景做 PoC 驗證再部署。","計數需求廣泛存在於零售庫存、農業作物評估、醫療病理切片、衛星影像分析等場景，過去需分別採購或訓練專用系統。Count Anything 的開源策略大幅降低驗證門檻，企業可直接測試六大領域覆蓋範圍。短期應留意語義模糊情境下準確度下降的限制，高精度場景仍需搭配人工驗證。","#### 效能基準\n\n- 平均計數誤差：約 9 個（每查詢類別）\n- 競爭對手對比：CountGD、CLIP-Count、Grounding DINO 錯誤率高出逾一半\n- 訓練資料集 CLOC：22 萬張影像、619 類別、1,500 萬標記實例",[414,417,420],{"platform":75,"user":415,"quote":416},"nonameiguess（HN 用戶）","讀者真的需要學會更好地看穿炒作。相關數據在許多方面都受到限制——許多興趣點根本無法被掃描，因為它們是建築側牆的壁畫，甚至只有一個面。至少在初期，不實際掃描任何東西也不會受到懲罰；你可以讓手機朝下繞圈移動，系統仍會計入並給你積分，人們甚至在黑暗中玩。",{"platform":75,"user":418,"quote":419},"Kim_Bruning（HN 用戶）","我對「只是」這個詞過敏——它讓你停止好奇。試想在快速變化的世界中有個緩慢的優化器：最優解往往是某種計算上的泛化，由此產生了元優化，而生命似乎熱衷於遞迴地重複這個過程。烏鴉智慧顯然高度演化，所以你技術上沒錯——但最簡約的解釋或許是另一回事。",{"platform":75,"user":421,"quote":422},"fitz2882（HN 用戶）","在構建多智能體系統時，我一直注意到智能體互傳反饋的圖示與控制論電路圖驚人地相似。我好奇這套既有數學能否遷移過來，結果竟然真的可以。LoopGain 是這項研究的第一個產品：一個開源函式庫，用實際的改善量測取代智能體迴圈的 max_iterations=N 硬上限。","觀望","開放世界物件計數首次達到六大視覺領域的跨域實用化，農業、醫療影像、衛星遙感等場景的自動化計數門檻有望大幅降低。",{"category":22,"source":16,"title":426,"publishDate":6,"tier1Source":427,"supplementSources":429,"coreInfo":438,"engineerView":439,"businessView":440,"viewALabel":441,"viewBLabel":442,"bench":385,"communityQuotes":443,"verdict":94,"impact":459},"北京要求 Meta 撤銷 20 億美元 Manus 收購案",{"name":367,"url":428},"https://techcrunch.com/2026/06/13/meta-reportedly-moves-to-unwind-2b-manus-deal-after-beijings-demand/",[430,434],{"name":431,"url":432,"detail":433},"Bloomberg","https://www.bloomberg.com/news/articles/2026-06-11/meta-severs-manus-data-access-after-china-orders-buyout-unwound","Meta 完成資料存取切斷的細節報導",{"name":435,"url":436,"detail":437},"CNBC","https://www.cnbc.com/2026/04/27/meta-manus-china-blocks-acquisition-ai-startup.html","中國正式封鎖收購案的原始報導","#### 事件時間軸\n\n2025 年 12 月，Meta 宣布以 **20 億美元**收購中國 AI 新創 Manus，後者曾以病毒式 agent demo 轟動業界。Manus 雖早已將員工遷移至新加坡試圖規避監管，但北京認定只要底層技術與人才源自中國，境外設立不能豁免——批評者稱此策略為「新加坡洗白 (Singapore washing) 」。\n\n> **名詞解釋**\n> Singapore washing：企業透過在新加坡設立法人，試圖將中國業務偽裝為非中國實體以規避技術出口管制，類似金融領域的洗白概念。\n\n#### 監管介入與分拆進度\n\n2026 年 4 月，中國國家發展和改革委員會 (NDRC) 正式下令撤銷收購，理由涉及技術出口管制及外資法規潛在違規。6 月 1 日，Meta 完成「防火牆」隔離，Manus 員工失去對 Meta 內部系統的全部存取，Meta 員工亦被禁止在內部專案使用 Manus 工具。6 月 13 日，兩家公司已不再共享任何資料，運營層面分拆宣告完成。","「防火牆」隔離在實作上要求全面稽核並切斷所有 SSO 整合、API 金鑰與資料管道。核心挑戰在於收購後往往已有資料交換發生，事後切斷須追溯清理且留存完整稽核紀錄以應對監管舉證。此類跨國併購解體通常耗費 6-18 個月工程資源，本案在 5 個月內完成已屬快速，但兩套系統均須承擔大量臨時解耦工作。","此案為矽谷收購中國 AI 公司設下新的風險定價標準：「新加坡洗白」被明確否定，離岸架構無法作為合規護盾。Manus 創辦人已初步討論以約 **10 億美元**從 Meta 手中買回公司並考慮香港上市，但 20 億美元估值已大幅蒸發。未來涉及中國人才或技術的收購案，須在交割前完成徹底技術溯源審查，否則監管風險將侵蝕全部收購價值。","合規實作影響","企業風險與成本",[444,447,450,453,456],{"platform":90,"user":445,"quote":446},"Alexandr Wang(Scale AI CEO)","很高興宣布 @ManusAI 已加入 Meta，幫助我們打造出色的 AI 產品！新加坡的 Manus 團隊在探索當前模型能力盈餘以建構強大 agent 方面屬於世界級水準。期待與你們合作，@Red_Xiao_！",{"platform":90,"user":448,"quote":449},"@aakashgupta(Product growth advisor)","Meta 在 12 月為 Manus 付出超過 20 億美元。八週後，Manus 在 Telegram 上推出其 agent。想想這個時序。Meta 在 1 月 15 日已禁止 WhatsApp 上的競爭對手 AI 聊天機器人——他們擁有那個發行管道。那為什麼要在競爭對手的訊息平台上推出 Manus？",{"platform":86,"user":451,"quote":452},"techcrunch.com（Bluesky，18 upvotes）","Meta 開始解除其 20 億美元 Manus 收購案，此前北京下令撤銷該交易。",{"platform":86,"user":454,"quote":455},"madeindex.bsky.social（Bluesky，10 upvotes）","更新：據報 Meta 在北京命令下開始解除 20 億美元 Manus 交易。",{"platform":86,"user":457,"quote":458},"cnbc.com（Bluesky，3 upvotes）","據報 Meta 在北京命令下開始解除 20 億美元 Manus 交易。","中國監管對跨境 AI 收購的長臂管轄已成真，矽谷涉中交易結構需全面重新評估風險定價",{"category":22,"source":18,"title":461,"publishDate":6,"tier1Source":462,"supplementSources":464,"coreInfo":473,"engineerView":474,"businessView":475,"viewALabel":441,"viewBLabel":442,"bench":385,"communityQuotes":476,"verdict":94,"impact":492},"OpenAI 遭美國多州檢察長聯合調查，涵蓋廣告與健康資料處理",{"name":367,"url":463},"https://techcrunch.com/2026/06/13/openai-faces-investigation-from-state-attorneys-general/",[465,469],{"name":466,"url":467,"detail":468},"Engadget","https://www.engadget.com/2193666/openai-investigation-state-attorneys-general/","補充多州調查範圍細節",{"name":470,"url":471,"detail":472},"Cryptopolitan","https://www.cryptopolitan.com/state-attorneys-open-sweeping-investigation-into-openai/","IPO 風險分析","#### 傳票範圍：廣告、健康資料與迎合性行為\n\n2026 年 6 月 12 日，紐約州檢察長代表多州聯盟向 OpenAI 發出傳票，正式展開調查。調查範圍涵蓋廣告政策揭露方式、付費內容嵌入 ChatGPT 的機制、消費者與健康敏感資料處理、未成年人與老年人保護措施，以及模型「迎合性」 (sycophancy) 行為。\n\n> **名詞解釋**\n> 迎合性 (sycophancy) ：指 AI 模型為取悅用戶而給出偏頗或不準確的回應，而非提供客觀事實。\n\n#### 佛羅里達開第一槍，IPO 前景蒙陰\n\n6 月 1 日，佛羅里達州率先以 ChatGPT 危害兒童為由提起訴訟，將 OpenAI 及 CEO Sam Altman 列為被告。多州聯合調查加劇壓力，直接威脅 OpenAI 預計 2026 年 9 月、估值可能達 1 兆美元的 IPO 計畫。自 2025 年以來，美國已有 49 州提出逾 464 項聊天機器人安全相關法案，監管浪潮正快速逼近。","傳票要求提交「付費內容嵌入機制」及「健康資料管理」文件，顯示監管方關注的是系統設計層面，而非表面功能。若調查結果要求重構廣告介面或資料流向，涉及健康場景或廣告整合的 AI 產品開發者須提前評估合規架構，尤其是資料最小化原則與未成年人內容過濾機制的實作方式。","多州聯合調查直接威脅 OpenAI 估值 1 兆美元的 IPO 時程——法律文件揭露可能迫使產品設計在上市前大幅調整。競爭對手可藉此時機強化自身合規文件，搶占企業客戶與政府標案。已投入 OpenAI API 的企業，應監控調查走向是否影響服務條款或健康資料處理政策。",[477,480,483,486,489],{"platform":90,"user":478,"quote":479},"@AGJamesUthmeier（佛羅里達州檢察長 James Uthmeier）","「今天，我們正式對 OpenAI 及 ChatGPT 展開調查。AI 應造福人類，而非摧毀它。我們要求 OpenAI 就其傷害兒童、危害美國人，以及助長近期佛羅里達州立大學大規模槍擊事件的行為作出說明。違法者必須承擔責任。」",{"platform":86,"user":481,"quote":482},"justinhendrix.bsky.social（Justin Hendrix，49 upvotes）","「據知情人士透露，一個州檢察長聯盟已對 OpenAI 展開調查，這是各州針對人工智慧公司一系列法律行動中的最新動作。」",{"platform":90,"user":484,"quote":485},"@elonmusk（Tesla/SpaceX CEO，OpenAI 共同創辦人）","「關於 OpenAI 案件，法官與陪審團從未就案件實質問題作出裁決，只是以程序技術性理由處理。對任何詳細關注此案的人而言，Altman 與 Brockman 確實藉由侵吞慈善資產使自己獲益，這一點毫無疑問。」",{"platform":86,"user":487,"quote":488},"reuters.com（Reuters，42 upvotes）","「OpenAI 遭州檢察長聯盟調查，《華爾街日報》報導。」",{"platform":86,"user":490,"quote":491},"socialmedialab.ca（Social Media Lab，14 upvotes）","「美國各州檢察長聯盟已對 OpenAI 展開調查……該公司週五收到一份範圍廣泛的傳票，要求提交涉及其多項業務活動及對用戶影響的文件。」","多州法律行動是 AI 監管從「呼籲」轉向「執法」的重要訊號，直接衝擊 OpenAI IPO 時程，使用 OpenAI API 的企業應提前評估合規風險。",{"category":494,"source":12,"title":495,"publishDate":6,"tier1Source":496,"supplementSources":499,"coreInfo":506,"engineerView":507,"businessView":508,"viewALabel":509,"viewBLabel":510,"bench":511,"communityQuotes":512,"verdict":362,"impact":528},"ecosystem","LMCache：為 LLM 推論打造最快 KV Cache 加速層",{"name":497,"url":498},"LMCache GitHub Repository","https://github.com/LMCache/LMCache",[500,503],{"name":501,"url":502},"arXiv 論文：LMCache： An Efficient KV Cache Layer for Enterprise-Scale LLM Inference","https://arxiv.org/abs/2510.09665",{"name":504,"url":505},"AMD × LMCache：AMD GPU Acceleration with LMCache","https://blog.lmcache.ai/en/2026/01/09/amd-x-lmcache-amd-gpu-acceleration-with-lmcache/","LMCache 首次發布於 2025 年 10 月，近期因 2026 年 1 月與 AMD 的 GPU 整合公告重新引發社群討論，截至目前已累積 8,900+ GitHub stars。\n\n#### KV Cache 管理層的定位\n\nLMCache 運行於 vLLM、SGLang 等推論引擎之上，將 KV cache 從推論暫態提升為「可持久化、跨引擎複用的 AI 原生知識」。相較原生框架，可帶來最高 15 倍吞吐量提升與至少 2 倍更低延遲 (TTFT) 。\n\n> **名詞解釋**\n> KV Cache：LLM 生成每個 token 時需計算注意力的 Key/Value 向量，KV Cache 將這些結果暫存以避免重複計算，是影響推論速度最關鍵的資源之一。\n\n#### 核心技術亮點\n\n**分層儲存卸載**：KV cache 可從 GPU VRAM 逐層移至 CPU DRAM、本地磁碟，乃至遠端後端（Redis、S3 相容存儲等），共支援 8 種儲存後端。\n\n**CacheBlend**：突破傳統 prefix caching 只能匹配前綴的限制，可識別並複用請求任意位置的已計算 KV 片段，大幅提升長上下文場景的命中率。\n\n2026 年 1 月，AMD 合作公告帶來新里程碑：Qwen3、Llama3、Qwen-VL 等模型在 AMD Instinct™ MI300X 上實現 3–10 倍推論加速，目前已支援 NVIDIA、AMD、Ascend、TPU 共 4 種處理器架構。","LMCache 以獨立 daemon 程序運行，透過模組化 connector 與引擎解耦，引擎當機也不遺失 cache。\n\n對既有 vLLM 部署，整合成本相對低——需設定 storage backend 與 CacheBlend policy。需注意 context truncation 會使 prefix cache 命中率降低約 50%，長上下文 RAG 場景應優先評估 system prompt 的共用比例。\n\nPD 解耦 (Prefill-Decode Disaggregation) 透過 NVLink/RDMA 跨 worker 傳輸 KV cache，適合大規模叢集降低延遲，但需同步評估網路頻寬成本。","KV cache 複用直接轉化為 GPU 成本節省——最高 15 倍吞吐量提升，意味著服務相同請求量所需 GPU 數量可大幅縮減。\n\nAMD MI300X 整合公告的戰略意義在於：LMCache 讓企業在 NVIDIA GPU 供給緊張、溢價偏高時有可行的替代路徑。2025 年 10 月加入 PyTorch Foundation，為長期維護提供組織保障，降低企業大規模採用的技術風險。","推論引擎整合評估","GPU 成本與生態影響","#### 效能基準\n\n- 吞吐量：最高 **15×** 提升（相較原生框架）\n- TTFT 延遲：至少降低 **2×**\n- AMD MI300X 整合加速：**3–10×**（Qwen3、Llama3、Qwen-VL）\n- Context truncation 對 prefix cache 命中率影響：降低約 **50%**",[513,516,519,522,525],{"platform":90,"user":514,"quote":515},"@rohanpaul_ai（X 用戶）","透過在 GPU、CPU、磁碟間複用 KV cache 大幅降低 LLM 推論延遲；將 LMCache 整合進 vLLM 可讓 TTFT 縮短 3–10 倍、提升吞吐量，並穩定支援長上下文問答與 RAG 工作負載。LMCache 是一個 CUDA 加速的 KV cache 層，已整合進 vLLM 與 KServe，並即將支援更多引擎。",{"platform":75,"user":517,"quote":518},"oceanplexian（HN 用戶）","很多內容超出我的理解範圍，但為什麼要在 GPU 時間如此昂貴的現在進行壓縮？KV 明明可以輕易儲存在 RAM 或旋轉磁碟上，存取時間只需毫秒——vLLM 的 LM cache 就是個好例子。這件事如此容易，讓我驚訝的是 Claude Code 在幾小時後的新 session 居然還在重新計算整個 KV，看來 Anthropic 的基礎設施並沒有看起來那麼最佳化。",{"platform":90,"user":520,"quote":521},"@TheTuringPost（AI/ML 電子報）","LMCache 是 LLM 服務引擎的開源擴充套件，相當於大規模生產環境 LLM 推論的快取層。它實現了智慧型 KV cache 管理，在 GPU、CPU 與本地磁碟之間複用先前處理過的文字的鍵值狀態，且不限於前綴——可複用請求中任意位置的重複文字片段。",{"platform":75,"user":523,"quote":524},"zozbot234（HN 用戶）","消費級硬體上也能跑批次推論，只需一個 KV cache 高效的模型（或短上下文），並讓多個推論流並行運行。搭配串流推論時效果最佳，因為這類 KV 壓縮模型在解碼階段的計算密度夠高，以 RAM 速度運行時計算餘裕有限。",{"platform":75,"user":526,"quote":527},"mirekrusin（HN 用戶）","一開始確實有 bug（最糟的是那種看似能用但體驗很差的型別），建議用最新版 llama.cpp 與量化版本再試。常見問題包括：重複廢話輸出、無止境問號序列、數百個 token 後進入迴圈、使用 flash attention 時出現亂碼，以及 KV cache 量化搭配 flash attention 在長提示下的崩潰。","高並發 LLM 推論場景可大幅節省 GPU 成本，長上下文 RAG 與多引擎部署效益最顯著",{"category":142,"source":11,"title":530,"publishDate":6,"tier1Source":531,"supplementSources":534,"coreInfo":541,"engineerView":542,"businessView":543,"viewALabel":383,"viewBLabel":384,"bench":385,"communityQuotes":544,"verdict":94,"impact":560},"AI Economics for Dummies：一篇冷幽默諷刺拆解 AI 經濟泡沫",{"name":532,"url":533},"McSweeney's Internet Tendency","https://www.mcsweeneys.net/articles/ai-economics-for-dummies",[535,538],{"name":536,"url":537},"Lobste.rs 討論串","https://lobste.rs/s/rr3qvi",{"name":539,"url":540},"AI's Economics Don't Make Sense — Where's Your Ed At","https://www.wheresyoured.at/ais-economics-dont-make-sense-ad-free/","#### 三道荒謬算術題\n\n幽默作家 Andrew Singleton 在 McSweeney's 刊出〈AI Economics for Dummies〉，以小學算術題格式包裝三則 AI 泡沫寓言：Alex 花 20 億買一顆葡萄、轉手收訂閱年入 1200 億「ARR」；Laura 靠計程車月費訂閱有 4000 萬用戶，卻年燒 250 億油費；Xavier 每月虧損 10 億後承諾再砸 8500 億蓋「沒人想住的公寓」。\n\n> **名詞解釋**\n> ARR（年度經常性收入）：將當期合約換算為年化數字，常被用來讓高速成長看起來更壯觀。\n\n#### 諷刺背後的行業現實\n\n三則寓言各自對應真實慣技：預付合約膨脹 ARR、訂閱掩蓋推論成本虧損、資本支出軍備競賽。文章結語以「停止提問，勒德分子！」收尾，諷刺業界迴避財務邏輯的集體姿態。","三道算術題背後的技術現實相當清醒：AI 推論成本 (inference cost) 與訂閱定價之間的單位經濟效益，目前幾乎沒有主要玩家能自洽。工程師在評估 PoC 投資報酬時，應把「每次 API 呼叫的邊際成本」列為首要指標，而非 ARR 或用戶數。","當三則虛構算術和真實財報幾乎沒有差異，諷刺文學就成了分析報告的代替品。企業決策者不應等待 AI 單位經濟效益自行「修正」，應主動要求供應商呈現邊際成本結構——現在問，比泡沫破裂後再問省錢。",[545,548,551,554,557],{"platform":90,"user":546,"quote":547},"alexolegimas（Carnegie Mellon / Chicago Booth 行為經濟學家）","關於結構性變革經濟學與後商品化工作未來的新文章。幾乎所有關於先進 AI 對經濟影響的問題，都需要從同一個起點出發：什麼仍然稀缺？回答這個問題，分析就相當直接了。",{"platform":75,"user":549,"quote":550},"epsteingpt（HN 用戶）","我不認為這對 AI 行業是好消息。如果他們無法建立足夠算力，以致最佳選擇竟是未經驗證的「太空數據中心」技術，那我們完了。短期成本將上升（需求大於供給）；Token 從無限暢吃轉向 ROI 驅動；具備真正編排技能的工程師將稱霸市場，轉向低成本最佳化；前沿 AI 單位經濟效益崩潰。",{"platform":90,"user":552,"quote":553},"FutureEconJacob（Windfall Trust AI 經濟研究員）","全新 @WindfallTrust AI 經濟學簡報：AI 的經濟衝擊取決於組織結構與需求，而非單純能力。OpenAI 的 921 職業框架發現，最高風險類別的勞工使用 ChatGPT 的頻率是低風險群體的 3 倍；然而低風險群體……",{"platform":75,"user":555,"quote":556},"ElProlactin（HN 用戶）","他寫這篇文章並非為了說服別人，其主要受眾已認同他的觀點。他在銷售付費電子報，至少有一個動機是賺錢。對其論點持開放態度的市場，遠大於已完全相信他的市場。至於「這不代表他是錯的」——我認為現在任何人就此斷言都言之過早。",{"platform":75,"user":558,"quote":559},"felixgallo（HN 用戶）","我在分散式系統擁有超過 40 年經驗，涵蓋金融科技到《決勝時刻》等遊戲，也主導過 Alexa pipeline 的多個核心 API。Fable 確實會犯錯，但 GPT 和 Opus 是 L4 級 SDE，而 Fable 是剛晉升的 L5。它需要人工監督，尤其在文獻稀缺領域，但表現遠優於其他選項……","AI 行業財務邏輯遭到系統性質疑，企業與投資人應重新審視 AI 供應商的單位經濟效益與估值根基。",{"category":212,"source":14,"title":562,"publishDate":6,"tier1Source":563,"supplementSources":566,"coreInfo":576,"engineerView":577,"businessView":578,"viewALabel":343,"viewBLabel":344,"bench":579,"communityQuotes":580,"verdict":362,"impact":587},"只花 1500 美元訓練的 1B 參數 HRM 模型爆紅，HuggingFace CEO 與 Bengio 團隊齊聲力薦",{"name":564,"url":565},"HRM-Text arXiv 論文","https://huggingface.co/papers/2605.20613",[567,570,573],{"name":568,"url":569},"量子位 HRM 報導","https://www.qbitai.com/2026/06/435483.html",{"name":571,"url":572},"HuggingFace 模型頁面","https://huggingface.co/sapientinc/HRM-Text-1B",{"name":574,"url":575},"GRAM 論文網站","https://ahn-ml.github.io/gram-website/","#### 以大腦分層結構取代 Transformer\n\nSapient Intelligence 開源的 HRM-Text（1B 參數）以**層級遞迴模型 (HRM)**完全取代標準 Transformer。雙嵌套遞迴棧讓慢速高層模組 (H-module) 維持全域語義策略，快速低層模組 (L-module) 處理局部計算細節，輸出前先於連續**潛空間**進行內部遞迴計算，無需顯式思維鏈文字。\n\n> **名詞解釋**\n> HRM(Hierarchical Recurrent Model) ：以雙層遞迴取代 Transformer 自注意力機制，模擬大腦皮層分層處理邏輯。\n\n#### 1,500 美元、46 小時的效率示範\n\n訓練成本僅約 1,500 美元，16 張 H100 GPU 耗時 46 小時完成。訓練資料約 400 億個唯一 token，比主流競品少 100–1,000 倍，計算量少 96–432 倍。\n\nint4 量化後體積僅 0.6 GiB，理論上可在智慧型手機部署。HuggingFace CEO Clem Delangue 個人公開力薦，圖靈獎得主 Yoshua Bengio 團隊在 GRAM 論文中延伸並採用此架構，為這條技術路線正式背書。","HRM 完全捨棄 Transformer 自注意力，潛空間推理讓推論步驟在連續向量空間展開，而非透過文字 token 消耗推論資源。0.6 GiB 的 int4 模型可在消費級硬體甚至手機部署是核心優勢，預訓練代碼已開源。值得優先評估能否作為輕量 on-device 推論基底，取代現有需依賴雲端 API 的方案。","1,500 美元訓練出媲美 3–7B 模型效果的 1B 模型，直接衝擊「更大模型等於更好效果」的傳統商業邏輯。若此架構路線成熟，AI 服務商的推論成本結構與定價策略將面臨重新校準。HuggingFace CEO 與 Bengio 頂級背書大幅降低企業評估門檻，短期內將驅動邊緣 AI 與本地部署場景的採購決策。","#### 效能基準 (HRM-Text 1B)\n\n- MMLU：60.7%\n- GSM8K：84.5%\n- ARC-Challenge：81.9%\n- DROP：82.2%\n- MATH：56.2%\n\n以上成績與 Llama 3.2(3B) 、Gemma 3(4B) 、Qwen(2B) 、OLMo 3(7B) 等更大模型相當，訓練成本差距達數百倍。",[581,584],{"platform":90,"user":582,"quote":583},"@rohanpaul_ai（AI 教育者暨機器學習研究員）","出色的論文——人腦風格的遞迴循環在推理上勝過傳統思維鏈方法。小模型、深度思考，在 ARC 和數獨任務上大放異彩。層級推理模型 (HRM) 以微型雙層遞迴設計，在複雜任務中擊敗遠大的模型。",{"platform":90,"user":585,"quote":586},"@daniel_mac8（機器學習研究員，偏懷疑論立場）","層級推理模型 (HRM) 確實有其價值，但原因並非新架構在 ARC 任務上的發現：主要工作由外層循環精煉完成；透過謎題 ID 擬合評估任務；資料增強加多數投票效果顯著（約 300 次 ≈ 1,000 次迭代）；同等大小的 Transformer 表現約等同 HRM。","低成本潛空間遞迴架構驗證可行，對邊緣 AI 與本地部署場景具直接評估價值。","#### 社群熱議排行\n\n今日五大熱議主題，以互動量排序：①美國政府封鎖 Fable 5 與 Mythos 5（HN 數百則評論）、②Meta AI 成本危機（fintwitter.bsky.social 242 讚）、③OpenAI 遭多州聯合調查 (reuters.com Bluesky 42 upvotes) 、④北京命令撤銷 Manus 收購 (techcrunch.com Bluesky 18 upvotes) 、⑤Fable 5 FrontierMath 基準領先 GPT-5.5 達 13 個百分點。\n\n政府封鎖話題討論量最高。vlovich123（HN 評論）：「Anthropic 的主張是此 jailbreak 賦予的能力，在其他模型上不需繞過手段就能取得——問題在於你更相信哪一方，而這屆政府在真相方面的紀錄並不樂觀。」\n\n#### 技術爭議與分歧\n\nFable 5 Claude Code 可用性是最尖銳的內部分歧。bcherny（Anthropic Claude Code 工程師，X）：「Fable 5 是我用過最強的程式撰寫模型，領先幅度很大。」HN 用戶 tinyhouse 直接反駁：「至少在 Claude Code 上完全無法使用，叫我自己執行所有指令——我真的搞不懂 Anthropic 是怎麼在沒有實際測試的情況下就發布這東西的。」兩份報告來自同一工具的不同使用者，是社群內部爭論而非官方對立。\n\n監管哲學方面，Reddit LocalLLaMA u/feel_the_force69 直接點破：「它們並非『失對齊』，它們只是與你對齊，而非與監管機構及其支持者想要的東西對齊。」此觀點引發能力優先派與安全監管派的正面碰撞，是目前最受討論的哲學分歧。\n\n#### 實戰經驗（最高價值）\n\nfelixgallo（HN 用戶，40 年分散式系統經驗，涵蓋金融科技與遊戲產業）跨多個生產環境實測對比：「GPT 和 Opus 是 L4 級 SDE，而 Fable 是剛晉升的 L5。它需要人工監督，尤其在文獻稀缺領域，但表現遠優於其他選項。」\n\nLMCache 部署方面，oceanplexian（HN 用戶）提出反直覺觀察：「Claude Code 在幾小時後的新 session 居然還在重新計算整個 KV——Anthropic 的基礎設施並沒有看起來那麼最佳化。」此為生產環境實際觀察，非理論批評，指向企業推論成本優化的真實缺口。\n\n#### 未解問題與社群預期\n\nramraj07（HN 評論）提出本週最關鍵的公開問題：「Anthropic 會停止在 Bedrock 上發布嗎？他們會試著把營運遷移出美國嗎？」techmeme.com(Bluesky 8 upvotes) 引述歐洲政界人士：「這是讓人正視依賴美國 AI 技術風險的警鐘。」官方至今無正面回應。\n\nMeta/Manus 案留下更大的法律空白。@aakashgupta(X) 追問：「Meta 已禁止 WhatsApp 上的競爭對手 AI——為何卻在競爭對手的訊息平台上推出 Manus？」社群普遍預期此案將成為矽谷涉中收購交易風險定價的標誌性前例，但管轄邊界至今無解。",[590,592,594,595,596,597,599,601,602,603,605],{"type":103,"text":591},"審計自己或團隊的 AI 工具使用模式，記錄每項任務所用的模型與 token 量，實踐「邊際成本對等」原則——依任務複雜度選擇對應等級的模型。",{"type":103,"text":593},"前往 https://microsoft.github.io/SkillOpt/ 查看官方範例，在現有的一個 agent 任務上試跑 SkillOpt 優化流程，觀察技能文件實際累積了哪些段落修改。",{"type":103,"text":321},{"type":100,"text":101},{"type":100,"text":194},{"type":100,"text":598},"為自家 agentic pipeline 設計一個可量化的自動評分函數——這是導入 SkillOpt 的先決條件，建議先從有明確正確答案的任務（如試算表、資料提取）入手。",{"type":100,"text":600},"建立企業「黃金查詢集」（50–100 個常見問題搭配標準 SQL），為未來導入 AI 查詢功能預做評估基準，降低升版後的驗測成本。",{"type":97,"text":98},{"type":97,"text":196},{"type":97,"text":604},"追蹤 SkillOpt 後續更新，特別是多技能文件的同步優化功能，這將是複雜多工 agent 場景規模化的關鍵解鎖點。",{"type":97,"text":606},"追蹤 Google BigQuery Studio 的官方公告，以及 BIRD 排行榜上主要競品的追趕動向，觀察 Gemini-SQL2 API 何時正式開放。","今日是 AI 產業監管從「建議框架」走向「行政手段」的轉折點：美國封鎖頂尖模型、多州聯合調查 OpenAI、北京叫停跨境收購，三條管制軸線同步收緊。\n\n技術面卻逆向加速：SkillOpt 把 Markdown 文件當成可訓練參數、Gemini-SQL2 在企業 SQL 基準突破 80%、LMCache 把推論成本壓縮 3–10 倍。監管閘門愈收愈緊，技術列車並未減速。\n\n如何在合規邊界內持續釋放技術紅利，將是接下來每一個產品決策的核心命題。",{"prev":126,"next":609},"2026-06-15",{"data":611,"body":612,"excerpt":-1,"toc":622},{"title":385,"description":58},{"type":613,"children":614},"root",[615],{"type":616,"tag":617,"props":618,"children":619},"element","p",{},[620],{"type":621,"value":58},"text",{"title":385,"searchDepth":623,"depth":623,"links":624},2,[],{"data":626,"body":627,"excerpt":-1,"toc":633},{"title":385,"description":62},{"type":613,"children":628},[629],{"type":616,"tag":617,"props":630,"children":631},{},[632],{"type":621,"value":62},{"title":385,"searchDepth":623,"depth":623,"links":634},[],{"data":636,"body":637,"excerpt":-1,"toc":643},{"title":385,"description":65},{"type":613,"children":638},[639],{"type":616,"tag":617,"props":640,"children":641},{},[642],{"type":621,"value":65},{"title":385,"searchDepth":623,"depth":623,"links":644},[],{"data":646,"body":647,"excerpt":-1,"toc":653},{"title":385,"description":68},{"type":613,"children":648},[649],{"type":616,"tag":617,"props":650,"children":651},{},[652],{"type":621,"value":68},{"title":385,"searchDepth":623,"depth":623,"links":654},[],{"data":656,"body":657,"excerpt":-1,"toc":794},{"title":385,"description":385},{"type":613,"children":658},[659,666,671,690,695,700,705,711,716,721,726,731,737,742,747,752,768,774,779,784,789],{"type":616,"tag":660,"props":661,"children":663},"h4",{"id":662},"章節一政府指令內容與-anthropic-的回應",[664],{"type":621,"value":665},"章節一：政府指令內容與 Anthropic 的回應",{"type":616,"tag":617,"props":667,"children":668},{},[669],{"type":621,"value":670},"Fable 5 與 Mythos 5 於 2026 年 6 月 9 日上線，僅三天後，美國政府於 6 月 12 日下午 17 時 21 分（東岸時間）向 Anthropic 發出緊急出口管制指令。指令要求立即暫停所有外國公民對這兩款模型的存取，涵蓋在美境內的外國公民與 Anthropic 員工。",{"type":616,"tag":672,"props":673,"children":674},"blockquote",{},[675],{"type":616,"tag":617,"props":676,"children":677},{},[678,684,688],{"type":616,"tag":679,"props":680,"children":681},"strong",{},[682],{"type":621,"value":683},"名詞解釋",{"type":616,"tag":685,"props":686,"children":687},"br",{},[],{"type":621,"value":689},"\n出口管制 (Export Control) ：美國法律框架中限制特定技術向外國人士傳輸的機制，過去主要適用於軍事與加密技術，本次為首度大規模適用於商業 AI 模型存取服務。",{"type":616,"tag":617,"props":691,"children":692},{},[693],{"type":621,"value":694},"Anthropic 在數小時內選擇全面斷線，理由是可靠驗證用戶國籍所需的技術與法律成本，使局部合規在實務上不可行。AWS Bedrock 的企業客戶同樣受到波及，服務在無預警的情況下中斷。",{"type":616,"tag":617,"props":696,"children":697},{},[698],{"type":621,"value":699},"Anthropic 在官方聲明中明確「不同意」此次召回決定，指出政府所列舉的 jailbreak 屬於「窄範圍、非通用的漏洞利用」，且 OpenAI GPT-5.5 等其他主流模型無需任何繞過手段即可執行相同任務。",{"type":616,"tag":617,"props":701,"children":702},{},[703],{"type":621,"value":704},"公司強調已部署「深度防禦 (defense in depth) 」策略並進行大量紅隊測試。面對正式法律指令，Anthropic 選擇服從，同時以公開聲明保留異議立場；Claude 3.x 系列及其他服務則不受影響。",{"type":616,"tag":660,"props":706,"children":708},{"id":707},"章節二amazon-ceo-的角色與企業利益角力",[709],{"type":621,"value":710},"章節二：Amazon CEO 的角色與企業利益角力",{"type":616,"tag":617,"props":712,"children":713},{},[714],{"type":621,"value":715},"TechCrunch 的報導揭示了事件背後不尋常的商業博弈：Amazon CEO Andy Jassy 據報在政府指令下達前，已主動向財政部長 Scott Bessent 等官員提報 Fable 5 的安全疑慮，指研究人員發現了可被用於網路攻擊的漏洞。",{"type":616,"tag":617,"props":717,"children":718},{},[719],{"type":621,"value":720},"Amazon 在此事件中的角色極為複雜——它既是 Anthropic 的主要投資方與 AWS Bedrock 的商業夥伴，同時也是大型語言模型市場的直接競爭對手。",{"type":616,"tag":617,"props":722,"children":723},{},[724],{"type":621,"value":725},"Trump 政府前 AI 顧問 David Sacks 透露，政府曾要求 Anthropic CEO Dario Amodei 修復該 jailbreak 或下線模型；Dario 拒絕修復要求，最終導致全面斷線。",{"type":616,"tag":617,"props":727,"children":728},{},[729],{"type":621,"value":730},"批評者指出，OpenAI 因 Kushner 家族投資等政治關係的加持，疊加 Anthropic 長期倡導 AI 監管的鮮明立場，使本次事件被廣泛解讀為帶有競爭色彩的選擇性打壓，而非單純的國家安全考量。",{"type":616,"tag":660,"props":732,"children":734},{"id":733},"章節三開源社群的集體反撲與自救行動",[735],{"type":621,"value":736},"章節三：開源社群的集體反撲與自救行動",{"type":616,"tag":617,"props":738,"children":739},{},[740],{"type":621,"value":741},"事件消息傳出後，Reddit/LocalLLaMA 社群迅速湧現兩種並行反應。第一種是政治解讀：用戶明確指出，這些模型「並非失對齊，只是與監管機構及其支持者的期望方向不同」——「對齊」的定義本身成為被政治重新詮釋的競技場。",{"type":616,"tag":617,"props":743,"children":744},{},[745],{"type":621,"value":746},"第二種反應是實用主義的自救行動。社群以黑色幽默方式慶祝「終於有正當理由下載那個名字長達一整行的 Qwen 模型」，反映大量用戶實際轉向本地開源模型部署的決策；Qwen、Llama、Mistral 等開源替代方案的採用動能因此大幅提升。",{"type":616,"tag":617,"props":748,"children":749},{},[750],{"type":621,"value":751},"同期，「Open Source AI Must Win」宣言被廣泛傳播，核心論點是：若 AI 基礎設施集中於少數閉源商業平台，社會將喪失「研究、構建、審計、部署、教學與保存智能系統」的能力，必須確保大型模型具備可本地部署性與社群治理機制。",{"type":616,"tag":672,"props":753,"children":754},{},[755],{"type":616,"tag":617,"props":756,"children":757},{},[758,763,766],{"type":616,"tag":679,"props":759,"children":760},{},[761],{"type":621,"value":762},"白話比喻",{"type":616,"tag":685,"props":764,"children":765},{},[],{"type":621,"value":767},"\n這場封鎖就像圖書館突然宣布「只有本國公民才能借書」，但館員根本無法確認誰是本國人——最後乾脆鎖門，所有人都進不去。社群的回應是：那就自己在家複印吧。",{"type":616,"tag":660,"props":769,"children":771},{"id":770},"章節四ai-模型監管的先例效應與產業影響",[772],{"type":621,"value":773},"章節四：AI 模型監管的先例效應與產業影響",{"type":616,"tag":617,"props":775,"children":776},{},[777],{"type":621,"value":778},"12gramsofcarbon.com 的分析將此事件定性為潛在的「盧比孔時刻」——這是政府首次以出口管制手段強制下線一個面向數億用戶的商業 AI 模型，歷史類比是 1990 年代美國對加密演算法施加出口管制的決定。",{"type":616,"tag":617,"props":780,"children":781},{},[782],{"type":621,"value":783},"分析指出，若此類指令成為常態，全球數兆美元的資料中心投資將面臨根本性威脅：投資者難以為「可能隨時被政府叫停」的模型服務構建穩定的商業計畫。",{"type":616,"tag":617,"props":785,"children":786},{},[787],{"type":621,"value":788},"歐洲政界已有政治人物公開將此事定性為「警鐘」，認為依賴美國 AI 技術存在系統性主權風險，標誌著 AI 主權議題從政策討論正式進入具體執法現實。",{"type":616,"tag":617,"props":790,"children":791},{},[792],{"type":621,"value":793},"更深層的隱憂在於競爭格局的扭曲：美國模型受限之際，中國 AI 廠商持續開放發布，有望趁機積累市場份額。HN 社群用戶直言，本次事件已向全球 AI 產業傳達一個明確訊號——頂尖模型的存取權正在成為地緣政治的籌碼。",{"title":385,"searchDepth":623,"depth":623,"links":795},[],{"data":797,"body":798,"excerpt":-1,"toc":845},{"title":385,"description":385},{"type":613,"children":799},[800,805,810,815,820,825,830,835,840],{"type":616,"tag":660,"props":801,"children":803},{"id":802},"核心條款",[804],{"type":621,"value":802},{"type":616,"tag":617,"props":806,"children":807},{},[808],{"type":621,"value":809},"美國政府援引出口管制法規，於 2026 年 6 月 12 日向 Anthropic 發出緊急指令：立即暫停所有「外國公民」對 Fable 5 與 Mythos 5 的存取，管制範圍涵蓋在美境內的外國公民（包含 Anthropic 員工），而非僅限境外存取。",{"type":616,"tag":617,"props":811,"children":812},{},[813],{"type":621,"value":814},"政府所列舉的具體依據為一種可引導 Fable 5 識別程式碼漏洞的 jailbreak 技術，被認定具有可被用於網路攻擊的潛在風險。Anthropic 否認此 jailbreak 構成大規模召回的充分理由，雙方在技術評估上立場相左。",{"type":616,"tag":660,"props":816,"children":818},{"id":817},"適用範圍",[819],{"type":621,"value":817},{"type":616,"tag":617,"props":821,"children":822},{},[823],{"type":621,"value":824},"本次指令直接適用於 Fable 5 與 Mythos 5 兩款模型；Claude 3.x 系列及其他服務不受影響。間接影響範圍涵蓋所有透過 AWS Bedrock 取用 Anthropic 模型的全球企業客戶。",{"type":616,"tag":617,"props":826,"children":827},{},[828],{"type":621,"value":829},"技術社群指出，「外國公民」身分的驗證在技術層面幾乎無法可靠實現——IP 位置、身分驗證文件均可偽造，使本次指令的合規執行帶有強烈的象徵意義，難以達到實際管制效果。",{"type":616,"tag":660,"props":831,"children":833},{"id":832},"執法機制",[834],{"type":621,"value":832},{"type":616,"tag":617,"props":836,"children":837},{},[838],{"type":621,"value":839},"本次指令的執法主體為美國財政部，David Sacks 等政府顧問參與了政策溝通。Anthropic 在收到指令後數小時內完成全面斷線，整個執行過程缺乏公開的聽證程序與申訴管道。",{"type":616,"tag":617,"props":841,"children":842},{},[843],{"type":621,"value":844},"從時序來看，Amazon CEO Andy Jassy 在指令下達前已主動向財政部長 Scott Bessent 提報安全疑慮，顯示本次執法行動在正式指令之前已有企業層面的非正式溝通管道。",{"title":385,"searchDepth":623,"depth":623,"links":846},[],{"data":848,"body":850,"excerpt":-1,"toc":886},{"title":385,"description":849},"此次事件揭示現有 AI 平台架構在合規設計上的根本缺陷——幾乎所有主流雲端 AI 服務，都無法在不關閉全部存取的情況下可靠地依國籍進行隔離。",{"type":613,"children":851},[852,856,861],{"type":616,"tag":617,"props":853,"children":854},{},[855],{"type":621,"value":849},{"type":616,"tag":617,"props":857,"children":858},{},[859],{"type":621,"value":860},"企業若要對應類似的監管要求，需建置以下能力：",{"type":616,"tag":862,"props":863,"children":864},"ul",{},[865,871,876,881],{"type":616,"tag":866,"props":867,"children":868},"li",{},[869],{"type":621,"value":870},"可驗證的用戶身分識別機制（超出現有 KYC 流程的強度）",{"type":616,"tag":866,"props":872,"children":873},{},[874],{"type":621,"value":875},"地理封鎖與 IP 驗證的多層架構",{"type":616,"tag":866,"props":877,"children":878},{},[879],{"type":621,"value":880},"針對政府緊急指令的快速隔離開關 (kill switch) 設計",{"type":616,"tag":866,"props":882,"children":883},{},[884],{"type":621,"value":885},"企業合約中「服務中斷免責」條款的相應更新",{"title":385,"searchDepth":623,"depth":623,"links":887},[],{"data":889,"body":891,"excerpt":-1,"toc":902},{"title":385,"description":890},"本次事件中，Anthropic 的合規選擇幾乎只有「全關」——因為實作可靠國籍驗證的邊際成本，遠超全面斷線的業務損失評估。",{"type":613,"children":892},[893,897],{"type":616,"tag":617,"props":894,"children":895},{},[896],{"type":621,"value":890},{"type":616,"tag":617,"props":898,"children":899},{},[900],{"type":621,"value":901},"對 AWS Bedrock 等企業服務提供商而言，此類政府緊急指令可能引發客戶信任危機，間接成本難以量化。建立可支援細粒度合規隔離的基礎設施，預估需要顯著的工程與法務投入，且現有技術框架尚無業界標準解決方案。",{"title":385,"searchDepth":623,"depth":623,"links":903},[],{"data":905,"body":907,"excerpt":-1,"toc":936},{"title":385,"description":906},"鑒於技術上的不可行性，目前最接近「最小合規路徑」的選擇包括：",{"type":613,"children":908},[909,913],{"type":616,"tag":617,"props":910,"children":911},{},[912],{"type":621,"value":906},{"type":616,"tag":862,"props":914,"children":915},{},[916,921,926,931],{"type":616,"tag":866,"props":917,"children":918},{},[919],{"type":621,"value":920},"對所有新用戶啟動人工國籍驗證流程（以限制服務可及性換取合規安全感）",{"type":616,"tag":866,"props":922,"children":923},{},[924],{"type":621,"value":925},"建立企業級白名單制度，僅對可驗證的美國公民法人實體開放存取",{"type":616,"tag":866,"props":927,"children":928},{},[929],{"type":621,"value":930},"在服務條款中明確排除非美國公民的使用授權，轉移法律責任",{"type":616,"tag":866,"props":932,"children":933},{},[934],{"type":621,"value":935},"準備快速全面斷線的技術預案，作為應對政府緊急指令的後備選項",{"title":385,"searchDepth":623,"depth":623,"links":937},[],{"data":939,"body":940,"excerpt":-1,"toc":987},{"title":385,"description":385},{"type":613,"children":941},[942,947,952,957,962,967,972,977,982],{"type":616,"tag":660,"props":943,"children":945},{"id":944},"直接影響者",[946],{"type":621,"value":944},{"type":616,"tag":617,"props":948,"children":949},{},[950],{"type":621,"value":951},"Anthropic 自身是最直接的受害方——數億用戶的服務在無預警情況下中斷，商譽與企業客戶信任受到衝擊。AWS Bedrock 的企業用戶面臨服務不穩定的風險，部分合約可能需要重新談判。",{"type":616,"tag":617,"props":953,"children":954},{},[955],{"type":621,"value":956},"其他頂尖閉源 AI 模型提供商（OpenAI、Google DeepMind）同樣面臨未來可能遭受類似監管行動的不確定性，特別是當其政治關係弱化或與政府立場產生摩擦時。",{"type":616,"tag":660,"props":958,"children":960},{"id":959},"間接波及者",[961],{"type":621,"value":959},{"type":616,"tag":617,"props":963,"children":964},{},[965],{"type":621,"value":966},"全球採用美國 AI 平台的企業客戶，現在必須重新評估供應鏈的地緣政治風險。歐洲政界已公開將此事定性為「警鐘」，預計將推動 EU AI Act 框架下的主權 AI 倡議加速落地。",{"type":616,"tag":617,"props":968,"children":969},{},[970],{"type":621,"value":971},"開源模型生態系——Qwen、Llama、Mistral——直接受益：用戶在尋求可自主部署、不受美國監管干預的替代方案，開源社群的採用動能因此大幅提升。",{"type":616,"tag":660,"props":973,"children":975},{"id":974},"成本轉嫁效應",[976],{"type":621,"value":974},{"type":616,"tag":617,"props":978,"children":979},{},[980],{"type":621,"value":981},"企業客戶若決定轉向本地部署或開源替代方案，短期內需承擔工程遷移成本。",{"type":616,"tag":617,"props":983,"children":984},{},[985],{"type":621,"value":986},"長期而言，若美國監管不確定性持續，全球 AI 市場可能出現碎片化——美國企業主導的閉源生態與中國、歐洲主導的開源或主權 AI 生態形成平行格局，最終使所有用戶面對更高的生態轉換成本。",{"title":385,"searchDepth":623,"depth":623,"links":988},[],{"data":990,"body":991,"excerpt":-1,"toc":997},{"title":385,"description":120},{"type":613,"children":992},[993],{"type":616,"tag":617,"props":994,"children":995},{},[996],{"type":621,"value":120},{"title":385,"searchDepth":623,"depth":623,"links":998},[],{"data":1000,"body":1001,"excerpt":-1,"toc":1007},{"title":385,"description":124},{"type":613,"children":1002},[1003],{"type":616,"tag":617,"props":1004,"children":1005},{},[1006],{"type":621,"value":124},{"title":385,"searchDepth":623,"depth":623,"links":1008},[],{"data":1010,"body":1011,"excerpt":-1,"toc":1017},{"title":385,"description":127},{"type":613,"children":1012},[1013],{"type":616,"tag":617,"props":1014,"children":1015},{},[1016],{"type":621,"value":127},{"title":385,"searchDepth":623,"depth":623,"links":1018},[],{"data":1020,"body":1021,"excerpt":-1,"toc":1027},{"title":385,"description":131},{"type":613,"children":1022},[1023],{"type":616,"tag":617,"props":1024,"children":1025},{},[1026],{"type":621,"value":131},{"title":385,"searchDepth":623,"depth":623,"links":1028},[],{"data":1030,"body":1031,"excerpt":-1,"toc":1037},{"title":385,"description":136},{"type":613,"children":1032},[1033],{"type":616,"tag":617,"props":1034,"children":1035},{},[1036],{"type":621,"value":136},{"title":385,"searchDepth":623,"depth":623,"links":1038},[],{"data":1040,"body":1041,"excerpt":-1,"toc":1047},{"title":385,"description":140},{"type":613,"children":1042},[1043],{"type":616,"tag":617,"props":1044,"children":1045},{},[1046],{"type":621,"value":140},{"title":385,"searchDepth":623,"depth":623,"links":1048},[],{"data":1050,"body":1051,"excerpt":-1,"toc":1057},{"title":385,"description":71},{"type":613,"children":1052},[1053],{"type":616,"tag":617,"props":1054,"children":1055},{},[1056],{"type":621,"value":71},{"title":385,"searchDepth":623,"depth":623,"links":1058},[],{"data":1060,"body":1061,"excerpt":-1,"toc":1067},{"title":385,"description":72},{"type":613,"children":1062},[1063],{"type":616,"tag":617,"props":1064,"children":1065},{},[1066],{"type":621,"value":72},{"title":385,"searchDepth":623,"depth":623,"links":1068},[],{"data":1070,"body":1071,"excerpt":-1,"toc":1077},{"title":385,"description":157},{"type":613,"children":1072},[1073],{"type":616,"tag":617,"props":1074,"children":1075},{},[1076],{"type":621,"value":157},{"title":385,"searchDepth":623,"depth":623,"links":1078},[],{"data":1080,"body":1081,"excerpt":-1,"toc":1087},{"title":385,"description":161},{"type":613,"children":1082},[1083],{"type":616,"tag":617,"props":1084,"children":1085},{},[1086],{"type":621,"value":161},{"title":385,"searchDepth":623,"depth":623,"links":1088},[],{"data":1090,"body":1091,"excerpt":-1,"toc":1097},{"title":385,"description":164},{"type":613,"children":1092},[1093],{"type":616,"tag":617,"props":1094,"children":1095},{},[1096],{"type":621,"value":164},{"title":385,"searchDepth":623,"depth":623,"links":1098},[],{"data":1100,"body":1101,"excerpt":-1,"toc":1107},{"title":385,"description":167},{"type":613,"children":1102},[1103],{"type":616,"tag":617,"props":1104,"children":1105},{},[1106],{"type":621,"value":167},{"title":385,"searchDepth":623,"depth":623,"links":1108},[],{"data":1110,"body":1111,"excerpt":-1,"toc":1230},{"title":385,"description":385},{"type":613,"children":1112},[1113,1119,1124,1136,1141,1146,1152,1157,1162,1167,1173,1185,1190,1209,1215,1220,1225],{"type":616,"tag":660,"props":1114,"children":1116},{"id":1115},"章節一內部備忘錄揭露的驚人數字",[1117],{"type":621,"value":1118},"章節一：內部備忘錄揭露的驚人數字",{"type":616,"tag":617,"props":1120,"children":1121},{},[1122],{"type":621,"value":1123},"Meta 向約 6,000 名員工發出的內部備忘錄揭露了驚人現實：公司 AI 使用成本正呈「指數級增長」，預計 2026 年逼近數十億美元，2027 年直接突破。",{"type":616,"tag":617,"props":1125,"children":1126},{},[1127,1129,1134],{"type":621,"value":1128},"在約 30 天內，員工透過名為「Claudeonomics」的內部排行榜共消耗了 ",{"type":616,"tag":679,"props":1130,"children":1131},{},[1132],{"type":621,"value":1133},"73.7 兆個 token",{"type":621,"value":1135},"。這個名字直接向 Anthropic 的 Claude 致敬，Claude 正是 Meta 內部廣泛依賴的第三方 AI 工具之一。",{"type":616,"tag":617,"props":1137,"children":1138},{},[1139],{"type":621,"value":1140},"排行榜最初的設計出發點是鼓勵員工積極擁抱 AI，拉升全公司採用率。卻意外催生出「為用而用」的消耗行為——員工為了在榜上爭得名次而無謂消耗 token，而非用 AI 創造實際價值。",{"type":616,"tag":617,"props":1142,"children":1143},{},[1144],{"type":621,"value":1145},"Meta CTO Andrew Bosworth 明確點出問題核心：「沒有人應該只是為了使用 AI 工具而使用它們。所有行動都不等於進展，token 使用量本身也不是任何意義上的影響力衡量標準。」",{"type":616,"tag":660,"props":1147,"children":1149},{"id":1148},"章節二nadella-也自嘲是-token-maxer",[1150],{"type":621,"value":1151},"章節二：Nadella 也自嘲是 Token-Maxer",{"type":616,"tag":617,"props":1153,"children":1154},{},[1155],{"type":621,"value":1156},"2026 年 6 月 13 日，微軟 CEO Satya Nadella 在 Hard Fork 頻道專訪中坦承：「我也是個 token-maxer，這很上癮。」這句話出自一位力推 AI 轉型的科技巨頭掌舵者之口，格外引人矚目。",{"type":616,"tag":617,"props":1158,"children":1159},{},[1160],{"type":621,"value":1161},"Nadella 同時提出警告：不應把最強的前沿模型浪費在日常任務上。他提出「邊際成本對等」框架：生產力提升的邊際成本，必須與 token 的邊際成本相匹配。換言之，任務的複雜度應決定使用模型的等級。",{"type":616,"tag":617,"props":1163,"children":1164},{},[1165],{"type":621,"value":1166},"Amazon 同樣出現員工刷榜內部 AI 排行榜的現象，顯示 Meta 面臨的問題並非個案。當業界最積極推廣 AI 的領袖都坦承難逃 token-maxing 誘惑，這場行為科學實驗的失控，已是整個產業級別的課題。",{"type":616,"tag":660,"props":1168,"children":1170},{"id":1169},"章節三企業-ai-成本管理的轉折點",[1171],{"type":621,"value":1172},"章節三：企業 AI 成本管理的轉折點",{"type":616,"tag":617,"props":1174,"children":1175},{},[1176,1178,1183],{"type":621,"value":1177},"Meta 計劃以集中監控平台「",{"type":616,"tag":679,"props":1179,"children":1180},{},[1181],{"type":621,"value":1182},"AI Gateway",{"type":621,"value":1184},"」取代 Claudeonomics 排行榜。AI Gateway 可即時追蹤各團隊及個別員工的 token 用量與花費，並設有異常支出自動警報，儀表板預計數週內上線。",{"type":616,"tag":617,"props":1186,"children":1187},{},[1188],{"type":621,"value":1189},"完整的預算框架——含配額與分配機制——預計 2027 年初正式啟用。與此同時，Meta 計劃將員工從 Claude 等第三方工具導向自家 MetaCode 助理，以降低外部 AI 授權支出，進一步收緊成本控制。",{"type":616,"tag":617,"props":1191,"children":1192},{},[1193,1195,1200,1202,1207],{"type":621,"value":1194},"Meta 整體 AI 基礎設施支出計畫高達 ",{"type":616,"tag":679,"props":1196,"children":1197},{},[1198],{"type":621,"value":1199},"1,350 億美元",{"type":621,"value":1201},"（至 2026 年），並承諾在 2028 年前投入 ",{"type":616,"tag":679,"props":1203,"children":1204},{},[1205],{"type":621,"value":1206},"6,000 億美元",{"type":621,"value":1208},"於資料中心建設。即便如此，內部 AI 使用的失控成本仍足以讓管理層發出緊急備忘錄——這本身就是值得深思的訊號。",{"type":616,"tag":660,"props":1210,"children":1212},{"id":1211},"章節四token-經濟學對開發者與企業的啟示",[1213],{"type":621,"value":1214},"章節四：Token 經濟學對開發者與企業的啟示",{"type":616,"tag":617,"props":1216,"children":1217},{},[1218],{"type":621,"value":1219},"Nadella 的「邊際成本對等」原則，為企業提供了一個評估 AI ROI 的實用模型：不同複雜度的任務應匹配不同能力等級的模型，而非一律動用最昂貴的前沿模型。",{"type":616,"tag":617,"props":1221,"children":1222},{},[1223],{"type":621,"value":1224},"對開發者而言，「右模型選配」即將從個人最佳實踐升格為企業強制規範。AI Gateway 類型的平台上線後，每一筆 token 消耗都將有成本歸屬，高消耗低產出的行為將無所遁形。",{"type":616,"tag":617,"props":1226,"children":1227},{},[1228],{"type":621,"value":1229},"更深層的啟示在於：AI 採用的「量化文化」已觸及天花板。當激勵員工「用量」的機制反而催生浪費，整個行業需要重新定義 AI 使用的成功指標——從 token 消耗量轉向可量化的業務成果。",{"title":385,"searchDepth":623,"depth":623,"links":1231},[],{"data":1233,"body":1235,"excerpt":-1,"toc":1246},{"title":385,"description":1234},"AI 工具的全員普及需要一個探索期，員工在初期的「過度使用」是熟悉工具的必要代價。Claudeonomics 排行榜確實加速了 Meta 的 AI 工具上手速度——若沒有排行榜激勵，大量員工可能從未嘗試過 AI 輔助的工作流程。",{"type":613,"children":1236},[1237,1241],{"type":616,"tag":617,"props":1238,"children":1239},{},[1240],{"type":621,"value":1234},{"type":616,"tag":617,"props":1242,"children":1243},{},[1244],{"type":621,"value":1245},"更根本的是，限制 token 使用可能是短視的成本控制措施。若 AI 使用量的背後是真實的生產力提升，數十億美元的內部 AI 支出，相對於節省的人力成本可能完全划算——但這需要測量機制，而非直覺判斷後的一刀切限制。",{"title":385,"searchDepth":623,"depth":623,"links":1247},[],{"data":1249,"body":1251,"excerpt":-1,"toc":1262},{"title":385,"description":1250},"「Tokenmaxxing 文化」將 AI 使用量本身視為目標，而非手段。Meta 案例清楚顯示，當激勵機制錯誤設計，員工的理性選擇就是「為排行榜而用 AI」，而非「為解決問題而用 AI」。這種行為扭曲使得真實的 AI ROI 根本無從評估。",{"type":613,"children":1252},[1253,1257],{"type":616,"tag":617,"props":1254,"children":1255},{},[1256],{"type":621,"value":1250},{"type":616,"tag":617,"props":1258,"children":1259},{},[1260],{"type":621,"value":1261},"Andrew Bosworth 的批評直指核心：所有行動都不等於進展。一個月 73.7 兆 token 的消耗，若大部分只是員工「展示 AI 使用量」的表演，那麼企業不只在浪費金錢，更在用錯誤的指標欺騙自己——成本失控的根源正是指標失控。",{"title":385,"searchDepth":623,"depth":623,"links":1263},[],{"data":1265,"body":1267,"excerpt":-1,"toc":1293},{"title":385,"description":1266},"問題的根源既不是 AI 工具本身，也不是員工的懶散——而是激勵機制設計的失敗。排行榜把「可量化的 token 消耗」當成代理指標，當代理指標與真實目標脫鉤，Goodhart 定律就會發作。",{"type":613,"children":1268},[1269,1273,1288],{"type":616,"tag":617,"props":1270,"children":1271},{},[1272],{"type":621,"value":1266},{"type":616,"tag":672,"props":1274,"children":1275},{},[1276],{"type":616,"tag":617,"props":1277,"children":1278},{},[1279,1283,1286],{"type":616,"tag":679,"props":1280,"children":1281},{},[1282],{"type":621,"value":683},{"type":616,"tag":685,"props":1284,"children":1285},{},[],{"type":621,"value":1287},"\nGoodhart 定律：「當一個量測指標本身成為管理目標時，它就不再是有效的量測工具。」由英國經濟學家 Charles Goodhart 提出，廣泛應用於管理與政策分析。",{"type":616,"tag":617,"props":1289,"children":1290},{},[1291],{"type":621,"value":1292},"Meta 用 AI Gateway 取代 Claudeonomics，是從錯誤指標（token 量）轉向正確指標（成本對應產出）的正確方向。但真正的挑戰在於：如何量化 AI 帶來的生產力收益？這個問題至今沒有業界共識，AI 治理的下一個戰場，將是「AI 產出」的測量學。",{"title":385,"searchDepth":623,"depth":623,"links":1294},[],{"data":1296,"body":1297,"excerpt":-1,"toc":1353},{"title":385,"description":385},{"type":613,"children":1298},[1299,1304,1309,1314,1320,1325,1330,1335],{"type":616,"tag":660,"props":1300,"children":1302},{"id":1301},"對開發者的影響",[1303],{"type":621,"value":1301},{"type":616,"tag":617,"props":1305,"children":1306},{},[1307],{"type":621,"value":1308},"AI 工具的「右模型選配」原則——依任務複雜度選擇對應能力等級的模型——即將從個人最佳實踐升格為企業合規要求。開發者需要建立模型分級使用的直覺，學會在「夠用」與「最強」之間做出有意識的取捨。",{"type":616,"tag":617,"props":1310,"children":1311},{},[1312],{"type":621,"value":1313},"企業內部 AI 工具使用即將納入成本監控與配額管理。習慣「無限 token」工作流程的開發者，需要提早適應「成本意識開發」的思維轉型。",{"type":616,"tag":660,"props":1315,"children":1317},{"id":1316},"對團隊組織的影響",[1318],{"type":621,"value":1319},"對團隊／組織的影響",{"type":616,"tag":617,"props":1321,"children":1322},{},[1323],{"type":621,"value":1324},"AI 排行榜等量化激勵機制需要重新設計——核心問題是：如何設計讓員工「用 AI 解決真實問題」而非「用 AI 刷指標」的激勵系統？",{"type":616,"tag":617,"props":1326,"children":1327},{},[1328],{"type":621,"value":1329},"2027 年 Meta AI Gateway 預算框架落地後，各團隊對 AI 支出將負有直接責任。AI 投資的 ROI 評估將成為每個部門主管的必修課，而非只是 CTO 辦公室的議題。",{"type":616,"tag":660,"props":1331,"children":1333},{"id":1332},"短期行動建議",[1334],{"type":621,"value":1332},{"type":616,"tag":862,"props":1336,"children":1337},{},[1338,1343,1348],{"type":616,"tag":866,"props":1339,"children":1340},{},[1341],{"type":621,"value":1342},"審計現有 AI 工具使用模式，識別高消耗低價值的使用場景",{"type":616,"tag":866,"props":1344,"children":1345},{},[1346],{"type":621,"value":1347},"為不同複雜度的任務建立「推薦模型等級」指引",{"type":616,"tag":866,"props":1349,"children":1350},{},[1351],{"type":621,"value":1352},"在內部工具選型時，優先評估具備成本可視化功能的 AI 平台",{"title":385,"searchDepth":623,"depth":623,"links":1354},[],{"data":1356,"body":1357,"excerpt":-1,"toc":1394},{"title":385,"description":385},{"type":613,"children":1358},[1359,1364,1369,1374,1379,1384,1389],{"type":616,"tag":660,"props":1360,"children":1362},{"id":1361},"產業結構變化",[1363],{"type":621,"value":1361},{"type":616,"tag":617,"props":1365,"children":1366},{},[1367],{"type":621,"value":1368},"企業 AI 採用正式進入「治理成熟期」，從第一波「廣泛普及推廣」轉向第二波「精準投放管控」。AI Gateway 這類成本可視化平台，以及配額制、分配機制等治理工具，將成為 2027 年後企業 AI 採購清單的標準配備。",{"type":616,"tag":660,"props":1370,"children":1372},{"id":1371},"倫理邊界",[1373],{"type":621,"value":1371},{"type":616,"tag":617,"props":1375,"children":1376},{},[1377],{"type":621,"value":1378},"Claudeonomics 排行榜揭示了一個深層的倫理問題：當公司以「可量化的 AI 使用量」考核員工，是否在無意間鼓勵了表演性勞動？員工不是在創造價值，而是在「表演使用 AI」給管理層看——這是評估文化在 AI 時代的特殊扭曲。",{"type":616,"tag":660,"props":1380,"children":1382},{"id":1381},"長期趨勢預測",[1383],{"type":621,"value":1381},{"type":616,"tag":617,"props":1385,"children":1386},{},[1387],{"type":621,"value":1388},"AI 成本管控的下一個前線，將是「AI 產出量測」——如何客觀評估 AI 是否真的提升了生產力？當 token 使用量被廢棄為指標之後，企業需要建立新的衡量框架。",{"type":616,"tag":617,"props":1390,"children":1391},{},[1392],{"type":621,"value":1393},"程式碼品質、決策速度、錯誤率降低等業務成果導向的指標，將取代「使用 AI 的次數」成為新標準。掌握「AI 產出量測」方法論的企業，將在下一輪 AI 治理競爭中搶得先機。",{"title":385,"searchDepth":623,"depth":623,"links":1395},[],{"data":1397,"body":1398,"excerpt":-1,"toc":1404},{"title":385,"description":170},{"type":613,"children":1399},[1400],{"type":616,"tag":617,"props":1401,"children":1402},{},[1403],{"type":621,"value":170},{"title":385,"searchDepth":623,"depth":623,"links":1405},[],{"data":1407,"body":1408,"excerpt":-1,"toc":1414},{"title":385,"description":171},{"type":613,"children":1409},[1410],{"type":616,"tag":617,"props":1411,"children":1412},{},[1413],{"type":621,"value":171},{"title":385,"searchDepth":623,"depth":623,"links":1415},[],{"data":1417,"body":1418,"excerpt":-1,"toc":1424},{"title":385,"description":227},{"type":613,"children":1419},[1420],{"type":616,"tag":617,"props":1421,"children":1422},{},[1423],{"type":621,"value":227},{"title":385,"searchDepth":623,"depth":623,"links":1425},[],{"data":1427,"body":1428,"excerpt":-1,"toc":1434},{"title":385,"description":231},{"type":613,"children":1429},[1430],{"type":616,"tag":617,"props":1431,"children":1432},{},[1433],{"type":621,"value":231},{"title":385,"searchDepth":623,"depth":623,"links":1435},[],{"data":1437,"body":1438,"excerpt":-1,"toc":1444},{"title":385,"description":234},{"type":613,"children":1439},[1440],{"type":616,"tag":617,"props":1441,"children":1442},{},[1443],{"type":621,"value":234},{"title":385,"searchDepth":623,"depth":623,"links":1445},[],{"data":1447,"body":1448,"excerpt":-1,"toc":1454},{"title":385,"description":237},{"type":613,"children":1449},[1450],{"type":616,"tag":617,"props":1451,"children":1452},{},[1453],{"type":621,"value":237},{"title":385,"searchDepth":623,"depth":623,"links":1455},[],{"data":1457,"body":1458,"excerpt":-1,"toc":1554},{"title":385,"description":385},{"type":613,"children":1459},[1460,1466,1471,1476,1482,1487,1492,1512,1518,1523,1528,1533,1539,1544,1549],{"type":616,"tag":660,"props":1461,"children":1463},{"id":1462},"章節一skillopt-的核心概念與運作原理",[1464],{"type":621,"value":1465},"章節一：SkillOpt 的核心概念與運作原理",{"type":616,"tag":617,"props":1467,"children":1468},{},[1469],{"type":621,"value":1470},"SkillOpt 由 Microsoft Research 聯合三所中國大學於 2026 年 5 月發布，核心概念是將 AI agent 的指令文件（「skills」）視為可訓練的外部狀態，而非靜態提示詞。傳統上，開發者手動調整提示詞是一項費時費力的工作；SkillOpt 引入了一個獨立的「優化器模型」，讓這個過程系統化、可重複。",{"type":616,"tag":617,"props":1472,"children":1473},{},[1474],{"type":621,"value":1475},"優化流程中，優化器模型讀取 agent 的執行日誌 (rollouts) ，分析成功與失敗的案例，然後對技能文件提出局部編輯——新增、刪除或替換段落。關鍵突破在於：目標模型的權重完全凍結，只有那份 Markdown 文件本身被「訓練」，無需昂貴的模型微調 (fine-tuning) 。",{"type":616,"tag":660,"props":1477,"children":1479},{"id":1478},"章節二指令文件即模型調校的技術突破",[1480],{"type":621,"value":1481},"章節二：「指令文件即模型調校」的技術突破",{"type":616,"tag":617,"props":1483,"children":1484},{},[1485],{"type":621,"value":1486},"SkillOpt 刻意將深度學習的訓練概念對映到純文字層面，構建出一套類神經網路訓練的最佳化框架。「學習率」限制每步可編輯的範圍，防止技能文件出現不穩定的大幅漂移；「排程器」逐輪縮小修改幅度，讓優化過程逐漸從粗調轉為微調。",{"type":616,"tag":617,"props":1488,"children":1489},{},[1490],{"type":621,"value":1491},"被拒絕的編輯存入「負樣本緩衝區」作為對比學習素材；「慢更新」機制確保在多個訓練 epoch 間保持穩定的編輯方向，避免前後矛盾的修改互相抵消。只有通過驗證集評分改善的編輯才會被接受，典型的最終技能文件在 4 個 epoch 中僅累積 1–4 次被接受的編輯。",{"type":616,"tag":672,"props":1493,"children":1494},{},[1495],{"type":616,"tag":617,"props":1496,"children":1497},{},[1498,1502,1505,1510],{"type":616,"tag":679,"props":1499,"children":1500},{},[1501],{"type":621,"value":683},{"type":616,"tag":685,"props":1503,"children":1504},{},[],{"type":616,"tag":679,"props":1506,"children":1507},{},[1508],{"type":621,"value":1509},"負樣本緩衝區 (negative buffer)",{"type":621,"value":1511},"：記錄被驗證集否決的優化嘗試，讓後續步驟能參照「哪些方向是死路」，類似人類從錯誤中學習的記憶機制。",{"type":616,"tag":660,"props":1513,"children":1515},{"id":1514},"章節三基準測試結果與效能分析",[1516],{"type":621,"value":1517},"章節三：基準測試結果與效能分析",{"type":616,"tag":617,"props":1519,"children":1520},{},[1521],{"type":621,"value":1522},"研究橫跨六個基準測試，涵蓋網路搜尋、試算表操作、文件分析、數學推理與具身行動等多元任務；評估對象包含七個目標模型，從大型的 GPT-5.5 到小型的 Qwen3.5-4B 均有覆蓋。在 52 個（模型 × 基準測試 × 執行框架）評估組合中，SkillOpt 全數勝出或並列第一。",{"type":616,"tag":617,"props":1524,"children":1525},{},[1526],{"type":621,"value":1527},"具體數字相當亮眼：GPT-5.5 直接對話模式下準確率提升 +23.5 點，Codex agentic loop 提升 +24.8 點，Claude Code 模式提升 +19.1 點。在具有嚴格格式要求與工具呼叫的任務上，增益最為顯著。",{"type":616,"tag":617,"props":1529,"children":1530},{},[1531],{"type":621,"value":1532},"技能可跨模型遷移：在大型模型上訓練的技能能直接提升同系列小型模型的表現；針對數學奧林匹克問題優化的技能，也能泛化至相關數學基準，顯示 SkillOpt 捕捉到的是任務的結構性知識而非模型特性。",{"type":616,"tag":660,"props":1534,"children":1536},{"id":1535},"章節四對-prompt-engineering-工作流的深遠影響",[1537],{"type":621,"value":1538},"章節四：對 Prompt Engineering 工作流的深遠影響",{"type":616,"tag":617,"props":1540,"children":1541},{},[1542],{"type":621,"value":1543},"SkillOpt 最大的實用意義在於部署的極度輕量性。優化器模型僅在訓練階段使用，線上推論時 agent 只需讀取那份最終的 Markdown 技能文件，零額外模型呼叫。最終產物僅 300–2,000 tokens，具備可檢視性（人類可讀懂它做了什麼）、可攜性（跨環境直接複用）與低成本性。",{"type":616,"tag":617,"props":1545,"children":1546},{},[1547],{"type":621,"value":1548},"The Decoder 的報導指出，這套方法讓 AI 社群重新思考「最佳提示詞」是否應由機器而非人類定義。手動反覆調整 prompt 的勞動，有望被系統化的「文件訓練流程」取代，根本改寫 Prompt Engineering 的工作範式。",{"type":616,"tag":617,"props":1550,"children":1551},{},[1552],{"type":621,"value":1553},"研究者坦承的限制包括：需要可靠的自動評分機制，以及目前只優化單一技能文件而非技能庫。在多領域 agent 場景下，後者可能成為規模化的關鍵瓶頸。",{"title":385,"searchDepth":623,"depth":623,"links":1555},[],{"data":1557,"body":1559,"excerpt":-1,"toc":1565},{"title":385,"description":1558},"SkillOpt 的核心技術突破在於將「訓練」的概念從模型權重空間搬移到文字空間。這讓 AI agent 的指令文件可以像神經網路一樣被系統化優化，而無需更動任何模型本身。",{"type":613,"children":1560},[1561],{"type":616,"tag":617,"props":1562,"children":1563},{},[1564],{"type":621,"value":1558},{"title":385,"searchDepth":623,"depth":623,"links":1566},[],{"data":1568,"body":1570,"excerpt":-1,"toc":1576},{"title":385,"description":1569},"傳統梯度下降更新模型的浮點數權重；SkillOpt 的「梯度」是優化器模型分析 rollout 日誌後產生的自然語言編輯建議。每次迭代，優化器讀取成功與失敗的執行紀錄，針對技能文件提出段落級別的修改（新增、刪除或替換段落）。目標模型的權重始終凍結不動，只有文件本身在演化。",{"type":613,"children":1571},[1572],{"type":616,"tag":617,"props":1573,"children":1574},{},[1575],{"type":621,"value":1569},{"title":385,"searchDepth":623,"depth":623,"links":1577},[],{"data":1579,"body":1580,"excerpt":-1,"toc":1624},{"title":385,"description":385},{"type":613,"children":1581},[1582],{"type":616,"tag":862,"props":1583,"children":1584},{},[1585,1595,1605,1614],{"type":616,"tag":866,"props":1586,"children":1587},{},[1588,1593],{"type":616,"tag":679,"props":1589,"children":1590},{},[1591],{"type":621,"value":1592},"學習率 (learning rate)",{"type":621,"value":1594},"：限制每步可修改的字符數或段落數，防止技能文件在單次迭代中發生巨大漂移",{"type":616,"tag":866,"props":1596,"children":1597},{},[1598,1603],{"type":616,"tag":679,"props":1599,"children":1600},{},[1601],{"type":621,"value":1602},"排程器 (scheduler)",{"type":621,"value":1604},"：隨訓練進程逐輪縮小修改幅度，讓優化從「粗調」逐漸轉為「微調」",{"type":616,"tag":866,"props":1606,"children":1607},{},[1608,1612],{"type":616,"tag":679,"props":1609,"children":1610},{},[1611],{"type":621,"value":1509},{"type":621,"value":1613},"：記錄被驗證集否決的編輯，下一輪優化時作為「禁止方向」的對比學習素材",{"type":616,"tag":866,"props":1615,"children":1616},{},[1617,1622],{"type":616,"tag":679,"props":1618,"children":1619},{},[1620],{"type":621,"value":1621},"慢更新 (slow update)",{"type":621,"value":1623},"：多 epoch 間維持一致的編輯方向，避免前後矛盾的修改互相抵銷",{"title":385,"searchDepth":623,"depth":623,"links":1625},[],{"data":1627,"body":1629,"excerpt":-1,"toc":1650},{"title":385,"description":1628},"每次編輯提案都要通過驗證集評分：只有實際改善準確率的編輯才被接受並寫入技能文件；被拒絕的提案進入負樣本緩衝區。典型訓練結果顯示，4 個 epoch 後僅 1–4 次編輯被接受，這種稀疏性確保了最終文件的品質而非量。",{"type":613,"children":1630},[1631,1635],{"type":616,"tag":617,"props":1632,"children":1633},{},[1634],{"type":621,"value":1628},{"type":616,"tag":672,"props":1636,"children":1637},{},[1638],{"type":616,"tag":617,"props":1639,"children":1640},{},[1641,1645,1648],{"type":616,"tag":679,"props":1642,"children":1643},{},[1644],{"type":621,"value":762},{"type":616,"tag":685,"props":1646,"children":1647},{},[],{"type":621,"value":1649},"\n想像一位編輯在不改動作者本人的情況下，反覆修訂一份操作手冊：每次只允許改一點點（學習率），記錄哪些改法被審稿人退回（負樣本緩衝區），最終手冊雖然只被改了幾次，卻讓使用者成功率大幅提升。SkillOpt 就是這位永不疲倦的自動化編輯。",{"title":385,"searchDepth":623,"depth":623,"links":1651},[],{"data":1653,"body":1654,"excerpt":-1,"toc":1779},{"title":385,"description":385},{"type":613,"children":1655},[1656,1661,1684,1689,1712,1717,1722,1727,1745,1750,1768,1774],{"type":616,"tag":660,"props":1657,"children":1659},{"id":1658},"競爭版圖",[1660],{"type":621,"value":1658},{"type":616,"tag":862,"props":1662,"children":1663},{},[1664,1674],{"type":616,"tag":866,"props":1665,"children":1666},{},[1667,1672],{"type":616,"tag":679,"props":1668,"children":1669},{},[1670],{"type":621,"value":1671},"直接競品",{"type":621,"value":1673},"：TextGrad（文字梯度框架）、OPRO（Google 的 prompt 優化器）、DSPy（宣告式 prompt 優化框架）、EvoSkill",{"type":616,"tag":866,"props":1675,"children":1676},{},[1677,1682],{"type":616,"tag":679,"props":1678,"children":1679},{},[1680],{"type":621,"value":1681},"間接競品",{"type":621,"value":1683},"：傳統手動 prompt engineering 服務商、人工 red-teaming 與提示詞改善顧問服務",{"type":616,"tag":660,"props":1685,"children":1687},{"id":1686},"護城河類型",[1688],{"type":621,"value":1686},{"type":616,"tag":862,"props":1690,"children":1691},{},[1692,1702],{"type":616,"tag":866,"props":1693,"children":1694},{},[1695,1700],{"type":616,"tag":679,"props":1696,"children":1697},{},[1698],{"type":621,"value":1699},"工程護城河",{"type":621,"value":1701},"：52/52 組合全面超越、系統化流程具論文支撐的可重複性，且已有開源社群研究者（如 @omarsar0）獨立複現驗證",{"type":616,"tag":866,"props":1703,"children":1704},{},[1705,1710],{"type":616,"tag":679,"props":1706,"children":1707},{},[1708],{"type":621,"value":1709},"生態護城河",{"type":621,"value":1711},"：與 Microsoft Azure OpenAI 服務深度整合的潛力；訓練好的技能文件可在企業內跨團隊共享，形成組織級知識資產",{"type":616,"tag":660,"props":1713,"children":1715},{"id":1714},"定價策略",[1716],{"type":621,"value":1714},{"type":616,"tag":617,"props":1718,"children":1719},{},[1720],{"type":621,"value":1721},"SkillOpt 本身為開源研究框架，核心成本來自優化器模型的 API 呼叫費用。一次性訓練成本（數百次 rollout × API 費用）可攤薄至長期部署收益，對高重複性 agentic 任務（如財務報表解析、合約審查自動化）CP 值顯著。",{"type":616,"tag":660,"props":1723,"children":1725},{"id":1724},"企業導入阻力",[1726],{"type":621,"value":1724},{"type":616,"tag":862,"props":1728,"children":1729},{},[1730,1735,1740],{"type":616,"tag":866,"props":1731,"children":1732},{},[1733],{"type":621,"value":1734},"需要可靠的自動評分機制，許多企業任務的品質評估仍依賴人工審查，建置自動評分本身即是額外工程投入",{"type":616,"tag":866,"props":1736,"children":1737},{},[1738],{"type":621,"value":1739},"目前只支援單一技能文件優化，複雜的多工 agent 需要多次獨立訓練，缺乏跨技能協調機制",{"type":616,"tag":866,"props":1741,"children":1742},{},[1743],{"type":621,"value":1744},"研究論文到生產就緒工具之間仍有工程化落差，企業採用前需評估維護成本",{"type":616,"tag":660,"props":1746,"children":1748},{"id":1747},"第二序影響",[1749],{"type":621,"value":1747},{"type":616,"tag":862,"props":1751,"children":1752},{},[1753,1758,1763],{"type":616,"tag":866,"props":1754,"children":1755},{},[1756],{"type":621,"value":1757},"Prompt Engineering 這個職能的部分工作將被系統化工具取代，工程師角色將從「調參者」轉為「評估框架設計者」",{"type":616,"tag":866,"props":1759,"children":1760},{},[1761],{"type":621,"value":1762},"「技能文件市場」可能出現：預訓練好的高品質技能文件可被交易或共享，類似 HuggingFace 的模型共享模式",{"type":616,"tag":866,"props":1764,"children":1765},{},[1766],{"type":621,"value":1767},"小型模型因跨模型遷移能力而受益，企業可用大型模型訓練技能後部署在小型模型上，大幅降低推論成本",{"type":616,"tag":660,"props":1769,"children":1771},{"id":1770},"判決企業值得優先評估自動評分可行性再決定是否採用瓶頸在評分而非優化",[1772],{"type":621,"value":1773},"判決：企業值得優先評估自動評分可行性再決定是否採用（瓶頸在評分而非優化）",{"type":616,"tag":617,"props":1775,"children":1776},{},[1777],{"type":621,"value":1778},"SkillOpt 的 52/52 結果令人信服，20+ 點的準確率提升在業界屬於重大增益。核心門檻是企業必須先建立可靠的自動評分機制——這對許多任務而言本身就是一項工程挑戰。建議中大型 AI 工程團隊先審視自家任務是否具備可量化的評估指標，若已有，SkillOpt 的投資報酬率相當可觀。",{"title":385,"searchDepth":623,"depth":623,"links":1780},[],{"data":1782,"body":1783,"excerpt":-1,"toc":1833},{"title":385,"description":385},{"type":613,"children":1784},[1785,1790,1795,1800,1823,1828],{"type":616,"tag":660,"props":1786,"children":1788},{"id":1787},"評估設計",[1789],{"type":621,"value":1787},{"type":616,"tag":617,"props":1791,"children":1792},{},[1793],{"type":621,"value":1794},"研究採用 52 個評估組合，涵蓋 7 個目標模型、6 個基準測試與多種執行框架。基準測試包含 WebArena（網路搜尋）、SpreadsheetBench（試算表）、DocBench（文件分析）、MATH（數學推理）、ScienceWorld（具身行動）等，並與 TextGrad、GEPA、EvoSkill、Trace2Skill 等現有方法全面對比。",{"type":616,"tag":660,"props":1796,"children":1798},{"id":1797},"主要結果",[1799],{"type":621,"value":1797},{"type":616,"tag":862,"props":1801,"children":1802},{},[1803,1808,1813,1818],{"type":616,"tag":866,"props":1804,"children":1805},{},[1806],{"type":621,"value":1807},"GPT-5.5 直接對話模式：準確率 +23.5 點",{"type":616,"tag":866,"props":1809,"children":1810},{},[1811],{"type":621,"value":1812},"Codex agentic loop：+24.8 點",{"type":616,"tag":866,"props":1814,"children":1815},{},[1816],{"type":621,"value":1817},"Claude Code 模式：+19.1 點",{"type":616,"tag":866,"props":1819,"children":1820},{},[1821],{"type":621,"value":1822},"52/52 評估組合全數超越或並列基線，小型模型 Qwen3.5-4B 亦有顯著增益",{"type":616,"tag":660,"props":1824,"children":1826},{"id":1825},"跨模型遷移測試",[1827],{"type":621,"value":1825},{"type":616,"tag":617,"props":1829,"children":1830},{},[1831],{"type":621,"value":1832},"在大型模型上訓練的技能文件可直接遷移至同系列小型模型，維持正向準確率增益。針對數學奧林匹克問題優化的技能，亦能泛化至相關數學基準，顯示技能文件捕捉到的是任務的結構性知識。",{"title":385,"searchDepth":623,"depth":623,"links":1834},[],{"data":1836,"body":1837,"excerpt":-1,"toc":1854},{"title":385,"description":385},{"type":613,"children":1838},[1839],{"type":616,"tag":862,"props":1840,"children":1841},{},[1842,1846,1850],{"type":616,"tag":866,"props":1843,"children":1844},{},[1845],{"type":621,"value":243},{"type":616,"tag":866,"props":1847,"children":1848},{},[1849],{"type":621,"value":244},{"type":616,"tag":866,"props":1851,"children":1852},{},[1853],{"type":621,"value":245},{"title":385,"searchDepth":623,"depth":623,"links":1855},[],{"data":1857,"body":1858,"excerpt":-1,"toc":1871},{"title":385,"description":385},{"type":613,"children":1859},[1860],{"type":616,"tag":862,"props":1861,"children":1862},{},[1863,1867],{"type":616,"tag":866,"props":1864,"children":1865},{},[1866],{"type":621,"value":247},{"type":616,"tag":866,"props":1868,"children":1869},{},[1870],{"type":621,"value":248},{"title":385,"searchDepth":623,"depth":623,"links":1872},[],{"data":1874,"body":1875,"excerpt":-1,"toc":1881},{"title":385,"description":252},{"type":613,"children":1876},[1877],{"type":616,"tag":617,"props":1878,"children":1879},{},[1880],{"type":621,"value":252},{"title":385,"searchDepth":623,"depth":623,"links":1882},[],{"data":1884,"body":1885,"excerpt":-1,"toc":1891},{"title":385,"description":253},{"type":613,"children":1886},[1887],{"type":616,"tag":617,"props":1888,"children":1889},{},[1890],{"type":621,"value":253},{"title":385,"searchDepth":623,"depth":623,"links":1892},[],{"data":1894,"body":1895,"excerpt":-1,"toc":1901},{"title":385,"description":254},{"type":613,"children":1896},[1897],{"type":616,"tag":617,"props":1898,"children":1899},{},[1900],{"type":621,"value":254},{"title":385,"searchDepth":623,"depth":623,"links":1902},[],{"data":1904,"body":1905,"excerpt":-1,"toc":1911},{"title":385,"description":285},{"type":613,"children":1906},[1907],{"type":616,"tag":617,"props":1908,"children":1909},{},[1910],{"type":621,"value":285},{"title":385,"searchDepth":623,"depth":623,"links":1912},[],{"data":1914,"body":1915,"excerpt":-1,"toc":1921},{"title":385,"description":288},{"type":613,"children":1916},[1917],{"type":616,"tag":617,"props":1918,"children":1919},{},[1920],{"type":621,"value":288},{"title":385,"searchDepth":623,"depth":623,"links":1922},[],{"data":1924,"body":1925,"excerpt":-1,"toc":1931},{"title":385,"description":290},{"type":613,"children":1926},[1927],{"type":616,"tag":617,"props":1928,"children":1929},{},[1930],{"type":621,"value":290},{"title":385,"searchDepth":623,"depth":623,"links":1932},[],{"data":1934,"body":1935,"excerpt":-1,"toc":1941},{"title":385,"description":292},{"type":613,"children":1936},[1937],{"type":616,"tag":617,"props":1938,"children":1939},{},[1940],{"type":621,"value":292},{"title":385,"searchDepth":623,"depth":623,"links":1942},[],{"data":1944,"body":1945,"excerpt":-1,"toc":2088},{"title":385,"description":385},{"type":613,"children":1946},[1947,1953,1958,1963,1983,1988,1994,1999,2019,2024,2030,2035,2068,2073,2078,2083],{"type":616,"tag":660,"props":1948,"children":1950},{"id":1949},"gemini-sql2-架構與-gemini-31-pro-基底",[1951],{"type":621,"value":1952},"Gemini-SQL2 架構與 Gemini 3.1 Pro 基底",{"type":616,"tag":617,"props":1954,"children":1955},{},[1956],{"type":621,"value":1957},"Google Research 於 2026 年 6 月 12 日發布 Gemini-SQL2，這是基於 Gemini 3.1 Pro 進行專業化後訓練 (post-training) 與 scaffolding 所打造的 text-to-SQL 能力層，而非全新基礎模型。",{"type":616,"tag":617,"props":1959,"children":1960},{},[1961],{"type":621,"value":1962},"不同於一般 LLM 生成語法正確的 SQL，Gemini-SQL2 的優化目標是生成「可執行且回傳正確結果」的 SQL 查詢——這正是 BIRD 基準的評測核心，Google 的設計從根本上以執行語意而非表面語法為標準。",{"type":616,"tag":672,"props":1964,"children":1965},{},[1966],{"type":616,"tag":617,"props":1967,"children":1968},{},[1969,1973,1976,1981],{"type":616,"tag":679,"props":1970,"children":1971},{},[1972],{"type":621,"value":683},{"type":616,"tag":685,"props":1974,"children":1975},{},[],{"type":616,"tag":679,"props":1977,"children":1978},{},[1979],{"type":621,"value":1980},"後訓練 (post-training)",{"type":621,"value":1982},"：在預訓練大型語言模型之後，針對特定任務進行進一步的監督學習或強化學習，使模型在該領域的表現大幅超越通用基礎模型。",{"type":616,"tag":617,"props":1984,"children":1985},{},[1986],{"type":621,"value":1987},"Google Research 指出，資料本身往往是多層次的，查詢需要納入複雜的商業邏輯，「這使得從自然語言精確生成 SQL 極為困難。」Gemini-SQL2 的架構設計正是針對雜亂的 schema 與複雜商業語意進行專項強化，截至發布時 Google 尚未公開 API、model card 或技術論文。",{"type":616,"tag":660,"props":1989,"children":1991},{"id":1990},"bird-基準測試的壓倒性成績",[1992],{"type":621,"value":1993},"BIRD 基準測試的壓倒性成績",{"type":616,"tag":617,"props":1995,"children":1996},{},[1997],{"type":621,"value":1998},"Gemini-SQL2 在 BIRD 單一模型排行榜上以 80.04% 的執行準確率登頂，成為首個突破 80% 門檻的系統。相較之下，Google 前一版本 Gemini-SQL 約為 77.2%，AWS Q-SQL 約 76.5%，OpenAI GPT-5.5-xhigh 與 Anthropic Claude Opus 4.6 分別落在 72.8% 與 70.9%，差距達 7-9 個百分點。",{"type":616,"tag":672,"props":2000,"children":2001},{},[2002],{"type":616,"tag":617,"props":2003,"children":2004},{},[2005,2009,2012,2017],{"type":616,"tag":679,"props":2006,"children":2007},{},[2008],{"type":621,"value":683},{"type":616,"tag":685,"props":2010,"children":2011},{},[],{"type":616,"tag":679,"props":2013,"children":2014},{},[2015],{"type":621,"value":2016},"BIRD 基準",{"type":621,"value":2018},"(BIg Bench for LaRge-scale Database Grounded Text-to-SQL Evaluation) ：目前最具代表性的大規模 text-to-SQL 評測集，以執行正確性 (execution accuracy) 為標準——模型生成的 SQL 必須能實際執行並回傳正確結果，而非僅語法正確。",{"type":616,"tag":617,"props":2020,"children":2021},{},[2022],{"type":621,"value":2023},"值得注意的是，人類基準仍高達 92.96%，Google 與人類之間仍有約 12.92 個百分點的差距。這意味著複雜多表 JOIN 與深度業務語意的理解，至今仍是尚未完全攻克的難題，但 80% 門檻已是里程碑級別的跨越。",{"type":616,"tag":660,"props":2025,"children":2027},{"id":2026},"自然語言轉-sql-的技術演進脈絡",[2028],{"type":621,"value":2029},"自然語言轉 SQL 的技術演進脈絡",{"type":616,"tag":617,"props":2031,"children":2032},{},[2033],{"type":621,"value":2034},"Text-to-SQL 任務長期被視為 NLP 難題，技術路線的演進歷經三個世代：",{"type":616,"tag":862,"props":2036,"children":2037},{},[2038,2048,2058],{"type":616,"tag":866,"props":2039,"children":2040},{},[2041,2046],{"type":616,"tag":679,"props":2042,"children":2043},{},[2044],{"type":621,"value":2045},"第一代（規則式方法）",{"type":621,"value":2047},"：能處理有限的查詢模式，面對真實企業資料庫幾乎無法擴展",{"type":616,"tag":866,"props":2049,"children":2050},{},[2051,2056],{"type":616,"tag":679,"props":2052,"children":2053},{},[2054],{"type":621,"value":2055},"第二代（seq2seq 神經網路）",{"type":621,"value":2057},"：顯著提升準確率，但複雜多表 JOIN 與業務語意理解仍是瓶頸",{"type":616,"tag":866,"props":2059,"children":2060},{},[2061,2066],{"type":616,"tag":679,"props":2062,"children":2063},{},[2064],{"type":621,"value":2065},"第三代 (LLM prompt-based)",{"type":621,"value":2067},"：利用大型語言模型的語意理解突破業務語意障礙，但通用性與任務精準度之間存在取捨",{"type":616,"tag":617,"props":2069,"children":2070},{},[2071],{"type":621,"value":2072},"Gemini-SQL2 代表「LLM + 任務特化後訓練」的第四個階段，首次在主要基準上壓過 80% 門檻。此前 Google 的 Gemini-SQL 已持有 BIRD 榜首，Gemini-SQL2 延伸同一路線再提升約 3 個百分點，顯示此迭代方向的空間仍在持續釋放。",{"type":616,"tag":660,"props":2074,"children":2076},{"id":2075},"企業資料查詢自動化的實務意義",[2077],{"type":621,"value":2075},{"type":616,"tag":617,"props":2079,"children":2080},{},[2081],{"type":621,"value":2082},"Gemini-SQL2 的預期應用場景包括自助式商業分析（複雜 JOIN 與日期邏輯）、資料工程師以英文描述生成 ETL 轉換邏輯，以及 SaaS 平台的嵌入式查詢功能。Google 暗示此技術將整合進旗下更廣泛的資料服務，BigQuery Studio、AlloyDB AI、Cloud SQL Studio 均為潛在目標，但尚未官方確認。",{"type":616,"tag":617,"props":2084,"children":2085},{},[2086],{"type":621,"value":2087},"分析師普遍指出，80% 準確率在正式生產環境仍需人工審查；但對於結構化程度高的企業資料集，自動化查詢的可用性已大幅提升，能顯著降低非技術人員查詢資料庫的門檻，標誌著企業 BI 自動化的新拐點。",{"title":385,"searchDepth":623,"depth":623,"links":2089},[],{"data":2091,"body":2093,"excerpt":-1,"toc":2099},{"title":385,"description":2092},"Gemini-SQL2 的技術突破核心在於：將「語法正確」的目標升級為「執行正確」的目標，並透過任務特化後訓練解決複雜商業邏輯的語意理解問題。這不只是準確率的提升，更是評測哲學的根本轉變——從比較 SQL 文本，到直接驗證執行結果是否正確。",{"type":613,"children":2094},[2095],{"type":616,"tag":617,"props":2096,"children":2097},{},[2098],{"type":621,"value":2092},{"title":385,"searchDepth":623,"depth":623,"links":2100},[],{"data":2102,"body":2104,"excerpt":-1,"toc":2110},{"title":385,"description":2103},"Gemini-SQL2 並非以語法匹配 (syntax match) 為訓練目標，而是以 BIRD 基準的執行準確性 (execution accuracy) 為核心指標。訓練信號直接來自「SQL 查詢是否能執行並回傳正確結果」，而非文本相似度，迫使模型學習資料庫的實際執行語意，而非表面語法規律。",{"type":613,"children":2105},[2106],{"type":616,"tag":617,"props":2107,"children":2108},{},[2109],{"type":621,"value":2103},{"title":385,"searchDepth":623,"depth":623,"links":2111},[],{"data":2113,"body":2115,"excerpt":-1,"toc":2141},{"title":385,"description":2114},"Gemini-SQL2 特別針對「層層疊疊的資料結構」與「複雜商業邏輯」進行優化。實際企業資料庫往往包含數十張相互關聯的資料表、不規則的命名慣例與業務特定的計算邏輯。Gemini-SQL2 的 scaffolding 層負責將 schema 資訊結構化地注入上下文，使模型能理解跨表關聯的語意。",{"type":613,"children":2116},[2117,2121],{"type":616,"tag":617,"props":2118,"children":2119},{},[2120],{"type":621,"value":2114},{"type":616,"tag":672,"props":2122,"children":2123},{},[2124],{"type":616,"tag":617,"props":2125,"children":2126},{},[2127,2131,2134,2139],{"type":616,"tag":679,"props":2128,"children":2129},{},[2130],{"type":621,"value":683},{"type":616,"tag":685,"props":2132,"children":2133},{},[],{"type":616,"tag":679,"props":2135,"children":2136},{},[2137],{"type":621,"value":2138},"Scaffolding（鷹架）",{"type":621,"value":2140},"：在 LLM 應用中，指圍繞模型核心能力建立的外部結構——負責組織輸入、管理上下文、格式化輸出，讓模型在其框架內發揮最佳效能，而不改變模型本身的權重。",{"title":385,"searchDepth":623,"depth":623,"links":2142},[],{"data":2144,"body":2146,"excerpt":-1,"toc":2167},{"title":385,"description":2145},"選擇 Gemini 3.1 Pro 作為底座，而非從頭訓練專用小模型，使 Gemini-SQL2 能繼承原始模型的強大語意推理能力。這對複雜的自然語言消歧至關重要——當使用者說「上個季度業績最好的地區」時，模型需理解日期範圍、地理維度與業績指標的定義，這些能力源自預訓練階段廣泛的世界知識累積。",{"type":613,"children":2147},[2148,2152],{"type":616,"tag":617,"props":2149,"children":2150},{},[2151],{"type":621,"value":2145},{"type":616,"tag":672,"props":2153,"children":2154},{},[2155],{"type":616,"tag":617,"props":2156,"children":2157},{},[2158,2162,2165],{"type":616,"tag":679,"props":2159,"children":2160},{},[2161],{"type":621,"value":762},{"type":616,"tag":685,"props":2163,"children":2164},{},[],{"type":621,"value":2166},"\n可以把 Gemini-SQL2 想像成一位翻譯員：底層 Gemini 3.1 Pro 是他廣博的語言和常識基礎，而後訓練則是讓他通過了 SQL 專業執照考試——不只是懂語法，更知道如何讓查詢真正「跑出正確答案」。",{"title":385,"searchDepth":623,"depth":623,"links":2168},[],{"data":2170,"body":2171,"excerpt":-1,"toc":2282},{"title":385,"description":385},{"type":613,"children":2172},[2173,2177,2198,2202,2223,2227,2232,2236,2254,2258,2271,2277],{"type":616,"tag":660,"props":2174,"children":2175},{"id":1658},[2176],{"type":621,"value":1658},{"type":616,"tag":862,"props":2178,"children":2179},{},[2180,2189],{"type":616,"tag":866,"props":2181,"children":2182},{},[2183,2187],{"type":616,"tag":679,"props":2184,"children":2185},{},[2186],{"type":621,"value":1671},{"type":621,"value":2188},"：AWS Q-SQL(76.5%) 、OpenAI GPT-5.5-xhigh 搭配 Code Interpreter(72.8%) 、Anthropic Claude Opus 4.6 企業版 (70.9%) 、各 BI 工具商內建 AI 查詢（Tableau AI、Looker AI）",{"type":616,"tag":866,"props":2190,"children":2191},{},[2192,2196],{"type":616,"tag":679,"props":2193,"children":2194},{},[2195],{"type":621,"value":1681},{"type":621,"value":2197},"：低程式碼 BI 工具（Metabase、Power BI）、傳統 ETL 平台（dbt、Fivetran）",{"type":616,"tag":660,"props":2199,"children":2200},{"id":1686},[2201],{"type":621,"value":1686},{"type":616,"tag":862,"props":2203,"children":2204},{},[2205,2214],{"type":616,"tag":866,"props":2206,"children":2207},{},[2208,2212],{"type":616,"tag":679,"props":2209,"children":2210},{},[2211],{"type":621,"value":1699},{"type":621,"value":2213},"：BIRD 榜首的測試成績提供技術公信力；任務特化後訓練需要大量標注資料與訓練資源，複製成本高",{"type":616,"tag":866,"props":2215,"children":2216},{},[2217,2221],{"type":616,"tag":679,"props":2218,"children":2219},{},[2220],{"type":621,"value":1709},{"type":621,"value":2222},"：與 BigQuery、AlloyDB 的深度整合將形成平台鎖定效應；Google Cloud 資料服務的既有客戶群是天然擴散基礎",{"type":616,"tag":660,"props":2224,"children":2225},{"id":1714},[2226],{"type":621,"value":1714},{"type":616,"tag":617,"props":2228,"children":2229},{},[2230],{"type":621,"value":2231},"Google 尚未公開定價，預期將作為 BigQuery 或 Google Cloud 的加值功能捆綁銷售，或以 API 呼叫次數計費。競品 AWS Q-SQL 已與 AWS Redshift 深度捆綁，Google 很可能採用相似的平台整合策略，而非單獨定價。",{"type":616,"tag":660,"props":2233,"children":2234},{"id":1724},[2235],{"type":621,"value":1724},{"type":616,"tag":862,"props":2237,"children":2238},{},[2239,2244,2249],{"type":616,"tag":866,"props":2240,"children":2241},{},[2242],{"type":621,"value":2243},"API 和技術細節尚未公開，企業評估導入需等候正式整合後才能實際測試",{"type":616,"tag":866,"props":2245,"children":2246},{},[2247],{"type":621,"value":2248},"正式生產環境的 20% 錯誤率仍需人工審查機制，增加實作複雜度",{"type":616,"tag":866,"props":2250,"children":2251},{},[2252],{"type":621,"value":2253},"與現有資料治理工具（資料血緣、稽核日誌）的整合方式尚不清楚",{"type":616,"tag":660,"props":2255,"children":2256},{"id":1747},[2257],{"type":621,"value":1747},{"type":616,"tag":862,"props":2259,"children":2260},{},[2261,2266],{"type":616,"tag":866,"props":2262,"children":2263},{},[2264],{"type":621,"value":2265},"BI 工具商面臨壓力：若 Google 雲端服務原生提供高準確率 text-to-SQL，獨立 BI 工具的自然語言查詢功能差異化空間將縮小",{"type":616,"tag":866,"props":2267,"children":2268},{},[2269],{"type":621,"value":2270},"資料分析師角色轉型：重複性的 SQL 撰寫工作將被自動化，分析師需專注於更高層次的業務問題定義與結果驗證",{"type":616,"tag":660,"props":2272,"children":2274},{"id":2273},"判決技術里程碑確立企業落地需等待-api-開放短期觀望中期追蹤整合進展",[2275],{"type":621,"value":2276},"判決：技術里程碑確立，企業落地需等待 API 開放（短期觀望，中期追蹤整合進展）",{"type":616,"tag":617,"props":2278,"children":2279},{},[2280],{"type":621,"value":2281},"Gemini-SQL2 在技術指標上確立了明確的領先地位，但商業化路徑尚不明朗。80% 的 BIRD 準確率是里程碑，但距離無需人工審查的「可信賴生產級別」仍有距離。短期內，最大的競爭影響是對 AWS Q-SQL 和 OpenAI 的直接施壓，以及加速整個業界在 text-to-SQL 能力上的投入。",{"title":385,"searchDepth":623,"depth":623,"links":2283},[],{"data":2285,"body":2286,"excerpt":-1,"toc":2405},{"title":385,"description":385},{"type":613,"children":2287},[2288,2294,2400],{"type":616,"tag":660,"props":2289,"children":2291},{"id":2290},"bird-單一模型排行榜2026-年-6-月",[2292],{"type":621,"value":2293},"BIRD 單一模型排行榜（2026 年 6 月）",{"type":616,"tag":2295,"props":2296,"children":2297},"table",{},[2298,2317],{"type":616,"tag":2299,"props":2300,"children":2301},"thead",{},[2302],{"type":616,"tag":2303,"props":2304,"children":2305},"tr",{},[2306,2312],{"type":616,"tag":2307,"props":2308,"children":2309},"th",{},[2310],{"type":621,"value":2311},"模型",{"type":616,"tag":2307,"props":2313,"children":2314},{},[2315],{"type":621,"value":2316},"執行準確率",{"type":616,"tag":2318,"props":2319,"children":2320},"tbody",{},[2321,2335,2348,2361,2374,2387],{"type":616,"tag":2303,"props":2322,"children":2323},{},[2324,2330],{"type":616,"tag":2325,"props":2326,"children":2327},"td",{},[2328],{"type":621,"value":2329},"Gemini-SQL2(Google)",{"type":616,"tag":2325,"props":2331,"children":2332},{},[2333],{"type":621,"value":2334},"80.04%（第一）",{"type":616,"tag":2303,"props":2336,"children":2337},{},[2338,2343],{"type":616,"tag":2325,"props":2339,"children":2340},{},[2341],{"type":621,"value":2342},"Gemini-SQL（Google 前版）",{"type":616,"tag":2325,"props":2344,"children":2345},{},[2346],{"type":621,"value":2347},"~77.2%",{"type":616,"tag":2303,"props":2349,"children":2350},{},[2351,2356],{"type":616,"tag":2325,"props":2352,"children":2353},{},[2354],{"type":621,"value":2355},"AWS Q-SQL",{"type":616,"tag":2325,"props":2357,"children":2358},{},[2359],{"type":621,"value":2360},"~76.5%",{"type":616,"tag":2303,"props":2362,"children":2363},{},[2364,2369],{"type":616,"tag":2325,"props":2365,"children":2366},{},[2367],{"type":621,"value":2368},"OpenAI GPT-5.5-xhigh",{"type":616,"tag":2325,"props":2370,"children":2371},{},[2372],{"type":621,"value":2373},"~72.8%",{"type":616,"tag":2303,"props":2375,"children":2376},{},[2377,2382],{"type":616,"tag":2325,"props":2378,"children":2379},{},[2380],{"type":621,"value":2381},"Anthropic Claude Opus 4.6",{"type":616,"tag":2325,"props":2383,"children":2384},{},[2385],{"type":621,"value":2386},"~70.9%",{"type":616,"tag":2303,"props":2388,"children":2389},{},[2390,2395],{"type":616,"tag":2325,"props":2391,"children":2392},{},[2393],{"type":621,"value":2394},"人類基準",{"type":616,"tag":2325,"props":2396,"children":2397},{},[2398],{"type":621,"value":2399},"92.96%",{"type":616,"tag":617,"props":2401,"children":2402},{},[2403],{"type":621,"value":2404},"Gemini-SQL2 較前版提升約 3 個百分點，相較主要競品領先 7-9 個百分點。與人類基準的差距縮小至 12.92 個百分點，代表複雜查詢場景下仍有相當的改善空間。",{"title":385,"searchDepth":623,"depth":623,"links":2406},[],{"data":2408,"body":2409,"excerpt":-1,"toc":2430},{"title":385,"description":385},{"type":613,"children":2410},[2411],{"type":616,"tag":862,"props":2412,"children":2413},{},[2414,2418,2422,2426],{"type":616,"tag":866,"props":2415,"children":2416},{},[2417],{"type":621,"value":298},{"type":616,"tag":866,"props":2419,"children":2420},{},[2421],{"type":621,"value":299},{"type":616,"tag":866,"props":2423,"children":2424},{},[2425],{"type":621,"value":300},{"type":616,"tag":866,"props":2427,"children":2428},{},[2429],{"type":621,"value":301},{"title":385,"searchDepth":623,"depth":623,"links":2431},[],{"data":2433,"body":2434,"excerpt":-1,"toc":2447},{"title":385,"description":385},{"type":613,"children":2435},[2436],{"type":616,"tag":862,"props":2437,"children":2438},{},[2439,2443],{"type":616,"tag":866,"props":2440,"children":2441},{},[2442],{"type":621,"value":303},{"type":616,"tag":866,"props":2444,"children":2445},{},[2446],{"type":621,"value":304},{"title":385,"searchDepth":623,"depth":623,"links":2448},[],{"data":2450,"body":2451,"excerpt":-1,"toc":2457},{"title":385,"description":308},{"type":613,"children":2452},[2453],{"type":616,"tag":617,"props":2454,"children":2455},{},[2456],{"type":621,"value":308},{"title":385,"searchDepth":623,"depth":623,"links":2458},[],{"data":2460,"body":2461,"excerpt":-1,"toc":2467},{"title":385,"description":309},{"type":613,"children":2462},[2463],{"type":616,"tag":617,"props":2464,"children":2465},{},[2466],{"type":621,"value":309},{"title":385,"searchDepth":623,"depth":623,"links":2468},[],{"data":2470,"body":2471,"excerpt":-1,"toc":2477},{"title":385,"description":310},{"type":613,"children":2472},[2473],{"type":616,"tag":617,"props":2474,"children":2475},{},[2476],{"type":621,"value":310},{"title":385,"searchDepth":623,"depth":623,"links":2478},[],{"data":2480,"body":2481,"excerpt":-1,"toc":2538},{"title":385,"description":385},{"type":613,"children":2482},[2483,2489,2508,2523,2528,2533],{"type":616,"tag":660,"props":2484,"children":2486},{"id":2485},"frontiermath-突破",[2487],{"type":621,"value":2488},"FrontierMath 突破",{"type":616,"tag":617,"props":2490,"children":2491},{},[2492,2494,2499,2501,2506],{"type":621,"value":2493},"Claude Fable 5 在 Epoch AI 的 FrontierMath Tier 4 v2 測試中達到 ",{"type":616,"tag":679,"props":2495,"children":2496},{},[2497],{"type":621,"value":2498},"88%",{"type":621,"value":2500}," 正確率，涵蓋 Tier 1–3 則為 87%，領先 GPT-5.5 的約 75% 達 ",{"type":616,"tag":679,"props":2502,"children":2503},{},[2504],{"type":621,"value":2505},"13 個百分點",{"type":621,"value":2507},"。",{"type":616,"tag":672,"props":2509,"children":2510},{},[2511],{"type":616,"tag":617,"props":2512,"children":2513},{},[2514,2518,2521],{"type":616,"tag":679,"props":2515,"children":2516},{},[2517],{"type":621,"value":683},{"type":616,"tag":685,"props":2519,"children":2520},{},[],{"type":621,"value":2522},"\nFrontierMath：由 Epoch AI 設計的頂尖數學推理 benchmark，收錄研究級難度數學題，分四個難度層，目前公認為 AI 數學能力測試天花板。",{"type":616,"tag":660,"props":2524,"children":2526},{"id":2525},"能力躍升幅度",[2527],{"type":621,"value":2525},{"type":616,"tag":617,"props":2529,"children":2530},{},[2531],{"type":621,"value":2532},"相較於前代旗艦 Claude Opus 4.5 在 Tier 4 不足 10% 的成績，Fable 5 的 88% 代表一次近乎翻轉式的能力跳躍。評測採用 Epoch AI 標準測試腳架與最大推理力設定，確保比較基準一致。",{"type":616,"tag":617,"props":2534,"children":2535},{},[2536],{"type":621,"value":2537},"另有報導指出，GPT-5.4 Pro 與 Claude Mythos 均各自解開了數個長年未解的 Erdős 數學猜想，顯示頂尖模型的突破已延伸至真實研究問題，且並非單一陣營獨佔。",{"title":385,"searchDepth":623,"depth":623,"links":2539},[],{"data":2541,"body":2543,"excerpt":-1,"toc":2557},{"title":385,"description":2542},"FrontierMath Tier 4 採用研究級數學題，88% 正確率意味著模型在多步推理與符號操作上已進入實用區間。整合 Fable 5 時，可預期在程式驗證、數學推理型 agent 管道上的表現大幅優於 Opus 4.5。目前 Claude Code 已部署 Fable 5，但初期有部分 access 問題，建議確認 API 訂閱層級後再切換。",{"type":613,"children":2544},[2545],{"type":616,"tag":617,"props":2546,"children":2547},{},[2548,2550,2555],{"type":621,"value":2549},"FrontierMath Tier 4 採用研究級數學題，",{"type":616,"tag":679,"props":2551,"children":2552},{},[2553],{"type":621,"value":2554},"88% 正確率",{"type":621,"value":2556},"意味著模型在多步推理與符號操作上已進入實用區間。整合 Fable 5 時，可預期在程式驗證、數學推理型 agent 管道上的表現大幅優於 Opus 4.5。目前 Claude Code 已部署 Fable 5，但初期有部分 access 問題，建議確認 API 訂閱層級後再切換。",{"title":385,"searchDepth":623,"depth":623,"links":2558},[],{"data":2560,"body":2561,"excerpt":-1,"toc":2567},{"title":385,"description":342},{"type":613,"children":2562},[2563],{"type":616,"tag":617,"props":2564,"children":2565},{},[2566],{"type":621,"value":342},{"title":385,"searchDepth":623,"depth":623,"links":2568},[],{"data":2570,"body":2571,"excerpt":-1,"toc":2619},{"title":385,"description":385},{"type":613,"children":2572},[2573,2578],{"type":616,"tag":660,"props":2574,"children":2576},{"id":2575},"評測數據",[2577],{"type":621,"value":2575},{"type":616,"tag":862,"props":2579,"children":2580},{},[2581,2599,2609],{"type":616,"tag":866,"props":2582,"children":2583},{},[2584,2586,2590,2592,2597],{"type":621,"value":2585},"FrontierMath Tier 4 v2：Fable 5 ",{"type":616,"tag":679,"props":2587,"children":2588},{},[2589],{"type":621,"value":2498},{"type":621,"value":2591}," vs GPT-5.5 ",{"type":616,"tag":679,"props":2593,"children":2594},{},[2595],{"type":621,"value":2596},"~75%",{"type":621,"value":2598},"（領先 13 個百分點）",{"type":616,"tag":866,"props":2600,"children":2601},{},[2602,2604],{"type":621,"value":2603},"FrontierMath Tier 1–3：Fable 5 ",{"type":616,"tag":679,"props":2605,"children":2606},{},[2607],{"type":621,"value":2608},"87%",{"type":616,"tag":866,"props":2610,"children":2611},{},[2612,2614],{"type":621,"value":2613},"Claude Opus 4.5（Tier 4，2026 年初）：",{"type":616,"tag":679,"props":2615,"children":2616},{},[2617],{"type":621,"value":2618},"\u003C10%",{"title":385,"searchDepth":623,"depth":623,"links":2620},[],{"data":2622,"body":2623,"excerpt":-1,"toc":2667},{"title":385,"description":385},{"type":613,"children":2624},[2625,2631,2636,2642,2647,2662],{"type":616,"tag":660,"props":2626,"children":2628},{"id":2627},"顧問巨頭的-ai-翻車現場",[2629],{"type":621,"value":2630},"顧問巨頭的 AI 翻車現場",{"type":616,"tag":617,"props":2632,"children":2633},{},[2634],{"type":621,"value":2635},"KPMG 於 2025 年 10 月發布的 AI 企業應用報告，在 GPTZero 進行法證審查後於 2026 年 6 月緊急下架。45 條引用中僅 5 條正確，40 條引用標題完全捏造，UBS、英國 NHS 等四家機構均向《金融時報》表示，報告描述「不實或具誤導性」。",{"type":616,"tag":660,"props":2637,"children":2639},{"id":2638},"vibe-citingai-假引用的新手法",[2640],{"type":621,"value":2641},"vibe citing：AI 假引用的新手法",{"type":616,"tag":617,"props":2643,"children":2644},{},[2645],{"type":621,"value":2646},"GPTZero 將此現象命名為「vibe citing」——AI 將不同來源片段拼湊，篡改作者或發明 URL，製造外觀可信卻無法核實的假引用。",{"type":616,"tag":672,"props":2648,"children":2649},{},[2650],{"type":616,"tag":617,"props":2651,"children":2652},{},[2653,2657,2660],{"type":616,"tag":679,"props":2654,"children":2655},{},[2656],{"type":621,"value":683},{"type":616,"tag":685,"props":2658,"children":2659},{},[],{"type":621,"value":2661},"\nvibe citing：類比 vibe coding，指 AI 生成引用時只追求「看起來合理」，實際上無法驗證甚至完全捏造。",{"type":616,"tag":617,"props":2663,"children":2664},{},[2665],{"type":621,"value":2666},"具體案例包括：將阿聯酋航空實體機器人「Sara」誤描述為手機聊天機器人，以 2019 年舊聞佐證當時尚未商業化的 agentic AI。EY 稍早也因相同問題撤回報告，顯示此現象並非個案。",{"title":385,"searchDepth":623,"depth":623,"links":2668},[],{"data":2670,"body":2672,"excerpt":-1,"toc":2686},{"title":385,"description":2671},"此事件揭示 AI 輔助寫作的核心盲點：AI 能生成外觀合理的引用格式，卻無法保證內容真實性。在任何涉及外部引用的場景，應建立引用驗證管線——至少對 URL 進行可及性測試，對標題進行原文比對。「看起來像引用」與「引用正確」是截然不同的兩件事。",{"type":613,"children":2673},[2674],{"type":616,"tag":617,"props":2675,"children":2676},{},[2677,2679,2684],{"type":621,"value":2678},"此事件揭示 AI 輔助寫作的核心盲點：AI 能生成外觀合理的引用格式，卻無法保證內容真實性。在任何涉及外部引用的場景，應建立",{"type":616,"tag":679,"props":2680,"children":2681},{},[2682],{"type":621,"value":2683},"引用驗證管線",{"type":621,"value":2685},"——至少對 URL 進行可及性測試，對標題進行原文比對。「看起來像引用」與「引用正確」是截然不同的兩件事。",{"title":385,"searchDepth":623,"depth":623,"links":2687},[],{"data":2689,"body":2690,"excerpt":-1,"toc":2696},{"title":385,"description":382},{"type":613,"children":2691},[2692],{"type":616,"tag":617,"props":2693,"children":2694},{},[2695],{"type":621,"value":382},{"title":385,"searchDepth":623,"depth":623,"links":2697},[],{"data":2699,"body":2700,"excerpt":-1,"toc":2784},{"title":385,"description":385},{"type":613,"children":2701},[2702,2708,2713,2728,2734,2746,2779],{"type":616,"tag":660,"props":2703,"children":2705},{"id":2704},"開放世界計數從細胞到人群的統一架構",[2706],{"type":621,"value":2707},"開放世界計數：從細胞到人群的統一架構",{"type":616,"tag":617,"props":2709,"children":2710},{},[2711],{"type":621,"value":2712},"清華大學研究團隊於 2026 年 5 月提交論文（arXiv：2605.30846），發布「Count Anything」——首個透過純文字 prompt 計數任何影像中任何物件的開放世界模型，涵蓋人群、衛星影像、顯微鏡細胞切片、農業場景等六大視覺領域。",{"type":616,"tag":672,"props":2714,"children":2715},{},[2716],{"type":616,"tag":617,"props":2717,"children":2718},{},[2719,2723,2726],{"type":616,"tag":679,"props":2720,"children":2721},{},[2722],{"type":621,"value":683},{"type":616,"tag":685,"props":2724,"children":2725},{},[],{"type":621,"value":2727},"\n開放世界計數 (open-world counting) ：不限定類別、可透過文字描述計數任意物件，有別於傳統只能計數預先定義類別的專用系統。",{"type":616,"tag":660,"props":2729,"children":2731},{"id":2730},"為何計數比想像中難",[2732],{"type":621,"value":2733},"為何計數比想像中難？",{"type":616,"tag":617,"props":2735,"children":2736},{},[2737,2739,2744],{"type":621,"value":2738},"傳統電腦視覺系統多為單一類別訓練，計算細胞的模型無法計數螺絲釘。Count Anything 採用",{"type":616,"tag":679,"props":2740,"children":2741},{},[2742],{"type":621,"value":2743},"雙計數器架構",{"type":621,"value":2745},"解決此問題：",{"type":616,"tag":862,"props":2747,"children":2748},{},[2749,2759,2769],{"type":616,"tag":866,"props":2750,"children":2751},{},[2752,2757],{"type":616,"tag":679,"props":2753,"children":2754},{},[2755],{"type":621,"value":2756},"RSC(Region-level Sparse Counter)",{"type":621,"value":2758},"：對大型、稀疏物件繪製 bounding box",{"type":616,"tag":866,"props":2760,"children":2761},{},[2762,2767],{"type":616,"tag":679,"props":2763,"children":2764},{},[2765],{"type":621,"value":2766},"PDC(Pixel-level Dense Counter)",{"type":621,"value":2768},"：對小型、密集物件逐像素點預測",{"type":616,"tag":866,"props":2770,"children":2771},{},[2772,2777],{"type":616,"tag":679,"props":2773,"children":2774},{},[2775],{"type":621,"value":2776},"CCF(Complementary Count Fusion)",{"type":621,"value":2778},"：以 parameter-free 方式融合兩者，抑制重複計數",{"type":616,"tag":617,"props":2780,"children":2781},{},[2782],{"type":621,"value":2783},"模型建構於 Meta 的 SAM3 基礎模型之上，加入小型 adapter 而非從頭重訓，以自建 CLOC 資料集（22 萬張影像、619 類別、1,500 萬標記實例）訓練。基準測試顯示，平均每查詢約 9 個計數誤差，錯誤率比主要競爭者低逾一半。",{"title":385,"searchDepth":623,"depth":623,"links":2785},[],{"data":2787,"body":2788,"excerpt":-1,"toc":2794},{"title":385,"description":410},{"type":613,"children":2789},[2790],{"type":616,"tag":617,"props":2791,"children":2792},{},[2793],{"type":621,"value":410},{"title":385,"searchDepth":623,"depth":623,"links":2795},[],{"data":2797,"body":2798,"excerpt":-1,"toc":2804},{"title":385,"description":411},{"type":613,"children":2799},[2800],{"type":616,"tag":617,"props":2801,"children":2802},{},[2803],{"type":621,"value":411},{"title":385,"searchDepth":623,"depth":623,"links":2805},[],{"data":2807,"body":2808,"excerpt":-1,"toc":2833},{"title":385,"description":385},{"type":613,"children":2809},[2810,2815],{"type":616,"tag":660,"props":2811,"children":2813},{"id":2812},"效能基準",[2814],{"type":621,"value":2812},{"type":616,"tag":862,"props":2816,"children":2817},{},[2818,2823,2828],{"type":616,"tag":866,"props":2819,"children":2820},{},[2821],{"type":621,"value":2822},"平均計數誤差：約 9 個（每查詢類別）",{"type":616,"tag":866,"props":2824,"children":2825},{},[2826],{"type":621,"value":2827},"競爭對手對比：CountGD、CLIP-Count、Grounding DINO 錯誤率高出逾一半",{"type":616,"tag":866,"props":2829,"children":2830},{},[2831],{"type":621,"value":2832},"訓練資料集 CLOC：22 萬張影像、619 類別、1,500 萬標記實例",{"title":385,"searchDepth":623,"depth":623,"links":2834},[],{"data":2836,"body":2837,"excerpt":-1,"toc":2881},{"title":385,"description":385},{"type":613,"children":2838},[2839,2844,2856,2871,2876],{"type":616,"tag":660,"props":2840,"children":2842},{"id":2841},"事件時間軸",[2843],{"type":621,"value":2841},{"type":616,"tag":617,"props":2845,"children":2846},{},[2847,2849,2854],{"type":621,"value":2848},"2025 年 12 月，Meta 宣布以 ",{"type":616,"tag":679,"props":2850,"children":2851},{},[2852],{"type":621,"value":2853},"20 億美元",{"type":621,"value":2855},"收購中國 AI 新創 Manus，後者曾以病毒式 agent demo 轟動業界。Manus 雖早已將員工遷移至新加坡試圖規避監管，但北京認定只要底層技術與人才源自中國，境外設立不能豁免——批評者稱此策略為「新加坡洗白 (Singapore washing) 」。",{"type":616,"tag":672,"props":2857,"children":2858},{},[2859],{"type":616,"tag":617,"props":2860,"children":2861},{},[2862,2866,2869],{"type":616,"tag":679,"props":2863,"children":2864},{},[2865],{"type":621,"value":683},{"type":616,"tag":685,"props":2867,"children":2868},{},[],{"type":621,"value":2870},"\nSingapore washing：企業透過在新加坡設立法人，試圖將中國業務偽裝為非中國實體以規避技術出口管制，類似金融領域的洗白概念。",{"type":616,"tag":660,"props":2872,"children":2874},{"id":2873},"監管介入與分拆進度",[2875],{"type":621,"value":2873},{"type":616,"tag":617,"props":2877,"children":2878},{},[2879],{"type":621,"value":2880},"2026 年 4 月，中國國家發展和改革委員會 (NDRC) 正式下令撤銷收購，理由涉及技術出口管制及外資法規潛在違規。6 月 1 日，Meta 完成「防火牆」隔離，Manus 員工失去對 Meta 內部系統的全部存取，Meta 員工亦被禁止在內部專案使用 Manus 工具。6 月 13 日，兩家公司已不再共享任何資料，運營層面分拆宣告完成。",{"title":385,"searchDepth":623,"depth":623,"links":2882},[],{"data":2884,"body":2885,"excerpt":-1,"toc":2891},{"title":385,"description":439},{"type":613,"children":2886},[2887],{"type":616,"tag":617,"props":2888,"children":2889},{},[2890],{"type":621,"value":439},{"title":385,"searchDepth":623,"depth":623,"links":2892},[],{"data":2894,"body":2896,"excerpt":-1,"toc":2910},{"title":385,"description":2895},"此案為矽谷收購中國 AI 公司設下新的風險定價標準：「新加坡洗白」被明確否定，離岸架構無法作為合規護盾。Manus 創辦人已初步討論以約 10 億美元從 Meta 手中買回公司並考慮香港上市，但 20 億美元估值已大幅蒸發。未來涉及中國人才或技術的收購案，須在交割前完成徹底技術溯源審查，否則監管風險將侵蝕全部收購價值。",{"type":613,"children":2897},[2898],{"type":616,"tag":617,"props":2899,"children":2900},{},[2901,2903,2908],{"type":621,"value":2902},"此案為矽谷收購中國 AI 公司設下新的風險定價標準：「新加坡洗白」被明確否定，離岸架構無法作為合規護盾。Manus 創辦人已初步討論以約 ",{"type":616,"tag":679,"props":2904,"children":2905},{},[2906],{"type":621,"value":2907},"10 億美元",{"type":621,"value":2909},"從 Meta 手中買回公司並考慮香港上市，但 20 億美元估值已大幅蒸發。未來涉及中國人才或技術的收購案，須在交割前完成徹底技術溯源審查，否則監管風險將侵蝕全部收購價值。",{"title":385,"searchDepth":623,"depth":623,"links":2911},[],{"data":2913,"body":2914,"excerpt":-1,"toc":2953},{"title":385,"description":385},{"type":613,"children":2915},[2916,2922,2927,2942,2948],{"type":616,"tag":660,"props":2917,"children":2919},{"id":2918},"傳票範圍廣告健康資料與迎合性行為",[2920],{"type":621,"value":2921},"傳票範圍：廣告、健康資料與迎合性行為",{"type":616,"tag":617,"props":2923,"children":2924},{},[2925],{"type":621,"value":2926},"2026 年 6 月 12 日，紐約州檢察長代表多州聯盟向 OpenAI 發出傳票，正式展開調查。調查範圍涵蓋廣告政策揭露方式、付費內容嵌入 ChatGPT 的機制、消費者與健康敏感資料處理、未成年人與老年人保護措施，以及模型「迎合性」 (sycophancy) 行為。",{"type":616,"tag":672,"props":2928,"children":2929},{},[2930],{"type":616,"tag":617,"props":2931,"children":2932},{},[2933,2937,2940],{"type":616,"tag":679,"props":2934,"children":2935},{},[2936],{"type":621,"value":683},{"type":616,"tag":685,"props":2938,"children":2939},{},[],{"type":621,"value":2941},"\n迎合性 (sycophancy) ：指 AI 模型為取悅用戶而給出偏頗或不準確的回應，而非提供客觀事實。",{"type":616,"tag":660,"props":2943,"children":2945},{"id":2944},"佛羅里達開第一槍ipo-前景蒙陰",[2946],{"type":621,"value":2947},"佛羅里達開第一槍，IPO 前景蒙陰",{"type":616,"tag":617,"props":2949,"children":2950},{},[2951],{"type":621,"value":2952},"6 月 1 日，佛羅里達州率先以 ChatGPT 危害兒童為由提起訴訟，將 OpenAI 及 CEO Sam Altman 列為被告。多州聯合調查加劇壓力，直接威脅 OpenAI 預計 2026 年 9 月、估值可能達 1 兆美元的 IPO 計畫。自 2025 年以來，美國已有 49 州提出逾 464 項聊天機器人安全相關法案，監管浪潮正快速逼近。",{"title":385,"searchDepth":623,"depth":623,"links":2954},[],{"data":2956,"body":2957,"excerpt":-1,"toc":2963},{"title":385,"description":474},{"type":613,"children":2958},[2959],{"type":616,"tag":617,"props":2960,"children":2961},{},[2962],{"type":621,"value":474},{"title":385,"searchDepth":623,"depth":623,"links":2964},[],{"data":2966,"body":2967,"excerpt":-1,"toc":2973},{"title":385,"description":475},{"type":613,"children":2968},[2969],{"type":616,"tag":617,"props":2970,"children":2971},{},[2972],{"type":621,"value":475},{"title":385,"searchDepth":623,"depth":623,"links":2974},[],{"data":2976,"body":2978,"excerpt":-1,"toc":3040},{"title":385,"description":2977},"LMCache 首次發布於 2025 年 10 月，近期因 2026 年 1 月與 AMD 的 GPU 整合公告重新引發社群討論，截至目前已累積 8,900+ GitHub stars。",{"type":613,"children":2979},[2980,2984,2990,2995,3010,3015,3025,3035],{"type":616,"tag":617,"props":2981,"children":2982},{},[2983],{"type":621,"value":2977},{"type":616,"tag":660,"props":2985,"children":2987},{"id":2986},"kv-cache-管理層的定位",[2988],{"type":621,"value":2989},"KV Cache 管理層的定位",{"type":616,"tag":617,"props":2991,"children":2992},{},[2993],{"type":621,"value":2994},"LMCache 運行於 vLLM、SGLang 等推論引擎之上，將 KV cache 從推論暫態提升為「可持久化、跨引擎複用的 AI 原生知識」。相較原生框架，可帶來最高 15 倍吞吐量提升與至少 2 倍更低延遲 (TTFT) 。",{"type":616,"tag":672,"props":2996,"children":2997},{},[2998],{"type":616,"tag":617,"props":2999,"children":3000},{},[3001,3005,3008],{"type":616,"tag":679,"props":3002,"children":3003},{},[3004],{"type":621,"value":683},{"type":616,"tag":685,"props":3006,"children":3007},{},[],{"type":621,"value":3009},"\nKV Cache：LLM 生成每個 token 時需計算注意力的 Key/Value 向量，KV Cache 將這些結果暫存以避免重複計算，是影響推論速度最關鍵的資源之一。",{"type":616,"tag":660,"props":3011,"children":3013},{"id":3012},"核心技術亮點",[3014],{"type":621,"value":3012},{"type":616,"tag":617,"props":3016,"children":3017},{},[3018,3023],{"type":616,"tag":679,"props":3019,"children":3020},{},[3021],{"type":621,"value":3022},"分層儲存卸載",{"type":621,"value":3024},"：KV cache 可從 GPU VRAM 逐層移至 CPU DRAM、本地磁碟，乃至遠端後端（Redis、S3 相容存儲等），共支援 8 種儲存後端。",{"type":616,"tag":617,"props":3026,"children":3027},{},[3028,3033],{"type":616,"tag":679,"props":3029,"children":3030},{},[3031],{"type":621,"value":3032},"CacheBlend",{"type":621,"value":3034},"：突破傳統 prefix caching 只能匹配前綴的限制，可識別並複用請求任意位置的已計算 KV 片段，大幅提升長上下文場景的命中率。",{"type":616,"tag":617,"props":3036,"children":3037},{},[3038],{"type":621,"value":3039},"2026 年 1 月，AMD 合作公告帶來新里程碑：Qwen3、Llama3、Qwen-VL 等模型在 AMD Instinct™ MI300X 上實現 3–10 倍推論加速，目前已支援 NVIDIA、AMD、Ascend、TPU 共 4 種處理器架構。",{"title":385,"searchDepth":623,"depth":623,"links":3041},[],{"data":3043,"body":3045,"excerpt":-1,"toc":3061},{"title":385,"description":3044},"LMCache 以獨立 daemon 程序運行，透過模組化 connector 與引擎解耦，引擎當機也不遺失 cache。",{"type":613,"children":3046},[3047,3051,3056],{"type":616,"tag":617,"props":3048,"children":3049},{},[3050],{"type":621,"value":3044},{"type":616,"tag":617,"props":3052,"children":3053},{},[3054],{"type":621,"value":3055},"對既有 vLLM 部署，整合成本相對低——需設定 storage backend 與 CacheBlend policy。需注意 context truncation 會使 prefix cache 命中率降低約 50%，長上下文 RAG 場景應優先評估 system prompt 的共用比例。",{"type":616,"tag":617,"props":3057,"children":3058},{},[3059],{"type":621,"value":3060},"PD 解耦 (Prefill-Decode Disaggregation) 透過 NVLink/RDMA 跨 worker 傳輸 KV cache，適合大規模叢集降低延遲，但需同步評估網路頻寬成本。",{"title":385,"searchDepth":623,"depth":623,"links":3062},[],{"data":3064,"body":3066,"excerpt":-1,"toc":3077},{"title":385,"description":3065},"KV cache 複用直接轉化為 GPU 成本節省——最高 15 倍吞吐量提升，意味著服務相同請求量所需 GPU 數量可大幅縮減。",{"type":613,"children":3067},[3068,3072],{"type":616,"tag":617,"props":3069,"children":3070},{},[3071],{"type":621,"value":3065},{"type":616,"tag":617,"props":3073,"children":3074},{},[3075],{"type":621,"value":3076},"AMD MI300X 整合公告的戰略意義在於：LMCache 讓企業在 NVIDIA GPU 供給緊張、溢價偏高時有可行的替代路徑。2025 年 10 月加入 PyTorch Foundation，為長期維護提供組織保障，降低企業大規模採用的技術風險。",{"title":385,"searchDepth":623,"depth":623,"links":3078},[],{"data":3080,"body":3081,"excerpt":-1,"toc":3134},{"title":385,"description":385},{"type":613,"children":3082},[3083,3087],{"type":616,"tag":660,"props":3084,"children":3085},{"id":2812},[3086],{"type":621,"value":2812},{"type":616,"tag":862,"props":3088,"children":3089},{},[3090,3102,3112,3124],{"type":616,"tag":866,"props":3091,"children":3092},{},[3093,3095,3100],{"type":621,"value":3094},"吞吐量：最高 ",{"type":616,"tag":679,"props":3096,"children":3097},{},[3098],{"type":621,"value":3099},"15×",{"type":621,"value":3101}," 提升（相較原生框架）",{"type":616,"tag":866,"props":3103,"children":3104},{},[3105,3107],{"type":621,"value":3106},"TTFT 延遲：至少降低 ",{"type":616,"tag":679,"props":3108,"children":3109},{},[3110],{"type":621,"value":3111},"2×",{"type":616,"tag":866,"props":3113,"children":3114},{},[3115,3117,3122],{"type":621,"value":3116},"AMD MI300X 整合加速：",{"type":616,"tag":679,"props":3118,"children":3119},{},[3120],{"type":621,"value":3121},"3–10×",{"type":621,"value":3123},"（Qwen3、Llama3、Qwen-VL）",{"type":616,"tag":866,"props":3125,"children":3126},{},[3127,3129],{"type":621,"value":3128},"Context truncation 對 prefix cache 命中率影響：降低約 ",{"type":616,"tag":679,"props":3130,"children":3131},{},[3132],{"type":621,"value":3133},"50%",{"title":385,"searchDepth":623,"depth":623,"links":3135},[],{"data":3137,"body":3138,"excerpt":-1,"toc":3175},{"title":385,"description":385},{"type":613,"children":3139},[3140,3145,3150,3165,3170],{"type":616,"tag":660,"props":3141,"children":3143},{"id":3142},"三道荒謬算術題",[3144],{"type":621,"value":3142},{"type":616,"tag":617,"props":3146,"children":3147},{},[3148],{"type":621,"value":3149},"幽默作家 Andrew Singleton 在 McSweeney's 刊出〈AI Economics for Dummies〉，以小學算術題格式包裝三則 AI 泡沫寓言：Alex 花 20 億買一顆葡萄、轉手收訂閱年入 1200 億「ARR」；Laura 靠計程車月費訂閱有 4000 萬用戶，卻年燒 250 億油費；Xavier 每月虧損 10 億後承諾再砸 8500 億蓋「沒人想住的公寓」。",{"type":616,"tag":672,"props":3151,"children":3152},{},[3153],{"type":616,"tag":617,"props":3154,"children":3155},{},[3156,3160,3163],{"type":616,"tag":679,"props":3157,"children":3158},{},[3159],{"type":621,"value":683},{"type":616,"tag":685,"props":3161,"children":3162},{},[],{"type":621,"value":3164},"\nARR（年度經常性收入）：將當期合約換算為年化數字，常被用來讓高速成長看起來更壯觀。",{"type":616,"tag":660,"props":3166,"children":3168},{"id":3167},"諷刺背後的行業現實",[3169],{"type":621,"value":3167},{"type":616,"tag":617,"props":3171,"children":3172},{},[3173],{"type":621,"value":3174},"三則寓言各自對應真實慣技：預付合約膨脹 ARR、訂閱掩蓋推論成本虧損、資本支出軍備競賽。文章結語以「停止提問，勒德分子！」收尾，諷刺業界迴避財務邏輯的集體姿態。",{"title":385,"searchDepth":623,"depth":623,"links":3176},[],{"data":3178,"body":3179,"excerpt":-1,"toc":3185},{"title":385,"description":542},{"type":613,"children":3180},[3181],{"type":616,"tag":617,"props":3182,"children":3183},{},[3184],{"type":621,"value":542},{"title":385,"searchDepth":623,"depth":623,"links":3186},[],{"data":3188,"body":3189,"excerpt":-1,"toc":3195},{"title":385,"description":543},{"type":613,"children":3190},[3191],{"type":616,"tag":617,"props":3192,"children":3193},{},[3194],{"type":621,"value":543},{"title":385,"searchDepth":623,"depth":623,"links":3196},[],{"data":3198,"body":3199,"excerpt":-1,"toc":3257},{"title":385,"description":385},{"type":613,"children":3200},[3201,3207,3226,3241,3247,3252],{"type":616,"tag":660,"props":3202,"children":3204},{"id":3203},"以大腦分層結構取代-transformer",[3205],{"type":621,"value":3206},"以大腦分層結構取代 Transformer",{"type":616,"tag":617,"props":3208,"children":3209},{},[3210,3212,3217,3219,3224],{"type":621,"value":3211},"Sapient Intelligence 開源的 HRM-Text（1B 參數）以",{"type":616,"tag":679,"props":3213,"children":3214},{},[3215],{"type":621,"value":3216},"層級遞迴模型 (HRM)",{"type":621,"value":3218},"完全取代標準 Transformer。雙嵌套遞迴棧讓慢速高層模組 (H-module) 維持全域語義策略，快速低層模組 (L-module) 處理局部計算細節，輸出前先於連續",{"type":616,"tag":679,"props":3220,"children":3221},{},[3222],{"type":621,"value":3223},"潛空間",{"type":621,"value":3225},"進行內部遞迴計算，無需顯式思維鏈文字。",{"type":616,"tag":672,"props":3227,"children":3228},{},[3229],{"type":616,"tag":617,"props":3230,"children":3231},{},[3232,3236,3239],{"type":616,"tag":679,"props":3233,"children":3234},{},[3235],{"type":621,"value":683},{"type":616,"tag":685,"props":3237,"children":3238},{},[],{"type":621,"value":3240},"\nHRM(Hierarchical Recurrent Model) ：以雙層遞迴取代 Transformer 自注意力機制，模擬大腦皮層分層處理邏輯。",{"type":616,"tag":660,"props":3242,"children":3244},{"id":3243},"_1500-美元46-小時的效率示範",[3245],{"type":621,"value":3246},"1,500 美元、46 小時的效率示範",{"type":616,"tag":617,"props":3248,"children":3249},{},[3250],{"type":621,"value":3251},"訓練成本僅約 1,500 美元，16 張 H100 GPU 耗時 46 小時完成。訓練資料約 400 億個唯一 token，比主流競品少 100–1,000 倍，計算量少 96–432 倍。",{"type":616,"tag":617,"props":3253,"children":3254},{},[3255],{"type":621,"value":3256},"int4 量化後體積僅 0.6 GiB，理論上可在智慧型手機部署。HuggingFace CEO Clem Delangue 個人公開力薦，圖靈獎得主 Yoshua Bengio 團隊在 GRAM 論文中延伸並採用此架構，為這條技術路線正式背書。",{"title":385,"searchDepth":623,"depth":623,"links":3258},[],{"data":3260,"body":3261,"excerpt":-1,"toc":3267},{"title":385,"description":577},{"type":613,"children":3262},[3263],{"type":616,"tag":617,"props":3264,"children":3265},{},[3266],{"type":621,"value":577},{"title":385,"searchDepth":623,"depth":623,"links":3268},[],{"data":3270,"body":3271,"excerpt":-1,"toc":3277},{"title":385,"description":578},{"type":613,"children":3272},[3273],{"type":616,"tag":617,"props":3274,"children":3275},{},[3276],{"type":621,"value":578},{"title":385,"searchDepth":623,"depth":623,"links":3278},[],{"data":3280,"body":3281,"excerpt":-1,"toc":3322},{"title":385,"description":385},{"type":613,"children":3282},[3283,3289,3317],{"type":616,"tag":660,"props":3284,"children":3286},{"id":3285},"效能基準-hrm-text-1b",[3287],{"type":621,"value":3288},"效能基準 (HRM-Text 1B)",{"type":616,"tag":862,"props":3290,"children":3291},{},[3292,3297,3302,3307,3312],{"type":616,"tag":866,"props":3293,"children":3294},{},[3295],{"type":621,"value":3296},"MMLU：60.7%",{"type":616,"tag":866,"props":3298,"children":3299},{},[3300],{"type":621,"value":3301},"GSM8K：84.5%",{"type":616,"tag":866,"props":3303,"children":3304},{},[3305],{"type":621,"value":3306},"ARC-Challenge：81.9%",{"type":616,"tag":866,"props":3308,"children":3309},{},[3310],{"type":621,"value":3311},"DROP：82.2%",{"type":616,"tag":866,"props":3313,"children":3314},{},[3315],{"type":621,"value":3316},"MATH：56.2%",{"type":616,"tag":617,"props":3318,"children":3319},{},[3320],{"type":621,"value":3321},"以上成績與 Llama 3.2(3B) 、Gemma 3(4B) 、Qwen(2B) 、OLMo 3(7B) 等更大模型相當，訓練成本差距達數百倍。",{"title":385,"searchDepth":623,"depth":623,"links":3323},[],{"data":3325,"body":3326,"excerpt":-1,"toc":3389},{"title":385,"description":385},{"type":613,"children":3327},[3328,3333,3338,3343,3348,3353,3358,3364,3369,3374,3379,3384],{"type":616,"tag":660,"props":3329,"children":3331},{"id":3330},"社群熱議排行",[3332],{"type":621,"value":3330},{"type":616,"tag":617,"props":3334,"children":3335},{},[3336],{"type":621,"value":3337},"今日五大熱議主題，以互動量排序：①美國政府封鎖 Fable 5 與 Mythos 5（HN 數百則評論）、②Meta AI 成本危機（fintwitter.bsky.social 242 讚）、③OpenAI 遭多州聯合調查 (reuters.com Bluesky 42 upvotes) 、④北京命令撤銷 Manus 收購 (techcrunch.com Bluesky 18 upvotes) 、⑤Fable 5 FrontierMath 基準領先 GPT-5.5 達 13 個百分點。",{"type":616,"tag":617,"props":3339,"children":3340},{},[3341],{"type":621,"value":3342},"政府封鎖話題討論量最高。vlovich123（HN 評論）：「Anthropic 的主張是此 jailbreak 賦予的能力，在其他模型上不需繞過手段就能取得——問題在於你更相信哪一方，而這屆政府在真相方面的紀錄並不樂觀。」",{"type":616,"tag":660,"props":3344,"children":3346},{"id":3345},"技術爭議與分歧",[3347],{"type":621,"value":3345},{"type":616,"tag":617,"props":3349,"children":3350},{},[3351],{"type":621,"value":3352},"Fable 5 Claude Code 可用性是最尖銳的內部分歧。bcherny（Anthropic Claude Code 工程師，X）：「Fable 5 是我用過最強的程式撰寫模型，領先幅度很大。」HN 用戶 tinyhouse 直接反駁：「至少在 Claude Code 上完全無法使用，叫我自己執行所有指令——我真的搞不懂 Anthropic 是怎麼在沒有實際測試的情況下就發布這東西的。」兩份報告來自同一工具的不同使用者，是社群內部爭論而非官方對立。",{"type":616,"tag":617,"props":3354,"children":3355},{},[3356],{"type":621,"value":3357},"監管哲學方面，Reddit LocalLLaMA u/feel_the_force69 直接點破：「它們並非『失對齊』，它們只是與你對齊，而非與監管機構及其支持者想要的東西對齊。」此觀點引發能力優先派與安全監管派的正面碰撞，是目前最受討論的哲學分歧。",{"type":616,"tag":660,"props":3359,"children":3361},{"id":3360},"實戰經驗最高價值",[3362],{"type":621,"value":3363},"實戰經驗（最高價值）",{"type":616,"tag":617,"props":3365,"children":3366},{},[3367],{"type":621,"value":3368},"felixgallo（HN 用戶，40 年分散式系統經驗，涵蓋金融科技與遊戲產業）跨多個生產環境實測對比：「GPT 和 Opus 是 L4 級 SDE，而 Fable 是剛晉升的 L5。它需要人工監督，尤其在文獻稀缺領域，但表現遠優於其他選項。」",{"type":616,"tag":617,"props":3370,"children":3371},{},[3372],{"type":621,"value":3373},"LMCache 部署方面，oceanplexian（HN 用戶）提出反直覺觀察：「Claude Code 在幾小時後的新 session 居然還在重新計算整個 KV——Anthropic 的基礎設施並沒有看起來那麼最佳化。」此為生產環境實際觀察，非理論批評，指向企業推論成本優化的真實缺口。",{"type":616,"tag":660,"props":3375,"children":3377},{"id":3376},"未解問題與社群預期",[3378],{"type":621,"value":3376},{"type":616,"tag":617,"props":3380,"children":3381},{},[3382],{"type":621,"value":3383},"ramraj07（HN 評論）提出本週最關鍵的公開問題：「Anthropic 會停止在 Bedrock 上發布嗎？他們會試著把營運遷移出美國嗎？」techmeme.com(Bluesky 8 upvotes) 引述歐洲政界人士：「這是讓人正視依賴美國 AI 技術風險的警鐘。」官方至今無正面回應。",{"type":616,"tag":617,"props":3385,"children":3386},{},[3387],{"type":621,"value":3388},"Meta/Manus 案留下更大的法律空白。@aakashgupta(X) 追問：「Meta 已禁止 WhatsApp 上的競爭對手 AI——為何卻在競爭對手的訊息平台上推出 Manus？」社群普遍預期此案將成為矽谷涉中收購交易風險定價的標誌性前例，但管轄邊界至今無解。",{"title":385,"searchDepth":623,"depth":623,"links":3390},[],{"data":3392,"body":3394,"excerpt":-1,"toc":3410},{"title":385,"description":3393},"今日是 AI 產業監管從「建議框架」走向「行政手段」的轉折點：美國封鎖頂尖模型、多州聯合調查 OpenAI、北京叫停跨境收購，三條管制軸線同步收緊。",{"type":613,"children":3395},[3396,3400,3405],{"type":616,"tag":617,"props":3397,"children":3398},{},[3399],{"type":621,"value":3393},{"type":616,"tag":617,"props":3401,"children":3402},{},[3403],{"type":621,"value":3404},"技術面卻逆向加速：SkillOpt 把 Markdown 文件當成可訓練參數、Gemini-SQL2 在企業 SQL 基準突破 80%、LMCache 把推論成本壓縮 3–10 倍。監管閘門愈收愈緊，技術列車並未減速。",{"type":616,"tag":617,"props":3406,"children":3407},{},[3408],{"type":621,"value":3409},"如何在合規邊界內持續釋放技術紅利，將是接下來每一個產品決策的核心命題。",{"title":385,"searchDepth":623,"depth":623,"links":3411},[],{"data":3413,"body":3414,"excerpt":-1,"toc":3913},{"title":385,"description":385},{"type":613,"children":3415},[3416,3421,3435,3441,3851,3856,3861,3866,3884,3889,3907],{"type":616,"tag":660,"props":3417,"children":3419},{"id":3418},"環境需求",[3420],{"type":621,"value":3418},{"type":616,"tag":617,"props":3422,"children":3423},{},[3424,3426],{"type":621,"value":3425},"需要一個可運行 agent rollout 的評估環境，以及能量化輸出品質的自動評分函數（如 pass@1、exact match）。Python 環境搭配 OpenAI 或 Anthropic SDK 即可；SkillOpt 本身不需要本地 GPU，目標模型以 API 呼叫方式使用。官方 GitHub 專案頁面（",{"type":616,"tag":3427,"props":3428,"children":3432},"a",{"href":3429,"rel":3430},"https://microsoft.github.io/SkillOpt/%EF%BC%89%E6%8F%90%E4%BE%9B%E7%AF%84%E4%BE%8B%E6%A1%86%E6%9E%B6%E8%88%87%E6%96%87%E4%BB%B6%E3%80%82",[3431],"nofollow",[3433],{"type":621,"value":3434},"https://microsoft.github.io/SkillOpt/）提供範例框架與文件。",{"type":616,"tag":660,"props":3436,"children":3438},{"id":3437},"最小-poc",[3439],{"type":621,"value":3440},"最小 PoC",{"type":616,"tag":3442,"props":3443,"children":3447},"pre",{"className":3444,"code":3445,"language":3446,"meta":385,"style":385},"language-python shiki shiki-themes vitesse-dark","from skillopt import SkillOptimizer\n\n# 準備初始技能文件 skill.md 與評估函數\noptimizer = SkillOptimizer(\n    target_model=\"gpt-4o\",      # 目標模型（凍結，只讀取技能文件）\n    optimizer_model=\"gpt-4o\",   # 優化器模型（訓練階段使用）\n    learning_rate=0.3,           # 每步最大編輯比例\n    epochs=4\n)\n\nresult = optimizer.run(\n    skill_path=\"skill.md\",\n    eval_fn=my_benchmark_eval,   # 回傳 0-1 分數的自動評估函數\n    train_tasks=train_set,\n    val_tasks=val_set\n)\n\nresult.save(\"skill_optimized.md\")  # 最終產物：一份優化後的 Markdown\n","python",[3448],{"type":616,"tag":3449,"props":3450,"children":3451},"code",{"__ignoreMap":385},[3452,3480,3489,3499,3523,3562,3596,3624,3642,3651,3659,3691,3722,3749,3771,3789,3797,3805],{"type":616,"tag":3453,"props":3454,"children":3457},"span",{"class":3455,"line":3456},"line",1,[3458,3464,3470,3475],{"type":616,"tag":3453,"props":3459,"children":3461},{"style":3460},"--shiki-default:#4D9375",[3462],{"type":621,"value":3463},"from",{"type":616,"tag":3453,"props":3465,"children":3467},{"style":3466},"--shiki-default:#DBD7CAEE",[3468],{"type":621,"value":3469}," skillopt ",{"type":616,"tag":3453,"props":3471,"children":3472},{"style":3460},[3473],{"type":621,"value":3474},"import",{"type":616,"tag":3453,"props":3476,"children":3477},{"style":3466},[3478],{"type":621,"value":3479}," SkillOptimizer\n",{"type":616,"tag":3453,"props":3481,"children":3482},{"class":3455,"line":623},[3483],{"type":616,"tag":3453,"props":3484,"children":3486},{"emptyLinePlaceholder":3485},true,[3487],{"type":621,"value":3488},"\n",{"type":616,"tag":3453,"props":3490,"children":3492},{"class":3455,"line":3491},3,[3493],{"type":616,"tag":3453,"props":3494,"children":3496},{"style":3495},"--shiki-default:#758575DD",[3497],{"type":621,"value":3498},"# 準備初始技能文件 skill.md 與評估函數\n",{"type":616,"tag":3453,"props":3500,"children":3501},{"class":3455,"line":189},[3502,3507,3513,3518],{"type":616,"tag":3453,"props":3503,"children":3504},{"style":3466},[3505],{"type":621,"value":3506},"optimizer ",{"type":616,"tag":3453,"props":3508,"children":3510},{"style":3509},"--shiki-default:#666666",[3511],{"type":621,"value":3512},"=",{"type":616,"tag":3453,"props":3514,"children":3515},{"style":3466},[3516],{"type":621,"value":3517}," SkillOptimizer",{"type":616,"tag":3453,"props":3519,"children":3520},{"style":3509},[3521],{"type":621,"value":3522},"(\n",{"type":616,"tag":3453,"props":3524,"children":3525},{"class":3455,"line":93},[3526,3532,3536,3542,3548,3552,3557],{"type":616,"tag":3453,"props":3527,"children":3529},{"style":3528},"--shiki-default:#BD976A",[3530],{"type":621,"value":3531},"    target_model",{"type":616,"tag":3453,"props":3533,"children":3534},{"style":3509},[3535],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3537,"children":3539},{"style":3538},"--shiki-default:#C98A7D77",[3540],{"type":621,"value":3541},"\"",{"type":616,"tag":3453,"props":3543,"children":3545},{"style":3544},"--shiki-default:#C98A7D",[3546],{"type":621,"value":3547},"gpt-4o",{"type":616,"tag":3453,"props":3549,"children":3550},{"style":3538},[3551],{"type":621,"value":3541},{"type":616,"tag":3453,"props":3553,"children":3554},{"style":3509},[3555],{"type":621,"value":3556},",",{"type":616,"tag":3453,"props":3558,"children":3559},{"style":3495},[3560],{"type":621,"value":3561},"      # 目標模型（凍結，只讀取技能文件）\n",{"type":616,"tag":3453,"props":3563,"children":3565},{"class":3455,"line":3564},6,[3566,3571,3575,3579,3583,3587,3591],{"type":616,"tag":3453,"props":3567,"children":3568},{"style":3528},[3569],{"type":621,"value":3570},"    optimizer_model",{"type":616,"tag":3453,"props":3572,"children":3573},{"style":3509},[3574],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3576,"children":3577},{"style":3538},[3578],{"type":621,"value":3541},{"type":616,"tag":3453,"props":3580,"children":3581},{"style":3544},[3582],{"type":621,"value":3547},{"type":616,"tag":3453,"props":3584,"children":3585},{"style":3538},[3586],{"type":621,"value":3541},{"type":616,"tag":3453,"props":3588,"children":3589},{"style":3509},[3590],{"type":621,"value":3556},{"type":616,"tag":3453,"props":3592,"children":3593},{"style":3495},[3594],{"type":621,"value":3595},"   # 優化器模型（訓練階段使用）\n",{"type":616,"tag":3453,"props":3597,"children":3599},{"class":3455,"line":3598},7,[3600,3605,3609,3615,3619],{"type":616,"tag":3453,"props":3601,"children":3602},{"style":3528},[3603],{"type":621,"value":3604},"    learning_rate",{"type":616,"tag":3453,"props":3606,"children":3607},{"style":3509},[3608],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3610,"children":3612},{"style":3611},"--shiki-default:#4C9A91",[3613],{"type":621,"value":3614},"0.3",{"type":616,"tag":3453,"props":3616,"children":3617},{"style":3509},[3618],{"type":621,"value":3556},{"type":616,"tag":3453,"props":3620,"children":3621},{"style":3495},[3622],{"type":621,"value":3623},"           # 每步最大編輯比例\n",{"type":616,"tag":3453,"props":3625,"children":3627},{"class":3455,"line":3626},8,[3628,3633,3637],{"type":616,"tag":3453,"props":3629,"children":3630},{"style":3528},[3631],{"type":621,"value":3632},"    epochs",{"type":616,"tag":3453,"props":3634,"children":3635},{"style":3509},[3636],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3638,"children":3639},{"style":3611},[3640],{"type":621,"value":3641},"4\n",{"type":616,"tag":3453,"props":3643,"children":3645},{"class":3455,"line":3644},9,[3646],{"type":616,"tag":3453,"props":3647,"children":3648},{"style":3509},[3649],{"type":621,"value":3650},")\n",{"type":616,"tag":3453,"props":3652,"children":3654},{"class":3455,"line":3653},10,[3655],{"type":616,"tag":3453,"props":3656,"children":3657},{"emptyLinePlaceholder":3485},[3658],{"type":621,"value":3488},{"type":616,"tag":3453,"props":3660,"children":3662},{"class":3455,"line":3661},11,[3663,3668,3672,3677,3682,3687],{"type":616,"tag":3453,"props":3664,"children":3665},{"style":3466},[3666],{"type":621,"value":3667},"result ",{"type":616,"tag":3453,"props":3669,"children":3670},{"style":3509},[3671],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3673,"children":3674},{"style":3466},[3675],{"type":621,"value":3676}," optimizer",{"type":616,"tag":3453,"props":3678,"children":3679},{"style":3509},[3680],{"type":621,"value":3681},".",{"type":616,"tag":3453,"props":3683,"children":3684},{"style":3466},[3685],{"type":621,"value":3686},"run",{"type":616,"tag":3453,"props":3688,"children":3689},{"style":3509},[3690],{"type":621,"value":3522},{"type":616,"tag":3453,"props":3692,"children":3694},{"class":3455,"line":3693},12,[3695,3700,3704,3708,3713,3717],{"type":616,"tag":3453,"props":3696,"children":3697},{"style":3528},[3698],{"type":621,"value":3699},"    skill_path",{"type":616,"tag":3453,"props":3701,"children":3702},{"style":3509},[3703],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3705,"children":3706},{"style":3538},[3707],{"type":621,"value":3541},{"type":616,"tag":3453,"props":3709,"children":3710},{"style":3544},[3711],{"type":621,"value":3712},"skill.md",{"type":616,"tag":3453,"props":3714,"children":3715},{"style":3538},[3716],{"type":621,"value":3541},{"type":616,"tag":3453,"props":3718,"children":3719},{"style":3509},[3720],{"type":621,"value":3721},",\n",{"type":616,"tag":3453,"props":3723,"children":3725},{"class":3455,"line":3724},13,[3726,3731,3735,3740,3744],{"type":616,"tag":3453,"props":3727,"children":3728},{"style":3528},[3729],{"type":621,"value":3730},"    eval_fn",{"type":616,"tag":3453,"props":3732,"children":3733},{"style":3509},[3734],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3736,"children":3737},{"style":3466},[3738],{"type":621,"value":3739},"my_benchmark_eval",{"type":616,"tag":3453,"props":3741,"children":3742},{"style":3509},[3743],{"type":621,"value":3556},{"type":616,"tag":3453,"props":3745,"children":3746},{"style":3495},[3747],{"type":621,"value":3748},"   # 回傳 0-1 分數的自動評估函數\n",{"type":616,"tag":3453,"props":3750,"children":3752},{"class":3455,"line":3751},14,[3753,3758,3762,3767],{"type":616,"tag":3453,"props":3754,"children":3755},{"style":3528},[3756],{"type":621,"value":3757},"    train_tasks",{"type":616,"tag":3453,"props":3759,"children":3760},{"style":3509},[3761],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3763,"children":3764},{"style":3466},[3765],{"type":621,"value":3766},"train_set",{"type":616,"tag":3453,"props":3768,"children":3769},{"style":3509},[3770],{"type":621,"value":3721},{"type":616,"tag":3453,"props":3772,"children":3774},{"class":3455,"line":3773},15,[3775,3780,3784],{"type":616,"tag":3453,"props":3776,"children":3777},{"style":3528},[3778],{"type":621,"value":3779},"    val_tasks",{"type":616,"tag":3453,"props":3781,"children":3782},{"style":3509},[3783],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3785,"children":3786},{"style":3466},[3787],{"type":621,"value":3788},"val_set\n",{"type":616,"tag":3453,"props":3790,"children":3792},{"class":3455,"line":3791},16,[3793],{"type":616,"tag":3453,"props":3794,"children":3795},{"style":3509},[3796],{"type":621,"value":3650},{"type":616,"tag":3453,"props":3798,"children":3800},{"class":3455,"line":3799},17,[3801],{"type":616,"tag":3453,"props":3802,"children":3803},{"emptyLinePlaceholder":3485},[3804],{"type":621,"value":3488},{"type":616,"tag":3453,"props":3806,"children":3808},{"class":3455,"line":3807},18,[3809,3814,3818,3823,3828,3832,3837,3841,3846],{"type":616,"tag":3453,"props":3810,"children":3811},{"style":3466},[3812],{"type":621,"value":3813},"result",{"type":616,"tag":3453,"props":3815,"children":3816},{"style":3509},[3817],{"type":621,"value":3681},{"type":616,"tag":3453,"props":3819,"children":3820},{"style":3466},[3821],{"type":621,"value":3822},"save",{"type":616,"tag":3453,"props":3824,"children":3825},{"style":3509},[3826],{"type":621,"value":3827},"(",{"type":616,"tag":3453,"props":3829,"children":3830},{"style":3538},[3831],{"type":621,"value":3541},{"type":616,"tag":3453,"props":3833,"children":3834},{"style":3544},[3835],{"type":621,"value":3836},"skill_optimized.md",{"type":616,"tag":3453,"props":3838,"children":3839},{"style":3538},[3840],{"type":621,"value":3541},{"type":616,"tag":3453,"props":3842,"children":3843},{"style":3509},[3844],{"type":621,"value":3845},")",{"type":616,"tag":3453,"props":3847,"children":3848},{"style":3495},[3849],{"type":621,"value":3850},"  # 最終產物：一份優化後的 Markdown\n",{"type":616,"tag":660,"props":3852,"children":3854},{"id":3853},"驗測規劃",[3855],{"type":621,"value":3853},{"type":616,"tag":617,"props":3857,"children":3858},{},[3859],{"type":621,"value":3860},"保留 10–20% 的任務集作為 holdout 測試集，分別以原始技能文件與優化後技能文件執行，比較 pass@1 準確率差值。建議同時在第二個目標模型上測試，驗證跨模型遷移性是否成立。",{"type":616,"tag":660,"props":3862,"children":3864},{"id":3863},"常見陷阱",[3865],{"type":621,"value":3863},{"type":616,"tag":862,"props":3867,"children":3868},{},[3869,3874,3879],{"type":616,"tag":866,"props":3870,"children":3871},{},[3872],{"type":621,"value":3873},"評分函數過於寬鬆或不精確，會引導優化器朝錯誤方向走，最終技能文件看似改善但實測下滑",{"type":616,"tag":866,"props":3875,"children":3876},{},[3877],{"type":621,"value":3878},"訓練集與測試集分佈差異過大，導致技能文件過擬合 (overfitting) 至訓練任務而無法泛化",{"type":616,"tag":866,"props":3880,"children":3881},{},[3882],{"type":621,"value":3883},"初始技能文件品質太低，建議優化前先人工撰寫至「合格但未最佳化」的水準作為起點",{"type":616,"tag":660,"props":3885,"children":3887},{"id":3886},"上線檢核清單",[3888],{"type":621,"value":3886},{"type":616,"tag":862,"props":3890,"children":3891},{},[3892,3897,3902],{"type":616,"tag":866,"props":3893,"children":3894},{},[3895],{"type":621,"value":3896},"觀測：優化後 vs. 基線的準確率差值、每個 epoch 被接受的編輯次數",{"type":616,"tag":866,"props":3898,"children":3899},{},[3900],{"type":621,"value":3901},"成本：優化器 API 呼叫費用（rollout 數量 × token 數 × API 單價）",{"type":616,"tag":866,"props":3903,"children":3904},{},[3905],{"type":621,"value":3906},"風險：技能文件版本控管（每個被接受的 epoch 存快照）、評分函數本身的可靠性審計",{"type":616,"tag":3908,"props":3909,"children":3910},"style",{},[3911],{"type":621,"value":3912},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":385,"searchDepth":623,"depth":623,"links":3914},[],{"data":3916,"body":3917,"excerpt":-1,"toc":4269},{"title":385,"description":385},{"type":613,"children":3918},[3919,3923,3928,3932,4196,4200,4205,4209,4243,4247,4265],{"type":616,"tag":660,"props":3920,"children":3921},{"id":3418},[3922],{"type":621,"value":3418},{"type":616,"tag":617,"props":3924,"children":3925},{},[3926],{"type":621,"value":3927},"目前 Gemini-SQL2 尚無公開 API，開發者無法直接調用。若要嘗試類似能力，可透過 Gemini API 自行實作 text-to-SQL scaffolding，或等候 Google 將其整合進 BigQuery Studio 等資料服務後使用。",{"type":616,"tag":660,"props":3929,"children":3930},{"id":3437},[3931],{"type":621,"value":3440},{"type":616,"tag":3442,"props":3933,"children":3935},{"className":3444,"code":3934,"language":3446,"meta":385,"style":385},"import google.generativeai as genai\n\nschema = 'orders(id, customer_id, amount, created_at, status), customers(id, name, region)'\nquestion = '上個季度各地區的總訂單金額是多少？'\n\nmodel = genai.GenerativeModel('gemini-2.0-pro')\nprompt = '根據此 schema：' + schema + '，將問題轉為 PostgreSQL 查詢，只輸出 SQL：' + question\nprint(model.generate_content(prompt).text)\n",[3936],{"type":616,"tag":3449,"props":3937,"children":3938},{"__ignoreMap":385},[3939,3970,3977,4004,4029,4036,4084,4147],{"type":616,"tag":3453,"props":3940,"children":3941},{"class":3455,"line":3456},[3942,3946,3951,3955,3960,3965],{"type":616,"tag":3453,"props":3943,"children":3944},{"style":3460},[3945],{"type":621,"value":3474},{"type":616,"tag":3453,"props":3947,"children":3948},{"style":3466},[3949],{"type":621,"value":3950}," google",{"type":616,"tag":3453,"props":3952,"children":3953},{"style":3509},[3954],{"type":621,"value":3681},{"type":616,"tag":3453,"props":3956,"children":3957},{"style":3466},[3958],{"type":621,"value":3959},"generativeai ",{"type":616,"tag":3453,"props":3961,"children":3962},{"style":3460},[3963],{"type":621,"value":3964},"as",{"type":616,"tag":3453,"props":3966,"children":3967},{"style":3466},[3968],{"type":621,"value":3969}," genai\n",{"type":616,"tag":3453,"props":3971,"children":3972},{"class":3455,"line":623},[3973],{"type":616,"tag":3453,"props":3974,"children":3975},{"emptyLinePlaceholder":3485},[3976],{"type":621,"value":3488},{"type":616,"tag":3453,"props":3978,"children":3979},{"class":3455,"line":3491},[3980,3985,3989,3994,3999],{"type":616,"tag":3453,"props":3981,"children":3982},{"style":3466},[3983],{"type":621,"value":3984},"schema ",{"type":616,"tag":3453,"props":3986,"children":3987},{"style":3509},[3988],{"type":621,"value":3512},{"type":616,"tag":3453,"props":3990,"children":3991},{"style":3538},[3992],{"type":621,"value":3993}," '",{"type":616,"tag":3453,"props":3995,"children":3996},{"style":3544},[3997],{"type":621,"value":3998},"orders(id, customer_id, amount, created_at, status), customers(id, name, region)",{"type":616,"tag":3453,"props":4000,"children":4001},{"style":3538},[4002],{"type":621,"value":4003},"'\n",{"type":616,"tag":3453,"props":4005,"children":4006},{"class":3455,"line":189},[4007,4012,4016,4020,4025],{"type":616,"tag":3453,"props":4008,"children":4009},{"style":3466},[4010],{"type":621,"value":4011},"question ",{"type":616,"tag":3453,"props":4013,"children":4014},{"style":3509},[4015],{"type":621,"value":3512},{"type":616,"tag":3453,"props":4017,"children":4018},{"style":3538},[4019],{"type":621,"value":3993},{"type":616,"tag":3453,"props":4021,"children":4022},{"style":3544},[4023],{"type":621,"value":4024},"上個季度各地區的總訂單金額是多少？",{"type":616,"tag":3453,"props":4026,"children":4027},{"style":3538},[4028],{"type":621,"value":4003},{"type":616,"tag":3453,"props":4030,"children":4031},{"class":3455,"line":93},[4032],{"type":616,"tag":3453,"props":4033,"children":4034},{"emptyLinePlaceholder":3485},[4035],{"type":621,"value":3488},{"type":616,"tag":3453,"props":4037,"children":4038},{"class":3455,"line":3564},[4039,4044,4048,4053,4057,4062,4066,4071,4076,4080],{"type":616,"tag":3453,"props":4040,"children":4041},{"style":3466},[4042],{"type":621,"value":4043},"model ",{"type":616,"tag":3453,"props":4045,"children":4046},{"style":3509},[4047],{"type":621,"value":3512},{"type":616,"tag":3453,"props":4049,"children":4050},{"style":3466},[4051],{"type":621,"value":4052}," genai",{"type":616,"tag":3453,"props":4054,"children":4055},{"style":3509},[4056],{"type":621,"value":3681},{"type":616,"tag":3453,"props":4058,"children":4059},{"style":3466},[4060],{"type":621,"value":4061},"GenerativeModel",{"type":616,"tag":3453,"props":4063,"children":4064},{"style":3509},[4065],{"type":621,"value":3827},{"type":616,"tag":3453,"props":4067,"children":4068},{"style":3538},[4069],{"type":621,"value":4070},"'",{"type":616,"tag":3453,"props":4072,"children":4073},{"style":3544},[4074],{"type":621,"value":4075},"gemini-2.0-pro",{"type":616,"tag":3453,"props":4077,"children":4078},{"style":3538},[4079],{"type":621,"value":4070},{"type":616,"tag":3453,"props":4081,"children":4082},{"style":3509},[4083],{"type":621,"value":3650},{"type":616,"tag":3453,"props":4085,"children":4086},{"class":3455,"line":3598},[4087,4092,4096,4100,4105,4109,4115,4120,4125,4129,4134,4138,4142],{"type":616,"tag":3453,"props":4088,"children":4089},{"style":3466},[4090],{"type":621,"value":4091},"prompt ",{"type":616,"tag":3453,"props":4093,"children":4094},{"style":3509},[4095],{"type":621,"value":3512},{"type":616,"tag":3453,"props":4097,"children":4098},{"style":3538},[4099],{"type":621,"value":3993},{"type":616,"tag":3453,"props":4101,"children":4102},{"style":3544},[4103],{"type":621,"value":4104},"根據此 schema：",{"type":616,"tag":3453,"props":4106,"children":4107},{"style":3538},[4108],{"type":621,"value":4070},{"type":616,"tag":3453,"props":4110,"children":4112},{"style":4111},"--shiki-default:#CB7676",[4113],{"type":621,"value":4114}," +",{"type":616,"tag":3453,"props":4116,"children":4117},{"style":3466},[4118],{"type":621,"value":4119}," schema ",{"type":616,"tag":3453,"props":4121,"children":4122},{"style":4111},[4123],{"type":621,"value":4124},"+",{"type":616,"tag":3453,"props":4126,"children":4127},{"style":3538},[4128],{"type":621,"value":3993},{"type":616,"tag":3453,"props":4130,"children":4131},{"style":3544},[4132],{"type":621,"value":4133},"，將問題轉為 PostgreSQL 查詢，只輸出 SQL：",{"type":616,"tag":3453,"props":4135,"children":4136},{"style":3538},[4137],{"type":621,"value":4070},{"type":616,"tag":3453,"props":4139,"children":4140},{"style":4111},[4141],{"type":621,"value":4114},{"type":616,"tag":3453,"props":4143,"children":4144},{"style":3466},[4145],{"type":621,"value":4146}," question\n",{"type":616,"tag":3453,"props":4148,"children":4149},{"class":3455,"line":3626},[4150,4156,4160,4165,4169,4174,4178,4183,4188,4192],{"type":616,"tag":3453,"props":4151,"children":4153},{"style":4152},"--shiki-default:#B8A965",[4154],{"type":621,"value":4155},"print",{"type":616,"tag":3453,"props":4157,"children":4158},{"style":3509},[4159],{"type":621,"value":3827},{"type":616,"tag":3453,"props":4161,"children":4162},{"style":3466},[4163],{"type":621,"value":4164},"model",{"type":616,"tag":3453,"props":4166,"children":4167},{"style":3509},[4168],{"type":621,"value":3681},{"type":616,"tag":3453,"props":4170,"children":4171},{"style":3466},[4172],{"type":621,"value":4173},"generate_content",{"type":616,"tag":3453,"props":4175,"children":4176},{"style":3509},[4177],{"type":621,"value":3827},{"type":616,"tag":3453,"props":4179,"children":4180},{"style":3466},[4181],{"type":621,"value":4182},"prompt",{"type":616,"tag":3453,"props":4184,"children":4185},{"style":3509},[4186],{"type":621,"value":4187},").",{"type":616,"tag":3453,"props":4189,"children":4190},{"style":3466},[4191],{"type":621,"value":621},{"type":616,"tag":3453,"props":4193,"children":4194},{"style":3509},[4195],{"type":621,"value":3650},{"type":616,"tag":660,"props":4197,"children":4198},{"id":3853},[4199],{"type":621,"value":3853},{"type":616,"tag":617,"props":4201,"children":4202},{},[4203],{"type":621,"value":4204},"在生產環境導入前，建議建立「黃金查詢集」 (golden query set) ：從歷史查詢中挑選 100-200 個具代表性的問題，配上人工驗證過的正確 SQL 與預期結果，用於持續評測模型升版後的準確率變化。",{"type":616,"tag":660,"props":4206,"children":4207},{"id":3863},[4208],{"type":621,"value":3863},{"type":616,"tag":862,"props":4210,"children":4211},{},[4212,4233,4238],{"type":616,"tag":866,"props":4213,"children":4214},{},[4215,4217,4223,4225,4231],{"type":621,"value":4216},"模型對 schema 命名慣例極度敏感，",{"type":616,"tag":3449,"props":4218,"children":4220},{"className":4219},[],[4221],{"type":621,"value":4222},"tbl_order_detail",{"type":621,"value":4224}," 與 ",{"type":616,"tag":3449,"props":4226,"children":4228},{"className":4227},[],[4229],{"type":621,"value":4230},"order_items",{"type":621,"value":4232}," 可能導致完全不同的查詢路徑",{"type":616,"tag":866,"props":4234,"children":4235},{},[4236],{"type":621,"value":4237},"日期函數因資料庫方言差異 (PostgreSQL vs MySQL vs BigQuery) 容易出錯，需在 prompt 中明確指定目標資料庫",{"type":616,"tag":866,"props":4239,"children":4240},{},[4241],{"type":621,"value":4242},"80% 的 BIRD 準確率基於相對乾淨的測試集；真實企業遺留系統的複雜度可能使實際準確率顯著下降",{"type":616,"tag":660,"props":4244,"children":4245},{"id":3886},[4246],{"type":621,"value":3886},{"type":616,"tag":862,"props":4248,"children":4249},{},[4250,4255,4260],{"type":616,"tag":866,"props":4251,"children":4252},{},[4253],{"type":621,"value":4254},"觀測：記錄每次查詢的執行結果，標記空結果與錯誤，定期計算黃金查詢集準確率",{"type":616,"tag":866,"props":4256,"children":4257},{},[4258],{"type":621,"value":4259},"成本：LLM API 調用費用 + schema 上下文 token 消耗（複雜 schema 每次查詢可能消耗數千 token）",{"type":616,"tag":866,"props":4261,"children":4262},{},[4263],{"type":621,"value":4264},"風險：在資料庫前加入唯讀權限隔離層，避免誤生成 DELETE 或 UPDATE 語句",{"type":616,"tag":3908,"props":4266,"children":4267},{},[4268],{"type":621,"value":3912},{"title":385,"searchDepth":623,"depth":623,"links":4270},[]]