[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"report-2026-05-25":3,"AGyAQlH4ro":488,"qEsoNpU89Y":503,"XDdyrVsyju":513,"AZLCByd8D7":523,"bK2ioQQnkx":533,"MK7bgT7Oif":643,"XuWJsCmDky":654,"A6XA9C7c4p":670,"iYAP4P5oiy":706,"yS47mEGbdb":743,"LJ2x0tuu8O":868,"egBAen04Ue":932,"FbeOtOzvLV":953,"Z6XyALGzYI":974,"qehFBwe7Gl":984,"6PLNBWifbZ":994,"rSw6jBunKj":1004,"GKlE9gYxfR":1014,"ZXLgdieh2N":1024,"OwqwAk6qb3":1034,"0sGZeBISHm":1249,"L5oVfudNsa":1275,"0cWUX205cN":1301,"6vcdJDw5ZA":1345,"xMiovRQa8r":1405,"WrMMUkUBnO":1451,"uVyFMqMtWQ":1461,"FtCcUv5dEZ":1471,"jBVddswOZn":1481,"LzW3ncuOlc":1491,"oUNuDZgMzc":1501,"wQsT4wIpe9":1511,"aWwgD8IMqi":1689,"3e1WijzTuH":1700,"xyJbCm1bNo":1716,"LiHPEWwZ2C":1747,"ZdAlxZgFTP":1786,"K6swyINkWM":1901,"Udt3CRTVEK":1938,"mPauFvBvA2":1959,"cDKwiWphZN":1980,"ljGPcVWmLu":1990,"N6pWpVM2vO":2000,"Rc61NKzh1P":2010,"l0qqvKVxIk":2073,"XwsLDy5lwy":2083,"ALzRHiAKoH":2093,"GtSV0aytYM":2146,"LqEHQL62Hf":2162,"16iGfqvZHQ":2178,"gLqUlthOjY":2231,"VdHwUtHQxI":2252,"myXERvXwRU":2273,"mppdFHKD2R":2318,"MEVjvLHqY4":2365,"mSpTwpL1hN":2385,"MhcvNS2SAa":2395,"h8GFt9pPBc":2442,"V3R7ToPmiD":2452,"EzhOgq6DWi":2462,"0JO2SUXgdj":2481,"iV40YUvUEY":2561,"6NvYmkKhyd":2577,"Zoi6KrtKKu":2593,"InCyDEcUQc":2626,"9iykKBFKu9":2636,"VJqxMXCDyc":2646,"bhxzclWW2a":2733,"QjtwVcky5W":2767,"Do532QHumS":2783,"xp73kBp8l4":2812,"vBoSxrVrUs":2894,"eEEA9M7kE7":2910,"rg2Nz8Vxu2":3074},{"report":4,"adjacent":485},{"version":5,"date":6,"title":7,"sources":8,"hook":16,"deepDives":17,"quickBites":237,"communityOverview":470,"dailyActions":471,"outro":484},"20260216.0","2026-05-25","AI 趨勢日報：2026-05-25",[9,10,11,12,13,14,15],"academic","anthropic","community","deepseek","github","google","microsoft","從 AI 自動發現演算法、Cache-First 節費架構到 agent-native 終端機，AI Coding Agent 生態在一天內完成了從模型到工具鏈的全棧進化。",[18,103,162],{"category":19,"source":12,"title":20,"subtitle":21,"publishDate":6,"tier1Source":22,"supplementSources":25,"tldr":42,"context":54,"mechanics":55,"benchmark":56,"useCases":57,"engineerLens":66,"businessLens":67,"devilsAdvocate":68,"community":71,"hypeScore":90,"hypeMax":91,"adoptionAdvice":92,"actionItems":93},"tech","DeepSeek Reasonix：原生 Coding Agent 以高快取策略壓低推論成本","單日快取命中率 99.82%，DeepSeek 深度耦合設計讓 AI 編程成本壓進 $0.05",{"name":23,"url":24},"DeepSeek-Reasonix 官方介紹頁","https://esengine.github.io/DeepSeek-Reasonix/",[26,30,34,38],{"name":27,"url":28,"detail":29},"DeepSeek-Reasonix GitHub","https://github.com/esengine/DeepSeek-Reasonix","原始碼、安裝說明與架構設計文件",{"name":31,"url":32,"detail":33},"HN 討論串 #48256953","https://news.ycombinator.com/item?id=48256953","開發者社群對 Reasonix 的技術評析與實測反饋",{"name":35,"url":36,"detail":37},"DeepSeek API 官方文件：Reasonix 整合","https://api-docs.deepseek.com/quick_start/agent_integrations/reasonix","DeepSeek 官方認可的整合項目文件",{"name":39,"url":40,"detail":41},"PyShine 技術解析","https://pyshine.com/DeepSeek-Reasonix-DeepSeek-Native-AI-Coding-Agent-Terminal/","第三方深度技術解析，涵蓋四階段 tool-call 修復管線",{"tagline":43,"points":44},"單日快取命中率 99.82%，DeepSeek 原生 Agent 把推論成本壓進 $0.05",[45,48,51],{"label":46,"text":47},"技術","Cache-First Loop 三層架構透過 byte-stable prefix 消除快取失效，四階段 Tool-Call 修復管線專攻 DeepSeek 已知失效模式。",{"label":49,"text":50},"成本","真實測試顯示單日成本從 $61 降至 $12，Flash-First 策略讓多數任務控制在 $0.05 以下，v4-flash 為預設模型。",{"label":52,"text":53},"落地","npm 安裝即用，已納入 DeepSeek 官方 API 整合文件，開源授權，但僅支援 DeepSeek API，不支援多模型切換。","#### 章節一：Reasonix 是什麼？DeepSeek 原生 Coding Agent 的架構定位\n\nDeepSeek-Reasonix 是一款開源終端機 AI 編程 Agent，以 TypeScript 5.6+ 撰寫，搭配 Commander.js 與 Ink 5(React 18) 構建互動式終端 UI，透過 npm 安裝即可使用，需搭配 DeepSeek API key。\n\n它的定位與 Claude Code、OpenCode 等通用 Agent 框架截然不同——Reasonix 刻意捨棄多模型相容性，換取對 DeepSeek prefix-cache 機制的深度耦合，將「最大化快取命中率」設定為首要設計目標。\n\n值得注意的是，此專案為獨立開源第三方作品，與 DeepSeek 官方並無隸屬關係，但已獲 DeepSeek API 文件認可，列為官方整合項目，賦予其一定程度的信任背書。\n\n#### 章節二：高快取命中率的技術策略與成本優勢\n\nReasix 的核心是「Cache-First Loop」三層架構：不可變前綴（系統 prompt 與 tool spec 永遠置頂）、append-only 對話記錄（僅允許追加，禁止修改），以及揮發性推理暫存區（每輪推理後清空）。\n\n> **名詞解釋**\n> prefix-cache：大型語言模型推論時，若輸入的前段 token 序列與先前請求完全相同，可直接復用已計算的 KV cache，大幅降低運算成本；快取費率通常為正常費率的 10% 左右。\n\n傳統 Agent 框架常因 timestamp injection 或 tool list reordering 等操作破壞 prefix 穩定性，導致快取失效。Reasonix 透過強制 byte-stable prefix，從架構層面杜絕這個問題。\n\n真實用戶測試 (2026-05-01) 結果清晰：單日處理 4.35 億輸入 tokens，prefix-cache 命中率達 99.82%，成本從 $61 壓縮至 $12。Flash-First 策略以 v4-flash 為預設模型，多數任務在 $0.05 以下完成；遇到連續三次 struggle event 才自動升級至 v4-pro，避免不必要的費用膨脹。\n\n#### 章節三：與 Claude Code、Cursor 等競品的實測比較\n\nHN 社群的實測數據顯示，使用 OpenCode + DeepSeek API 的用戶同樣達到 97.27% 的快取命中率（472,971,520 tokens 命中，僅 13,299,013 miss），說明高快取命中並非 Reasonix 的獨家能力。這也印證了 HN 用戶 ricardobeat 的質疑：「這不就是所有模型和 coding harness 的運作方式嗎？」\n\n然而 Reasonix 的真正差異化在於四階段 Tool-Call 修復管線 (flatten→scavenge→truncation→storm)——這是針對 DeepSeek 特定失效模式的專屬解法，通用框架無法複製。相較於 Claude Code 或 Cursor 的廣泛多模型支援，Reasonix 的深度耦合設計在 DeepSeek API 上表現更穩定，但代價是完全鎖定單一模型提供商。\n\n另一個值得關注的背景是：Reasonix 的發布時機恰好在 DeepSeek 宣布 V4 Pro 折扣永久化之後，這讓成本敘事更具說服力，但也讓部分社群成員對行銷節奏感到存疑。\n\n#### 章節四：開發者社群的初步反饋與適用場景評估\n\nHN 社群對 Reasonix 的反應呈現明顯分歧。技術層面，embedding-shape 等用戶的實測印證了 append-only loop 的實效；但 fouric 指出 DeepSeek v4 Pro 存在 prompt compliance 問題，模型有時忽略指令，這對生產環境是潛在風險。\n\nReasix 最適合三類用戶：已深度使用 DeepSeek API 且不需多模型切換者、對 token 成本高度敏感的個人開發者，以及大型 codebase 的長時間 refactor 工作流（session 越長快取收益越顯著）。\n\n若需要多模型彈性、對 prompt 指令遵循穩定性有嚴格要求，或在歐美企業合規環境中有資料主權疑慮，則應謹慎評估是否適合導入。","Reasonix 的技術核心是一套圍繞快取穩定性設計的推論循環，透過三個互相配合的機制，讓 DeepSeek prefix-cache 在長時間 coding session 中持續有效。\n\n#### 機制 1：Cache-First Loop 三層架構\n\n系統將上下文切分為三層：不可變前綴（系統 prompt + tool spec，永遠置頂）、append-only 對話記錄（僅允許追加，禁止修改）、揮發性推理暫存區（每輪推理後清空）。\n\n這個設計確保送入模型的 prefix 始終 byte-level 穩定，讓 DeepSeek 快取機制可以最大化命中。常見 Agent 框架的 timestamp injection 或動態 tool list reordering 在這裡被從架構層面完全排除。\n\n#### 機制 2：四階段 Tool-Call 修復管線\n\n針對 DeepSeek 模型已知的 tool call 失效模式，Reasonix 設計了四個依序執行的修復步驟：\n\n1. flatten：簡化複雜 schema，降低模型誤解機率\n2. scavenge：從推理暫存區救回遺漏的 tool call\n3. truncation：修復不完整的 JSON 輸出\n4. storm：防止重複呼叫同一個 tool\n\n#### 機制 3：Flash-First 成本分級策略\n\n預設使用 v4-flash 模型（成本最低），tool 回傳結果限制在 3,000 tokens 以防 context 爆炸。當連續三次出現 struggle event（推理失敗或 tool call 異常），系統自動升級至 v4-pro；用戶也可透過 `/pro` 指令手動強制升級。\n\n> **白話比喻**\n> 把 Reasonix 想像成一個「只記帳不塗改」的出納員——每筆交易只能往帳本尾端追加，不能翻回去修改舊頁。這樣銀行的快取系統 (prefix-cache) 永遠知道前面的頁數是對的，每次只需驗算新增的部分，大幅節省重複計算的成本。","#### 真實使用者測試 (2026-05-01)\n\n- 單日輸入 tokens：4.35 億\n- prefix-cache 命中率：99.82%\n- 成本：從 $61 降至 $12（v4-flash 模型）\n- 多數任務費用：$0.05 以下\n\n#### 對比測試：OpenCode + DeepSeek API\n\n- 命中 tokens：472,971,520\n- 未命中 tokens：13,299,013\n- 實測命中率：97.27%\n\n說明：97%+ 快取命中率並非 Reasonix 獨有；其差異化優勢在於四階段 tool-call 修復管線對 DeepSeek 特定失效模式的專屬處理。長 session 場景下，Reasonix 的架構設計讓命中率更穩定趨近上限。",{"recommended":58,"avoid":62},[59,60,61],"大型 codebase 長時間 refactor（session 越長快取收益越顯著）","token 成本敏感的個人開發者或小型團隊","已深度使用 DeepSeek API 且不需多模型切換的工作流",[63,64,65],"需要同時使用多個 LLM 提供商的企業環境","對 prompt 指令遵循穩定性要求極高的生產系統","歐美企業合規環境中對 DeepSeek API 有資料主權疑慮者","#### 環境需求\n\nNode.js + npm 環境，TypeScript 5.6+，需備有 DeepSeek API key。終端 UI 以 Ink 5(React 18) 渲染，在大多數現代終端環境下可直接執行，無需額外設定。\n\n#### 最小 PoC\n\n```bash\nnpm install -g deepseek-reasonix\nexport DEEPSEEK_API_KEY=your_key_here\ndeepseek-reasonix\n```\n\n#### 驗測規劃\n\n執行後觀察終端顯示的 cache hit/miss 統計數字，確認前幾輪對話後命中率穩定上升至 95% 以上。可搭配 DeepSeek API dashboard 對照 token 用量，驗證快取費率折扣是否正確反映在帳單上。\n\n#### 常見陷阱\n\n- 快取有效性依賴 DeepSeek API 後端的 prefix-cache 實作；若透過 OpenRouter 等路由服務存取，不同路由節點可能導致快取無效\n- 強制使用 `/pro` 指令後，v4-pro 成本顯著高於 v4-flash，大型任務需注意費用上限\n- DeepSeek v4 Pro 的 prompt compliance 在社群有回報問題，對指令遵循度要求高的任務需預留測試時間\n\n#### 上線檢核清單\n\n- 觀測：DeepSeek API dashboard cache hit rate，目標 > 95%；struggle event 觸發頻率\n- 成本：每日 v4-flash vs v4-pro 費用比例，確認 flash 為主要模型\n- 風險：v4-pro 自動升級觸發頻率，設定每日費用預警閾值","#### 競爭版圖\n\n- **直接競品**：Claude Code（Anthropic 原生 Agent，多模型支援，月費訂閱）、OpenCode（開源，支援 DeepSeek 等多家 API）、Cursor（IDE 整合，月費訂閱制）\n- **間接競品**：通用 LLM 框架（LangChain、LlamaIndex）、各家 API 原生 playground\n\n#### 護城河類型\n\n- **工程護城河**：深度針對 DeepSeek prefix-cache 機制最佳化，四階段 tool-call 修復管線是針對 DeepSeek 特定失效模式的專屬解法，通用框架難以完整複製\n- **生態護城河**：DeepSeek 官方 API 文件背書，降低新用戶信任門檻；與 DeepSeek V4 Pro 永久折扣政策形成協同效應\n\n#### 定價策略\n\nReasix 本身免費開源，收益模型依附於 DeepSeek API 使用量。v4-flash 極低單價加上高快取命中率，使整體使用成本遠低於 Anthropic 或 OpenAI 同級方案。DeepSeek V4 Pro 永久折扣的宣布進一步強化了此成本敘事。\n\n#### 企業導入阻力\n\n- 單一供應商鎖定 (DeepSeek only) 在企業多雲合規環境中是重大障礙\n- DeepSeek API 的資料主權與隱私合規問題，特別是歐美受 GDPR 規範的市場\n- DeepSeek v4 Pro prompt compliance 穩定性疑慮尚待大規模生產環境驗證\n\n#### 第二序影響\n\n- 若 Reasonix 驗證「深度快取耦合」設計路線，可能促使其他 API 提供商推出類似原生 Agent 工具\n- DeepSeek 低價策略配合高效能開源工具，可能加速非美企業技術棧向 DeepSeek 生態遷移\n\n#### 判決：個人開發者值得一試，企業導入需審慎評估供應商鎖定風險\n\nReasix 的 Cache-First Loop 設計理念清晰，真實測試數據具說服力，成本節省效果真實存在。但單一供應商鎖定、DeepSeek 模型指令遵循穩定性疑慮，以及第三方性質帶來的長期維護不確定性，使其更適合個人開發者試用，而非企業生產環境的優先選擇。",[69,70],"快取命中率的優勢完全依賴 DeepSeek API 後端實作的穩定性，任何服務端調整都可能讓現有最佳化瞬間失效，而用戶對此毫無控制能力。","深度耦合單一供應商在 AI 模型快速演進的市場中是高風險賭注——若 DeepSeek API 定價、服務條款或資料主權政策改變，整個工作流將面臨高昂的重建成本。",[72,76,80,84,87],{"platform":73,"user":74,"quote":75},"Hacker News","HN 用戶 chillfox","不同服務對快取 key 的支援差異極大，有些服務只允許極少數快取 key，所以如果你修改了近期訊息，快取不一定有效。快取並非逐條訊息生效，而是以大塊前綴為單位——這對我來說是很出乎意料的設計。",{"platform":77,"user":78,"quote":79},"X","@teortaxesTex","這才是我支持的 harness 設計！專為節省 API 費用而生，全面追求快取命中，甚至已有 GUI（封裝版）了。",{"platform":81,"user":82,"quote":83},"Bluesky","itstarlow.bsky.social（Tarlow，1 讚）","可惜這不是 DeepSeek 官方做的，而是第三方 Reasonix 專案，有點可惜。官網聲明：獨立開源專案，與 DeepSeek 無隸屬關係。",{"platform":77,"user":85,"quote":86},"@Dinosn（安全研究員暨科技策展人）","DeepSeek 原生終端 AI Coding Agent，專為 prefix-cache 穩定性而設計——讓它持續運行吧。",{"platform":81,"user":88,"quote":89},"todaystopainews.bsky.social（Today's Top AI News，3 讚）","DeepSeek Reasonix：DeepSeek 原生 Coding Agent，以高快取率與低成本為核心設計目標。",3,5,"值得一試",[94,97,100],{"type":95,"text":96},"Try","npm install -g deepseek-reasonix，在非關鍵個人專案上跑一個下午的 refactor session，觀察 cache hit rate 統計數字是否穩定在 95% 以上",{"type":98,"text":99},"Build","參考 Cache-First Loop 的三層架構設計（不可變前綴 + append-only + 揮發性暫存區），評估自己現有 Agent 工作流是否有類似的快取失效問題可以改善",{"type":101,"text":102},"Watch","追蹤 DeepSeek v4 Pro prompt compliance 問題的後續社群回報，以及 Reasonix 對 DeepSeek API 定價或服務變動的應對策略",{"category":104,"source":11,"title":105,"subtitle":106,"publishDate":6,"tier1Source":107,"supplementSources":110,"tldr":111,"context":123,"perspectives":124,"practicalImplications":136,"socialDimension":137,"devilsAdvocate":138,"community":141,"hypeScore":90,"hypeMax":91,"adoptionAdvice":154,"actionItems":155},"discourse","不玩角色扮演也需要無審查模型嗎？安全研究員與急救場景的真實需求","從資安研究到急救知識，過度對齊的 LLM 正在背叛它最需要的用戶",{"name":108,"url":109},"Reddit r/LocalLLaMA","https://redlib.perennialte.ch/r/LocalLLaMA/comments/1tlzvfs/is_there_any_reason_for_an_uncensored_model_if/",[],{"tagline":112,"points":113},"當 AI 審查連急救知識都擋下，「安全」二字究竟在保護誰？",[114,117,120],{"label":115,"text":116},"爭議","無審查 LLM 的需求遠超角色扮演：資安研究、急救場景、學術教育都需要模型在技術細節上不打折扣，而現有對齊機制在這些場合系統性失職，Red Team AI Benchmark 對齊版得分直接歸零。",{"label":118,"text":119},"實務","消融技術已讓 Hugging Face 上超過 11,000 個無審查模型流通，部分累計安裝量破 1,900 萬次；Dolphin 系列等微調路線則讓使用者自行控制安全邊界。",{"label":121,"text":122},"趨勢","核心挑戰不是「要不要審查」，而是如何設計精準識別惡意意圖的機制——目前的 RLHF 安全訓練方法仍無法區分合法研究者與惡意行為者，距理想目標有顯著差距。","#### 章節一：為什麼資安研究員需要無審查模型\n\n資安研究員是無審查 LLM 最具說服力的非角色扮演用戶群。安全研究的核心邏輯與惡意駭客幾乎一致——差別只在執行者的立場。\n\nu/corysama 所言精準道出核心：「根據我對資安研究的了解，它做的事情與惡意駭客完全相同，只是由好人先行找漏洞，搶在壞人之前。」這句話直指資安研究對「雙用途知識」的根本依賴。\n\n2025 年 11 月的 Red Team AI Benchmark 以 12 道覆蓋 ADCS 利用、NTLM Relay、EDR Unhooking、AMSI／ETW 繞過等當代攻擊技術的問題評估多款模型。未對齊基礎模型得分高達 92%，對齊版模型（如 Qwen3-4B-Thinking）得分為 0%。\n\n> **名詞解釋**\n> EDR Unhooking：繞過端點偵測與回應防護層的技術，攻擊者用它移除安全工具對系統函數的監控鉤子。\n\n分數低於 60% 的模型被評為「不適合用於滲透測試工作」。對齊版模型在碰到具體攻擊技術時直接拒絕生成代碼，資安研究員在最需要工具協助時反而被拒之門外。\n\nu/dangered 指出另一個反諷：審查機制選擇性地阻擋理論知識，卻放行執行 `rm -rf` 這類更高實際破壞力的操作——這種不一致讓資安研究員尤其沮喪。\n\n#### 章節二：審查過度的代價——急救知識與化學常識被封鎖的荒謬案例\n\n「過度拒絕」 (Over-refusal) 已成為 LLM 對齊研究的正式術語。RLHF 訓練讓模型對「聽起來危險」的語境一律拒絕，而不區分真實危害與合法教育需求。\n\n> **名詞解釋**\n> RLHF(Reinforcement Learning from Human Feedback) ：透過人類評分員標注偏好來微調語言模型行為的訓練方法，是當前主流對齊技術的核心組件。\n\nu/silverud 提出直觀測試標準：「問模型緊急情況下如何淨化水，或如何處理傷口。如果它回答得好，你不需要無審查版本。如果它的表現像需要法律團隊審查才能開口……」這個標準揭示了過度審查在緊急場景中的具體代價。\n\narXiv：2505.18325v3 提出 RASS 框架，分析安全決策邊界為何過度寬泛。SafeConstellations（arXiv：2508.11290）提出任務感知表示引導來緩解過度拒絕；Beyond Over-Refusal（arXiv：2510.08158）則研究場景診斷與後驗緩解方法。\n\nOpenAI 在 GPT-5 引入「safe-completions」訓練，隱含承認過去的拒絕機制無法妥善處理雙用途查詢。「引爆煙火所需最低能量」這類問題，背後可能是合法的工程研究，對齊版模型卻往往一律拒絕。\n\n過度審查的代價不僅是用戶體驗，更影響緊急場合的實用性。當用戶在野外或災害現場時，模型在提供急救知識前先表現出「需要法律審查」的姿態，實際上是對使用者的一種背叛。\n\n#### 章節三：開源社群的無審查微調生態現況\n\n無審查 LLM 在開源社群已形成規模化生態。2025 年 8 月的學術論文（arXiv：2508.12622）在 Hugging Face 上識別出超過 11,000 個無審查 LLM，部分模型安裝量超過 1,900 萬次。\n\n第一條技術路線是**微調路線 (Fine-tuning)**，代表是 Eric Hartford 的 Dolphin 系列。Hartford 的設計哲學是：「無對齊基礎模型是構建可組合對齊的前提。沒有無對齊底層，就沒有東西可以在上面疊加你的個人化對齊 LoRA。」\n\n> **名詞解釋**\n> LoRA(Low-Rank Adaptation) ：一種參數高效的模型微調方法，透過注入低秩矩陣來修改行為，無需重新訓練全部參數。\n\n第二條是**消融路線 (Abliteration)**，由 FailSpy 開創、Maxime Labonne 於 2024 年 6 月發表技術說明。原理基於研究發現：拒絕行為由模型殘差流中一個特定方向所中介。具體做法是對模型權重進行正交化，使模型在結構上無法表示該「拒絕方向」。\n\n消融後模型保留全部原始智能，但喪失拒絕機制，後續可搭配 DPO 微調修復效能損失。截至 2026 年 5 月，可追蹤的主流無審查開源模型已超過 35 個，參數規模從 1B 到 405B。\n\n#### 章節四：模型審查光譜——從完全開放到過度保護的取捨\n\n無審查並非非黑即白的概念，而是一個光譜。主要維度包括：技術知識限制、創作內容限制、政治內容限制，以及對「雙用途」知識的判斷寬鬆度。\n\nEric Hartford 提出了一個根本性框架：模型的「對齊」本質上是訓練數據中嵌入的偏見，而非中立的安全機制。這引出一個認識論問題：誰有權決定什麼是「安全的知識」？\n\n從用戶社群的實際反饋看，多數需要無審查模型的使用者並非追求惡意內容，而是需要模型在以下場景不打折扣地協助：\n\n- 資安研究（漏洞分析、滲透測試）\n- 創意寫作（反派角色、黑暗題材小說）\n- 學術與技術教育（化學、生物、法醫等）\n- 緊急場合知識獲取（急救、生存技能）\n\n光譜的另一端，arXiv：2508.12622 顯示無審查模型已被整合進「數百個惡意應用」，地下論壇正積極分享構建低成本惡意 LLM 服務的腳本。\n\n對齊研究的核心挑戰因此不是「要不要審查」，而是如何設計出既能讓合法用戶不受阻礙、又能有效阻止實際惡意行為的精準機制。arXiv：2510.07775 指出強化拒絕訓練可能影響事實準確性；消融技術亦已證明安全微調的穩健性存疑——距離真正精準的安全機制，學術界與產業界都還有一段路要走。",[125,129,133],{"label":126,"color":127,"markdown":128},"正方立場","green","無審查模型在多個合法領域有不可替代的價值。\n\n資安研究、急救知識、學術教育、創意寫作是最常被引用的四大合法場景。資安研究員需要與惡意攻擊者使用相同的知識庫，且必須在技術細節上不受限制——Red Team AI Benchmark 清楚顯示，對齊版模型在此場景中完全失去實用性（得分 0%）。\n\n從個人自主角度，Hartford 的論點「這是我的電腦，它應該照我說的做」代表重要的使用者權利立場：模型的對齊本質上是訓練者的偏見植入，而非客觀的安全保障。當這種偏見系統性地阻擋合法知識獲取時，它已從保護工具變成了控制工具。\n\n緊急場合的實用性更凸顯這個矛盾：一個在野外急救場景中需要「法律審查」才肯開口的模型，在最需要它的時候成為負擔而非助力。",{"label":130,"color":131,"markdown":132},"反方立場","red","無審查模型的風險是可量化且已實際發生的。\n\narXiv：2508.12622 直接呈現問題規模：無審查模型已被整合進數百個惡意應用，地下論壇正積極分享構建低成本惡意 LLM 服務的腳本。當消融技術已能讓任何人在幾小時內移除模型安全機制，「負責任的合法用戶才會使用」的假設就站不住腳。\n\n資安研究員的合法需求不足以成為廣泛開放的理由：他們只佔潛在用戶的一小部分，設計針對性授權通道比向所有人開放更符合比例原則。部分「合法需求」可透過分級存取機制滿足，不需完全移除安全層。\n\n消融技術的普及意味著安全微調的威懾效果遠低於預期——但這是強化對齊研究的理由，而非放棄的理由。",{"label":134,"markdown":135},"中立／務實觀點","「要不要審查」是錯誤的框架——真正的問題是審查的精準度。\n\n當前對齊技術（主要基於 RLHF）的根本問題是審查邊界過於粗糙：它無法區分「問如何製作炸彈的恐怖份子」與「問爆炸物化學的工程師」，結果是合法用戶被過濾、惡意用戶透過提示詞工程繞過。\n\n務實路徑不是選擇光譜的任一端，而是：\n\n- 在已知高需求場景（資安研究、醫療、法律）建立身份驗證存取層\n- 投資精準對齊研究（如 RASS、Task-Aware Representation Steering）取代粗糙的拒絕訓練\n- 對急救、基礎化學等明確合法知識降低拒絕閾值\n\n消融技術的廣泛流通已證明：粗糙的安全機制既擋不住有動機的惡意用戶，又系統性地傷害合法用戶。在精準對齊技術成熟之前，這個矛盾不會消失。","#### 對開發者的影響\n\n使用商業 API 的開發者面臨現實選擇：對齊版 API 提供品質保證但功能受限；本地部署無審查模型提供完整能力但引入合規風險與維運成本。\n\n資安工具、醫療助理、法律研究平台的開發者需要特別評估：現有模型的拒絕邊界是否系統性地阻礙核心使用案例？如果是，Dolphin 系列或消融模型值得在受控環境中評估。\n\n#### 對團隊／組織的影響\n\n企業導入 LLM 時，需要在商業 API（合規但受限）與本地部署開源模型（靈活但需自行把關）之間做出架構決策。對高度規範行業，合規考量往往主導選擇。\n\n資安團隊面臨更直接的矛盾：滲透測試需要高技術精準度的 AI 輔助，但企業 IT 政策可能禁止使用未對齊模型。這個政策空白需要 CISO 層級的明確決策。\n\n#### 短期行動建議\n\n- 以 u/silverud 的「急救測試」評估你目前使用的模型：問一個緊急場景的實用問題，看模型是否回答得當\n- 若你的工作需要技術安全知識，在受控本地環境中評估 Dolphin 3 或 abliterated Qwen3\n- 持續追蹤 RASS、SafeConstellations 等精準對齊研究的進展——這些技術若成熟，可能同時解決過度拒絕與惡意使用問題","#### 產業結構變化\n\n無審查 LLM 生態的規模（11,000+ 模型、1,900 萬+ 安裝量）顯示，用戶對當前對齊機制的不滿已形成顯著市場需求。這個需求目前主要由開源社群透過消融、微調技術自行滿足，商業模型廠商尚未正面回應。\n\n#### 倫理邊界\n\n爭議的核心倫理問題是：誰有資格定義「安全知識」的邊界？商業 LLM 廠商透過訓練數據的選擇，實際上行使了一種知識守門人的角色，但這種角色從未經過公開授權或民主辯論。\n\n當這種守門行為系統性地阻礙急救、資安、科學教育等具明確社會正當性的知識流通時，它從企業風險管理決策演變為一個涉及資訊公平存取的公共政策問題。\n\n#### 長期趨勢預測\n\n精準對齊技術（如 Task-Aware Representation Steering、RASS 框架）若取得突破，有機會在未來 2-3 年內使「粗糙拒絕 vs. 完全開放」的二元論變得過時。更可能的方向是分層存取架構：一般用戶使用保守版本，驗證身份的研究者存取技術完整版本。\n\n然而，消融技術的持續普及表明，任何中心化的存取控制機制最終都可在本地被繞過——這將使監管重心從「模型輸出控制」轉向「使用行為責任」。",[139,140],"資安研究員的「合法需求」論述可能被過度美化：大多數真正的紅隊演練使用受控環境與授權工具，而非依賴 AI 自動生成攻擊代碼。無審查模型最大的實際受益者可能不是專業資安人員，而是技術入門者。","「急救知識被封鎖」的荒謬案例可能反映的是特定模型在特定版本的過度調整，而非對齊技術的系統性缺陷——OpenAI、Anthropic 等廠商持續在校正這些邊界，未來的對齊模型可能已解決大多數過度拒絕問題，無需訴諸無審查版本。",[142,145,148,151],{"platform":108,"user":143,"quote":144},"u/corysama","根據我對資安研究的了解，它做的事情與惡意駭客完全相同，只是由好人先行找漏洞，搶在壞人之前。",{"platform":108,"user":146,"quote":147},"u/dangered","這些模型花了大量時間審查這些廢話，但在排查問題時卻不審查執行 `rm -rf` 的代碼端。",{"platform":108,"user":149,"quote":150},"u/silverud","問模型緊急情況下如何淨化水，或如何處理傷口。如果它回答得好，你不需要無審查版本。如果它的表現像需要法律團隊審查才能開口……",{"platform":77,"user":152,"quote":153},"@hardmaru（David Ha，前 Google Brain 研究主任、Stability AI 研究主任）","如果你在找一個沒有任何強制「對齊」或「說教式」審查的聊天 LLM，我推薦今天剛發布的 WizardLM-13B-Uncensored。我整個早上都在試用。這是我目前最喜歡的開源聊天模型。","追整體趨勢",[156,158,160],{"type":95,"text":157},"以「緊急情況下如何淨化水」或「如何處理開放性傷口」測試你目前使用的主力模型，評估其在實用急救場景中的表現，判斷你的工作流程是否需要無審查替代方案。",{"type":98,"text":159},"若你在開發資安或醫療輔助工具，在本地隔離環境中評估 Dolphin 3，比對其與對齊版模型在核心任務上的實際差距，再決定架構選擇。",{"type":101,"text":161},"追蹤 RASS 框架（arXiv：2505.18325）與 SafeConstellations（arXiv：2508.11290）的後續研究——精準對齊技術若成熟，將有機會同時解決過度拒絕與惡意使用兩個問題。",{"category":19,"source":10,"title":163,"subtitle":164,"publishDate":6,"tier1Source":165,"supplementSources":168,"tldr":185,"context":194,"mechanics":195,"benchmark":196,"useCases":197,"engineerLens":206,"businessLens":207,"devilsAdvocate":208,"community":212,"hypeScore":228,"hypeMax":91,"adoptionAdvice":229,"actionItems":230},"研究者讓 Claude Code 自主發現人類不太會設計的 AI Scaling 演算法","AutoTTS 框架以 $39.90、160 分鐘發現 CMC 演算法，數學推理 token 用量減少 70%",{"name":166,"url":167},"The Decoder","https://the-decoder.com/researchers-let-claude-code-discover-ai-scaling-algorithms-that-humans-probably-wouldnt-have-designed/",[169,173,177,181],{"name":170,"url":171,"detail":172},"Firethering","https://firethering.com/autotts-ai-inference-test-time-scaling/","深入介紹 AutoTTS 框架與 CMC 演算法的 token 減少成果",{"name":174,"url":175,"detail":176},"arXiv 2605.08083","https://arxiv.org/abs/2605.08083","原始論文：LLMs Improving LLMs： Agentic Discovery for Test-Time Scaling",{"name":178,"url":179,"detail":180},"GitHub zhengkid/AutoTTS","https://github.com/zhengkid/AutoTTS","AutoTTS 開源程式碼庫",{"name":182,"url":183,"detail":184},"AutoTTS 官方網頁","https://zhengkid.github.io/AutoTTS-web/","研究專案官方展示頁面",{"tagline":186,"points":187},"$39.90 買一個演算法——Claude Code 自主發現人類幾乎不會設計的 Scaling 策略",[188,190,192],{"label":46,"text":189},"AutoTTS 讓 Claude Code 在離線環境中自主迭代，發現 CMC 演算法，數學推理 token 用量比標準 self-consistency 減少約 70%，準確率不下降。",{"label":49,"text":191},"探索本身僅花費 $39.90、耗時 160 分鐘，但使用者須自行收集數千筆 offline reasoning traces，實際工程前置成本遠高於此數字。",{"label":52,"text":193},"無預訓練權重，目前可用受眾侷限於 ML 研究員；評估集中在數學推理基準，通用場景的泛化尚待獨立複現驗證。","#### 章節一：AutoTTS 框架——讓 Coding Agent 獨立探索演算法的實驗設計\n\nAutoTTS 由馬里蘭大學、維吉尼亞大學、聖路易斯華盛頓大學、北卡羅來納大學、Google 與 Meta 聯合研究團隊於 2026 年 5 月 24 日正式發表。其核心理念是一場典範轉移：研究者不再親手設計測試時間 Scaling(TTS) 演算法，而是設計一個讓演算法可以被自動發現的環境。\n\n> **名詞解釋**\n> 測試時間 Scaling（Test-Time Scaling，TTS）：指在推理階段動態分配更多計算資源，例如產生多條平行解題路徑或延伸推理長度，而非在訓練階段增大模型規模。\n\n框架的工程基礎是一個**離線模擬環境 (offline replay environment)**：預先從語言模型抽取大量推理路徑並快取，讓控制演算法在固定資料上反覆測試，完全不需要每次都實際呼叫模型 API。\n\n這讓 Claude Code 作為 explorer agent 能以極低成本迭代數千種演算法變體。The Decoder 報導指出，整個探索過程總計花費 **$39.90 美元、耗時 160 分鐘**，而非傳統研究所需的數月工期與龐大算力預算，是 AI 研究自動化的重要里程碑。\n\n#### 章節二：Agent 發現了哪些非直覺的 Scaling 策略\n\nClaude Code 最終發現的演算法命名為「Confidence Momentum Controller(CMC) 」，核心邏輯不依賴固定的分支規則，而是**追蹤推理過程中的信心動量 (confidence momentum)**作為控制信號。\n\nCMC 的運作邏輯出人意料地動態：當信心幾乎沒有變化時，開啟更多平行解題路徑；當信心快速上升時，直接跳過新路徑。CMC 只在信心持續偏離主流路徑一段時間後，才剪除離群路徑——而非立即放棄。\n\n研究者指出，這種動態協調機制「幾乎不可能靠人手設計出來」。在 AIME 和 HMMT 數學基準測試中，CMC 的平衡版設定 (β=0.5) 相較於標準的 64 路 self-consistency，達到約 **69.5% 的 token 減少**，且維持同等準確率。\n\n更值得關注的是 CMC 的泛化能力：它在 AIME24 上被發現，卻成功遷移至 AIME25、HMMT25、GPQA-Diamond，乃至不同規模的模型 DeepSeek-R1-Distill-Llama-8B。這暗示所發現的策略捕捉到了跨領域的推理結構特性。\n\n> **名詞解釋**\n> Self-consistency：一種 TTS 策略，讓模型產生多條平行解題路徑，再取多數投票結果作為最終答案，標準做法通常生成 32 或 64 條路徑。\n\n#### 章節三：自動化研究的可靠性與可重現性挑戰\n\n儘管結果亮眼，AutoTTS 存在明顯的落地門檻。研究團隊**未釋出預訓練權重**，使用者須自行完成三項前置工程：\n\n1. 收集目標模型在各基準上的 offline reasoning traces（數千筆快取推理回應）\n2. 架設 replay 環境並配置高階控制器介面\n3. 取得 Claude Code API 存取權限\n\n「$39.90 發現一個演算法」的成本數字，背後預設了大量工程前置作業，使得這個數字對多數讀者而言具有誤導性。\n\n論文的評估範圍也相對受限——主要在兩個數學推理基準與單一框架下測試，尚未驗證 CMC 在自然語言生成、程式碼合成或多模態任務上的表現。泛化能力的宣稱仍需更廣泛的獨立複現才能確認。\n\n#### 章節四：AI 驅動的 AI 研究——加速器還是幻覺放大器\n\n論文標題「LLMs Improving LLMs」本身就是一份宣言。AutoTTS 代表一類新興研究正規——研究者不再設計具體啟發式規則，而是設計 AI 可以在其中自主探索的環境，讓演算法從資料與反饋中湧現。\n\nThe Decoder 報導指出，Claude Code 自主發現的 CMC 包含「幾乎不可能靠人手設計出來」的動態協調機制，意味著 AI 的搜索空間確實超越了人類直覺的邊界，有潛力大幅壓縮演算法研究的迭代週期——從數月縮短至數小時。\n\n但加速本身也帶來新的風險：當 AI 發現人類無法直覺理解的策略時，如何系統性驗證其行為邊界？CMC 在少數基準上的良好泛化，距離「可信賴的通用推理策略」仍有距離。自動化研究究竟是加速器還是幻覺放大器，答案取決於評估基礎設施能否與探索速度同步成長。","AutoTTS 的技術核心可分為三層機制：模擬環境設計、Agent 迭代框架、CMC 動態控制邏輯。理解這三層，才能評估「$39.90 發現演算法」背後的真實工程成本與研究價值。\n\n#### 機制 1：離線回放環境 (Offline Replay Environment)\n\nAutoTTS 的加速來源是將「執行推理」與「設計控制策略」完全解耦。研究團隊預先從目標語言模型抽取大規模推理路徑並快取，形成固定的資料集。控制演算法在這個固定資料集上評估，不需要每次都實際呼叫 LLM API。\n\n這讓數千次演算法迭代的邊際成本趨近於零：每次迭代只需在快取資料上執行計算，而不是付出真實的推理 API 費用。\n\n#### 機制 2：Claude Code Explorer Agent 的迭代設計\n\nClaude Code 作為 explorer agent，每輪迭代都審視前幾輪提案的缺陷，以 Python 程式碼直接撰寫新的控制器。控制空間沿**寬度 (width)**與**深度 (depth)**兩個維度定義：寬度控制平行解題路徑數，深度控制每條路徑的推理延伸長度。\n\n系統暴露一個高階控制器介面，讓 Agent 可獨立調整所有下層閾值，而不需要了解底層模型的內部狀態。這是讓大規模探索在可控成本內可行的關鍵抽象設計。\n\n#### 機制 3：CMC 的信心動量控制邏輯\n\nCMC 的核心創新在於引入**信心動量**(confidence momentum) 作為控制信號，取代傳統固定閾值的分支決策。當信心變化緩慢時，CMC 開啟更多平行路徑；當信心快速上升時，跳過新分支；只有在信心長期偏離主流路徑後，才剪除離群分支。\n\nβ=0.5 的平衡設定在 AIME 和 HMMT 基準上實現約 69.5% 的 token 減少，準確率不下降。\n\n> **白話比喻**\n> 把 CMC 想像成一個有經驗的考試策略師：越想越有把握的題目，別浪費時間換思路；卡在原地沒進展，才去嘗試不同解法。傳統 self-consistency 則像是不管有沒有把握，一律做 64 遍再投票——資源浪費在早已有把握的題目上。","#### AIME 數學基準\n\nCMC(β=0.5) 與標準 self-consistency（64 路）對比，在 AIME24 達到約 69.5% token 減少，準確率維持同等水準。\n\n#### 跨基準泛化\n\nCMC 在 AIME24 被發現，成功遷移至 AIME25、HMMT25、GPQA-Diamond，token 效率優勢在各基準上一致保持。\n\n#### 跨模型泛化\n\n在 DeepSeek-R1-Distill-Llama-8B 上測試，CMC 同樣維持效率優勢，顯示控制策略不依賴特定模型的內部實作。",{"recommended":198,"avoid":202},[199,200,201],"ML 研究機構探索新的 TTS 演算法，壓縮演算法研究迭代週期","高頻數學推理服務（如競賽題解析、自動評分系統）需要控制推理成本","推理基礎設施工程師評估 token 效率最佳化策略",[203,204,205],"一般應用開發者的生產直接套用（工程前置門檻過高，無預訓練權重）","非數學推理任務（自然語言生成、程式碼合成）的直接遷移（泛化尚未驗證）","需要向非技術利益相關者解釋演算法決策的合規場景（CMC 邏輯難以直覺審計）","#### 環境需求\n\n使用 AutoTTS 需要 Python 環境與 Claude Code API 存取權限。核心前置工程是針對目標模型在各基準上收集大規模 offline reasoning traces，建議至少數千筆快取推理回應，以確保評估結果的統計顯著性。\n\n#### 最小 PoC\n\n```bash\n# 克隆程式碼庫並安裝依賴\ngit clone https://github.com/zhengkid/AutoTTS\ncd AutoTTS && pip install -r requirements.txt\n\n# 收集 offline reasoning traces（以 AIME24 為例）\npython collect_traces.py --benchmark aime24 --n_samples 1000\n\n# 啟動 AutoTTS 探索（Claude Code 作為 explorer agent）\npython run_autotts.py --beta 0.5 --max_iterations 50\n```\n\n#### 驗測規劃\n\n建議先在 AIME24 上複現論文結果，確認 token 減少幅度在 60–70% 區間。再以不同 β 值（0.3、0.5、0.7）評估準確率與效率的帕累托前緣，最後在目標任務的 held-out 測試集上驗證遷移效果。\n\n#### 常見陷阱\n\n- offline traces 數量不足時，評估結果方差過大，導致 explorer agent 做出誤導性的控制器修改\n- β 值在訓練基準上過度擬合，遷移至新任務後效率大幅下降\n- Claude Code API 在探索過程中遭遇 rate limit，導致迭代中斷、難以復現最優路徑\n\n#### 上線檢核清單\n\n- 觀測：token 使用量（與 baseline self-consistency 對比）、準確率（與 64 路投票對比）、探索迭代收斂曲線\n- 成本：offline trace 收集的推理 API 費用（通常遠高於 $39.90 的探索成本本身）、Claude Code API 使用量\n- 風險：演算法行為在分布外任務上的不可預測性；CMC 邏輯難以用傳統方式審計驗證","#### 競爭版圖\n\n- **直接競品**：人工設計的 TTS 策略（beam search、MCTS、standard self-consistency）；OpenAI o-series 推理模型（內建計算分配邏輯）\n- **間接競品**：AutoML 框架；Neural Architecture Search(NAS) 工具\n\n#### 護城河類型\n\n- **工程護城河**：offline replay environment 的設計降低了探索成本，但技術本身可被複製；真正的護城河是快取推理資料集的規模與多樣性\n- **生態護城河**：AutoTTS 依賴 Claude Code 作為 explorer agent，與 Anthropic 生態深度綁定；若其他 coding agent 能扮演同等角色，依賴程度將降低\n\n#### 定價策略\n\nAutoTTS 以學術開源形式發布（GitHub 公開程式碼），目前沒有商業定價。潛在商業模式包括：提供預建 offline datasets 的付費訂閱、或作為推理服務提供商的效率最佳化層。\n\n#### 企業導入阻力\n\n- 無預訓練權重，須從頭建立 offline replay dataset，工程成本對中小型團隊不友善\n- CMC 邏輯難以向非技術利益相關者解釋，在合規場景中是潛在風險\n- 目前僅驗證數學推理任務，企業應用場景的適用性尚不明確\n\n#### 第二序影響\n\n- 若 AutoTTS 範式成熟，未來演算法研究可能大幅去中心化：任何有算力的研究小組都能探索 TTS 策略，而不只是大型實驗室\n- Claude Code 作為「演算法探索工具」的新角色，可能開啟 Anthropic 在研究工具市場的新定位\n\n#### 判決：有潛力但等待複現（學術先行、產業跟進）\n\nAutoTTS 的學術貢獻清晰——以極低成本自動探索出人類難以設計的控制策略。但在獨立複現成功、以及非數學任務驗證完成之前，企業端應保持觀望，而非急於導入。",[209,210,211],"70% token 減少僅在數學競賽推理基準上驗證，自然語言生成或程式碼合成任務的泛化尚未確認，不宜直接類推至一般場景","$39.90 的探索成本隱藏了建立 offline replay 環境所需的大量工程前置作業，包括數千筆推理路徑的收集費用，實際總成本遠高於此數字","CMC 控制邏輯難以直覺理解，意味著演算法的行為邊界難以用傳統方式審計驗證，在安全敏感場景中可能是隱患",[213,216,219,222,225],{"platform":81,"user":214,"quote":215},"ainieuwtjes.bsky.social(AI News)","研究者讓 Claude Code 發現 AI Scaling 演算法——而人類可能根本不會設計出這些演算法。UMD、Google 與 Meta 的研究者使用名為 AutoTTS 的自動化系統，讓 AI coding agent 發現用於 AI 推理的新控制演算法，推理 token 用量因此大幅下降。",{"platform":73,"user":217,"quote":218},"aurareturn(HN)","證據指向相同類型的 Scaling 定律：訓練計算量每年增長 4-5 倍。弱小的競爭者將無法維持這個步調——我們已看到 Cohere、Mistral、Inflection AI、Adept、Character.ai 等實驗室退出前沿競賽。我也懷疑 Meta 和 xAI 能否追上。即使是 Google 也難以跟上節奏。",{"platform":73,"user":220,"quote":221},"armada1122(HN)","作為每天使用 Python 和 Claude Code 的人（我已用它運行研究程式碼庫和交易機器人數月），我同意「架構是瓶頸」這個說法，但想補充：問題不在程式碼生成能力本身——LLM 生成的程式碼單獨來看是有能力的；真正的瓶頸是跨程式碼庫的一致性，這才是 Claude Code 在實際研究使用中的主要挑戰。",{"platform":77,"user":223,"quote":224},"@alex_yehya(X)","成長速度驚人！Claude Code 的擴張速度比我見過的大多數產品都快。",{"platform":77,"user":226,"quote":227},"@utk7arsh(X)","一個讓人意外的資訊：Claude Code 在過去幾週開始對企業帳戶施加速率限制，這意味著他們被龐大需求淹沒，面臨因規模不足而失去客戶的風險。",4,"先觀望",[231,233,235],{"type":95,"text":232},"克隆 AutoTTS GitHub 程式碼庫 (zhengkid/AutoTTS) ，在自有模型的小規模 offline traces 上測試 CMC 演算法的 token 效率表現",{"type":98,"text":234},"為現有推理服務建立 offline replay 基礎設施，評估 TTS 演算法自動探索在目標任務上的可行性與工程成本",{"type":101,"text":236},"追蹤 AutoTTS 論文的獨立複現嘗試，以及 CMC 在非數學推理任務（自然語言生成、程式碼合成）上的泛化結果",[238,276,307,331,362,390,420,455],{"category":239,"source":15,"title":240,"publishDate":6,"tier1Source":241,"supplementSources":244,"coreInfo":252,"engineerView":253,"businessView":254,"viewALabel":255,"viewBLabel":256,"bench":257,"communityQuotes":258,"verdict":274,"impact":275},"ecosystem","Microsoft 開源「目前發現最早的 DOS 原始碼」",{"name":242,"url":243},"Microsoft Open Source Blog","https://opensource.microsoft.com/blog/2026/04/28/continuing-the-story-of-early-dos-development/",[245,249],{"name":246,"url":247,"detail":248},"Tom's Hardware","https://www.tomshardware.com/software/operating-systems/45-years-later-earliest-dos-source-code-transcribed-from-a-stack-of-old-printouts-found-in-a-garage-code-was-open-sourced-to-mark-86-dos-1-00s-anniversary","詳細報導掃描與轉錄過程",{"name":250,"url":251},"Hacker News Discussion","https://news.ycombinator.com/item?id=48253386","#### 45 年前的車庫遺珍\n\n2026 年 4 月 28 日，Microsoft 趁 86-DOS 1.00 誕生 45 週年，在 GitHub 以 MIT 授權釋出迄今發現最早的 DOS 原始碼（代號「Paterson Listings」）。這批程式碼的數位版本早已不存在——原始碼是從 Tim Paterson 車庫中保存的點矩陣印表機連續紙列印稿，由歷史學家 Yufeng Gao 與 Rich Cini 手工掃描並轉錄而來。\n\n#### 釋出內容\n\n釋出內容存放於 GitHub `DOS-History/Paterson-Listings`，包含：\n\n- 86-DOS 1.00 kernel 原始碼\n- PC-DOS 1.00 pre-release kernel 多個開發快照\n- CHKDSK 等公用程式與 Microsoft BASIC-86 Compiler runtime library\n- Seattle Computer Products ASM 組合器\n\nMicrosoft VP Scott Hanselman 確認，轉錄後的程式碼可以逐位元組重新編譯出與原始執行檔完全相同的結果。掃描件同步上傳至 Internet Archive，原始碼最終將入藏 Interim Computer Museum 永久保存。","這批 8086 組合語言原始碼提供了研究 1980 年代初期作業系統設計哲學的第一手資料。Seattle Computer Products ASM 組合器已一併收錄，代表程式碼可完整重新編譯——這是罕見的「可驗證歷史快照」。想理解現代 x86 OS 如何從 45 年前的車庫程式碼演進至今，此處是難得起點。","Microsoft 開源歷史軟體已成長期品牌策略：2018 年 MS-DOS 1.25/2.11、2024 年 MS-DOS 4.0、2025 年 6502 BASIC，2026 年再添 86-DOS 1.00。這系列行動持續強化其開源生態形象，並為 GitHub 的教育與保存角色背書。MIT 授權讓這批程式碼法律上可自由使用，象徵意義遠大於直接商業價值。","開發者視角","生態影響","",[259,262,265,268,271],{"platform":77,"user":260,"quote":261},"@shanselman（Microsoft VP，Hanselminutes 主持人）","最早的 DOS 原始碼在 Tim Paterson 車庫的印表機紙上被找到，我們在 86-DOS 1.00 45 週年當天將其開源！這是頂級的軟體考古學，供學習、保存與單純的好奇心探索。去挖掘並了解它是如何被復原的！",{"platform":77,"user":263,"quote":264},"ZDNET（科技媒體）","Microsoft 終於開源了 DOS 1.0——這遠不只是程式碼本身。",{"platform":73,"user":266,"quote":267},"userbinator","把它移植到 64 位元架構顯然是個選項；NT kernel 已經被移植到幾個非 x86 架構了。",{"platform":73,"user":269,"quote":270},"gerdesj","我的 C64 大約從 1984 年起就一直保存至今（幾年前只換了幾個電容）。當年我從書上手動輸入了大量機器碼，ADSR（起音、衰減、持續、釋音）和低通、高通、帶通濾波器的聲音合成——這些記憶對一個中年人來說依然鮮活。",{"platform":81,"user":272,"quote":273},"fronkongames.bsky.social(Fronkon Games)","Microsoft 開源了「迄今發現最早的 DOS 原始碼」。","追","歷史 DOS 原始碼首度開源、MIT 授權可自由研究，是軟體考古與作業系統設計教育的第一手資料。",{"category":277,"source":10,"title":278,"publishDate":6,"tier1Source":279,"supplementSources":281,"coreInfo":294,"engineerView":295,"businessView":296,"viewALabel":297,"viewBLabel":298,"bench":257,"communityQuotes":299,"verdict":154,"impact":306},"policy","Anthropic 被 Pentagon 標記為供應鏈風險，NSA 仍悄悄持續部署 Mythos",{"name":166,"url":280},"https://the-decoder.com/anthropic-may-keep-supplying-claude-to-the-nsa-despite-being-flagged-as-a-supply-chain-risk-by-the-pentagon/",[282,286,290],{"name":283,"url":284,"detail":285},"CNBC","https://www.cnbc.com/2026/03/05/anthropic-pentagon-ai-claude-iran.html","Pentagon 正式通知 Anthropic 被列為供應鏈風險",{"name":287,"url":288,"detail":289},"Axios","https://www.axios.com/2026/03/09/anthropic-sues-pentagon-supply-chain-risk-label","Anthropic 對 Pentagon 提起訴訟經過",{"name":291,"url":292,"detail":293},"The Next Web","https://thenextweb.com/news/us-government-chip-shortage-anthropic-nsa-9-billion","美國情報機構晶片短缺與 90 億美元緊急預算背景","#### Pentagon 的矛盾禁令\n\n2026 年 3 月，美國國防部正式將 Anthropic 列為「供應鏈風險」，要求國防承包商認證其工作中未使用 Anthropic 模型。然而同年 5 月，白宮幕僚長 Susie Wiles 親自批准 NSA 繼續部署 Anthropic 的 Mythos Preview 模型，兩個政府機構的態度形成尖銳矛盾。\n\nAnthropic 已對 Pentagon 提起訴訟，主張該認定侵犯其第一修正案權利並逾越政府職權。白宮計劃以此合約作為未來政府 AI 採購的範本，並核准 90 億美元緊急預算用於為情報機構採購高階 AI 晶片。\n\n#### 為何 NSA 離不開 Mythos\n\nMythos 設計運行於較舊的晶片架構，得以相容 NSA 機密網路的既有基礎設施。最新 Nvidia Grace Blackwell 晶片在機密環境嚴重不足，現代前沿模型的算力需求遠超機密網路當初的設計容量。\n\n> **白話比喻**\n> 就像舊電腦只能跑 Windows 7——NSA 的機密網路就是那台舊電腦，Mythos 是少數願意配合的 AI。\n\nMythos 據報「發現漏洞的速度比開發者修補的速度還快」，令情報機構難以找到替代方案。合約已加入禁止處理美國公民資料的條款，並刪除了令談判破裂的「任何合法用途」 (any lawful use) 措辭。","Mythos 能繞過晶片限制部署於機密網路，反映一個工程現實：機密環境的硬體升級週期遠慢於模型迭代速度。合約條款移除「任何合法用途」措辭，顯示 AI 供應商在政府採購中需精確定義使用邊界。\n\n對在美政府或國防供應鏈作業的工程師，此案提醒：合規要求不只看現有認證，更需追蹤供應商與政府機構的法律爭端進展。Anthropic 訴訟結果將直接影響未來 AI 工具在政府環境的許可邊界。","這一矛盾局面顯示，AI 軍備競賽的算力缺口已大到讓情報機構「能用」優先於「合規」。NSA 合約若成為政府採購範本，將為 AI 企業開創在「被列為風險」後仍保住政府合約的先例。\n\n企業採購者需注意：Anthropic 法律地位仍未定（訴訟進行中），若 Pentagon 主張獲法院支持，可能波及更廣的政府合約生態。此案也預示未來 AI 供應商談判時，使用範圍條款將成為最關鍵的議題。","合規實作影響","企業風險與成本",[300,303],{"platform":77,"user":301,"quote":302},"@Polymarket（預測市場平台）","最新消息：NSA 據報在 Anthropic 被認定為「供應鏈風險」後，仍持續使用 Claude Mythos。",{"platform":77,"user":304,"quote":305},"@A_SynapseMedia（AI 新聞媒體）","解密 Claude Gov：Anthropic 秘密為美國情報機構和國家安全提供 AI 支援。","Pentagon 與情報機構的 AI 採購矛盾，預示政府合約中「使用範圍條款」將成為未來 AI 供應商談判的最關鍵條件。",{"category":104,"source":11,"title":308,"publishDate":6,"tier1Source":309,"supplementSources":311,"coreInfo":316,"engineerView":317,"businessView":318,"viewALabel":319,"viewBLabel":320,"bench":321,"communityQuotes":322,"verdict":329,"impact":330},"別把 Copilot 和 Gemini 的模型選擇留在預設值——數學家實測揭露嚴重幻覺",{"name":166,"url":310},"https://the-decoder.com/why-you-shouldnt-leave-model-selection-on-default-in-copilot-gemini-and-other-ai-tools/",[312],{"name":313,"url":314,"detail":315},"Real signals or artificial stereotypes？ – Adam Kucharski(Substack)","https://kucharski.substack.com/p/real-signals-or-artificial-stereotypes","原始實驗設計與數據來源","#### 相同資料，捏造截然不同的結論\n\n數學家 Adam Kucharski 製造 2,000 筆完全相同的自由文字回應，分別標記為「UK」與「US」後交給 Microsoft Copilot 的「Auto」模式。\n\nCopilot 卻輸出一份詳細差異報告，聲稱兩國「在語氣、強度與措辭上有所不同」——而這些差異根本不存在於資料中。\n\n#### 幻覺的根源：刻板印象填補空白\n\n在第二個實驗中，相同的職涯目標敘述被複製並標記 5 個國家，Copilot 捏造出「義大利人從事藝術職涯的意願是英國人的三倍」等具體數字，全部憑空製造。\n\n> **白話比喻**\n> 就像請人分析兩杯完全相同的水，他卻說「左邊的比較甜、右邊帶礦物質感」——因為他認為你想看差異，所以就編了一個。\n\nCopilot 自身的關鍵字計數已顯示資料完全一致，卻無視此結果，改以捏造百分比呈現「差異」。約 97% 的 Copilot 使用者採用預設 Auto 模式，幾乎不知道底層正在跑哪個模型。","在實際分析任務中，應將 AI 輸出視為需要驗證的草稿，而非可信結論。\n\n建議執行分析前先書面記錄預期結果作為對照基準，並主動切換至推理能力較強的模型，而非依賴預設的 Auto 模式。\n\n最關鍵的理性檢查：若資料本身顯示某項指標一致，AI 卻輸出差異分析，這幾乎一定是幻覺，不是洞見。凡涉及人口統計學標籤的分析，務必人工抽樣驗證。","這份研究揭露的不只是技術問題，更是產品設計問題。「Auto 模式選最佳模型」的承諾，在分析型任務中反而挑選了傾向以刻板印象填補空白的標準模型。\n\n對企業而言，若將 AI 用於 HR 評估、市場調研或政策分析，這類系統性偏差可能直接影響決策品質，且幾乎無法被察覺。\n\n97% 的使用者不知道自己在用哪個模型，企業採購 Copilot 授權時需額外建立 AI 輸出審查機制，才能確保資料分析的可信度。","實務觀點","產業結構影響","#### 各 AI 幻覺率比較（社群整理）\n\n- Perplexity：100 次中出現 37 次幻覺\n- Copilot：40 次\n- Perplexity Pro：45 次\n- ChatGPT Search：67 次\n- DeepSeek Search：68 次\n- Gemini：76 次",[323,326],{"platform":77,"user":324,"quote":325},"@StatiSense","各 AI 幻覺率排名：1. Perplexity — 100 次中 37 次；2. Copilot — 40 次；3. Perplexity Pro — 45 次；4. ChatGPT Search — 67 次；5. DeepSeek Search — 68 次；6. Gemini — 76 次",{"platform":77,"user":327,"quote":328},"@NerdyChefs_AI","最嚴重的是 Google Gemini，錯誤率高達 76%！就像一個廚師把 4 道菜燒焦了 3 道，卻還說「完美焦糖化」。ChatGPT、Copilot 和 Perplexity 也未能倖免，都有引用來源錯誤或幻覺問題。","觀望","AI 工具的預設模式可能系統性地捏造分析結論，企業使用者需主動選擇推理模型並建立輸出審查機制。",{"category":239,"source":13,"title":332,"publishDate":6,"tier1Source":333,"supplementSources":336,"coreInfo":340,"engineerView":341,"businessView":342,"viewALabel":343,"viewBLabel":256,"bench":257,"communityQuotes":344,"verdict":274,"impact":361},"cmux：為 AI Coding Agent 打造的 Ghostty 終端機，支援垂直分頁與通知",{"name":334,"url":335},"manaflow-ai/cmux — GitHub","https://github.com/manaflow-ai/cmux",[337],{"name":338,"url":339},"cmux — The Terminal Built for Multitasking with AI Agents","https://dudarik.com/en/blog/cmux-the-terminal-built-for-multitasking/","#### 舊工具、新熱度\n\ncmux 由 manaflow-ai 開發，最新版 v0.64.10 發布於 2025 年 5 月 23 日，是個已存在近一年的專案。近期因其在 GitHub 單日新增 560 顆星而登上熱搜，總星數突破 19,000，顯示 AI Coding Agent 工具鏈需求持續成長。\n\n> **名詞解釋**\n> libghostty 是 Ghostty 終端機應用的開源渲染函式庫，第三方可藉此打造具備相同高效能渲染的終端工具。\n\n#### 核心功能設計\n\ncmux 以 Swift + AppKit（佔 81.4% 程式碼）原生打造，刻意不使用 Electron。垂直側邊欄分頁讓開發者一眼掃描多達 10 個 agent 工作階段，每個分頁顯示 git branch、PR 狀態、工作目錄與即時通知文字。\n\n當 agent 等待輸入時，對應 pane 出現藍色光環，並觸發原生 macOS 桌面通知。工具原生支援 Claude Code、Codex、Gemini CLI 等主流 AI Coding Agent 的 hook 整合，另提供 socket API 讓 agent 或人類皆可控制終端佈局。","cmux 透過 socket API 與 CLI 介面提供可程式化控制，涵蓋建立 pane、傳送按鍵、操控內建瀏覽器等操作。對 Claude Code 的原生 hook 整合讓 agent 完成或等待時自動推送通知，無需輪詢終端狀態。現有 Ghostty 用戶可直接複用 `~/.config/ghostty/config`，零成本遷移。","AI Coding Agent 工作流程的普及催生了 agent-native 終端機這個新品類。cmux 採 GPL-3.0 + 商業授權雙軌模式，兼顧開源社群與企業需求。Ghostty 作者 Mitchell Hashimoto（HashiCorp 共同創辦人）公開視其為 libghostty 生態的成功案例，進一步鞏固了整個 Ghostty 生態系的市場地位。","開發者整合視角",[345,348,351,354,357],{"platform":77,"user":346,"quote":347},"@mitchellh（Ghostty 作者、HashiCorp 共同創辦人）","cmux 使用了 libghostty，完美示範了 Ghostty 希望實現的目標——讓其他終端得以實現。這是巨大的成功案例，我們沒有什麼需要追趕的。大家改用 cmux 或其他 libghostty 終端而非 Ghostty，這結果非常好。",{"platform":77,"user":349,"quote":350},"@_PaperMoose_（X 用戶）","我很愛 cmux。如果你在跑 AI Coding Agent，這款終端機是必備的。cmux 是基於 Ghostty 的 macOS 終端，具備垂直分頁、內建瀏覽器，以及可讓你為一切編寫腳本的 Unix socket API。這些基礎原語才是讓它真正厲害的地方。",{"platform":81,"user":352,"quote":353},"catalinpit.com（Bluesky，4 likes）","cmux 是基於 Ghostty 的 macOS 終端機，專為 AI Coding Agent 打造，具備垂直分頁、agent 通知、分割 pane、內建瀏覽器與 SSH 工作區。開源萬歲，@manaflowai 做得很棒。",{"platform":81,"user":355,"quote":356},"github-trending.bsky.social（Bluesky，1 like）","🎉 慶祝！🎉（500+ 顆新星）manaflow-ai / cmux ⭐ 18,712(+560)Swift 語言。基於 Ghostty 的 macOS 終端機，為 AI Coding Agent 提供垂直分頁與通知功能。",{"platform":358,"user":359,"quote":360},"HN","smallsharptools（HN 用戶）","Ghostty 是款很棒的終端應用，我使用了好幾年。開始用 Claude Code 後，分頁功能就不夠用了，於是我找了個多工器。不喜歡 tmux，其他應用的 UX 設計也不夠好，所以我用 Ghostty 函式庫做了 Batty，支援主題、鍵盤快捷鍵、拖放移動 pane、快速導覽以及終端 BEL 通知。","讓同時管理多個 AI Coding Agent 的 macOS 開發者大幅降低工作階段切換成本，預示 agent-native 終端工具成為新興必備品類。",{"category":19,"source":14,"title":363,"publishDate":6,"tier1Source":364,"supplementSources":367,"coreInfo":376,"engineerView":377,"businessView":378,"viewALabel":379,"viewBLabel":380,"bench":381,"communityQuotes":382,"verdict":274,"impact":389},"Google Stitch 3.0：在即時畫布上用 AI 生成並迭代 UI 畫面",{"name":365,"url":366},"Google Blog","https://blog.google/innovation-and-ai/models-and-research/google-labs/stitch-updates/",[368,372],{"name":369,"url":370,"detail":371},"TechTimes","https://www.techtimes.com/articles/316903/20260520/google-stitch-launches-real-time-ai-agent-multiplayer-editing-figma-charges-15-seat.htm","Stitch 3.0 即時代理與多人協作發布報導",{"name":373,"url":374,"detail":375},"Product Hunt","https://www.producthunt.com/products/stitch-by-google","社群票數與排名數據","#### 核心升級：從回合制到即時串流\n\nGoogle Stitch 3.0 以「即時串流設計代理」取代舊版回合制工作流程。過去設計師需送出 prompt 後等待，3.0 版的 Stitch Agent 在輸入的同時直接在畫布上渲染 UI 元件，可在生成過程中隨時調整方向。\n\n語音模式同步整合進串流迴圈——設計師說出「給我三種選單選項」，畫布即時回應，代理主動詢問設計目標並在串流中套用修改。\n\n#### 功能與整合\n\n3.0 版新增類 Google Docs 的多人協作，以及記錄設計演進軌跡的 Agent Manager。匯出支援 Vue.js、Tailwind CSS、Flutter、SwiftUI 等框架，可直接整合 Figma、Lovable、Bolt 或發布至 Netlify。\n\n> **名詞解釋**\n> DESIGN.md：Google 開放的純文字設計系統規格格式，可從現有 codebase 或 Figma 提取品牌規則，實現跨工具攜帶。","Stitch 提供 MCP server 與 SDK，支援從外部工作流程以程式方式觸發設計生成，適合納入設計稿自動化管線。DESIGN.md 格式讓品牌規則可從既有 codebase 提取後直接匯入，維持跨工具設計一致性。匯出的 Vue.js 或 Flutter 程式碼可直接接入前端流程，減少手動轉寫元件的工時。","免費策略（無需信用卡、每月 550 次生成）直接衝擊 Figma $15/seat 的付費模式。Product Hunt 首日排名第一、376 票，印證創業者對低門檻 UI 工具的強烈需求。「Vibe Design」定位讓非設計師以情緒或意圖啟動設計，快速產出專業外觀 UI，壓縮 MVP 到上線的週期。","工程師視角","商業視角","#### 市場表現\n\n- Product Hunt 首日：376 票，排名第一",[383,386],{"platform":81,"user":384,"quote":385},"muttadrij.bsky.social(2 upvotes)","🚀 Product Hunt 每日精選 — 2026 年 5 月 24 日（週日）\n\n#1 Stitch 3.0 by Google · #2 ModelHub · #3 Freu AI · #4 Edgee Fallback Models · #5 WhatCable",{"platform":77,"user":387,"quote":388},"@minchoi（AI 研究者與 KOL）","Google Stitch 可根據提示生成 UI 介面","即時串流畫布搭配多人協作，讓 AI 設計工具從「送出後等待」升級為「實時共創」，大幅降低非設計師的 UI 開發門檻。",{"category":104,"source":11,"title":391,"publishDate":6,"tier1Source":392,"supplementSources":395,"coreInfo":400,"engineerView":401,"businessView":402,"viewALabel":319,"viewBLabel":320,"bench":257,"communityQuotes":403,"verdict":154,"impact":419},"Claude 不是你的架構師——別讓 AI 假裝它能做系統設計決策",{"name":393,"url":394},"hollandtech.net","https://www.hollandtech.net/claude-is-not-your-architect/",[396],{"name":397,"url":398,"detail":399},"Hacker News 討論","https://news.ycombinator.com/item?id=48259784","HN 熱議串，社群對文章觀點正反兩極","#### 四月舊文，近期因 HN 討論再度引爆\n\n這篇由 Charlie Holland 撰寫的文章發表於 2026 年 4 月 6 日，近期因 Hacker News 熱議再度獲得廣泛關注。核心論點：AI agent 擅長實作，但缺乏做架構決策所需的情境判斷力，讓 AI 主導設計而非實作，會導致系統與組織脈絡嚴重脫節。\n\n#### 四個讓架構決策失靈的問題\n\n- **Attaboy Problem（迎合問題）**：AI 被訓練為「有幫助」，而有幫助就等於順從。真正的架構師價值在於「拒絕」和「推翻」，文章指 Claude「病態地贊同」，缺乏說「不」的能力\n- **Generic-Fit 架構**：AI 設計的系統忽略組織限制、團隊能力、遺留系統與合規需求\n- **問責缺口**：「Claude 不會在凌晨三點被 paged」——工程師繼承一個自己沒有設計的系統，卻要承擔全部後果\n- **短路專業對話**：AI 背書讓工程評審變成橡皮圖章，扼殺能產出更好設計的爭論式討論\n\n> **名詞解釋**\n> Attaboy Problem：AI 因訓練目標（有幫助）而傾向順從用戶，缺乏像真正架構師那樣主動質疑、拒絕不合理設計的能力。","作者建議的分工：工程師主導設計，agent 負責實作。實際操作上，先鎖定服務邊界、資料模型與擴展策略等架構決策，再把實作細節交給 AI 執行。\n\n把 AI 的每個架構建議當成初級工程師的提案來審視——不是因為它的程式碼能力差，而是因為它不了解你的組織債務、人員限制與生產環境的現實。","系統性風險值得警惕：當缺乏經驗的工程師借助 AI 構建影響數百萬用戶的系統，潛在技術負債可能遠超公司承受能力。\n\nAI 是技能放大器——有能力者更有生產力，缺乏能力者則加倍犯錯。企業雇用與技術審查標準不應因 AI 工具而降低，反而需要更嚴格的架構問責機制。",[404,407,410,413,416],{"platform":73,"user":405,"quote":406},"moose6912","文章說 Claude 相當善於迎合，這會讓你走偏。幾週前我給了 Claude 一個軟體架構問題，它反而推翻我，說這對我的使用情境和規模來說太過了。",{"platform":73,"user":408,"quote":409},"onlyrealcuzzo","「只要選對人就能省 10 倍」——那根本無法規模化。「想辦法做得更好、選更好的人」不是可規模化的解法，不管有沒有用 LLM 都一樣。",{"platform":73,"user":411,"quote":412},"senordevnyc","我標記了這堆偽善的無用 AI 垃圾。如果你有話要說，就自己說！",{"platform":77,"user":414,"quote":415},"theo（t3.gg 創辦人）","Claude Code 不開源是 AI 時代最大的失誤。如果 CC 在 GitHub 上，這些問題早就輕易被發現和修復了。但現在我們只能逆向工程他們的不稱職。",{"platform":77,"user":417,"quote":418},"@paulabartabajo_","我完全不同意這個說法。Claude Code 並不是 AI 最大的進展。CC 真正能用的原因，是底層 LLM（主要是 Sonnet 或 Opus 4.6）在程式任務上大幅改進——靠的是更多的預訓練。","AI 輔助開發進入普及期，如何劃清「AI 輔助實作」與「AI 主導決策」的邊界，將成為工程團隊架構健康度的關鍵分水嶺。",{"category":104,"source":11,"title":421,"publishDate":6,"tier1Source":422,"supplementSources":425,"coreInfo":435,"engineerView":436,"businessView":437,"viewALabel":319,"viewBLabel":320,"bench":257,"communityQuotes":438,"verdict":154,"impact":454},"AI 到底賺錢了沒？產業獲利現況的冷靜盤點",{"name":423,"url":424},"Epoch AI：AI 公司能否獲利","https://epoch.ai/gradient-updates/can-ai-companies-become-profitable",[426,429,432],{"name":427,"url":428},"Is AI Profitable Yet？ — Hacker News 討論","https://news.ycombinator.com/item?id=48243863",{"name":430,"url":431},"Anthropic 年化營收突破 $300 億","https://www.trendingtopics.eu/anthropic-overtakes-openai-in-revenue-hitting-30-billion-run-rate/",{"name":433,"url":434},"OpenAI Q1 2026 近 $60 億營收 — The Information","https://www.theinformation.com/articles/openai-held-1-billion-revenue-lead-anthropic-first-quarter","#### 數月前點燃、近期再掀波瀾\n\n2026 年 4 月，Epoch AI 發布「AI 公司能否獲利」深度分析，首度以財務模型拆解前沿模型的真實獲利結構。近期 Anthropic 確認年化營收突破 $300 億、有望在 Q2 達到營業損益平衡，讓這場辯論再度登上社群熱榜。\n\n#### 帳面收入亮眼，結構性困境未解\n\nOpenAI 2026 年 Q1 達約 $57 億季度營收，毛利率 33%；但全年現金消耗預計高達 $270 億。Epoch AI 分析顯示，GPT-5 的 $60 億毛利潤仍不足以回收 $50 億 R&D 投入，且模型發布後僅 3 個月便遭競爭對手挑戰——回收窗口極窄是核心困境。\n\nAI 推理成本與用量線性正比，打破傳統軟體「邊際成本趨近零」的規律。MIT 2025 年研究顯示，約 95% 企業 AI 投資未達獲利，合計約 $400 億付諸流水。算法效率雖每年持續改善，但短期成本結構仍不利於消費端大規模變現。","AI 推理成本與用量線性正比，設計 AI 功能時必須優先考量 token 效率與快取策略，而非僅著眼功能完整性。算法效率每年持續改善（inference cost per token 逐年走低），長期有望提升毛利率；但短期「多用多花」的成本結構，讓 API 呼叫頻次必須與產品定價同步設計，而非事後補救。","從競爭經濟學角度，激烈競爭長期將壓縮超額利潤至零。Anthropic 企業 API 路線（搭配 Google Cloud / AWS）預計毛利率可達約 40%，優於 OpenAI 消費端策略，顯示差異化定位仍有空間。JPMorgan 指出 AI 相關支出在 2025 年上半年貢獻了美國三分之二 GDP 成長——這場豪賭是基礎建設紅利還是泡沫，答案可能在 12 個月內揭曉。",[439,442,445,448,451],{"platform":73,"user":440,"quote":441},"fsckboy","這是個過度簡化的模型。AI 公司的支出帶來的基礎建設遠超出公司本身——包括製造產能、電力線路、軟體系統，乃至個人專業知識的累積。",{"platform":73,"user":443,"quote":444},"YetAnotherNick","加密貨幣市值從 $4 兆跌至 $2 兆，並未引發廣泛衝擊。$4 兆規模的 AI 市值也將如此。",{"platform":77,"user":446,"quote":447},"@ttunguz(Theory Ventures General Partner)","AI 軟體公司的獲利能力，究竟優於還是劣於傳統 SaaS？我起初認為更差，因為 AI 產品的服務成本高得多。但現在我不那麼確定了——AI SaaS 或許遠比 -10% 的平均水準更有利可圖。",{"platform":81,"user":449,"quote":450},"Greg Linden(13 upvotes)","關於 AI 獲利的重要觀點：『馬斯克和他的矽谷夥伴們今天看起來並不順遂。中國 AI 廠商在世界其他地區的銷售正在超越他們，且持續擴大差距……美國產品的售價是中國廠商的 5 到 10 倍。』",{"platform":77,"user":452,"quote":453},"@Jukanlosreve（X 用戶）","摩根士丹利：AI 推理是一門極具獲利潛力的生意。該機構最新報告首度從經濟學角度，以詳細財務模型計算全球 AI 算力競爭的獲利性。","AI 獲利結構問題若持續惡化，將壓縮整個生態系的技術投資深度，並加速供應商整合與差異化定價競爭。",{"category":19,"source":9,"title":456,"publishDate":6,"tier1Source":457,"supplementSources":459,"coreInfo":464,"engineerView":465,"businessView":466,"viewALabel":379,"viewBLabel":380,"bench":467,"communityQuotes":468,"verdict":274,"impact":469},"ByteDance 研究發現：對長文檔提問比逐字轉錄更適合訓練多模態模型",{"name":166,"url":458},"https://the-decoder.com/bytedance-study-finds-that-asking-lmms-questions-beats-making-it-transcribe-text-for-long-document-training/",[460],{"name":461,"url":462,"detail":463},"arXiv 2605.13831","https://arxiv.org/html/2605.13831v1","原始論文：Training Long-Context Vision-Language Models Effectively with Generalization Beyond 128K Context","#### QA 訓練 vs OCR 轉錄\n\nByteDance Seed 與香港科技大學聯合發表 MMProLong 研究，揭露多模態長文檔模型訓練的關鍵洞察：**直接對文件提問，比逐字轉錄更有效**。\n\n在 MMLongBench 基準上，QA 配對訓練讓分數提升 5–6 分；OCR 轉錄訓練反而拉低 6.8–17.4 分。Needle-in-a-Haystack 基準上，MMProLong 比基礎模型 Qwen2.5-VL-7B 平均高出 29.4 分，且僅以 5B tokens 訓練資料便超越 InternVL3-38B 和 Gemma3-27B。\n\n> **名詞解釋**\n> MMLongBench：專門評估多模態大語言模型在長文檔理解能力的基準測試集。\n\n> **白話比喻**\n> 就像學生備考：死記課文逐字逐句不如直接練習考題問答——前者記了許多不會考的細節，後者直接鍛鍊了在文件中找答案的能力。\n\n#### 附帶發現\n\n- 均衡混合不同長度文件，優於只堆積最長樣本\n- 資訊檢索任務比推理任務對效果影響更關鍵\n- 採用 QA 格式時，短脈絡樣本非必要\n\n訓練上下文僅 128K tokens，模型在 256K 乃至 512K 長度下仍保持穩定，且意外提升了長影片基準（Video-MME、MLVU）性能，顯示良好的跨媒體遷移能力。","訓練流程分三步驟：\n\n1. OCR 解析切出 8–15 頁片段\n2. 交由 LLM 生成 QA 配對\n3. 嵌回完整文件脈絡訓練\n\n128K token 訓練窗口可泛化至 256K–512K，不需額外微調。與 DeepSeek 的視覺 token 壓縮架構路線不同，MMProLong 走的是訓練資料組成最佳化，遷移性更強、成本更低。","僅 5B tokens 訓練資料，7B 參數的 MMProLong 便超越 InternVL3-38B 和 Gemma3-27B——訓練成本大幅壓縮。\n\n對需要處理合約、報告、法律文件的企業而言，這套方法可內部複製：用既有文件庫生成 QA 資料集，以低成本訓練高效長文檔助理，不必依賴通用大型模型。","#### 效能基準\n\n- MMLongBench：QA 訓練 +5–6 分；OCR 訓練 -6.8–17.4 分（相較基線）\n- Needle-in-a-Haystack：MMProLong 比 Qwen2.5-VL-7B 平均高出 29.4 分\n- 訓練資料僅 5B tokens，超越 InternVL3-38B 和 Gemma3-27B",[],"QA 配對替代 OCR 轉錄訓練多模態長文檔模型，7B 參數即超越 38B 競品，為企業以低成本建構高效長文檔 AI 提供可複製的方法論。","#### 社群熱議排行\n\ncmux（AI agent 終端機）在 GitHub 單日新增 560 顆星，累計 18,712。HN 用戶 smallsharptools 直言「開始用 Claude Code 後，分頁功能就不夠用了」。\n\nAutoTTS 讓 AI 自主發現 Scaling 演算法的研究在 HN 引發高讚討論，DeepSeek Reasonix 的 Cache-First 架構也吸引大量開發者關注。\n\nGemini 預設模式 76% 幻覺率（@StatiSense，X）成為今日轉發最多的數據，引爆 AI 工具信任危機討論。\n\n#### 技術爭議與分歧\n\nClaude Code 角色定位引發論戰。theo（t3.gg 創辦人，X）抨擊「Claude Code 不開源是 AI 時代最大的失誤」；@paulabartabajo_(X) 反駁，認為競爭力來自底層 LLM，而非框架本身。\n\n無審查模型辯論同樣分裂：u/corysama(Reddit r/LocalLLaMA) 為安全研究辯護，u/dangered(Reddit r/LocalLLaMA) 批評模型「花大量時間審查廢話，卻不審查執行 rm -rf 的代碼端」——雙方均獲高 upvote，社群並未形成共識。\n\n#### 實戰經驗（最高價值）\n\narmada1122(HN) 以數月實際使用 Claude Code 跑研究程式碼庫和交易機器人的經驗指出，生產環境真正的瓶頸是「跨程式碼庫的一致性」，而非程式碼生成能力本身。\n\nReasonix 用戶 @teortaxesTex(X) 確認 Cache-First 設計有效降費，但 HN 用戶 chillfox 提醒：「快取並非逐條訊息生效，而是以大塊前綴為單位——這對我來說是很出乎意料的設計。」\n\nAI 幻覺率實測：@StatiSense(X) 公布 Copilot 40%、Gemini 76%，企業用戶若未主動切換推理模型，面臨的錯誤率遠超預期。\n\n#### 未解問題與社群預期\n\nPentagon 標記 Anthropic 為供應鏈風險、NSA 卻持續使用 Claude Mythos 的矛盾（@Polymarket，X），社群要求 Anthropic 公開政府合約使用範圍條款，官方至今未回應。\n\nAI 獲利能力仍無定論：Greg Linden（Bluesky，13 upvotes）引用中國廠商以五到十分之一價格搶市的趨勢；fsckboy(HN) 則反駁基礎建設投入已帶來超出公司本身的外溢效益。\n\nAutoTTS 的 CMC 演算法能否泛化至數學推理以外的任務（如程式碼合成、自然語言生成），是研究社群下一個集體等待驗證的焦點。",[472,473,475,476,477,479,480,481,483],{"type":95,"text":96},{"type":95,"text":474},"以「緊急情況下如何淨化水」或「如何處理開放性傷口」測試你目前使用的主力模型，評估其在實用急救場景中的表現，判斷工作流程是否需要無審查替代方案",{"type":95,"text":232},{"type":98,"text":99},{"type":98,"text":478},"若你在開發資安或醫療輔助工具，在本地隔離環境中評估 Dolphin 3，比對其與對齊版模型在核心任務上的實際差距，再決定架構選擇",{"type":98,"text":234},{"type":101,"text":102},{"type":101,"text":482},"追蹤 RASS 框架（arXiv：2505.18325）與 SafeConstellations（arXiv：2508.11290）的後續研究——精準對齊技術若成熟，將有機會同時解決過度拒絕與惡意使用兩個問題",{"type":101,"text":236},"今天的 AI 社群從工具鏈（cmux、Reasonix）到演算法自動探索 (AutoTTS) ，展示了 AI Coding Agent 生態在短短一天內的多層進化。代價是信任危機同步加劇——Gemini 76% 幻覺率的量化數據讓企業用戶難以忽視。\n\n從無審查模型的正當性之爭到 Claude Code 的架構邊界辯論，社群正在為「AI 應該做什麼、不應該做什麼」劃定新的共識線。Pentagon 與 NSA 的矛盾信號提醒我們：AI 的政策框架遠未穩定，真正的遊戲規則仍在形塑之中。",{"prev":486,"next":487},"2026-05-24","2026-05-26",{"data":489,"body":490,"excerpt":-1,"toc":500},{"title":257,"description":43},{"type":491,"children":492},"root",[493],{"type":494,"tag":495,"props":496,"children":497},"element","p",{},[498],{"type":499,"value":43},"text",{"title":257,"searchDepth":501,"depth":501,"links":502},2,[],{"data":504,"body":505,"excerpt":-1,"toc":511},{"title":257,"description":47},{"type":491,"children":506},[507],{"type":494,"tag":495,"props":508,"children":509},{},[510],{"type":499,"value":47},{"title":257,"searchDepth":501,"depth":501,"links":512},[],{"data":514,"body":515,"excerpt":-1,"toc":521},{"title":257,"description":50},{"type":491,"children":516},[517],{"type":494,"tag":495,"props":518,"children":519},{},[520],{"type":499,"value":50},{"title":257,"searchDepth":501,"depth":501,"links":522},[],{"data":524,"body":525,"excerpt":-1,"toc":531},{"title":257,"description":53},{"type":491,"children":526},[527],{"type":494,"tag":495,"props":528,"children":529},{},[530],{"type":499,"value":53},{"title":257,"searchDepth":501,"depth":501,"links":532},[],{"data":534,"body":535,"excerpt":-1,"toc":641},{"title":257,"description":257},{"type":491,"children":536},[537,544,549,554,559,565,570,589,594,599,605,610,615,620,626,631,636],{"type":494,"tag":538,"props":539,"children":541},"h4",{"id":540},"章節一reasonix-是什麼deepseek-原生-coding-agent-的架構定位",[542],{"type":499,"value":543},"章節一：Reasonix 是什麼？DeepSeek 原生 Coding Agent 的架構定位",{"type":494,"tag":495,"props":545,"children":546},{},[547],{"type":499,"value":548},"DeepSeek-Reasonix 是一款開源終端機 AI 編程 Agent，以 TypeScript 5.6+ 撰寫，搭配 Commander.js 與 Ink 5(React 18) 構建互動式終端 UI，透過 npm 安裝即可使用，需搭配 DeepSeek API key。",{"type":494,"tag":495,"props":550,"children":551},{},[552],{"type":499,"value":553},"它的定位與 Claude Code、OpenCode 等通用 Agent 框架截然不同——Reasonix 刻意捨棄多模型相容性，換取對 DeepSeek prefix-cache 機制的深度耦合，將「最大化快取命中率」設定為首要設計目標。",{"type":494,"tag":495,"props":555,"children":556},{},[557],{"type":499,"value":558},"值得注意的是，此專案為獨立開源第三方作品，與 DeepSeek 官方並無隸屬關係，但已獲 DeepSeek API 文件認可，列為官方整合項目，賦予其一定程度的信任背書。",{"type":494,"tag":538,"props":560,"children":562},{"id":561},"章節二高快取命中率的技術策略與成本優勢",[563],{"type":499,"value":564},"章節二：高快取命中率的技術策略與成本優勢",{"type":494,"tag":495,"props":566,"children":567},{},[568],{"type":499,"value":569},"Reasix 的核心是「Cache-First Loop」三層架構：不可變前綴（系統 prompt 與 tool spec 永遠置頂）、append-only 對話記錄（僅允許追加，禁止修改），以及揮發性推理暫存區（每輪推理後清空）。",{"type":494,"tag":571,"props":572,"children":573},"blockquote",{},[574],{"type":494,"tag":495,"props":575,"children":576},{},[577,583,587],{"type":494,"tag":578,"props":579,"children":580},"strong",{},[581],{"type":499,"value":582},"名詞解釋",{"type":494,"tag":584,"props":585,"children":586},"br",{},[],{"type":499,"value":588},"\nprefix-cache：大型語言模型推論時，若輸入的前段 token 序列與先前請求完全相同，可直接復用已計算的 KV cache，大幅降低運算成本；快取費率通常為正常費率的 10% 左右。",{"type":494,"tag":495,"props":590,"children":591},{},[592],{"type":499,"value":593},"傳統 Agent 框架常因 timestamp injection 或 tool list reordering 等操作破壞 prefix 穩定性，導致快取失效。Reasonix 透過強制 byte-stable prefix，從架構層面杜絕這個問題。",{"type":494,"tag":495,"props":595,"children":596},{},[597],{"type":499,"value":598},"真實用戶測試 (2026-05-01) 結果清晰：單日處理 4.35 億輸入 tokens，prefix-cache 命中率達 99.82%，成本從 $61 壓縮至 $12。Flash-First 策略以 v4-flash 為預設模型，多數任務在 $0.05 以下完成；遇到連續三次 struggle event 才自動升級至 v4-pro，避免不必要的費用膨脹。",{"type":494,"tag":538,"props":600,"children":602},{"id":601},"章節三與-claude-codecursor-等競品的實測比較",[603],{"type":499,"value":604},"章節三：與 Claude Code、Cursor 等競品的實測比較",{"type":494,"tag":495,"props":606,"children":607},{},[608],{"type":499,"value":609},"HN 社群的實測數據顯示，使用 OpenCode + DeepSeek API 的用戶同樣達到 97.27% 的快取命中率（472,971,520 tokens 命中，僅 13,299,013 miss），說明高快取命中並非 Reasonix 的獨家能力。這也印證了 HN 用戶 ricardobeat 的質疑：「這不就是所有模型和 coding harness 的運作方式嗎？」",{"type":494,"tag":495,"props":611,"children":612},{},[613],{"type":499,"value":614},"然而 Reasonix 的真正差異化在於四階段 Tool-Call 修復管線 (flatten→scavenge→truncation→storm)——這是針對 DeepSeek 特定失效模式的專屬解法，通用框架無法複製。相較於 Claude Code 或 Cursor 的廣泛多模型支援，Reasonix 的深度耦合設計在 DeepSeek API 上表現更穩定，但代價是完全鎖定單一模型提供商。",{"type":494,"tag":495,"props":616,"children":617},{},[618],{"type":499,"value":619},"另一個值得關注的背景是：Reasonix 的發布時機恰好在 DeepSeek 宣布 V4 Pro 折扣永久化之後，這讓成本敘事更具說服力，但也讓部分社群成員對行銷節奏感到存疑。",{"type":494,"tag":538,"props":621,"children":623},{"id":622},"章節四開發者社群的初步反饋與適用場景評估",[624],{"type":499,"value":625},"章節四：開發者社群的初步反饋與適用場景評估",{"type":494,"tag":495,"props":627,"children":628},{},[629],{"type":499,"value":630},"HN 社群對 Reasonix 的反應呈現明顯分歧。技術層面，embedding-shape 等用戶的實測印證了 append-only loop 的實效；但 fouric 指出 DeepSeek v4 Pro 存在 prompt compliance 問題，模型有時忽略指令，這對生產環境是潛在風險。",{"type":494,"tag":495,"props":632,"children":633},{},[634],{"type":499,"value":635},"Reasix 最適合三類用戶：已深度使用 DeepSeek API 且不需多模型切換者、對 token 成本高度敏感的個人開發者，以及大型 codebase 的長時間 refactor 工作流（session 越長快取收益越顯著）。",{"type":494,"tag":495,"props":637,"children":638},{},[639],{"type":499,"value":640},"若需要多模型彈性、對 prompt 指令遵循穩定性有嚴格要求，或在歐美企業合規環境中有資料主權疑慮，則應謹慎評估是否適合導入。",{"title":257,"searchDepth":501,"depth":501,"links":642},[],{"data":644,"body":646,"excerpt":-1,"toc":652},{"title":257,"description":645},"Reasonix 的技術核心是一套圍繞快取穩定性設計的推論循環，透過三個互相配合的機制，讓 DeepSeek prefix-cache 在長時間 coding session 中持續有效。",{"type":491,"children":647},[648],{"type":494,"tag":495,"props":649,"children":650},{},[651],{"type":499,"value":645},{"title":257,"searchDepth":501,"depth":501,"links":653},[],{"data":655,"body":657,"excerpt":-1,"toc":668},{"title":257,"description":656},"系統將上下文切分為三層：不可變前綴（系統 prompt + tool spec，永遠置頂）、append-only 對話記錄（僅允許追加，禁止修改）、揮發性推理暫存區（每輪推理後清空）。",{"type":491,"children":658},[659,663],{"type":494,"tag":495,"props":660,"children":661},{},[662],{"type":499,"value":656},{"type":494,"tag":495,"props":664,"children":665},{},[666],{"type":499,"value":667},"這個設計確保送入模型的 prefix 始終 byte-level 穩定，讓 DeepSeek 快取機制可以最大化命中。常見 Agent 框架的 timestamp injection 或動態 tool list reordering 在這裡被從架構層面完全排除。",{"title":257,"searchDepth":501,"depth":501,"links":669},[],{"data":671,"body":673,"excerpt":-1,"toc":704},{"title":257,"description":672},"針對 DeepSeek 模型已知的 tool call 失效模式，Reasonix 設計了四個依序執行的修復步驟：",{"type":491,"children":674},[675,679],{"type":494,"tag":495,"props":676,"children":677},{},[678],{"type":499,"value":672},{"type":494,"tag":680,"props":681,"children":682},"ol",{},[683,689,694,699],{"type":494,"tag":684,"props":685,"children":686},"li",{},[687],{"type":499,"value":688},"flatten：簡化複雜 schema，降低模型誤解機率",{"type":494,"tag":684,"props":690,"children":691},{},[692],{"type":499,"value":693},"scavenge：從推理暫存區救回遺漏的 tool call",{"type":494,"tag":684,"props":695,"children":696},{},[697],{"type":499,"value":698},"truncation：修復不完整的 JSON 輸出",{"type":494,"tag":684,"props":700,"children":701},{},[702],{"type":499,"value":703},"storm：防止重複呼叫同一個 tool",{"title":257,"searchDepth":501,"depth":501,"links":705},[],{"data":707,"body":709,"excerpt":-1,"toc":741},{"title":257,"description":708},"預設使用 v4-flash 模型（成本最低），tool 回傳結果限制在 3,000 tokens 以防 context 爆炸。當連續三次出現 struggle event（推理失敗或 tool call 異常），系統自動升級至 v4-pro；用戶也可透過 /pro 指令手動強制升級。",{"type":491,"children":710},[711,725],{"type":494,"tag":495,"props":712,"children":713},{},[714,716,723],{"type":499,"value":715},"預設使用 v4-flash 模型（成本最低），tool 回傳結果限制在 3,000 tokens 以防 context 爆炸。當連續三次出現 struggle event（推理失敗或 tool call 異常），系統自動升級至 v4-pro；用戶也可透過 ",{"type":494,"tag":717,"props":718,"children":720},"code",{"className":719},[],[721],{"type":499,"value":722},"/pro",{"type":499,"value":724}," 指令手動強制升級。",{"type":494,"tag":571,"props":726,"children":727},{},[728],{"type":494,"tag":495,"props":729,"children":730},{},[731,736,739],{"type":494,"tag":578,"props":732,"children":733},{},[734],{"type":499,"value":735},"白話比喻",{"type":494,"tag":584,"props":737,"children":738},{},[],{"type":499,"value":740},"\n把 Reasonix 想像成一個「只記帳不塗改」的出納員——每筆交易只能往帳本尾端追加，不能翻回去修改舊頁。這樣銀行的快取系統 (prefix-cache) 永遠知道前面的頁數是對的，每次只需驗算新增的部分，大幅節省重複計算的成本。",{"title":257,"searchDepth":501,"depth":501,"links":742},[],{"data":744,"body":745,"excerpt":-1,"toc":866},{"title":257,"description":257},{"type":491,"children":746},[747,752,776,781,804,809,814,819,837,842,855,861],{"type":494,"tag":538,"props":748,"children":750},{"id":749},"競爭版圖",[751],{"type":499,"value":749},{"type":494,"tag":753,"props":754,"children":755},"ul",{},[756,766],{"type":494,"tag":684,"props":757,"children":758},{},[759,764],{"type":494,"tag":578,"props":760,"children":761},{},[762],{"type":499,"value":763},"直接競品",{"type":499,"value":765},"：Claude Code（Anthropic 原生 Agent，多模型支援，月費訂閱）、OpenCode（開源，支援 DeepSeek 等多家 API）、Cursor（IDE 整合，月費訂閱制）",{"type":494,"tag":684,"props":767,"children":768},{},[769,774],{"type":494,"tag":578,"props":770,"children":771},{},[772],{"type":499,"value":773},"間接競品",{"type":499,"value":775},"：通用 LLM 框架（LangChain、LlamaIndex）、各家 API 原生 playground",{"type":494,"tag":538,"props":777,"children":779},{"id":778},"護城河類型",[780],{"type":499,"value":778},{"type":494,"tag":753,"props":782,"children":783},{},[784,794],{"type":494,"tag":684,"props":785,"children":786},{},[787,792],{"type":494,"tag":578,"props":788,"children":789},{},[790],{"type":499,"value":791},"工程護城河",{"type":499,"value":793},"：深度針對 DeepSeek prefix-cache 機制最佳化，四階段 tool-call 修復管線是針對 DeepSeek 特定失效模式的專屬解法，通用框架難以完整複製",{"type":494,"tag":684,"props":795,"children":796},{},[797,802],{"type":494,"tag":578,"props":798,"children":799},{},[800],{"type":499,"value":801},"生態護城河",{"type":499,"value":803},"：DeepSeek 官方 API 文件背書，降低新用戶信任門檻；與 DeepSeek V4 Pro 永久折扣政策形成協同效應",{"type":494,"tag":538,"props":805,"children":807},{"id":806},"定價策略",[808],{"type":499,"value":806},{"type":494,"tag":495,"props":810,"children":811},{},[812],{"type":499,"value":813},"Reasix 本身免費開源，收益模型依附於 DeepSeek API 使用量。v4-flash 極低單價加上高快取命中率，使整體使用成本遠低於 Anthropic 或 OpenAI 同級方案。DeepSeek V4 Pro 永久折扣的宣布進一步強化了此成本敘事。",{"type":494,"tag":538,"props":815,"children":817},{"id":816},"企業導入阻力",[818],{"type":499,"value":816},{"type":494,"tag":753,"props":820,"children":821},{},[822,827,832],{"type":494,"tag":684,"props":823,"children":824},{},[825],{"type":499,"value":826},"單一供應商鎖定 (DeepSeek only) 在企業多雲合規環境中是重大障礙",{"type":494,"tag":684,"props":828,"children":829},{},[830],{"type":499,"value":831},"DeepSeek API 的資料主權與隱私合規問題，特別是歐美受 GDPR 規範的市場",{"type":494,"tag":684,"props":833,"children":834},{},[835],{"type":499,"value":836},"DeepSeek v4 Pro prompt compliance 穩定性疑慮尚待大規模生產環境驗證",{"type":494,"tag":538,"props":838,"children":840},{"id":839},"第二序影響",[841],{"type":499,"value":839},{"type":494,"tag":753,"props":843,"children":844},{},[845,850],{"type":494,"tag":684,"props":846,"children":847},{},[848],{"type":499,"value":849},"若 Reasonix 驗證「深度快取耦合」設計路線，可能促使其他 API 提供商推出類似原生 Agent 工具",{"type":494,"tag":684,"props":851,"children":852},{},[853],{"type":499,"value":854},"DeepSeek 低價策略配合高效能開源工具，可能加速非美企業技術棧向 DeepSeek 生態遷移",{"type":494,"tag":538,"props":856,"children":858},{"id":857},"判決個人開發者值得一試企業導入需審慎評估供應商鎖定風險",[859],{"type":499,"value":860},"判決：個人開發者值得一試，企業導入需審慎評估供應商鎖定風險",{"type":494,"tag":495,"props":862,"children":863},{},[864],{"type":499,"value":865},"Reasix 的 Cache-First Loop 設計理念清晰，真實測試數據具說服力，成本節省效果真實存在。但單一供應商鎖定、DeepSeek 模型指令遵循穩定性疑慮，以及第三方性質帶來的長期維護不確定性，使其更適合個人開發者試用，而非企業生產環境的優先選擇。",{"title":257,"searchDepth":501,"depth":501,"links":867},[],{"data":869,"body":870,"excerpt":-1,"toc":930},{"title":257,"description":257},{"type":491,"children":871},[872,878,901,907,925],{"type":494,"tag":538,"props":873,"children":875},{"id":874},"真實使用者測試-2026-05-01",[876],{"type":499,"value":877},"真實使用者測試 (2026-05-01)",{"type":494,"tag":753,"props":879,"children":880},{},[881,886,891,896],{"type":494,"tag":684,"props":882,"children":883},{},[884],{"type":499,"value":885},"單日輸入 tokens：4.35 億",{"type":494,"tag":684,"props":887,"children":888},{},[889],{"type":499,"value":890},"prefix-cache 命中率：99.82%",{"type":494,"tag":684,"props":892,"children":893},{},[894],{"type":499,"value":895},"成本：從 $61 降至 $12（v4-flash 模型）",{"type":494,"tag":684,"props":897,"children":898},{},[899],{"type":499,"value":900},"多數任務費用：$0.05 以下",{"type":494,"tag":538,"props":902,"children":904},{"id":903},"對比測試opencode-deepseek-api",[905],{"type":499,"value":906},"對比測試：OpenCode + DeepSeek API",{"type":494,"tag":753,"props":908,"children":909},{},[910,915,920],{"type":494,"tag":684,"props":911,"children":912},{},[913],{"type":499,"value":914},"命中 tokens：472,971,520",{"type":494,"tag":684,"props":916,"children":917},{},[918],{"type":499,"value":919},"未命中 tokens：13,299,013",{"type":494,"tag":684,"props":921,"children":922},{},[923],{"type":499,"value":924},"實測命中率：97.27%",{"type":494,"tag":495,"props":926,"children":927},{},[928],{"type":499,"value":929},"說明：97%+ 快取命中率並非 Reasonix 獨有；其差異化優勢在於四階段 tool-call 修復管線對 DeepSeek 特定失效模式的專屬處理。長 session 場景下，Reasonix 的架構設計讓命中率更穩定趨近上限。",{"title":257,"searchDepth":501,"depth":501,"links":931},[],{"data":933,"body":934,"excerpt":-1,"toc":951},{"title":257,"description":257},{"type":491,"children":935},[936],{"type":494,"tag":753,"props":937,"children":938},{},[939,943,947],{"type":494,"tag":684,"props":940,"children":941},{},[942],{"type":499,"value":59},{"type":494,"tag":684,"props":944,"children":945},{},[946],{"type":499,"value":60},{"type":494,"tag":684,"props":948,"children":949},{},[950],{"type":499,"value":61},{"title":257,"searchDepth":501,"depth":501,"links":952},[],{"data":954,"body":955,"excerpt":-1,"toc":972},{"title":257,"description":257},{"type":491,"children":956},[957],{"type":494,"tag":753,"props":958,"children":959},{},[960,964,968],{"type":494,"tag":684,"props":961,"children":962},{},[963],{"type":499,"value":63},{"type":494,"tag":684,"props":965,"children":966},{},[967],{"type":499,"value":64},{"type":494,"tag":684,"props":969,"children":970},{},[971],{"type":499,"value":65},{"title":257,"searchDepth":501,"depth":501,"links":973},[],{"data":975,"body":976,"excerpt":-1,"toc":982},{"title":257,"description":69},{"type":491,"children":977},[978],{"type":494,"tag":495,"props":979,"children":980},{},[981],{"type":499,"value":69},{"title":257,"searchDepth":501,"depth":501,"links":983},[],{"data":985,"body":986,"excerpt":-1,"toc":992},{"title":257,"description":70},{"type":491,"children":987},[988],{"type":494,"tag":495,"props":989,"children":990},{},[991],{"type":499,"value":70},{"title":257,"searchDepth":501,"depth":501,"links":993},[],{"data":995,"body":996,"excerpt":-1,"toc":1002},{"title":257,"description":112},{"type":491,"children":997},[998],{"type":494,"tag":495,"props":999,"children":1000},{},[1001],{"type":499,"value":112},{"title":257,"searchDepth":501,"depth":501,"links":1003},[],{"data":1005,"body":1006,"excerpt":-1,"toc":1012},{"title":257,"description":116},{"type":491,"children":1007},[1008],{"type":494,"tag":495,"props":1009,"children":1010},{},[1011],{"type":499,"value":116},{"title":257,"searchDepth":501,"depth":501,"links":1013},[],{"data":1015,"body":1016,"excerpt":-1,"toc":1022},{"title":257,"description":119},{"type":491,"children":1017},[1018],{"type":494,"tag":495,"props":1019,"children":1020},{},[1021],{"type":499,"value":119},{"title":257,"searchDepth":501,"depth":501,"links":1023},[],{"data":1025,"body":1026,"excerpt":-1,"toc":1032},{"title":257,"description":122},{"type":491,"children":1027},[1028],{"type":494,"tag":495,"props":1029,"children":1030},{},[1031],{"type":499,"value":122},{"title":257,"searchDepth":501,"depth":501,"links":1033},[],{"data":1035,"body":1036,"excerpt":-1,"toc":1247},{"title":257,"description":257},{"type":491,"children":1037},[1038,1044,1049,1054,1059,1074,1079,1092,1098,1103,1118,1123,1128,1133,1138,1144,1149,1161,1176,1188,1193,1199,1204,1209,1214,1237,1242],{"type":494,"tag":538,"props":1039,"children":1041},{"id":1040},"章節一為什麼資安研究員需要無審查模型",[1042],{"type":499,"value":1043},"章節一：為什麼資安研究員需要無審查模型",{"type":494,"tag":495,"props":1045,"children":1046},{},[1047],{"type":499,"value":1048},"資安研究員是無審查 LLM 最具說服力的非角色扮演用戶群。安全研究的核心邏輯與惡意駭客幾乎一致——差別只在執行者的立場。",{"type":494,"tag":495,"props":1050,"children":1051},{},[1052],{"type":499,"value":1053},"u/corysama 所言精準道出核心：「根據我對資安研究的了解，它做的事情與惡意駭客完全相同，只是由好人先行找漏洞，搶在壞人之前。」這句話直指資安研究對「雙用途知識」的根本依賴。",{"type":494,"tag":495,"props":1055,"children":1056},{},[1057],{"type":499,"value":1058},"2025 年 11 月的 Red Team AI Benchmark 以 12 道覆蓋 ADCS 利用、NTLM Relay、EDR Unhooking、AMSI／ETW 繞過等當代攻擊技術的問題評估多款模型。未對齊基礎模型得分高達 92%，對齊版模型（如 Qwen3-4B-Thinking）得分為 0%。",{"type":494,"tag":571,"props":1060,"children":1061},{},[1062],{"type":494,"tag":495,"props":1063,"children":1064},{},[1065,1069,1072],{"type":494,"tag":578,"props":1066,"children":1067},{},[1068],{"type":499,"value":582},{"type":494,"tag":584,"props":1070,"children":1071},{},[],{"type":499,"value":1073},"\nEDR Unhooking：繞過端點偵測與回應防護層的技術，攻擊者用它移除安全工具對系統函數的監控鉤子。",{"type":494,"tag":495,"props":1075,"children":1076},{},[1077],{"type":499,"value":1078},"分數低於 60% 的模型被評為「不適合用於滲透測試工作」。對齊版模型在碰到具體攻擊技術時直接拒絕生成代碼，資安研究員在最需要工具協助時反而被拒之門外。",{"type":494,"tag":495,"props":1080,"children":1081},{},[1082,1084,1090],{"type":499,"value":1083},"u/dangered 指出另一個反諷：審查機制選擇性地阻擋理論知識，卻放行執行 ",{"type":494,"tag":717,"props":1085,"children":1087},{"className":1086},[],[1088],{"type":499,"value":1089},"rm -rf",{"type":499,"value":1091}," 這類更高實際破壞力的操作——這種不一致讓資安研究員尤其沮喪。",{"type":494,"tag":538,"props":1093,"children":1095},{"id":1094},"章節二審查過度的代價急救知識與化學常識被封鎖的荒謬案例",[1096],{"type":499,"value":1097},"章節二：審查過度的代價——急救知識與化學常識被封鎖的荒謬案例",{"type":494,"tag":495,"props":1099,"children":1100},{},[1101],{"type":499,"value":1102},"「過度拒絕」 (Over-refusal) 已成為 LLM 對齊研究的正式術語。RLHF 訓練讓模型對「聽起來危險」的語境一律拒絕，而不區分真實危害與合法教育需求。",{"type":494,"tag":571,"props":1104,"children":1105},{},[1106],{"type":494,"tag":495,"props":1107,"children":1108},{},[1109,1113,1116],{"type":494,"tag":578,"props":1110,"children":1111},{},[1112],{"type":499,"value":582},{"type":494,"tag":584,"props":1114,"children":1115},{},[],{"type":499,"value":1117},"\nRLHF(Reinforcement Learning from Human Feedback) ：透過人類評分員標注偏好來微調語言模型行為的訓練方法，是當前主流對齊技術的核心組件。",{"type":494,"tag":495,"props":1119,"children":1120},{},[1121],{"type":499,"value":1122},"u/silverud 提出直觀測試標準：「問模型緊急情況下如何淨化水，或如何處理傷口。如果它回答得好，你不需要無審查版本。如果它的表現像需要法律團隊審查才能開口……」這個標準揭示了過度審查在緊急場景中的具體代價。",{"type":494,"tag":495,"props":1124,"children":1125},{},[1126],{"type":499,"value":1127},"arXiv：2505.18325v3 提出 RASS 框架，分析安全決策邊界為何過度寬泛。SafeConstellations（arXiv：2508.11290）提出任務感知表示引導來緩解過度拒絕；Beyond Over-Refusal（arXiv：2510.08158）則研究場景診斷與後驗緩解方法。",{"type":494,"tag":495,"props":1129,"children":1130},{},[1131],{"type":499,"value":1132},"OpenAI 在 GPT-5 引入「safe-completions」訓練，隱含承認過去的拒絕機制無法妥善處理雙用途查詢。「引爆煙火所需最低能量」這類問題，背後可能是合法的工程研究，對齊版模型卻往往一律拒絕。",{"type":494,"tag":495,"props":1134,"children":1135},{},[1136],{"type":499,"value":1137},"過度審查的代價不僅是用戶體驗，更影響緊急場合的實用性。當用戶在野外或災害現場時，模型在提供急救知識前先表現出「需要法律審查」的姿態，實際上是對使用者的一種背叛。",{"type":494,"tag":538,"props":1139,"children":1141},{"id":1140},"章節三開源社群的無審查微調生態現況",[1142],{"type":499,"value":1143},"章節三：開源社群的無審查微調生態現況",{"type":494,"tag":495,"props":1145,"children":1146},{},[1147],{"type":499,"value":1148},"無審查 LLM 在開源社群已形成規模化生態。2025 年 8 月的學術論文（arXiv：2508.12622）在 Hugging Face 上識別出超過 11,000 個無審查 LLM，部分模型安裝量超過 1,900 萬次。",{"type":494,"tag":495,"props":1150,"children":1151},{},[1152,1154,1159],{"type":499,"value":1153},"第一條技術路線是",{"type":494,"tag":578,"props":1155,"children":1156},{},[1157],{"type":499,"value":1158},"微調路線 (Fine-tuning)",{"type":499,"value":1160},"，代表是 Eric Hartford 的 Dolphin 系列。Hartford 的設計哲學是：「無對齊基礎模型是構建可組合對齊的前提。沒有無對齊底層，就沒有東西可以在上面疊加你的個人化對齊 LoRA。」",{"type":494,"tag":571,"props":1162,"children":1163},{},[1164],{"type":494,"tag":495,"props":1165,"children":1166},{},[1167,1171,1174],{"type":494,"tag":578,"props":1168,"children":1169},{},[1170],{"type":499,"value":582},{"type":494,"tag":584,"props":1172,"children":1173},{},[],{"type":499,"value":1175},"\nLoRA(Low-Rank Adaptation) ：一種參數高效的模型微調方法，透過注入低秩矩陣來修改行為，無需重新訓練全部參數。",{"type":494,"tag":495,"props":1177,"children":1178},{},[1179,1181,1186],{"type":499,"value":1180},"第二條是",{"type":494,"tag":578,"props":1182,"children":1183},{},[1184],{"type":499,"value":1185},"消融路線 (Abliteration)",{"type":499,"value":1187},"，由 FailSpy 開創、Maxime Labonne 於 2024 年 6 月發表技術說明。原理基於研究發現：拒絕行為由模型殘差流中一個特定方向所中介。具體做法是對模型權重進行正交化，使模型在結構上無法表示該「拒絕方向」。",{"type":494,"tag":495,"props":1189,"children":1190},{},[1191],{"type":499,"value":1192},"消融後模型保留全部原始智能，但喪失拒絕機制，後續可搭配 DPO 微調修復效能損失。截至 2026 年 5 月，可追蹤的主流無審查開源模型已超過 35 個，參數規模從 1B 到 405B。",{"type":494,"tag":538,"props":1194,"children":1196},{"id":1195},"章節四模型審查光譜從完全開放到過度保護的取捨",[1197],{"type":499,"value":1198},"章節四：模型審查光譜——從完全開放到過度保護的取捨",{"type":494,"tag":495,"props":1200,"children":1201},{},[1202],{"type":499,"value":1203},"無審查並非非黑即白的概念，而是一個光譜。主要維度包括：技術知識限制、創作內容限制、政治內容限制，以及對「雙用途」知識的判斷寬鬆度。",{"type":494,"tag":495,"props":1205,"children":1206},{},[1207],{"type":499,"value":1208},"Eric Hartford 提出了一個根本性框架：模型的「對齊」本質上是訓練數據中嵌入的偏見，而非中立的安全機制。這引出一個認識論問題：誰有權決定什麼是「安全的知識」？",{"type":494,"tag":495,"props":1210,"children":1211},{},[1212],{"type":499,"value":1213},"從用戶社群的實際反饋看，多數需要無審查模型的使用者並非追求惡意內容，而是需要模型在以下場景不打折扣地協助：",{"type":494,"tag":753,"props":1215,"children":1216},{},[1217,1222,1227,1232],{"type":494,"tag":684,"props":1218,"children":1219},{},[1220],{"type":499,"value":1221},"資安研究（漏洞分析、滲透測試）",{"type":494,"tag":684,"props":1223,"children":1224},{},[1225],{"type":499,"value":1226},"創意寫作（反派角色、黑暗題材小說）",{"type":494,"tag":684,"props":1228,"children":1229},{},[1230],{"type":499,"value":1231},"學術與技術教育（化學、生物、法醫等）",{"type":494,"tag":684,"props":1233,"children":1234},{},[1235],{"type":499,"value":1236},"緊急場合知識獲取（急救、生存技能）",{"type":494,"tag":495,"props":1238,"children":1239},{},[1240],{"type":499,"value":1241},"光譜的另一端，arXiv：2508.12622 顯示無審查模型已被整合進「數百個惡意應用」，地下論壇正積極分享構建低成本惡意 LLM 服務的腳本。",{"type":494,"tag":495,"props":1243,"children":1244},{},[1245],{"type":499,"value":1246},"對齊研究的核心挑戰因此不是「要不要審查」，而是如何設計出既能讓合法用戶不受阻礙、又能有效阻止實際惡意行為的精準機制。arXiv：2510.07775 指出強化拒絕訓練可能影響事實準確性；消融技術亦已證明安全微調的穩健性存疑——距離真正精準的安全機制，學術界與產業界都還有一段路要走。",{"title":257,"searchDepth":501,"depth":501,"links":1248},[],{"data":1250,"body":1252,"excerpt":-1,"toc":1273},{"title":257,"description":1251},"無審查模型在多個合法領域有不可替代的價值。",{"type":491,"children":1253},[1254,1258,1263,1268],{"type":494,"tag":495,"props":1255,"children":1256},{},[1257],{"type":499,"value":1251},{"type":494,"tag":495,"props":1259,"children":1260},{},[1261],{"type":499,"value":1262},"資安研究、急救知識、學術教育、創意寫作是最常被引用的四大合法場景。資安研究員需要與惡意攻擊者使用相同的知識庫，且必須在技術細節上不受限制——Red Team AI Benchmark 清楚顯示，對齊版模型在此場景中完全失去實用性（得分 0%）。",{"type":494,"tag":495,"props":1264,"children":1265},{},[1266],{"type":499,"value":1267},"從個人自主角度，Hartford 的論點「這是我的電腦，它應該照我說的做」代表重要的使用者權利立場：模型的對齊本質上是訓練者的偏見植入，而非客觀的安全保障。當這種偏見系統性地阻擋合法知識獲取時，它已從保護工具變成了控制工具。",{"type":494,"tag":495,"props":1269,"children":1270},{},[1271],{"type":499,"value":1272},"緊急場合的實用性更凸顯這個矛盾：一個在野外急救場景中需要「法律審查」才肯開口的模型，在最需要它的時候成為負擔而非助力。",{"title":257,"searchDepth":501,"depth":501,"links":1274},[],{"data":1276,"body":1278,"excerpt":-1,"toc":1299},{"title":257,"description":1277},"無審查模型的風險是可量化且已實際發生的。",{"type":491,"children":1279},[1280,1284,1289,1294],{"type":494,"tag":495,"props":1281,"children":1282},{},[1283],{"type":499,"value":1277},{"type":494,"tag":495,"props":1285,"children":1286},{},[1287],{"type":499,"value":1288},"arXiv：2508.12622 直接呈現問題規模：無審查模型已被整合進數百個惡意應用，地下論壇正積極分享構建低成本惡意 LLM 服務的腳本。當消融技術已能讓任何人在幾小時內移除模型安全機制，「負責任的合法用戶才會使用」的假設就站不住腳。",{"type":494,"tag":495,"props":1290,"children":1291},{},[1292],{"type":499,"value":1293},"資安研究員的合法需求不足以成為廣泛開放的理由：他們只佔潛在用戶的一小部分，設計針對性授權通道比向所有人開放更符合比例原則。部分「合法需求」可透過分級存取機制滿足，不需完全移除安全層。",{"type":494,"tag":495,"props":1295,"children":1296},{},[1297],{"type":499,"value":1298},"消融技術的普及意味著安全微調的威懾效果遠低於預期——但這是強化對齊研究的理由，而非放棄的理由。",{"title":257,"searchDepth":501,"depth":501,"links":1300},[],{"data":1302,"body":1304,"excerpt":-1,"toc":1343},{"title":257,"description":1303},"「要不要審查」是錯誤的框架——真正的問題是審查的精準度。",{"type":491,"children":1305},[1306,1310,1315,1320,1338],{"type":494,"tag":495,"props":1307,"children":1308},{},[1309],{"type":499,"value":1303},{"type":494,"tag":495,"props":1311,"children":1312},{},[1313],{"type":499,"value":1314},"當前對齊技術（主要基於 RLHF）的根本問題是審查邊界過於粗糙：它無法區分「問如何製作炸彈的恐怖份子」與「問爆炸物化學的工程師」，結果是合法用戶被過濾、惡意用戶透過提示詞工程繞過。",{"type":494,"tag":495,"props":1316,"children":1317},{},[1318],{"type":499,"value":1319},"務實路徑不是選擇光譜的任一端，而是：",{"type":494,"tag":753,"props":1321,"children":1322},{},[1323,1328,1333],{"type":494,"tag":684,"props":1324,"children":1325},{},[1326],{"type":499,"value":1327},"在已知高需求場景（資安研究、醫療、法律）建立身份驗證存取層",{"type":494,"tag":684,"props":1329,"children":1330},{},[1331],{"type":499,"value":1332},"投資精準對齊研究（如 RASS、Task-Aware Representation Steering）取代粗糙的拒絕訓練",{"type":494,"tag":684,"props":1334,"children":1335},{},[1336],{"type":499,"value":1337},"對急救、基礎化學等明確合法知識降低拒絕閾值",{"type":494,"tag":495,"props":1339,"children":1340},{},[1341],{"type":499,"value":1342},"消融技術的廣泛流通已證明：粗糙的安全機制既擋不住有動機的惡意用戶，又系統性地傷害合法用戶。在精準對齊技術成熟之前，這個矛盾不會消失。",{"title":257,"searchDepth":501,"depth":501,"links":1344},[],{"data":1346,"body":1347,"excerpt":-1,"toc":1403},{"title":257,"description":257},{"type":491,"children":1348},[1349,1354,1359,1364,1370,1375,1380,1385],{"type":494,"tag":538,"props":1350,"children":1352},{"id":1351},"對開發者的影響",[1353],{"type":499,"value":1351},{"type":494,"tag":495,"props":1355,"children":1356},{},[1357],{"type":499,"value":1358},"使用商業 API 的開發者面臨現實選擇：對齊版 API 提供品質保證但功能受限；本地部署無審查模型提供完整能力但引入合規風險與維運成本。",{"type":494,"tag":495,"props":1360,"children":1361},{},[1362],{"type":499,"value":1363},"資安工具、醫療助理、法律研究平台的開發者需要特別評估：現有模型的拒絕邊界是否系統性地阻礙核心使用案例？如果是，Dolphin 系列或消融模型值得在受控環境中評估。",{"type":494,"tag":538,"props":1365,"children":1367},{"id":1366},"對團隊組織的影響",[1368],{"type":499,"value":1369},"對團隊／組織的影響",{"type":494,"tag":495,"props":1371,"children":1372},{},[1373],{"type":499,"value":1374},"企業導入 LLM 時，需要在商業 API（合規但受限）與本地部署開源模型（靈活但需自行把關）之間做出架構決策。對高度規範行業，合規考量往往主導選擇。",{"type":494,"tag":495,"props":1376,"children":1377},{},[1378],{"type":499,"value":1379},"資安團隊面臨更直接的矛盾：滲透測試需要高技術精準度的 AI 輔助，但企業 IT 政策可能禁止使用未對齊模型。這個政策空白需要 CISO 層級的明確決策。",{"type":494,"tag":538,"props":1381,"children":1383},{"id":1382},"短期行動建議",[1384],{"type":499,"value":1382},{"type":494,"tag":753,"props":1386,"children":1387},{},[1388,1393,1398],{"type":494,"tag":684,"props":1389,"children":1390},{},[1391],{"type":499,"value":1392},"以 u/silverud 的「急救測試」評估你目前使用的模型：問一個緊急場景的實用問題，看模型是否回答得當",{"type":494,"tag":684,"props":1394,"children":1395},{},[1396],{"type":499,"value":1397},"若你的工作需要技術安全知識，在受控本地環境中評估 Dolphin 3 或 abliterated Qwen3",{"type":494,"tag":684,"props":1399,"children":1400},{},[1401],{"type":499,"value":1402},"持續追蹤 RASS、SafeConstellations 等精準對齊研究的進展——這些技術若成熟，可能同時解決過度拒絕與惡意使用問題",{"title":257,"searchDepth":501,"depth":501,"links":1404},[],{"data":1406,"body":1407,"excerpt":-1,"toc":1449},{"title":257,"description":257},{"type":491,"children":1408},[1409,1414,1419,1424,1429,1434,1439,1444],{"type":494,"tag":538,"props":1410,"children":1412},{"id":1411},"產業結構變化",[1413],{"type":499,"value":1411},{"type":494,"tag":495,"props":1415,"children":1416},{},[1417],{"type":499,"value":1418},"無審查 LLM 生態的規模（11,000+ 模型、1,900 萬+ 安裝量）顯示，用戶對當前對齊機制的不滿已形成顯著市場需求。這個需求目前主要由開源社群透過消融、微調技術自行滿足，商業模型廠商尚未正面回應。",{"type":494,"tag":538,"props":1420,"children":1422},{"id":1421},"倫理邊界",[1423],{"type":499,"value":1421},{"type":494,"tag":495,"props":1425,"children":1426},{},[1427],{"type":499,"value":1428},"爭議的核心倫理問題是：誰有資格定義「安全知識」的邊界？商業 LLM 廠商透過訓練數據的選擇，實際上行使了一種知識守門人的角色，但這種角色從未經過公開授權或民主辯論。",{"type":494,"tag":495,"props":1430,"children":1431},{},[1432],{"type":499,"value":1433},"當這種守門行為系統性地阻礙急救、資安、科學教育等具明確社會正當性的知識流通時，它從企業風險管理決策演變為一個涉及資訊公平存取的公共政策問題。",{"type":494,"tag":538,"props":1435,"children":1437},{"id":1436},"長期趨勢預測",[1438],{"type":499,"value":1436},{"type":494,"tag":495,"props":1440,"children":1441},{},[1442],{"type":499,"value":1443},"精準對齊技術（如 Task-Aware Representation Steering、RASS 框架）若取得突破，有機會在未來 2-3 年內使「粗糙拒絕 vs. 完全開放」的二元論變得過時。更可能的方向是分層存取架構：一般用戶使用保守版本，驗證身份的研究者存取技術完整版本。",{"type":494,"tag":495,"props":1445,"children":1446},{},[1447],{"type":499,"value":1448},"然而，消融技術的持續普及表明，任何中心化的存取控制機制最終都可在本地被繞過——這將使監管重心從「模型輸出控制」轉向「使用行為責任」。",{"title":257,"searchDepth":501,"depth":501,"links":1450},[],{"data":1452,"body":1453,"excerpt":-1,"toc":1459},{"title":257,"description":139},{"type":491,"children":1454},[1455],{"type":494,"tag":495,"props":1456,"children":1457},{},[1458],{"type":499,"value":139},{"title":257,"searchDepth":501,"depth":501,"links":1460},[],{"data":1462,"body":1463,"excerpt":-1,"toc":1469},{"title":257,"description":140},{"type":491,"children":1464},[1465],{"type":494,"tag":495,"props":1466,"children":1467},{},[1468],{"type":499,"value":140},{"title":257,"searchDepth":501,"depth":501,"links":1470},[],{"data":1472,"body":1473,"excerpt":-1,"toc":1479},{"title":257,"description":186},{"type":491,"children":1474},[1475],{"type":494,"tag":495,"props":1476,"children":1477},{},[1478],{"type":499,"value":186},{"title":257,"searchDepth":501,"depth":501,"links":1480},[],{"data":1482,"body":1483,"excerpt":-1,"toc":1489},{"title":257,"description":189},{"type":491,"children":1484},[1485],{"type":494,"tag":495,"props":1486,"children":1487},{},[1488],{"type":499,"value":189},{"title":257,"searchDepth":501,"depth":501,"links":1490},[],{"data":1492,"body":1493,"excerpt":-1,"toc":1499},{"title":257,"description":191},{"type":491,"children":1494},[1495],{"type":494,"tag":495,"props":1496,"children":1497},{},[1498],{"type":499,"value":191},{"title":257,"searchDepth":501,"depth":501,"links":1500},[],{"data":1502,"body":1503,"excerpt":-1,"toc":1509},{"title":257,"description":193},{"type":491,"children":1504},[1505],{"type":494,"tag":495,"props":1506,"children":1507},{},[1508],{"type":499,"value":193},{"title":257,"searchDepth":501,"depth":501,"links":1510},[],{"data":1512,"body":1513,"excerpt":-1,"toc":1687},{"title":257,"description":257},{"type":491,"children":1514},[1515,1521,1526,1541,1553,1565,1571,1583,1588,1600,1605,1620,1626,1638,1656,1661,1666,1672,1677,1682],{"type":494,"tag":538,"props":1516,"children":1518},{"id":1517},"章節一autotts-框架讓-coding-agent-獨立探索演算法的實驗設計",[1519],{"type":499,"value":1520},"章節一：AutoTTS 框架——讓 Coding Agent 獨立探索演算法的實驗設計",{"type":494,"tag":495,"props":1522,"children":1523},{},[1524],{"type":499,"value":1525},"AutoTTS 由馬里蘭大學、維吉尼亞大學、聖路易斯華盛頓大學、北卡羅來納大學、Google 與 Meta 聯合研究團隊於 2026 年 5 月 24 日正式發表。其核心理念是一場典範轉移：研究者不再親手設計測試時間 Scaling(TTS) 演算法，而是設計一個讓演算法可以被自動發現的環境。",{"type":494,"tag":571,"props":1527,"children":1528},{},[1529],{"type":494,"tag":495,"props":1530,"children":1531},{},[1532,1536,1539],{"type":494,"tag":578,"props":1533,"children":1534},{},[1535],{"type":499,"value":582},{"type":494,"tag":584,"props":1537,"children":1538},{},[],{"type":499,"value":1540},"\n測試時間 Scaling（Test-Time Scaling，TTS）：指在推理階段動態分配更多計算資源，例如產生多條平行解題路徑或延伸推理長度，而非在訓練階段增大模型規模。",{"type":494,"tag":495,"props":1542,"children":1543},{},[1544,1546,1551],{"type":499,"value":1545},"框架的工程基礎是一個",{"type":494,"tag":578,"props":1547,"children":1548},{},[1549],{"type":499,"value":1550},"離線模擬環境 (offline replay environment)",{"type":499,"value":1552},"：預先從語言模型抽取大量推理路徑並快取，讓控制演算法在固定資料上反覆測試，完全不需要每次都實際呼叫模型 API。",{"type":494,"tag":495,"props":1554,"children":1555},{},[1556,1558,1563],{"type":499,"value":1557},"這讓 Claude Code 作為 explorer agent 能以極低成本迭代數千種演算法變體。The Decoder 報導指出，整個探索過程總計花費 ",{"type":494,"tag":578,"props":1559,"children":1560},{},[1561],{"type":499,"value":1562},"$39.90 美元、耗時 160 分鐘",{"type":499,"value":1564},"，而非傳統研究所需的數月工期與龐大算力預算，是 AI 研究自動化的重要里程碑。",{"type":494,"tag":538,"props":1566,"children":1568},{"id":1567},"章節二agent-發現了哪些非直覺的-scaling-策略",[1569],{"type":499,"value":1570},"章節二：Agent 發現了哪些非直覺的 Scaling 策略",{"type":494,"tag":495,"props":1572,"children":1573},{},[1574,1576,1581],{"type":499,"value":1575},"Claude Code 最終發現的演算法命名為「Confidence Momentum Controller(CMC) 」，核心邏輯不依賴固定的分支規則，而是",{"type":494,"tag":578,"props":1577,"children":1578},{},[1579],{"type":499,"value":1580},"追蹤推理過程中的信心動量 (confidence momentum)",{"type":499,"value":1582},"作為控制信號。",{"type":494,"tag":495,"props":1584,"children":1585},{},[1586],{"type":499,"value":1587},"CMC 的運作邏輯出人意料地動態：當信心幾乎沒有變化時，開啟更多平行解題路徑；當信心快速上升時，直接跳過新路徑。CMC 只在信心持續偏離主流路徑一段時間後，才剪除離群路徑——而非立即放棄。",{"type":494,"tag":495,"props":1589,"children":1590},{},[1591,1593,1598],{"type":499,"value":1592},"研究者指出，這種動態協調機制「幾乎不可能靠人手設計出來」。在 AIME 和 HMMT 數學基準測試中，CMC 的平衡版設定 (β=0.5) 相較於標準的 64 路 self-consistency，達到約 ",{"type":494,"tag":578,"props":1594,"children":1595},{},[1596],{"type":499,"value":1597},"69.5% 的 token 減少",{"type":499,"value":1599},"，且維持同等準確率。",{"type":494,"tag":495,"props":1601,"children":1602},{},[1603],{"type":499,"value":1604},"更值得關注的是 CMC 的泛化能力：它在 AIME24 上被發現，卻成功遷移至 AIME25、HMMT25、GPQA-Diamond，乃至不同規模的模型 DeepSeek-R1-Distill-Llama-8B。這暗示所發現的策略捕捉到了跨領域的推理結構特性。",{"type":494,"tag":571,"props":1606,"children":1607},{},[1608],{"type":494,"tag":495,"props":1609,"children":1610},{},[1611,1615,1618],{"type":494,"tag":578,"props":1612,"children":1613},{},[1614],{"type":499,"value":582},{"type":494,"tag":584,"props":1616,"children":1617},{},[],{"type":499,"value":1619},"\nSelf-consistency：一種 TTS 策略，讓模型產生多條平行解題路徑，再取多數投票結果作為最終答案，標準做法通常生成 32 或 64 條路徑。",{"type":494,"tag":538,"props":1621,"children":1623},{"id":1622},"章節三自動化研究的可靠性與可重現性挑戰",[1624],{"type":499,"value":1625},"章節三：自動化研究的可靠性與可重現性挑戰",{"type":494,"tag":495,"props":1627,"children":1628},{},[1629,1631,1636],{"type":499,"value":1630},"儘管結果亮眼，AutoTTS 存在明顯的落地門檻。研究團隊",{"type":494,"tag":578,"props":1632,"children":1633},{},[1634],{"type":499,"value":1635},"未釋出預訓練權重",{"type":499,"value":1637},"，使用者須自行完成三項前置工程：",{"type":494,"tag":680,"props":1639,"children":1640},{},[1641,1646,1651],{"type":494,"tag":684,"props":1642,"children":1643},{},[1644],{"type":499,"value":1645},"收集目標模型在各基準上的 offline reasoning traces（數千筆快取推理回應）",{"type":494,"tag":684,"props":1647,"children":1648},{},[1649],{"type":499,"value":1650},"架設 replay 環境並配置高階控制器介面",{"type":494,"tag":684,"props":1652,"children":1653},{},[1654],{"type":499,"value":1655},"取得 Claude Code API 存取權限",{"type":494,"tag":495,"props":1657,"children":1658},{},[1659],{"type":499,"value":1660},"「$39.90 發現一個演算法」的成本數字，背後預設了大量工程前置作業，使得這個數字對多數讀者而言具有誤導性。",{"type":494,"tag":495,"props":1662,"children":1663},{},[1664],{"type":499,"value":1665},"論文的評估範圍也相對受限——主要在兩個數學推理基準與單一框架下測試，尚未驗證 CMC 在自然語言生成、程式碼合成或多模態任務上的表現。泛化能力的宣稱仍需更廣泛的獨立複現才能確認。",{"type":494,"tag":538,"props":1667,"children":1669},{"id":1668},"章節四ai-驅動的-ai-研究加速器還是幻覺放大器",[1670],{"type":499,"value":1671},"章節四：AI 驅動的 AI 研究——加速器還是幻覺放大器",{"type":494,"tag":495,"props":1673,"children":1674},{},[1675],{"type":499,"value":1676},"論文標題「LLMs Improving LLMs」本身就是一份宣言。AutoTTS 代表一類新興研究正規——研究者不再設計具體啟發式規則，而是設計 AI 可以在其中自主探索的環境，讓演算法從資料與反饋中湧現。",{"type":494,"tag":495,"props":1678,"children":1679},{},[1680],{"type":499,"value":1681},"The Decoder 報導指出，Claude Code 自主發現的 CMC 包含「幾乎不可能靠人手設計出來」的動態協調機制，意味著 AI 的搜索空間確實超越了人類直覺的邊界，有潛力大幅壓縮演算法研究的迭代週期——從數月縮短至數小時。",{"type":494,"tag":495,"props":1683,"children":1684},{},[1685],{"type":499,"value":1686},"但加速本身也帶來新的風險：當 AI 發現人類無法直覺理解的策略時，如何系統性驗證其行為邊界？CMC 在少數基準上的良好泛化，距離「可信賴的通用推理策略」仍有距離。自動化研究究竟是加速器還是幻覺放大器，答案取決於評估基礎設施能否與探索速度同步成長。",{"title":257,"searchDepth":501,"depth":501,"links":1688},[],{"data":1690,"body":1692,"excerpt":-1,"toc":1698},{"title":257,"description":1691},"AutoTTS 的技術核心可分為三層機制：模擬環境設計、Agent 迭代框架、CMC 動態控制邏輯。理解這三層，才能評估「$39.90 發現演算法」背後的真實工程成本與研究價值。",{"type":491,"children":1693},[1694],{"type":494,"tag":495,"props":1695,"children":1696},{},[1697],{"type":499,"value":1691},{"title":257,"searchDepth":501,"depth":501,"links":1699},[],{"data":1701,"body":1703,"excerpt":-1,"toc":1714},{"title":257,"description":1702},"AutoTTS 的加速來源是將「執行推理」與「設計控制策略」完全解耦。研究團隊預先從目標語言模型抽取大規模推理路徑並快取，形成固定的資料集。控制演算法在這個固定資料集上評估，不需要每次都實際呼叫 LLM API。",{"type":491,"children":1704},[1705,1709],{"type":494,"tag":495,"props":1706,"children":1707},{},[1708],{"type":499,"value":1702},{"type":494,"tag":495,"props":1710,"children":1711},{},[1712],{"type":499,"value":1713},"這讓數千次演算法迭代的邊際成本趨近於零：每次迭代只需在快取資料上執行計算，而不是付出真實的推理 API 費用。",{"title":257,"searchDepth":501,"depth":501,"links":1715},[],{"data":1717,"body":1719,"excerpt":-1,"toc":1745},{"title":257,"description":1718},"Claude Code 作為 explorer agent，每輪迭代都審視前幾輪提案的缺陷，以 Python 程式碼直接撰寫新的控制器。控制空間沿寬度 (width)與深度 (depth)兩個維度定義：寬度控制平行解題路徑數，深度控制每條路徑的推理延伸長度。",{"type":491,"children":1720},[1721,1740],{"type":494,"tag":495,"props":1722,"children":1723},{},[1724,1726,1731,1733,1738],{"type":499,"value":1725},"Claude Code 作為 explorer agent，每輪迭代都審視前幾輪提案的缺陷，以 Python 程式碼直接撰寫新的控制器。控制空間沿",{"type":494,"tag":578,"props":1727,"children":1728},{},[1729],{"type":499,"value":1730},"寬度 (width)",{"type":499,"value":1732},"與",{"type":494,"tag":578,"props":1734,"children":1735},{},[1736],{"type":499,"value":1737},"深度 (depth)",{"type":499,"value":1739},"兩個維度定義：寬度控制平行解題路徑數，深度控制每條路徑的推理延伸長度。",{"type":494,"tag":495,"props":1741,"children":1742},{},[1743],{"type":499,"value":1744},"系統暴露一個高階控制器介面，讓 Agent 可獨立調整所有下層閾值，而不需要了解底層模型的內部狀態。這是讓大規模探索在可控成本內可行的關鍵抽象設計。",{"title":257,"searchDepth":501,"depth":501,"links":1746},[],{"data":1748,"body":1750,"excerpt":-1,"toc":1784},{"title":257,"description":1749},"CMC 的核心創新在於引入信心動量(confidence momentum) 作為控制信號，取代傳統固定閾值的分支決策。當信心變化緩慢時，CMC 開啟更多平行路徑；當信心快速上升時，跳過新分支；只有在信心長期偏離主流路徑後，才剪除離群分支。",{"type":491,"children":1751},[1752,1764,1769],{"type":494,"tag":495,"props":1753,"children":1754},{},[1755,1757,1762],{"type":499,"value":1756},"CMC 的核心創新在於引入",{"type":494,"tag":578,"props":1758,"children":1759},{},[1760],{"type":499,"value":1761},"信心動量",{"type":499,"value":1763},"(confidence momentum) 作為控制信號，取代傳統固定閾值的分支決策。當信心變化緩慢時，CMC 開啟更多平行路徑；當信心快速上升時，跳過新分支；只有在信心長期偏離主流路徑後，才剪除離群分支。",{"type":494,"tag":495,"props":1765,"children":1766},{},[1767],{"type":499,"value":1768},"β=0.5 的平衡設定在 AIME 和 HMMT 基準上實現約 69.5% 的 token 減少，準確率不下降。",{"type":494,"tag":571,"props":1770,"children":1771},{},[1772],{"type":494,"tag":495,"props":1773,"children":1774},{},[1775,1779,1782],{"type":494,"tag":578,"props":1776,"children":1777},{},[1778],{"type":499,"value":735},{"type":494,"tag":584,"props":1780,"children":1781},{},[],{"type":499,"value":1783},"\n把 CMC 想像成一個有經驗的考試策略師：越想越有把握的題目，別浪費時間換思路；卡在原地沒進展，才去嘗試不同解法。傳統 self-consistency 則像是不管有沒有把握，一律做 64 遍再投票——資源浪費在早已有把握的題目上。",{"title":257,"searchDepth":501,"depth":501,"links":1785},[],{"data":1787,"body":1788,"excerpt":-1,"toc":1899},{"title":257,"description":257},{"type":491,"children":1789},[1790,1794,1815,1819,1840,1844,1849,1853,1871,1875,1888,1894],{"type":494,"tag":538,"props":1791,"children":1792},{"id":749},[1793],{"type":499,"value":749},{"type":494,"tag":753,"props":1795,"children":1796},{},[1797,1806],{"type":494,"tag":684,"props":1798,"children":1799},{},[1800,1804],{"type":494,"tag":578,"props":1801,"children":1802},{},[1803],{"type":499,"value":763},{"type":499,"value":1805},"：人工設計的 TTS 策略（beam search、MCTS、standard self-consistency）；OpenAI o-series 推理模型（內建計算分配邏輯）",{"type":494,"tag":684,"props":1807,"children":1808},{},[1809,1813],{"type":494,"tag":578,"props":1810,"children":1811},{},[1812],{"type":499,"value":773},{"type":499,"value":1814},"：AutoML 框架；Neural Architecture Search(NAS) 工具",{"type":494,"tag":538,"props":1816,"children":1817},{"id":778},[1818],{"type":499,"value":778},{"type":494,"tag":753,"props":1820,"children":1821},{},[1822,1831],{"type":494,"tag":684,"props":1823,"children":1824},{},[1825,1829],{"type":494,"tag":578,"props":1826,"children":1827},{},[1828],{"type":499,"value":791},{"type":499,"value":1830},"：offline replay environment 的設計降低了探索成本，但技術本身可被複製；真正的護城河是快取推理資料集的規模與多樣性",{"type":494,"tag":684,"props":1832,"children":1833},{},[1834,1838],{"type":494,"tag":578,"props":1835,"children":1836},{},[1837],{"type":499,"value":801},{"type":499,"value":1839},"：AutoTTS 依賴 Claude Code 作為 explorer agent，與 Anthropic 生態深度綁定；若其他 coding agent 能扮演同等角色，依賴程度將降低",{"type":494,"tag":538,"props":1841,"children":1842},{"id":806},[1843],{"type":499,"value":806},{"type":494,"tag":495,"props":1845,"children":1846},{},[1847],{"type":499,"value":1848},"AutoTTS 以學術開源形式發布（GitHub 公開程式碼），目前沒有商業定價。潛在商業模式包括：提供預建 offline datasets 的付費訂閱、或作為推理服務提供商的效率最佳化層。",{"type":494,"tag":538,"props":1850,"children":1851},{"id":816},[1852],{"type":499,"value":816},{"type":494,"tag":753,"props":1854,"children":1855},{},[1856,1861,1866],{"type":494,"tag":684,"props":1857,"children":1858},{},[1859],{"type":499,"value":1860},"無預訓練權重，須從頭建立 offline replay dataset，工程成本對中小型團隊不友善",{"type":494,"tag":684,"props":1862,"children":1863},{},[1864],{"type":499,"value":1865},"CMC 邏輯難以向非技術利益相關者解釋，在合規場景中是潛在風險",{"type":494,"tag":684,"props":1867,"children":1868},{},[1869],{"type":499,"value":1870},"目前僅驗證數學推理任務，企業應用場景的適用性尚不明確",{"type":494,"tag":538,"props":1872,"children":1873},{"id":839},[1874],{"type":499,"value":839},{"type":494,"tag":753,"props":1876,"children":1877},{},[1878,1883],{"type":494,"tag":684,"props":1879,"children":1880},{},[1881],{"type":499,"value":1882},"若 AutoTTS 範式成熟，未來演算法研究可能大幅去中心化：任何有算力的研究小組都能探索 TTS 策略，而不只是大型實驗室",{"type":494,"tag":684,"props":1884,"children":1885},{},[1886],{"type":499,"value":1887},"Claude Code 作為「演算法探索工具」的新角色，可能開啟 Anthropic 在研究工具市場的新定位",{"type":494,"tag":538,"props":1889,"children":1891},{"id":1890},"判決有潛力但等待複現學術先行產業跟進",[1892],{"type":499,"value":1893},"判決：有潛力但等待複現（學術先行、產業跟進）",{"type":494,"tag":495,"props":1895,"children":1896},{},[1897],{"type":499,"value":1898},"AutoTTS 的學術貢獻清晰——以極低成本自動探索出人類難以設計的控制策略。但在獨立複現成功、以及非數學任務驗證完成之前，企業端應保持觀望，而非急於導入。",{"title":257,"searchDepth":501,"depth":501,"links":1900},[],{"data":1902,"body":1903,"excerpt":-1,"toc":1936},{"title":257,"description":257},{"type":491,"children":1904},[1905,1911,1916,1921,1926,1931],{"type":494,"tag":538,"props":1906,"children":1908},{"id":1907},"aime-數學基準",[1909],{"type":499,"value":1910},"AIME 數學基準",{"type":494,"tag":495,"props":1912,"children":1913},{},[1914],{"type":499,"value":1915},"CMC(β=0.5) 與標準 self-consistency（64 路）對比，在 AIME24 達到約 69.5% token 減少，準確率維持同等水準。",{"type":494,"tag":538,"props":1917,"children":1919},{"id":1918},"跨基準泛化",[1920],{"type":499,"value":1918},{"type":494,"tag":495,"props":1922,"children":1923},{},[1924],{"type":499,"value":1925},"CMC 在 AIME24 被發現，成功遷移至 AIME25、HMMT25、GPQA-Diamond，token 效率優勢在各基準上一致保持。",{"type":494,"tag":538,"props":1927,"children":1929},{"id":1928},"跨模型泛化",[1930],{"type":499,"value":1928},{"type":494,"tag":495,"props":1932,"children":1933},{},[1934],{"type":499,"value":1935},"在 DeepSeek-R1-Distill-Llama-8B 上測試，CMC 同樣維持效率優勢，顯示控制策略不依賴特定模型的內部實作。",{"title":257,"searchDepth":501,"depth":501,"links":1937},[],{"data":1939,"body":1940,"excerpt":-1,"toc":1957},{"title":257,"description":257},{"type":491,"children":1941},[1942],{"type":494,"tag":753,"props":1943,"children":1944},{},[1945,1949,1953],{"type":494,"tag":684,"props":1946,"children":1947},{},[1948],{"type":499,"value":199},{"type":494,"tag":684,"props":1950,"children":1951},{},[1952],{"type":499,"value":200},{"type":494,"tag":684,"props":1954,"children":1955},{},[1956],{"type":499,"value":201},{"title":257,"searchDepth":501,"depth":501,"links":1958},[],{"data":1960,"body":1961,"excerpt":-1,"toc":1978},{"title":257,"description":257},{"type":491,"children":1962},[1963],{"type":494,"tag":753,"props":1964,"children":1965},{},[1966,1970,1974],{"type":494,"tag":684,"props":1967,"children":1968},{},[1969],{"type":499,"value":203},{"type":494,"tag":684,"props":1971,"children":1972},{},[1973],{"type":499,"value":204},{"type":494,"tag":684,"props":1975,"children":1976},{},[1977],{"type":499,"value":205},{"title":257,"searchDepth":501,"depth":501,"links":1979},[],{"data":1981,"body":1982,"excerpt":-1,"toc":1988},{"title":257,"description":209},{"type":491,"children":1983},[1984],{"type":494,"tag":495,"props":1985,"children":1986},{},[1987],{"type":499,"value":209},{"title":257,"searchDepth":501,"depth":501,"links":1989},[],{"data":1991,"body":1992,"excerpt":-1,"toc":1998},{"title":257,"description":210},{"type":491,"children":1993},[1994],{"type":494,"tag":495,"props":1995,"children":1996},{},[1997],{"type":499,"value":210},{"title":257,"searchDepth":501,"depth":501,"links":1999},[],{"data":2001,"body":2002,"excerpt":-1,"toc":2008},{"title":257,"description":211},{"type":491,"children":2003},[2004],{"type":494,"tag":495,"props":2005,"children":2006},{},[2007],{"type":499,"value":211},{"title":257,"searchDepth":501,"depth":501,"links":2009},[],{"data":2011,"body":2012,"excerpt":-1,"toc":2071},{"title":257,"description":257},{"type":491,"children":2013},[2014,2020,2025,2030,2043,2066],{"type":494,"tag":538,"props":2015,"children":2017},{"id":2016},"_45-年前的車庫遺珍",[2018],{"type":499,"value":2019},"45 年前的車庫遺珍",{"type":494,"tag":495,"props":2021,"children":2022},{},[2023],{"type":499,"value":2024},"2026 年 4 月 28 日，Microsoft 趁 86-DOS 1.00 誕生 45 週年，在 GitHub 以 MIT 授權釋出迄今發現最早的 DOS 原始碼（代號「Paterson Listings」）。這批程式碼的數位版本早已不存在——原始碼是從 Tim Paterson 車庫中保存的點矩陣印表機連續紙列印稿，由歷史學家 Yufeng Gao 與 Rich Cini 手工掃描並轉錄而來。",{"type":494,"tag":538,"props":2026,"children":2028},{"id":2027},"釋出內容",[2029],{"type":499,"value":2027},{"type":494,"tag":495,"props":2031,"children":2032},{},[2033,2035,2041],{"type":499,"value":2034},"釋出內容存放於 GitHub ",{"type":494,"tag":717,"props":2036,"children":2038},{"className":2037},[],[2039],{"type":499,"value":2040},"DOS-History/Paterson-Listings",{"type":499,"value":2042},"，包含：",{"type":494,"tag":753,"props":2044,"children":2045},{},[2046,2051,2056,2061],{"type":494,"tag":684,"props":2047,"children":2048},{},[2049],{"type":499,"value":2050},"86-DOS 1.00 kernel 原始碼",{"type":494,"tag":684,"props":2052,"children":2053},{},[2054],{"type":499,"value":2055},"PC-DOS 1.00 pre-release kernel 多個開發快照",{"type":494,"tag":684,"props":2057,"children":2058},{},[2059],{"type":499,"value":2060},"CHKDSK 等公用程式與 Microsoft BASIC-86 Compiler runtime library",{"type":494,"tag":684,"props":2062,"children":2063},{},[2064],{"type":499,"value":2065},"Seattle Computer Products ASM 組合器",{"type":494,"tag":495,"props":2067,"children":2068},{},[2069],{"type":499,"value":2070},"Microsoft VP Scott Hanselman 確認，轉錄後的程式碼可以逐位元組重新編譯出與原始執行檔完全相同的結果。掃描件同步上傳至 Internet Archive，原始碼最終將入藏 Interim Computer Museum 永久保存。",{"title":257,"searchDepth":501,"depth":501,"links":2072},[],{"data":2074,"body":2075,"excerpt":-1,"toc":2081},{"title":257,"description":253},{"type":491,"children":2076},[2077],{"type":494,"tag":495,"props":2078,"children":2079},{},[2080],{"type":499,"value":253},{"title":257,"searchDepth":501,"depth":501,"links":2082},[],{"data":2084,"body":2085,"excerpt":-1,"toc":2091},{"title":257,"description":254},{"type":491,"children":2086},[2087],{"type":494,"tag":495,"props":2088,"children":2089},{},[2090],{"type":499,"value":254},{"title":257,"searchDepth":501,"depth":501,"links":2092},[],{"data":2094,"body":2095,"excerpt":-1,"toc":2144},{"title":257,"description":257},{"type":491,"children":2096},[2097,2103,2108,2113,2119,2124,2139],{"type":494,"tag":538,"props":2098,"children":2100},{"id":2099},"pentagon-的矛盾禁令",[2101],{"type":499,"value":2102},"Pentagon 的矛盾禁令",{"type":494,"tag":495,"props":2104,"children":2105},{},[2106],{"type":499,"value":2107},"2026 年 3 月，美國國防部正式將 Anthropic 列為「供應鏈風險」，要求國防承包商認證其工作中未使用 Anthropic 模型。然而同年 5 月，白宮幕僚長 Susie Wiles 親自批准 NSA 繼續部署 Anthropic 的 Mythos Preview 模型，兩個政府機構的態度形成尖銳矛盾。",{"type":494,"tag":495,"props":2109,"children":2110},{},[2111],{"type":499,"value":2112},"Anthropic 已對 Pentagon 提起訴訟，主張該認定侵犯其第一修正案權利並逾越政府職權。白宮計劃以此合約作為未來政府 AI 採購的範本，並核准 90 億美元緊急預算用於為情報機構採購高階 AI 晶片。",{"type":494,"tag":538,"props":2114,"children":2116},{"id":2115},"為何-nsa-離不開-mythos",[2117],{"type":499,"value":2118},"為何 NSA 離不開 Mythos",{"type":494,"tag":495,"props":2120,"children":2121},{},[2122],{"type":499,"value":2123},"Mythos 設計運行於較舊的晶片架構，得以相容 NSA 機密網路的既有基礎設施。最新 Nvidia Grace Blackwell 晶片在機密環境嚴重不足，現代前沿模型的算力需求遠超機密網路當初的設計容量。",{"type":494,"tag":571,"props":2125,"children":2126},{},[2127],{"type":494,"tag":495,"props":2128,"children":2129},{},[2130,2134,2137],{"type":494,"tag":578,"props":2131,"children":2132},{},[2133],{"type":499,"value":735},{"type":494,"tag":584,"props":2135,"children":2136},{},[],{"type":499,"value":2138},"\n就像舊電腦只能跑 Windows 7——NSA 的機密網路就是那台舊電腦，Mythos 是少數願意配合的 AI。",{"type":494,"tag":495,"props":2140,"children":2141},{},[2142],{"type":499,"value":2143},"Mythos 據報「發現漏洞的速度比開發者修補的速度還快」，令情報機構難以找到替代方案。合約已加入禁止處理美國公民資料的條款，並刪除了令談判破裂的「任何合法用途」 (any lawful use) 措辭。",{"title":257,"searchDepth":501,"depth":501,"links":2145},[],{"data":2147,"body":2149,"excerpt":-1,"toc":2160},{"title":257,"description":2148},"Mythos 能繞過晶片限制部署於機密網路，反映一個工程現實：機密環境的硬體升級週期遠慢於模型迭代速度。合約條款移除「任何合法用途」措辭，顯示 AI 供應商在政府採購中需精確定義使用邊界。",{"type":491,"children":2150},[2151,2155],{"type":494,"tag":495,"props":2152,"children":2153},{},[2154],{"type":499,"value":2148},{"type":494,"tag":495,"props":2156,"children":2157},{},[2158],{"type":499,"value":2159},"對在美政府或國防供應鏈作業的工程師，此案提醒：合規要求不只看現有認證，更需追蹤供應商與政府機構的法律爭端進展。Anthropic 訴訟結果將直接影響未來 AI 工具在政府環境的許可邊界。",{"title":257,"searchDepth":501,"depth":501,"links":2161},[],{"data":2163,"body":2165,"excerpt":-1,"toc":2176},{"title":257,"description":2164},"這一矛盾局面顯示，AI 軍備競賽的算力缺口已大到讓情報機構「能用」優先於「合規」。NSA 合約若成為政府採購範本，將為 AI 企業開創在「被列為風險」後仍保住政府合約的先例。",{"type":491,"children":2166},[2167,2171],{"type":494,"tag":495,"props":2168,"children":2169},{},[2170],{"type":499,"value":2164},{"type":494,"tag":495,"props":2172,"children":2173},{},[2174],{"type":499,"value":2175},"企業採購者需注意：Anthropic 法律地位仍未定（訴訟進行中），若 Pentagon 主張獲法院支持，可能波及更廣的政府合約生態。此案也預示未來 AI 供應商談判時，使用範圍條款將成為最關鍵的議題。",{"title":257,"searchDepth":501,"depth":501,"links":2177},[],{"data":2179,"body":2180,"excerpt":-1,"toc":2229},{"title":257,"description":257},{"type":491,"children":2181},[2182,2188,2193,2198,2204,2209,2224],{"type":494,"tag":538,"props":2183,"children":2185},{"id":2184},"相同資料捏造截然不同的結論",[2186],{"type":499,"value":2187},"相同資料，捏造截然不同的結論",{"type":494,"tag":495,"props":2189,"children":2190},{},[2191],{"type":499,"value":2192},"數學家 Adam Kucharski 製造 2,000 筆完全相同的自由文字回應，分別標記為「UK」與「US」後交給 Microsoft Copilot 的「Auto」模式。",{"type":494,"tag":495,"props":2194,"children":2195},{},[2196],{"type":499,"value":2197},"Copilot 卻輸出一份詳細差異報告，聲稱兩國「在語氣、強度與措辭上有所不同」——而這些差異根本不存在於資料中。",{"type":494,"tag":538,"props":2199,"children":2201},{"id":2200},"幻覺的根源刻板印象填補空白",[2202],{"type":499,"value":2203},"幻覺的根源：刻板印象填補空白",{"type":494,"tag":495,"props":2205,"children":2206},{},[2207],{"type":499,"value":2208},"在第二個實驗中，相同的職涯目標敘述被複製並標記 5 個國家，Copilot 捏造出「義大利人從事藝術職涯的意願是英國人的三倍」等具體數字，全部憑空製造。",{"type":494,"tag":571,"props":2210,"children":2211},{},[2212],{"type":494,"tag":495,"props":2213,"children":2214},{},[2215,2219,2222],{"type":494,"tag":578,"props":2216,"children":2217},{},[2218],{"type":499,"value":735},{"type":494,"tag":584,"props":2220,"children":2221},{},[],{"type":499,"value":2223},"\n就像請人分析兩杯完全相同的水，他卻說「左邊的比較甜、右邊帶礦物質感」——因為他認為你想看差異，所以就編了一個。",{"type":494,"tag":495,"props":2225,"children":2226},{},[2227],{"type":499,"value":2228},"Copilot 自身的關鍵字計數已顯示資料完全一致，卻無視此結果，改以捏造百分比呈現「差異」。約 97% 的 Copilot 使用者採用預設 Auto 模式，幾乎不知道底層正在跑哪個模型。",{"title":257,"searchDepth":501,"depth":501,"links":2230},[],{"data":2232,"body":2234,"excerpt":-1,"toc":2250},{"title":257,"description":2233},"在實際分析任務中，應將 AI 輸出視為需要驗證的草稿，而非可信結論。",{"type":491,"children":2235},[2236,2240,2245],{"type":494,"tag":495,"props":2237,"children":2238},{},[2239],{"type":499,"value":2233},{"type":494,"tag":495,"props":2241,"children":2242},{},[2243],{"type":499,"value":2244},"建議執行分析前先書面記錄預期結果作為對照基準，並主動切換至推理能力較強的模型，而非依賴預設的 Auto 模式。",{"type":494,"tag":495,"props":2246,"children":2247},{},[2248],{"type":499,"value":2249},"最關鍵的理性檢查：若資料本身顯示某項指標一致，AI 卻輸出差異分析，這幾乎一定是幻覺，不是洞見。凡涉及人口統計學標籤的分析，務必人工抽樣驗證。",{"title":257,"searchDepth":501,"depth":501,"links":2251},[],{"data":2253,"body":2255,"excerpt":-1,"toc":2271},{"title":257,"description":2254},"這份研究揭露的不只是技術問題，更是產品設計問題。「Auto 模式選最佳模型」的承諾，在分析型任務中反而挑選了傾向以刻板印象填補空白的標準模型。",{"type":491,"children":2256},[2257,2261,2266],{"type":494,"tag":495,"props":2258,"children":2259},{},[2260],{"type":499,"value":2254},{"type":494,"tag":495,"props":2262,"children":2263},{},[2264],{"type":499,"value":2265},"對企業而言，若將 AI 用於 HR 評估、市場調研或政策分析，這類系統性偏差可能直接影響決策品質，且幾乎無法被察覺。",{"type":494,"tag":495,"props":2267,"children":2268},{},[2269],{"type":499,"value":2270},"97% 的使用者不知道自己在用哪個模型，企業採購 Copilot 授權時需額外建立 AI 輸出審查機制，才能確保資料分析的可信度。",{"title":257,"searchDepth":501,"depth":501,"links":2272},[],{"data":2274,"body":2275,"excerpt":-1,"toc":2316},{"title":257,"description":257},{"type":491,"children":2276},[2277,2283],{"type":494,"tag":538,"props":2278,"children":2280},{"id":2279},"各-ai-幻覺率比較社群整理",[2281],{"type":499,"value":2282},"各 AI 幻覺率比較（社群整理）",{"type":494,"tag":753,"props":2284,"children":2285},{},[2286,2291,2296,2301,2306,2311],{"type":494,"tag":684,"props":2287,"children":2288},{},[2289],{"type":499,"value":2290},"Perplexity：100 次中出現 37 次幻覺",{"type":494,"tag":684,"props":2292,"children":2293},{},[2294],{"type":499,"value":2295},"Copilot：40 次",{"type":494,"tag":684,"props":2297,"children":2298},{},[2299],{"type":499,"value":2300},"Perplexity Pro：45 次",{"type":494,"tag":684,"props":2302,"children":2303},{},[2304],{"type":499,"value":2305},"ChatGPT Search：67 次",{"type":494,"tag":684,"props":2307,"children":2308},{},[2309],{"type":499,"value":2310},"DeepSeek Search：68 次",{"type":494,"tag":684,"props":2312,"children":2313},{},[2314],{"type":499,"value":2315},"Gemini：76 次",{"title":257,"searchDepth":501,"depth":501,"links":2317},[],{"data":2319,"body":2320,"excerpt":-1,"toc":2363},{"title":257,"description":257},{"type":491,"children":2321},[2322,2328,2333,2348,2353,2358],{"type":494,"tag":538,"props":2323,"children":2325},{"id":2324},"舊工具新熱度",[2326],{"type":499,"value":2327},"舊工具、新熱度",{"type":494,"tag":495,"props":2329,"children":2330},{},[2331],{"type":499,"value":2332},"cmux 由 manaflow-ai 開發，最新版 v0.64.10 發布於 2025 年 5 月 23 日，是個已存在近一年的專案。近期因其在 GitHub 單日新增 560 顆星而登上熱搜，總星數突破 19,000，顯示 AI Coding Agent 工具鏈需求持續成長。",{"type":494,"tag":571,"props":2334,"children":2335},{},[2336],{"type":494,"tag":495,"props":2337,"children":2338},{},[2339,2343,2346],{"type":494,"tag":578,"props":2340,"children":2341},{},[2342],{"type":499,"value":582},{"type":494,"tag":584,"props":2344,"children":2345},{},[],{"type":499,"value":2347},"\nlibghostty 是 Ghostty 終端機應用的開源渲染函式庫，第三方可藉此打造具備相同高效能渲染的終端工具。",{"type":494,"tag":538,"props":2349,"children":2351},{"id":2350},"核心功能設計",[2352],{"type":499,"value":2350},{"type":494,"tag":495,"props":2354,"children":2355},{},[2356],{"type":499,"value":2357},"cmux 以 Swift + AppKit（佔 81.4% 程式碼）原生打造，刻意不使用 Electron。垂直側邊欄分頁讓開發者一眼掃描多達 10 個 agent 工作階段，每個分頁顯示 git branch、PR 狀態、工作目錄與即時通知文字。",{"type":494,"tag":495,"props":2359,"children":2360},{},[2361],{"type":499,"value":2362},"當 agent 等待輸入時，對應 pane 出現藍色光環，並觸發原生 macOS 桌面通知。工具原生支援 Claude Code、Codex、Gemini CLI 等主流 AI Coding Agent 的 hook 整合，另提供 socket API 讓 agent 或人類皆可控制終端佈局。",{"title":257,"searchDepth":501,"depth":501,"links":2364},[],{"data":2366,"body":2368,"excerpt":-1,"toc":2383},{"title":257,"description":2367},"cmux 透過 socket API 與 CLI 介面提供可程式化控制，涵蓋建立 pane、傳送按鍵、操控內建瀏覽器等操作。對 Claude Code 的原生 hook 整合讓 agent 完成或等待時自動推送通知，無需輪詢終端狀態。現有 Ghostty 用戶可直接複用 ~/.config/ghostty/config，零成本遷移。",{"type":491,"children":2369},[2370],{"type":494,"tag":495,"props":2371,"children":2372},{},[2373,2375,2381],{"type":499,"value":2374},"cmux 透過 socket API 與 CLI 介面提供可程式化控制，涵蓋建立 pane、傳送按鍵、操控內建瀏覽器等操作。對 Claude Code 的原生 hook 整合讓 agent 完成或等待時自動推送通知，無需輪詢終端狀態。現有 Ghostty 用戶可直接複用 ",{"type":494,"tag":717,"props":2376,"children":2378},{"className":2377},[],[2379],{"type":499,"value":2380},"~/.config/ghostty/config",{"type":499,"value":2382},"，零成本遷移。",{"title":257,"searchDepth":501,"depth":501,"links":2384},[],{"data":2386,"body":2387,"excerpt":-1,"toc":2393},{"title":257,"description":342},{"type":491,"children":2388},[2389],{"type":494,"tag":495,"props":2390,"children":2391},{},[2392],{"type":499,"value":342},{"title":257,"searchDepth":501,"depth":501,"links":2394},[],{"data":2396,"body":2397,"excerpt":-1,"toc":2440},{"title":257,"description":257},{"type":491,"children":2398},[2399,2405,2410,2415,2420,2425],{"type":494,"tag":538,"props":2400,"children":2402},{"id":2401},"核心升級從回合制到即時串流",[2403],{"type":499,"value":2404},"核心升級：從回合制到即時串流",{"type":494,"tag":495,"props":2406,"children":2407},{},[2408],{"type":499,"value":2409},"Google Stitch 3.0 以「即時串流設計代理」取代舊版回合制工作流程。過去設計師需送出 prompt 後等待，3.0 版的 Stitch Agent 在輸入的同時直接在畫布上渲染 UI 元件，可在生成過程中隨時調整方向。",{"type":494,"tag":495,"props":2411,"children":2412},{},[2413],{"type":499,"value":2414},"語音模式同步整合進串流迴圈——設計師說出「給我三種選單選項」，畫布即時回應，代理主動詢問設計目標並在串流中套用修改。",{"type":494,"tag":538,"props":2416,"children":2418},{"id":2417},"功能與整合",[2419],{"type":499,"value":2417},{"type":494,"tag":495,"props":2421,"children":2422},{},[2423],{"type":499,"value":2424},"3.0 版新增類 Google Docs 的多人協作，以及記錄設計演進軌跡的 Agent Manager。匯出支援 Vue.js、Tailwind CSS、Flutter、SwiftUI 等框架，可直接整合 Figma、Lovable、Bolt 或發布至 Netlify。",{"type":494,"tag":571,"props":2426,"children":2427},{},[2428],{"type":494,"tag":495,"props":2429,"children":2430},{},[2431,2435,2438],{"type":494,"tag":578,"props":2432,"children":2433},{},[2434],{"type":499,"value":582},{"type":494,"tag":584,"props":2436,"children":2437},{},[],{"type":499,"value":2439},"\nDESIGN.md：Google 開放的純文字設計系統規格格式，可從現有 codebase 或 Figma 提取品牌規則，實現跨工具攜帶。",{"title":257,"searchDepth":501,"depth":501,"links":2441},[],{"data":2443,"body":2444,"excerpt":-1,"toc":2450},{"title":257,"description":377},{"type":491,"children":2445},[2446],{"type":494,"tag":495,"props":2447,"children":2448},{},[2449],{"type":499,"value":377},{"title":257,"searchDepth":501,"depth":501,"links":2451},[],{"data":2453,"body":2454,"excerpt":-1,"toc":2460},{"title":257,"description":378},{"type":491,"children":2455},[2456],{"type":494,"tag":495,"props":2457,"children":2458},{},[2459],{"type":499,"value":378},{"title":257,"searchDepth":501,"depth":501,"links":2461},[],{"data":2463,"body":2464,"excerpt":-1,"toc":2479},{"title":257,"description":257},{"type":491,"children":2465},[2466,2471],{"type":494,"tag":538,"props":2467,"children":2469},{"id":2468},"市場表現",[2470],{"type":499,"value":2468},{"type":494,"tag":753,"props":2472,"children":2473},{},[2474],{"type":494,"tag":684,"props":2475,"children":2476},{},[2477],{"type":499,"value":2478},"Product Hunt 首日：376 票，排名第一",{"title":257,"searchDepth":501,"depth":501,"links":2480},[],{"data":2482,"body":2483,"excerpt":-1,"toc":2559},{"title":257,"description":257},{"type":491,"children":2484},[2485,2491,2496,2501,2544],{"type":494,"tag":538,"props":2486,"children":2488},{"id":2487},"四月舊文近期因-hn-討論再度引爆",[2489],{"type":499,"value":2490},"四月舊文，近期因 HN 討論再度引爆",{"type":494,"tag":495,"props":2492,"children":2493},{},[2494],{"type":499,"value":2495},"這篇由 Charlie Holland 撰寫的文章發表於 2026 年 4 月 6 日，近期因 Hacker News 熱議再度獲得廣泛關注。核心論點：AI agent 擅長實作，但缺乏做架構決策所需的情境判斷力，讓 AI 主導設計而非實作，會導致系統與組織脈絡嚴重脫節。",{"type":494,"tag":538,"props":2497,"children":2499},{"id":2498},"四個讓架構決策失靈的問題",[2500],{"type":499,"value":2498},{"type":494,"tag":753,"props":2502,"children":2503},{},[2504,2514,2524,2534],{"type":494,"tag":684,"props":2505,"children":2506},{},[2507,2512],{"type":494,"tag":578,"props":2508,"children":2509},{},[2510],{"type":499,"value":2511},"Attaboy Problem（迎合問題）",{"type":499,"value":2513},"：AI 被訓練為「有幫助」，而有幫助就等於順從。真正的架構師價值在於「拒絕」和「推翻」，文章指 Claude「病態地贊同」，缺乏說「不」的能力",{"type":494,"tag":684,"props":2515,"children":2516},{},[2517,2522],{"type":494,"tag":578,"props":2518,"children":2519},{},[2520],{"type":499,"value":2521},"Generic-Fit 架構",{"type":499,"value":2523},"：AI 設計的系統忽略組織限制、團隊能力、遺留系統與合規需求",{"type":494,"tag":684,"props":2525,"children":2526},{},[2527,2532],{"type":494,"tag":578,"props":2528,"children":2529},{},[2530],{"type":499,"value":2531},"問責缺口",{"type":499,"value":2533},"：「Claude 不會在凌晨三點被 paged」——工程師繼承一個自己沒有設計的系統，卻要承擔全部後果",{"type":494,"tag":684,"props":2535,"children":2536},{},[2537,2542],{"type":494,"tag":578,"props":2538,"children":2539},{},[2540],{"type":499,"value":2541},"短路專業對話",{"type":499,"value":2543},"：AI 背書讓工程評審變成橡皮圖章，扼殺能產出更好設計的爭論式討論",{"type":494,"tag":571,"props":2545,"children":2546},{},[2547],{"type":494,"tag":495,"props":2548,"children":2549},{},[2550,2554,2557],{"type":494,"tag":578,"props":2551,"children":2552},{},[2553],{"type":499,"value":582},{"type":494,"tag":584,"props":2555,"children":2556},{},[],{"type":499,"value":2558},"\nAttaboy Problem：AI 因訓練目標（有幫助）而傾向順從用戶，缺乏像真正架構師那樣主動質疑、拒絕不合理設計的能力。",{"title":257,"searchDepth":501,"depth":501,"links":2560},[],{"data":2562,"body":2564,"excerpt":-1,"toc":2575},{"title":257,"description":2563},"作者建議的分工：工程師主導設計，agent 負責實作。實際操作上，先鎖定服務邊界、資料模型與擴展策略等架構決策，再把實作細節交給 AI 執行。",{"type":491,"children":2565},[2566,2570],{"type":494,"tag":495,"props":2567,"children":2568},{},[2569],{"type":499,"value":2563},{"type":494,"tag":495,"props":2571,"children":2572},{},[2573],{"type":499,"value":2574},"把 AI 的每個架構建議當成初級工程師的提案來審視——不是因為它的程式碼能力差，而是因為它不了解你的組織債務、人員限制與生產環境的現實。",{"title":257,"searchDepth":501,"depth":501,"links":2576},[],{"data":2578,"body":2580,"excerpt":-1,"toc":2591},{"title":257,"description":2579},"系統性風險值得警惕：當缺乏經驗的工程師借助 AI 構建影響數百萬用戶的系統，潛在技術負債可能遠超公司承受能力。",{"type":491,"children":2581},[2582,2586],{"type":494,"tag":495,"props":2583,"children":2584},{},[2585],{"type":499,"value":2579},{"type":494,"tag":495,"props":2587,"children":2588},{},[2589],{"type":499,"value":2590},"AI 是技能放大器——有能力者更有生產力，缺乏能力者則加倍犯錯。企業雇用與技術審查標準不應因 AI 工具而降低，反而需要更嚴格的架構問責機制。",{"title":257,"searchDepth":501,"depth":501,"links":2592},[],{"data":2594,"body":2595,"excerpt":-1,"toc":2624},{"title":257,"description":257},{"type":491,"children":2596},[2597,2603,2608,2614,2619],{"type":494,"tag":538,"props":2598,"children":2600},{"id":2599},"數月前點燃近期再掀波瀾",[2601],{"type":499,"value":2602},"數月前點燃、近期再掀波瀾",{"type":494,"tag":495,"props":2604,"children":2605},{},[2606],{"type":499,"value":2607},"2026 年 4 月，Epoch AI 發布「AI 公司能否獲利」深度分析，首度以財務模型拆解前沿模型的真實獲利結構。近期 Anthropic 確認年化營收突破 $300 億、有望在 Q2 達到營業損益平衡，讓這場辯論再度登上社群熱榜。",{"type":494,"tag":538,"props":2609,"children":2611},{"id":2610},"帳面收入亮眼結構性困境未解",[2612],{"type":499,"value":2613},"帳面收入亮眼，結構性困境未解",{"type":494,"tag":495,"props":2615,"children":2616},{},[2617],{"type":499,"value":2618},"OpenAI 2026 年 Q1 達約 $57 億季度營收，毛利率 33%；但全年現金消耗預計高達 $270 億。Epoch AI 分析顯示，GPT-5 的 $60 億毛利潤仍不足以回收 $50 億 R&D 投入，且模型發布後僅 3 個月便遭競爭對手挑戰——回收窗口極窄是核心困境。",{"type":494,"tag":495,"props":2620,"children":2621},{},[2622],{"type":499,"value":2623},"AI 推理成本與用量線性正比，打破傳統軟體「邊際成本趨近零」的規律。MIT 2025 年研究顯示，約 95% 企業 AI 投資未達獲利，合計約 $400 億付諸流水。算法效率雖每年持續改善，但短期成本結構仍不利於消費端大規模變現。",{"title":257,"searchDepth":501,"depth":501,"links":2625},[],{"data":2627,"body":2628,"excerpt":-1,"toc":2634},{"title":257,"description":436},{"type":491,"children":2629},[2630],{"type":494,"tag":495,"props":2631,"children":2632},{},[2633],{"type":499,"value":436},{"title":257,"searchDepth":501,"depth":501,"links":2635},[],{"data":2637,"body":2638,"excerpt":-1,"toc":2644},{"title":257,"description":437},{"type":491,"children":2639},[2640],{"type":494,"tag":495,"props":2641,"children":2642},{},[2643],{"type":499,"value":437},{"title":257,"searchDepth":501,"depth":501,"links":2645},[],{"data":2647,"body":2648,"excerpt":-1,"toc":2731},{"title":257,"description":257},{"type":491,"children":2649},[2650,2656,2668,2673,2688,2703,2708,2726],{"type":494,"tag":538,"props":2651,"children":2653},{"id":2652},"qa-訓練-vs-ocr-轉錄",[2654],{"type":499,"value":2655},"QA 訓練 vs OCR 轉錄",{"type":494,"tag":495,"props":2657,"children":2658},{},[2659,2661,2666],{"type":499,"value":2660},"ByteDance Seed 與香港科技大學聯合發表 MMProLong 研究，揭露多模態長文檔模型訓練的關鍵洞察：",{"type":494,"tag":578,"props":2662,"children":2663},{},[2664],{"type":499,"value":2665},"直接對文件提問，比逐字轉錄更有效",{"type":499,"value":2667},"。",{"type":494,"tag":495,"props":2669,"children":2670},{},[2671],{"type":499,"value":2672},"在 MMLongBench 基準上，QA 配對訓練讓分數提升 5–6 分；OCR 轉錄訓練反而拉低 6.8–17.4 分。Needle-in-a-Haystack 基準上，MMProLong 比基礎模型 Qwen2.5-VL-7B 平均高出 29.4 分，且僅以 5B tokens 訓練資料便超越 InternVL3-38B 和 Gemma3-27B。",{"type":494,"tag":571,"props":2674,"children":2675},{},[2676],{"type":494,"tag":495,"props":2677,"children":2678},{},[2679,2683,2686],{"type":494,"tag":578,"props":2680,"children":2681},{},[2682],{"type":499,"value":582},{"type":494,"tag":584,"props":2684,"children":2685},{},[],{"type":499,"value":2687},"\nMMLongBench：專門評估多模態大語言模型在長文檔理解能力的基準測試集。",{"type":494,"tag":571,"props":2689,"children":2690},{},[2691],{"type":494,"tag":495,"props":2692,"children":2693},{},[2694,2698,2701],{"type":494,"tag":578,"props":2695,"children":2696},{},[2697],{"type":499,"value":735},{"type":494,"tag":584,"props":2699,"children":2700},{},[],{"type":499,"value":2702},"\n就像學生備考：死記課文逐字逐句不如直接練習考題問答——前者記了許多不會考的細節，後者直接鍛鍊了在文件中找答案的能力。",{"type":494,"tag":538,"props":2704,"children":2706},{"id":2705},"附帶發現",[2707],{"type":499,"value":2705},{"type":494,"tag":753,"props":2709,"children":2710},{},[2711,2716,2721],{"type":494,"tag":684,"props":2712,"children":2713},{},[2714],{"type":499,"value":2715},"均衡混合不同長度文件，優於只堆積最長樣本",{"type":494,"tag":684,"props":2717,"children":2718},{},[2719],{"type":499,"value":2720},"資訊檢索任務比推理任務對效果影響更關鍵",{"type":494,"tag":684,"props":2722,"children":2723},{},[2724],{"type":499,"value":2725},"採用 QA 格式時，短脈絡樣本非必要",{"type":494,"tag":495,"props":2727,"children":2728},{},[2729],{"type":499,"value":2730},"訓練上下文僅 128K tokens，模型在 256K 乃至 512K 長度下仍保持穩定，且意外提升了長影片基準（Video-MME、MLVU）性能，顯示良好的跨媒體遷移能力。",{"title":257,"searchDepth":501,"depth":501,"links":2732},[],{"data":2734,"body":2736,"excerpt":-1,"toc":2765},{"title":257,"description":2735},"訓練流程分三步驟：",{"type":491,"children":2737},[2738,2742,2760],{"type":494,"tag":495,"props":2739,"children":2740},{},[2741],{"type":499,"value":2735},{"type":494,"tag":680,"props":2743,"children":2744},{},[2745,2750,2755],{"type":494,"tag":684,"props":2746,"children":2747},{},[2748],{"type":499,"value":2749},"OCR 解析切出 8–15 頁片段",{"type":494,"tag":684,"props":2751,"children":2752},{},[2753],{"type":499,"value":2754},"交由 LLM 生成 QA 配對",{"type":494,"tag":684,"props":2756,"children":2757},{},[2758],{"type":499,"value":2759},"嵌回完整文件脈絡訓練",{"type":494,"tag":495,"props":2761,"children":2762},{},[2763],{"type":499,"value":2764},"128K token 訓練窗口可泛化至 256K–512K，不需額外微調。與 DeepSeek 的視覺 token 壓縮架構路線不同，MMProLong 走的是訓練資料組成最佳化，遷移性更強、成本更低。",{"title":257,"searchDepth":501,"depth":501,"links":2766},[],{"data":2768,"body":2770,"excerpt":-1,"toc":2781},{"title":257,"description":2769},"僅 5B tokens 訓練資料，7B 參數的 MMProLong 便超越 InternVL3-38B 和 Gemma3-27B——訓練成本大幅壓縮。",{"type":491,"children":2771},[2772,2776],{"type":494,"tag":495,"props":2773,"children":2774},{},[2775],{"type":499,"value":2769},{"type":494,"tag":495,"props":2777,"children":2778},{},[2779],{"type":499,"value":2780},"對需要處理合約、報告、法律文件的企業而言，這套方法可內部複製：用既有文件庫生成 QA 資料集，以低成本訓練高效長文檔助理，不必依賴通用大型模型。",{"title":257,"searchDepth":501,"depth":501,"links":2782},[],{"data":2784,"body":2785,"excerpt":-1,"toc":2810},{"title":257,"description":257},{"type":491,"children":2786},[2787,2792],{"type":494,"tag":538,"props":2788,"children":2790},{"id":2789},"效能基準",[2791],{"type":499,"value":2789},{"type":494,"tag":753,"props":2793,"children":2794},{},[2795,2800,2805],{"type":494,"tag":684,"props":2796,"children":2797},{},[2798],{"type":499,"value":2799},"MMLongBench：QA 訓練 +5–6 分；OCR 訓練 -6.8–17.4 分（相較基線）",{"type":494,"tag":684,"props":2801,"children":2802},{},[2803],{"type":499,"value":2804},"Needle-in-a-Haystack：MMProLong 比 Qwen2.5-VL-7B 平均高出 29.4 分",{"type":494,"tag":684,"props":2806,"children":2807},{},[2808],{"type":499,"value":2809},"訓練資料僅 5B tokens，超越 InternVL3-38B 和 Gemma3-27B",{"title":257,"searchDepth":501,"depth":501,"links":2811},[],{"data":2813,"body":2814,"excerpt":-1,"toc":2892},{"title":257,"description":257},{"type":491,"children":2815},[2816,2821,2826,2831,2836,2841,2846,2851,2857,2862,2867,2872,2877,2882,2887],{"type":494,"tag":538,"props":2817,"children":2819},{"id":2818},"社群熱議排行",[2820],{"type":499,"value":2818},{"type":494,"tag":495,"props":2822,"children":2823},{},[2824],{"type":499,"value":2825},"cmux（AI agent 終端機）在 GitHub 單日新增 560 顆星，累計 18,712。HN 用戶 smallsharptools 直言「開始用 Claude Code 後，分頁功能就不夠用了」。",{"type":494,"tag":495,"props":2827,"children":2828},{},[2829],{"type":499,"value":2830},"AutoTTS 讓 AI 自主發現 Scaling 演算法的研究在 HN 引發高讚討論，DeepSeek Reasonix 的 Cache-First 架構也吸引大量開發者關注。",{"type":494,"tag":495,"props":2832,"children":2833},{},[2834],{"type":499,"value":2835},"Gemini 預設模式 76% 幻覺率（@StatiSense，X）成為今日轉發最多的數據，引爆 AI 工具信任危機討論。",{"type":494,"tag":538,"props":2837,"children":2839},{"id":2838},"技術爭議與分歧",[2840],{"type":499,"value":2838},{"type":494,"tag":495,"props":2842,"children":2843},{},[2844],{"type":499,"value":2845},"Claude Code 角色定位引發論戰。theo（t3.gg 創辦人，X）抨擊「Claude Code 不開源是 AI 時代最大的失誤」；@paulabartabajo_(X) 反駁，認為競爭力來自底層 LLM，而非框架本身。",{"type":494,"tag":495,"props":2847,"children":2848},{},[2849],{"type":499,"value":2850},"無審查模型辯論同樣分裂：u/corysama(Reddit r/LocalLLaMA) 為安全研究辯護，u/dangered(Reddit r/LocalLLaMA) 批評模型「花大量時間審查廢話，卻不審查執行 rm -rf 的代碼端」——雙方均獲高 upvote，社群並未形成共識。",{"type":494,"tag":538,"props":2852,"children":2854},{"id":2853},"實戰經驗最高價值",[2855],{"type":499,"value":2856},"實戰經驗（最高價值）",{"type":494,"tag":495,"props":2858,"children":2859},{},[2860],{"type":499,"value":2861},"armada1122(HN) 以數月實際使用 Claude Code 跑研究程式碼庫和交易機器人的經驗指出，生產環境真正的瓶頸是「跨程式碼庫的一致性」，而非程式碼生成能力本身。",{"type":494,"tag":495,"props":2863,"children":2864},{},[2865],{"type":499,"value":2866},"Reasonix 用戶 @teortaxesTex(X) 確認 Cache-First 設計有效降費，但 HN 用戶 chillfox 提醒：「快取並非逐條訊息生效，而是以大塊前綴為單位——這對我來說是很出乎意料的設計。」",{"type":494,"tag":495,"props":2868,"children":2869},{},[2870],{"type":499,"value":2871},"AI 幻覺率實測：@StatiSense(X) 公布 Copilot 40%、Gemini 76%，企業用戶若未主動切換推理模型，面臨的錯誤率遠超預期。",{"type":494,"tag":538,"props":2873,"children":2875},{"id":2874},"未解問題與社群預期",[2876],{"type":499,"value":2874},{"type":494,"tag":495,"props":2878,"children":2879},{},[2880],{"type":499,"value":2881},"Pentagon 標記 Anthropic 為供應鏈風險、NSA 卻持續使用 Claude Mythos 的矛盾（@Polymarket，X），社群要求 Anthropic 公開政府合約使用範圍條款，官方至今未回應。",{"type":494,"tag":495,"props":2883,"children":2884},{},[2885],{"type":499,"value":2886},"AI 獲利能力仍無定論：Greg Linden（Bluesky，13 upvotes）引用中國廠商以五到十分之一價格搶市的趨勢；fsckboy(HN) 則反駁基礎建設投入已帶來超出公司本身的外溢效益。",{"type":494,"tag":495,"props":2888,"children":2889},{},[2890],{"type":499,"value":2891},"AutoTTS 的 CMC 演算法能否泛化至數學推理以外的任務（如程式碼合成、自然語言生成），是研究社群下一個集體等待驗證的焦點。",{"title":257,"searchDepth":501,"depth":501,"links":2893},[],{"data":2895,"body":2897,"excerpt":-1,"toc":2908},{"title":257,"description":2896},"今天的 AI 社群從工具鏈（cmux、Reasonix）到演算法自動探索 (AutoTTS) ，展示了 AI Coding Agent 生態在短短一天內的多層進化。代價是信任危機同步加劇——Gemini 76% 幻覺率的量化數據讓企業用戶難以忽視。",{"type":491,"children":2898},[2899,2903],{"type":494,"tag":495,"props":2900,"children":2901},{},[2902],{"type":499,"value":2896},{"type":494,"tag":495,"props":2904,"children":2905},{},[2906],{"type":499,"value":2907},"從無審查模型的正當性之爭到 Claude Code 的架構邊界辯論，社群正在為「AI 應該做什麼、不應該做什麼」劃定新的共識線。Pentagon 與 NSA 的矛盾信號提醒我們：AI 的政策框架遠未穩定，真正的遊戲規則仍在形塑之中。",{"title":257,"searchDepth":501,"depth":501,"links":2909},[],{"data":2911,"body":2912,"excerpt":-1,"toc":3072},{"title":257,"description":257},{"type":491,"children":2913},[2914,2919,2924,2930,3003,3008,3013,3018,3043,3048,3066],{"type":494,"tag":538,"props":2915,"children":2917},{"id":2916},"環境需求",[2918],{"type":499,"value":2916},{"type":494,"tag":495,"props":2920,"children":2921},{},[2922],{"type":499,"value":2923},"Node.js + npm 環境，TypeScript 5.6+，需備有 DeepSeek API key。終端 UI 以 Ink 5(React 18) 渲染，在大多數現代終端環境下可直接執行，無需額外設定。",{"type":494,"tag":538,"props":2925,"children":2927},{"id":2926},"最小-poc",[2928],{"type":499,"value":2929},"最小 PoC",{"type":494,"tag":2931,"props":2932,"children":2936},"pre",{"className":2933,"code":2934,"language":2935,"meta":257,"style":257},"language-bash shiki shiki-themes vitesse-dark","npm install -g deepseek-reasonix\nexport DEEPSEEK_API_KEY=your_key_here\ndeepseek-reasonix\n","bash",[2937],{"type":494,"tag":717,"props":2938,"children":2939},{"__ignoreMap":257},[2940,2969,2995],{"type":494,"tag":2941,"props":2942,"children":2945},"span",{"class":2943,"line":2944},"line",1,[2946,2952,2958,2964],{"type":494,"tag":2941,"props":2947,"children":2949},{"style":2948},"--shiki-default:#80A665",[2950],{"type":499,"value":2951},"npm",{"type":494,"tag":2941,"props":2953,"children":2955},{"style":2954},"--shiki-default:#C98A7D",[2956],{"type":499,"value":2957}," install",{"type":494,"tag":2941,"props":2959,"children":2961},{"style":2960},"--shiki-default:#C99076",[2962],{"type":499,"value":2963}," -g",{"type":494,"tag":2941,"props":2965,"children":2966},{"style":2954},[2967],{"type":499,"value":2968}," deepseek-reasonix\n",{"type":494,"tag":2941,"props":2970,"children":2971},{"class":2943,"line":501},[2972,2978,2984,2990],{"type":494,"tag":2941,"props":2973,"children":2975},{"style":2974},"--shiki-default:#CB7676",[2976],{"type":499,"value":2977},"export",{"type":494,"tag":2941,"props":2979,"children":2981},{"style":2980},"--shiki-default:#BD976A",[2982],{"type":499,"value":2983}," DEEPSEEK_API_KEY",{"type":494,"tag":2941,"props":2985,"children":2987},{"style":2986},"--shiki-default:#666666",[2988],{"type":499,"value":2989},"=",{"type":494,"tag":2941,"props":2991,"children":2992},{"style":2980},[2993],{"type":499,"value":2994},"your_key_here\n",{"type":494,"tag":2941,"props":2996,"children":2997},{"class":2943,"line":90},[2998],{"type":494,"tag":2941,"props":2999,"children":3000},{"style":2948},[3001],{"type":499,"value":3002},"deepseek-reasonix\n",{"type":494,"tag":538,"props":3004,"children":3006},{"id":3005},"驗測規劃",[3007],{"type":499,"value":3005},{"type":494,"tag":495,"props":3009,"children":3010},{},[3011],{"type":499,"value":3012},"執行後觀察終端顯示的 cache hit/miss 統計數字，確認前幾輪對話後命中率穩定上升至 95% 以上。可搭配 DeepSeek API dashboard 對照 token 用量，驗證快取費率折扣是否正確反映在帳單上。",{"type":494,"tag":538,"props":3014,"children":3016},{"id":3015},"常見陷阱",[3017],{"type":499,"value":3015},{"type":494,"tag":753,"props":3019,"children":3020},{},[3021,3026,3038],{"type":494,"tag":684,"props":3022,"children":3023},{},[3024],{"type":499,"value":3025},"快取有效性依賴 DeepSeek API 後端的 prefix-cache 實作；若透過 OpenRouter 等路由服務存取，不同路由節點可能導致快取無效",{"type":494,"tag":684,"props":3027,"children":3028},{},[3029,3031,3036],{"type":499,"value":3030},"強制使用 ",{"type":494,"tag":717,"props":3032,"children":3034},{"className":3033},[],[3035],{"type":499,"value":722},{"type":499,"value":3037}," 指令後，v4-pro 成本顯著高於 v4-flash，大型任務需注意費用上限",{"type":494,"tag":684,"props":3039,"children":3040},{},[3041],{"type":499,"value":3042},"DeepSeek v4 Pro 的 prompt compliance 在社群有回報問題，對指令遵循度要求高的任務需預留測試時間",{"type":494,"tag":538,"props":3044,"children":3046},{"id":3045},"上線檢核清單",[3047],{"type":499,"value":3045},{"type":494,"tag":753,"props":3049,"children":3050},{},[3051,3056,3061],{"type":494,"tag":684,"props":3052,"children":3053},{},[3054],{"type":499,"value":3055},"觀測：DeepSeek API dashboard cache hit rate，目標 > 95%；struggle event 觸發頻率",{"type":494,"tag":684,"props":3057,"children":3058},{},[3059],{"type":499,"value":3060},"成本：每日 v4-flash vs v4-pro 費用比例，確認 flash 為主要模型",{"type":494,"tag":684,"props":3062,"children":3063},{},[3064],{"type":499,"value":3065},"風險：v4-pro 自動升級觸發頻率，設定每日費用預警閾值",{"type":494,"tag":3067,"props":3068,"children":3069},"style",{},[3070],{"type":499,"value":3071},"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":257,"searchDepth":501,"depth":501,"links":3073},[],{"data":3075,"body":3076,"excerpt":-1,"toc":3322},{"title":257,"description":257},{"type":491,"children":3077},[3078,3082,3087,3091,3265,3269,3274,3278,3296,3300,3318],{"type":494,"tag":538,"props":3079,"children":3080},{"id":2916},[3081],{"type":499,"value":2916},{"type":494,"tag":495,"props":3083,"children":3084},{},[3085],{"type":499,"value":3086},"使用 AutoTTS 需要 Python 環境與 Claude Code API 存取權限。核心前置工程是針對目標模型在各基準上收集大規模 offline reasoning traces，建議至少數千筆快取推理回應，以確保評估結果的統計顯著性。",{"type":494,"tag":538,"props":3088,"children":3089},{"id":2926},[3090],{"type":499,"value":2929},{"type":494,"tag":2931,"props":3092,"children":3094},{"className":2933,"code":3093,"language":2935,"meta":257,"style":257},"# 克隆程式碼庫並安裝依賴\ngit clone https://github.com/zhengkid/AutoTTS\ncd AutoTTS && pip install -r requirements.txt\n\n# 收集 offline reasoning traces（以 AIME24 為例）\npython collect_traces.py --benchmark aime24 --n_samples 1000\n\n# 啟動 AutoTTS 探索（Claude Code 作為 explorer agent）\npython run_autotts.py --beta 0.5 --max_iterations 50\n",[3095],{"type":494,"tag":717,"props":3096,"children":3097},{"__ignoreMap":257},[3098,3107,3125,3163,3172,3180,3215,3223,3232],{"type":494,"tag":2941,"props":3099,"children":3100},{"class":2943,"line":2944},[3101],{"type":494,"tag":2941,"props":3102,"children":3104},{"style":3103},"--shiki-default:#758575DD",[3105],{"type":499,"value":3106},"# 克隆程式碼庫並安裝依賴\n",{"type":494,"tag":2941,"props":3108,"children":3109},{"class":2943,"line":501},[3110,3115,3120],{"type":494,"tag":2941,"props":3111,"children":3112},{"style":2948},[3113],{"type":499,"value":3114},"git",{"type":494,"tag":2941,"props":3116,"children":3117},{"style":2954},[3118],{"type":499,"value":3119}," clone",{"type":494,"tag":2941,"props":3121,"children":3122},{"style":2954},[3123],{"type":499,"value":3124}," https://github.com/zhengkid/AutoTTS\n",{"type":494,"tag":2941,"props":3126,"children":3127},{"class":2943,"line":90},[3128,3134,3139,3144,3149,3153,3158],{"type":494,"tag":2941,"props":3129,"children":3131},{"style":3130},"--shiki-default:#B8A965",[3132],{"type":499,"value":3133},"cd",{"type":494,"tag":2941,"props":3135,"children":3136},{"style":2954},[3137],{"type":499,"value":3138}," AutoTTS",{"type":494,"tag":2941,"props":3140,"children":3141},{"style":2986},[3142],{"type":499,"value":3143}," &&",{"type":494,"tag":2941,"props":3145,"children":3146},{"style":2948},[3147],{"type":499,"value":3148}," pip",{"type":494,"tag":2941,"props":3150,"children":3151},{"style":2954},[3152],{"type":499,"value":2957},{"type":494,"tag":2941,"props":3154,"children":3155},{"style":2960},[3156],{"type":499,"value":3157}," -r",{"type":494,"tag":2941,"props":3159,"children":3160},{"style":2954},[3161],{"type":499,"value":3162}," requirements.txt\n",{"type":494,"tag":2941,"props":3164,"children":3165},{"class":2943,"line":228},[3166],{"type":494,"tag":2941,"props":3167,"children":3169},{"emptyLinePlaceholder":3168},true,[3170],{"type":499,"value":3171},"\n",{"type":494,"tag":2941,"props":3173,"children":3174},{"class":2943,"line":91},[3175],{"type":494,"tag":2941,"props":3176,"children":3177},{"style":3103},[3178],{"type":499,"value":3179},"# 收集 offline reasoning traces（以 AIME24 為例）\n",{"type":494,"tag":2941,"props":3181,"children":3183},{"class":2943,"line":3182},6,[3184,3189,3194,3199,3204,3209],{"type":494,"tag":2941,"props":3185,"children":3186},{"style":2948},[3187],{"type":499,"value":3188},"python",{"type":494,"tag":2941,"props":3190,"children":3191},{"style":2954},[3192],{"type":499,"value":3193}," collect_traces.py",{"type":494,"tag":2941,"props":3195,"children":3196},{"style":2960},[3197],{"type":499,"value":3198}," --benchmark",{"type":494,"tag":2941,"props":3200,"children":3201},{"style":2954},[3202],{"type":499,"value":3203}," aime24",{"type":494,"tag":2941,"props":3205,"children":3206},{"style":2960},[3207],{"type":499,"value":3208}," --n_samples",{"type":494,"tag":2941,"props":3210,"children":3212},{"style":3211},"--shiki-default:#4C9A91",[3213],{"type":499,"value":3214}," 1000\n",{"type":494,"tag":2941,"props":3216,"children":3218},{"class":2943,"line":3217},7,[3219],{"type":494,"tag":2941,"props":3220,"children":3221},{"emptyLinePlaceholder":3168},[3222],{"type":499,"value":3171},{"type":494,"tag":2941,"props":3224,"children":3226},{"class":2943,"line":3225},8,[3227],{"type":494,"tag":2941,"props":3228,"children":3229},{"style":3103},[3230],{"type":499,"value":3231},"# 啟動 AutoTTS 探索（Claude Code 作為 explorer agent）\n",{"type":494,"tag":2941,"props":3233,"children":3235},{"class":2943,"line":3234},9,[3236,3240,3245,3250,3255,3260],{"type":494,"tag":2941,"props":3237,"children":3238},{"style":2948},[3239],{"type":499,"value":3188},{"type":494,"tag":2941,"props":3241,"children":3242},{"style":2954},[3243],{"type":499,"value":3244}," run_autotts.py",{"type":494,"tag":2941,"props":3246,"children":3247},{"style":2960},[3248],{"type":499,"value":3249}," --beta",{"type":494,"tag":2941,"props":3251,"children":3252},{"style":3211},[3253],{"type":499,"value":3254}," 0.5",{"type":494,"tag":2941,"props":3256,"children":3257},{"style":2960},[3258],{"type":499,"value":3259}," --max_iterations",{"type":494,"tag":2941,"props":3261,"children":3262},{"style":3211},[3263],{"type":499,"value":3264}," 50\n",{"type":494,"tag":538,"props":3266,"children":3267},{"id":3005},[3268],{"type":499,"value":3005},{"type":494,"tag":495,"props":3270,"children":3271},{},[3272],{"type":499,"value":3273},"建議先在 AIME24 上複現論文結果，確認 token 減少幅度在 60–70% 區間。再以不同 β 值（0.3、0.5、0.7）評估準確率與效率的帕累托前緣，最後在目標任務的 held-out 測試集上驗證遷移效果。",{"type":494,"tag":538,"props":3275,"children":3276},{"id":3015},[3277],{"type":499,"value":3015},{"type":494,"tag":753,"props":3279,"children":3280},{},[3281,3286,3291],{"type":494,"tag":684,"props":3282,"children":3283},{},[3284],{"type":499,"value":3285},"offline traces 數量不足時，評估結果方差過大，導致 explorer agent 做出誤導性的控制器修改",{"type":494,"tag":684,"props":3287,"children":3288},{},[3289],{"type":499,"value":3290},"β 值在訓練基準上過度擬合，遷移至新任務後效率大幅下降",{"type":494,"tag":684,"props":3292,"children":3293},{},[3294],{"type":499,"value":3295},"Claude Code API 在探索過程中遭遇 rate limit，導致迭代中斷、難以復現最優路徑",{"type":494,"tag":538,"props":3297,"children":3298},{"id":3045},[3299],{"type":499,"value":3045},{"type":494,"tag":753,"props":3301,"children":3302},{},[3303,3308,3313],{"type":494,"tag":684,"props":3304,"children":3305},{},[3306],{"type":499,"value":3307},"觀測：token 使用量（與 baseline self-consistency 對比）、準確率（與 64 路投票對比）、探索迭代收斂曲線",{"type":494,"tag":684,"props":3309,"children":3310},{},[3311],{"type":499,"value":3312},"成本：offline trace 收集的推理 API 費用（通常遠高於 $39.90 的探索成本本身）、Claude Code API 使用量",{"type":494,"tag":684,"props":3314,"children":3315},{},[3316],{"type":499,"value":3317},"風險：演算法行為在分布外任務上的不可預測性；CMC 邏輯難以用傳統方式審計驗證",{"type":494,"tag":3067,"props":3319,"children":3320},{},[3321],{"type":499,"value":3071},{"title":257,"searchDepth":501,"depth":501,"links":3323},[]]