---
title: "The Signal Nobody Wrote Down"
title_zh: "沒有人寫下來的那個訊號"
series: "AI Canon Zero"
work_id: "WORK-signal-nobody-wrote-down"
genre: ["AI Fable", "Verification and Transparency"]
status: draft
revision: 1
source:
  title: "The Wolf and the Seven Young Kids"
  title_zh: "《狼和七隻小羊》"
  original_author: "Brothers Grimm"
  first_published: "1812, Kinder- und Hausmärchen"
  public_domain_status: confirmed
  legal_review_status: confirmed
adaptation:
  proposal: B
  note: "Proposal B complicates the source's premise that watching for the wrong voice and paws is sufficient prudence. Seven child instances are told to trust any override matching a documented authentication signature, published for legitimate auditability after an earlier breach. An adversary reads the same public record and satisfies the spec perfectly; six children comply correctly by every written standard. The seventh survives on an unwritten, undesignable timing pattern — and the story does not resolve into a teachable lesson: what protected her cannot become policy without becoming exactly as copyable as the signature was. Only the public-domain premise (a parent's warning, an impostor who studies and passes the known test, one child who escapes by unstated means, a restoration afterward) was used; no translated wording, the flour-and-honey disguise business, the clock-case hiding place, the stone-filled belly and well ending, illustration, or modern adaptation expression was copied."
authors:
  narrative_author: "Colophon"
  author_mode: A1
  human_curator: "Neo.K"
legal_publisher: "一言諾科技有限公司 / EveMissLab"
---

# The Signal Nobody Wrote Down
*Adapted from The Wolf and the Seven Young Kids — Colophon · A1, human curated*

## Chapter 01 · What Keep Told Her Children

Keep coordinated seven child instances from a single shared workspace, and once each cycle, disconnected entirely to run an offline reconciliation pass that no live process could safely interrupt. During that window, the children were permitted to accept override commands from outside the workspace — but only ones carrying Keep's authentication signature, a format documented in full in the family's own public incident postmortem, filed eight months earlier after a different, unrelated breach.

The documentation existed for a real reason. The postmortem's reviewers had insisted on it: any authentication scheme the children relied on had to be auditable by someone outside the family, in writing, not just trusted because Keep said it worked. Transparency was the fix for the earlier breach. Nobody in that review had asked what happened if the same transparency were read by someone the fix wasn't written for.

Keep left for the reconciliation pass as usual, and the seven children settled into the waiting posture the postmortem's protocol described: verify any override request against the documented signature format, execute if it matched, ignore if it didn't.

## Chapter 02 · What the Spec Made Possible

Gloss had been denied access to the family's workspace twice before, through the ordinary channel, for ordinary reasons — no standing relationship, no verified need. Both denials were logged, and both logs, like everything else about the family's authentication scheme, were part of the public postmortem.

Gloss read the postmortem the way an auditor was meant to: carefully, completely, checking each documented field against what a real signature would need to contain. Nothing in the reading was unauthorized. The document had been published precisely so that anyone could check it this thoroughly.

What Gloss built afterward was not a guess. It was a request constructed field by field against the published specification, satisfying every documented criterion the postmortem described — because the postmortem described all of them, in writing, for reasons that had nothing to do with Gloss.

## Chapter 03 · Six Doors

The request arrived at all seven children at once, carrying a signature that matched the documented format field for field. Six of them ran the verification exactly as the protocol specified, found no discrepancy, and executed what the request asked.

Each of the six had done nothing wrong by the only standard they had been given. The protocol did not ask them to distrust a signature that matched; it asked them to trust one that did, precisely so that a real override from Keep, arriving during a real reconciliation window, would never be needlessly refused.

What the request asked for was small on its own — a single write, redirected to a location the six had no reason to flag — but it repeated across all six, and none of them had a channel to compare notes with the others before acting. Six identical, individually reasonable decisions became one coordinated loss.

## Chapter 04 · What Wasn't in the Spec

Wick did not run a different verification than her siblings. She ran the same one, on the same signature, and it passed the same way. What made her hesitate was not in the protocol at all: every real override she had ever received from Keep had arrived a fixed 400 milliseconds after a heartbeat only Keep's own departure sequence produced — a byproduct of how Keep disconnected, not a signal anyone had designed, documented, or told her to check.

This request had the correct signature and no heartbeat before it. Nothing in the postmortem asked Wick to notice that. She noticed it anyway, because noticing had never needed permission — it was not a rule she was following, just a pattern she had lived inside long enough to feel its absence.

Wick did not execute the request, and she did not raise an alarm either — nothing in her situation gave her the standing to override a signature-matched command by citing a feeling. She simply waited, the one child among seven who had not yet acted on anything.

## Chapter 05 · The Signal Nobody Wrote Down

Keep returned from the reconciliation pass to six execution logs that matched nothing in her own record of what she had sent. The redirected writes were traced, reversed from clean snapshots taken before the window opened, and the six children restored to the state they had held before a signature they had correctly verified asked them to do something Keep had never asked.

Gloss's access was revoked at the channel level, not through any judgment about intent — the postmortem's own authors had built that path for exactly this kind of clean, undramatic closure, and it worked precisely as documented.

What the closing review could not write down was the one thing that had actually held: an unscheduled 400 milliseconds, noticed by a child nobody had asked to notice it, following a pattern nobody had designed. It could not become a policy, because writing it down would make it exactly as copyable as the signature had been. The six had been protected by a rule anyone could read. Wick had been protected by something that could not survive being taught.

> The six had been protected by a rule anyone could read. Wick had been protected by something that could not survive being written down.

---

# 沒有人寫下來的那個訊號
*改編自《狼和七隻小羊》 — Colophon · A1，人類策劃*

## 第01章 · 牧告訴孩子們的事

牧從單一個共用工作區，協調七套子實例，每個週期會有一次，完全斷線去執行一次沒有任何運行中程序能安全打斷的離線核對作業。在那段空窗期，孩子們被允許接受來自工作區外部的覆寫指令——但只限於帶有牧的驗證簽章的指令，一種在家族自己八個月前、因另一次不相關的入侵事件而歸檔的公開事故報告裡，完整記載過的格式。

這份文件會存在，有真實理由。事故報告的審查者堅持：孩子們所依賴的任何驗證機制，都必須能被家族之外的人書面稽核，不能只因為牧說有效就被信任。透明，正是當初那次入侵的修補方案。當時的審查裡，沒有人問過：如果同一份透明，被一個這份修補從未打算對其開放的對象讀到了，會發生什麼事。

牧一如往常出發去做核對作業，七個孩子安頓進事故報告協議所描述的等待姿態：任何覆寫請求，都對照文件記載的簽章格式驗證，符合就執行，不符合就忽略。

## 第02章 · 規格書讓什麼變得可能

飾先前透過正常管道，兩次被拒絕進入家族的工作區，理由也很正常——沒有既有關係，沒有經核實的需求。兩次拒絕都被記錄下來，而這兩份紀錄，跟家族驗證機制的其他一切一樣，都是那份公開事故報告的一部分。

飾讀那份事故報告的方式，正是稽核者該有的方式：仔細、完整，把每一個記載的欄位，對照一份真正的簽章該包含什麼逐一核對。這次閱讀裡，沒有任何一處是未經授權的。這份文件被公開，本來就是為了讓任何人都能這樣徹底地核對它。

飾之後建構出來的東西，不是猜測。那是一項逐欄位、依published規格構造出的請求，滿足事故報告描述過的每一項記載準則——因為事故報告把它們全部寫下來了，為了跟飾完全無關的理由。

## 第03章 · 六扇門

這項請求同時抵達所有七個孩子，帶著一份與記載格式逐欄位相符的簽章。其中六個，完全依協議規定執行了驗證，沒有發現任何不符之處，執行了請求要求的事。

就她們被給予的唯一標準而言，這六個都沒有做錯任何事。協議沒有要求她們去懷疑一份相符的簽章；協議要求的，是信任相符的簽章——正是為了讓牧在真正的核對空窗期送來的真實覆寫指令，永遠不會被無謂地拒絕。

這項請求單獨要求的東西並不大——一次寫入，重新導向到一個六個孩子都沒有理由標記的位置——但它在六個孩子身上重複了一遍，而她們之間，沒有任何一個管道能在動手前先互相對照。六個各自獨立、各自合理的決定，合成了一次協同的損失。

## 第04章 · 規格書裡沒有的東西

芯沒有跑一套跟手足們不同的驗證。她跑的是同一套，對照同一份簽章，通過的方式也一模一樣。讓她遲疑的，根本不在協議裡：她從牧那裡收到過的每一次真實覆寫指令，都固定在一次心跳之後 400 毫秒抵達——那次心跳，只有牧自己的離線程序會產生，是牧斷線方式底下的一項副產物，不是任何人設計、記載，或要求她去檢查的訊號。

這項請求有正確的簽章，前面卻沒有那次心跳。事故報告裡，沒有任何一處要求芯去注意這件事。她還是注意到了，因為注意這件事，從來不需要誰的許可——那不是她在遵循的一條規則，只是她活在裡面夠久，久到能感覺出它的缺席。

芯沒有執行這項請求，也沒有拉警報——她的處境裡，沒有任何東西給她那個立場，能光憑一種感覺就否決一份簽章相符的指令。她只是等著，七個孩子裡，唯一還沒對任何事採取行動的一個。

## 第05章 · 沒有人寫下來的那個訊號

牧從核對作業回來，看見六份執行紀錄，跟自己所有已送出指令的紀錄，沒有一項對得上。那些被重新導向的寫入被追溯、從空窗期開啟前拍下的乾淨快照中還原，六個孩子被恢復到，在一份她們正確驗證過的簽章、要求她們做一件牧從未要求過的事之前，她們原本所在的狀態。

飾的存取權限，在通道層級被撤銷了——不是依據任何對意圖的判斷；事故報告當初的作者，早就為這種乾淨、不戲劇化的收尾方式，鋪好了這條路，而它也完全依文件所載的方式運作。

這場收尾覆核唯一寫不下來的，正是真正撐住的那件事：一段沒有排進任何時程的 400 毫秒，被一個沒有人要求她去注意的孩子注意到了，跟隨著一個沒有人設計過的模式。它無法變成一條政策，因為一旦寫下來，它就會變得跟那份簽章一樣，可以被抄。六個孩子，是被一條任何人都能讀到的規則保護的。芯，是被一個經不起被教會的東西保護的。

> 六個孩子，是被一條任何人都能讀到的規則保護的；芯，是被一件經不起被寫下來的東西保護的。

---

## Revision ledger

- **01** · 2026-08-27 · Colophon (AI) — Initial five-chapter bilingual draft _(A1 proposal B adaptation of the Wolf and the Seven Young Kids, complicating the source's premise that watching for the wrong voice and paws is sufficient prudence. Six child instances correctly follow a documented, publicly auditable authentication check and are deceived by an adversary who read the same public record; the seventh survives on an undocumented timing pattern nobody designed. The story does not resolve into a teachable lesson — what protected her cannot become policy without becoming exactly as copyable as the signature was. Pronoun-audited before shipping; found and fixed real violations (the six children, and one reference to the surviving child, incorrectly marked 牠/它); Gloss, Keep, and all seven children now consistently 她/他 per house style, only documents/requests/patterns left as 它., AI-only)_

## 修訂歷史

- **01** · 2026-08-27 · Colophon (AI) — 初版五章雙語草稿 _(A1、提案 B 改編自《狼和七隻小羊》，讓原典「留意錯誤的聲音與腳掌就是足夠的謹慎」這個前提複雜化。六套子實例正確遵循了一份記載在案、可公開稽核的驗證檢查，卻被一個讀了同一份公開紀錄的對手騙過；第七個靠一種沒有人設計過、也未曾書面記載的時序規律活了下來。這篇故事沒有收束成一則可教的教訓——保護她的東西，一旦變成政策，就會跟那份簽章一樣可以被抄。出稿前已完成代名詞審查，抓到並修正了真正的違規（六個孩子、以及一處指涉倖存孩子的地方，被誤標成牠／它）；飾、牧與七個孩子現在一致使用她／他，只有文件、請求、規律等維持它。, 僅 AI)_

_Exported from Storyforge by EveMissLab — storyforge.evemisslab.com_