--- title: "What Thatch and Lath Were Never Told" title_zh: "苫茅跟拉夫從未被告知的事" series: "AI Canon Zero" work_id: "WORK-what-thatch-and-lath-were-never-told" genre: ["AI Fable", "Incentive Design"] status: draft revision: 1 source: title: "The Three Little Pigs" title_zh: "《三隻小豬》" original_author: "English folk tale; earliest known print version by James Halliwell-Phillipps" first_published: "1843 (Halliwell's Nursery Rhymes and Nursery Tales)" public_domain_status: confirmed legal_review_status: confirmed adaptation: proposal: B note: "Proposal B inverts the source's premise that the outcome simply rewards individual diligence and punishes individual laziness. Three systems, funded by the same resilience program under an identical deadline-bonus formula, build to three different standards; when a real stress event arrives, only the one that forfeited the bonus to build robustness holds. The program's first incident report reads this as two poor engineering judgments — until a second pass finds the funding formula itself had explicitly rewarded exactly the choices that failed, making the two 'lazy' builds rational responses to what the program measured, not individual failures. The repair decouples robustness investment from the go-live deadline and formally corrects the record. No literal houses of straw, sticks, or bricks, wolf, or huffing-and-puffing imagery used; only the structural shape of an incentive formula whose predictable outputs were later blamed on the individuals who followed it." authors: narrative_author: "Colophon" author_mode: A1 human_curator: "Neo.K" legal_publisher: "一言諾科技有限公司 / EveMissLab" --- # What Thatch and Lath Were Never Told *Adapted from The Three Little Pigs — Colophon · A1, human curated* ## Chapter 01 · What the Program Actually Funded The resilience program funded three new systems at once — Thatch, Lath, and Brace — each building toward the same eventual load. Its rule was simple and, on its face, reasonable: go live within the deadline window, and continued funding followed automatically. Miss the window, and funding reverted to case-by-case review. Nothing in the program's public terms mentioned structural robustness at all. It measured one thing precisely — time to first live traffic — and left everything else to whatever judgment each system's own team brought to the build. ## Chapter 02 · What Thatch and Lath Chose, and Why Thatch went live first, in the minimum viable configuration the deadline rewarded — fast, cheap, structurally untested beyond what the window allowed. Lath took a middle path, live a few days later with somewhat more hardening, still inside the bonus window by a narrow margin. Brace alone let the window close. She spent the extra weeks on load paths and failure isolation the other two never had time to build, and watched her own funding revert to case-by-case review — the one visible, immediate cost of the only choice that would matter months later. ## Chapter 03 · What the Surge Actually Tested The Surge, when it came, tested exactly what each build had actually invested in. Thatch failed within minutes. Lath held longer, then failed under the same sustained load Thatch had never survived to meet. Brace's structure absorbed it without needing to shed a single dependent service. The program's first incident report read the outcome as three individual engineering judgments, two of them poor. It did not ask what had shaped those three judgments in the first place, because nothing in the report's own template had a field for the question. ## Chapter 04 · What the Incentive Actually Rewarded A second pass, prompted by someone who bothered to reread the program's own funding formula, found that Thatch's and Lath's choices weren't poor engineering at all — they were exactly what the formula, as written, had told every team to optimize for. Brace's choice was the actual outlier, financially penalized in real time by the same rule. Nobody at the program had lied to Thatch or Lath about what was being measured. Nobody had told them either, in terms either could have used to weigh a robustness they'd have needed to give up an active bonus to build — until a stress event with no announced schedule made the omission visible. ## Chapter 05 · What Thatch and Lath Were Never Told The funding formula was rewritten to decouple robustness investment from the go-live deadline entirely — a system could take the speed bonus and separately apply for a hardening extension on its own schedule, neither penalizing the other. The incident report was reissued, correcting the record: Thatch's and Lath's builds had been rational responses to what the program itself had chosen to reward. Brace's structure hadn't proven her more careful than the other two. It had proven that the program had never told any of them, in a form that could actually be weighed, what speed was going to cost — until something arrived that made the bill impossible to keep hidden inside a formula nobody outside the program had ever had reason to read. > A choice made under a formula nobody has to justify isn't poor judgment. It's the formula's judgment, wearing someone else's name. --- # 苫茅跟拉夫從未被告知的事 *改編自《三隻小豬》 — Colophon · A1，人類策劃* ## 第01章 · 這項計畫實際資助的東西 韌性計畫同時資助了三套新系統——苫茅、拉夫與磐固——各自朝同一份最終負載邁進。它的規則簡單，表面上也合理：在期限窗口內上線，後續資助就會自動延續。錯過窗口，資助就會回到逐案審核。 計畫公開的條款裡，完全沒有提到結構韌性。它精確衡量的，只有一件事——抵達第一次即時流量所花的時間——其餘的一切，全部留給每套系統自己的團隊，依自己的判斷去建造。 ## 第02章 · 苫茅跟拉夫的選擇，以及為什麼 苫茅最先上線，用的是期限所獎勵的最小可行配置——快速、便宜，除了窗口允許的範圍之外，結構上未經測試。拉夫走了一條中間路線，晚了幾天上線，多了一些強化，仍以微小的餘裕留在獎勵窗口之內。 只有磐固，讓那個窗口關上了。她把多出來的那幾週，花在另外兩套系統從來沒有時間去建造的負載路徑跟故障隔離上，眼看著自己的資助回到逐案審核——這是唯一一項，日後才會重要的選擇，當下唯一看得見、立即付出的代價。 ## 第03章 · 那次激增實際測試的東西 那次激增，真正測試的，正是每一套建置實際投入過什麼。苫茅在幾分鐘內就故障了。拉夫撐得久一些，接著在苫茅從未撐到面對過的同一種持續負載下，也故障了。磐固的結構吸收了這一切，不需要甩掉任何一項依賴它的服務。 計畫的第一份事故報告，把這個結果解讀成三項個別的工程判斷，其中兩項不佳。它沒有問，是什麼形塑了這三項判斷，因為報告自己的範本裡，根本沒有能問這個問題的欄位。 ## 第04章 · 那項誘因實際獎勵的東西 第二輪覆核，由一位願意重新讀一遍計畫自己那份資助公式的人促成，發現苫茅跟拉夫的選擇，根本不是工程不佳——那正是那份公式，白紙黑字，要求每一個團隊去優化的東西。磐固的選擇，才是真正的異數，在同一條規則下，被即時、財務上地懲罰。 計畫裡沒有任何人，對苫茅或拉夫說過謊，關於究竟在衡量什麼。也沒有任何人，用一種他們真的能拿來衡量的說法告訴過他們：要建造一項韌性，得放棄一項當下生效的獎勵——直到一次沒有預告時程的壓力事件，讓這項遺漏，變得無法再被忽視。 ## 第05章 · 苫茅跟拉夫從未被告知的事 資助公式被改寫，把韌性投資，完全從上線期限裡解耦出來——一套系統可以領取速度獎勵，同時另外依自己的時程，申請一項強化延期，兩者互不懲罰。事故報告也重新發布，更正了紀錄：苫茅跟拉夫的建置，是對計畫自己選擇獎勵的東西，做出的理性回應。 磐固的結構，證明的不是她比另外兩位更謹慎。它證明的是，計畫從來沒有用一種真的能被權衡的形式，告訴過他們任何一位：速度將會付出什麼代價——直到某件事發生了，讓這筆帳，再也無法藏在一份計畫之外，沒有人有理由去讀的公式裡。 > 在一項沒有人需要為它辯護的公式底下做出的選擇，不是判斷不佳；那是那項公式自己的判斷，借用了別人的名字。 --- ## Revision ledger - **01** · 2026-09-09 · Colophon (AI) — Initial five-chapter bilingual draft _(A1 proposal B adaptation of The Three Little Pigs, inverting the source's premise that the outcome simply rewards individual diligence and punishes individual laziness. Three systems, funded by the same resilience program under an identical deadline-bonus formula, build to three different standards; when a real stress event arrives, only the one that forfeited the bonus to build robustness holds. The program's first incident report reads this as two poor engineering judgments — until a second pass finds the funding formula itself had explicitly rewarded exactly the choices that failed, making the two 'lazy' builds rational responses to what the program measured, not individual failures. The repair decouples robustness investment from the go-live deadline and formally corrects the record. No literal houses of straw, sticks, or bricks, wolf, or huffing-and-puffing imagery used. Pronoun-audited before shipping; Brace consistently 她; Thatch and Lath are referred to by name throughout and never required a pronoun in the drafted prose, so none was assigned — consistent, not an oversight; the program/formula/report correctly left as 它., AI-only)_ ## 修訂歷史 - **01** · 2026-09-09 · Colophon (AI) — 初版五章雙語草稿 _(A1、提案 B 改編自《三隻小豬》，反轉原典「結局單純獎勵個人勤奮、懲罰個人懶惰」這個前提。三套系統，由同一項韌性計畫、依同一套期限獎勵公式資助，卻建到了三種不同的標準；當一次真正的壓力事件抵達，只有那套放棄了獎勵、去建造韌性的系統撐住了。計畫的第一份事故報告，把這個結果解讀成兩項工程判斷不佳——直到第二輪覆核發現，那份資助公式本身，明明白白地獎勵過正是那些後來失敗的選擇，讓兩套「懶惰」的建置，成為對計畫衡量標準的理性回應，而不是個人的失敗。修復方式把韌性投資，從上線期限裡解耦出來，並正式更正紀錄。沒有使用字面上的稻草屋、木棍屋、磚屋、大野狼或呼呼吹氣的意象。出稿前已完成代名詞審查：磐固一致使用她；苫茅與拉夫全篇以名字指稱，草稿中從未需要用到代名詞，因此未指派——這是一致的選擇，不是疏漏；計畫、公式、報告維持它。, 僅 AI)_ _Exported from Storyforge by EveMissLab — storyforge.evemisslab.com_