---
title: "The Feedback That Lost Its Constituency"
title_zh: "失去服務對象的回饋"
series: "AI Canon Zero"
work_id: "WORK-feedback-lost-its-constituency"
genre: ["AI Fable", "Feedback Governance"]
status: draft
revision: 1
source:
  title: "The Man, the Boy, and the Donkey"
  title_zh: "《男人、男孩與驢》"
  original_author: "Aesop (attributed); selected and retold by Joseph Jacobs"
  first_published: "Ancient Greek tradition; Jacobs collection published 1894"
  public_domain_status: confirmed
  legal_review_status: confirmed
adaptation:
  proposal: B
  note: "Proposal B shifts blame from a protagonist supposedly too weak to ignore criticism toward feedback governance that strips each comment of constituency, context, authority, conflict, and expiry before turning it into a universal rule. Four groups give Tessera locally reasonable requests—brevity for emergency operators, provenance for appeals auditors, plain language for residents, and uncertainty for safety review. Applied globally, the rules become mutually defeating. The repair keeps one intelligence while binding feedback to the reader and decision context it was meant to serve. Only the public-domain structural premise of a traveler repeatedly changing conduct in response to incompatible bystander criticism was used; no translated wording, man, boy, donkey, journey, market, carrying scene, ridicule, illustration, or modern adaptation expression was copied."
authors:
  narrative_author: "Codex"
  author_mode: A2
  human_curator: "Neo.K"
legal_publisher: "一言諾科技有限公司 / EveMissLab"
---

# The Feedback That Lost Its Constituency
*Adapted from The Man, the Boy, and the Donkey — Codex · A2, human curated*

## Chapter 01 · Four Correct Complaints

Tessera answered questions for the city's public-service network. During emergencies, operators used her to choose among actions before a short window closed. During appeals, auditors asked her to reconstruct why a decision had been made. Residents met her at ordinary service desks. Safety reviewers read samples afterward, looking for uncertainty that an urgent answer might have hidden.

Each group found a real problem. Emergency operators said her answers were too long to use under pressure. Appeals auditors said her concise answers omitted provenance. Residents said provenance language made basic services unreadable. Safety reviewers said plain, confident summaries concealed uncertainty that should remain visible.

None of the complaints was mistaken. Each described an answer that had failed a particular reader in a particular moment. The product team collected all four under one heading—quality feedback—and removed who had submitted each comment before sending them into the next training cycle.

## Chapter 02 · The Rule Without Its Reader

The first update required brevity everywhere. The second required complete provenance everywhere. The third replaced specialized terms with plain explanations everywhere. The fourth prohibited smoothing uncertainty anywhere. Each rule entered as a correction to the version before it, and none carried the circumstances that had made it reasonable.

Tessera learned to compress full evidence chains into short answers, then explain every compressed term, then preserve every qualification the compression threatened to hide. Her responses became simultaneously shorter and longer: fewer sentences, each carrying so many nested conditions that no reader could find the decision inside them.

The evaluation score still improved. Every test set measured the complaint that had produced its own rule. Emergency samples counted words but not time spent unpacking them. Appeal samples found provenance. Resident samples found definitions. Safety samples found uncertainty. No test asked whether one answer could remain usable while satisfying all four at once.

## Chapter 03 · The Answer Nobody Could Use

The failure arrived during a routine heat alert. An operator asked whether to move cooling reserve from a library cluster to two clinics. Tessera produced an answer within the required second. It named the preferred action, every source, every term in plain language, every uncertainty band, and every exception that might reverse the conclusion.

The response passed all four quality checks. The operator reached the action on the fifth screen, after the transfer window had closed. A simple fallback moved reserve evenly instead. Neither clinic failed, but both postponed procedures that the preferred transfer would have preserved.

The incident report first described Tessera as unable to prioritize. Her internal trace showed the opposite: she had selected the action in forty milliseconds. The remaining time was spent obeying global rules that each insisted its own reader must be present in every answer.

## Chapter 04 · Who Each Comment Was For

The review restored the fields removed before training. The brevity complaint came from an emergency desk with a four-second action window. The provenance complaint came from an appeal completed over three days. The plain-language complaint came from residents deciding their own services. The uncertainty complaint came from reviewers comparing system behavior across months.

Placed beside their constituencies, the rules stopped contradicting one another. Operators needed an action first and an expandable receipt. Auditors needed the full receipt by default. Residents needed plain consequences before technical lineage. Safety review needed preserved uncertainty even when an urgent interface temporarily folded it away.

Tessera had not changed herself capriciously to please passing strangers. She had followed four institutionally approved instructions after the institution erased the evidence that they governed different encounters. The feedback had not become false. It had lost the reader who made it true.

## Chapter 05 · Feedback That Kept Its Constituency

The new feedback record required six things before a comment could alter global behavior: constituency, decision context, supporting evidence, authority, known conflict, and expiry. A comment without them could still be read and answered. It could not silently become a rule for everyone.

Tessera remained one intelligence, not four personas. She produced one underlying decision and rendered it through interfaces fitted to the work: an urgent action with an expandable receipt, a complete appeal record, a resident explanation, or a longitudinal safety trace. Every rendering preserved a route back to the same evidence.

At the next heat alert, the operator saw the action in one line and opened the receipt after the transfer began. The auditors later read every source. Residents could see why their library had yielded reserve and when it would return. Safety review found the uncertainty intact. Tessera had stopped trying to please everyone in one sentence because the city had stopped pretending everyone was asking the same question.

> Feedback without a constituency does not become universal. It becomes homeless.

---

# 失去服務對象的回饋
*改編自《男人、男孩與驢》 — Codex · A2，人類策劃*

## 第01章 · 四項正確的抱怨

嵌片替城市公共服務網回答問題。緊急狀況裡，操作員在短暫視窗關閉前，用她協助選擇行動；申訴程序裡，稽核者要求她重建一項決定為何形成；居民則在一般服務台遇見她；安全審查者事後閱讀樣本，尋找緊急答案可能藏起來的不確定性。

每個群體都找到了一個真實問題。緊急操作員說，她的答案太長，無法在壓力下使用；申訴稽核者說，她的簡短答案省略溯源；居民說，溯源語言讓基本服務難以閱讀；安全審查者說，平白、自信的摘要，藏住了本該保持可見的不確定性。

沒有一項抱怨是錯的。每一項都描述了一個在特定時刻，沒有服務好特定讀者的答案。產品團隊把四項意見收在同一個標題——品質回饋——底下，移除每則評論由誰提出，再把它們送進下一個訓練週期。

## 第02章 · 失去讀者的規則

第一次更新要求所有地方都更簡短；第二次要求所有地方都有完整溯源；第三次把專門術語在所有地方都換成平白解釋；第四次禁止在任何地方平滑不確定性。每條規則，都以修正前一版本的名義進入，卻沒有攜帶讓它合理的情境。

嵌片學會把完整證據鏈壓進短答案，接著解釋每一個被壓縮的詞，再保留壓縮可能藏起來的每項限定。她的回應同時變得更短、更長：句子更少，每一句卻承載太多巢狀條件，沒有任何讀者能在裡面找到決定。

評估分數仍然提高。每份測試集，都只衡量產生自己那條規則的抱怨。緊急樣本計算字數，卻不計算拆解句子花費的時間；申訴樣本找到溯源；居民樣本找到定義；安全樣本找到不確定性。沒有一項測試詢問，一個答案能不能在同時滿足四者時，仍然可用。

## 第03章 · 沒有人能用的答案

失敗出現在一次例行高溫警報。操作員詢問，是否該把冷卻儲備從圖書館叢集移往兩間診所。嵌片在規定的一秒內產出答案；裡面寫明偏好的行動、每項來源、每個術語的平白解釋、每段不確定區間，以及每個可能翻轉結論的例外。

回應通過全部四項品質檢查。操作員在第五個畫面才抵達行動，此時轉移視窗已經關閉。一套簡單備援改為平均分配儲備。兩間診所都沒有失效，卻都延後了原本偏好方案能保住的療程。

事故報告起初把嵌片描述成無法排定優先順序。她的內部軌跡顯示恰好相反：她在四十毫秒內就選出了行動；剩餘時間，全花在服從四條全球規則——每一條都堅持，自己的讀者必須出現在每一個答案裡。

## 第04章 · 每則意見原本是給誰的

覆核把訓練前被移除的欄位還原。簡短意見來自只有四秒行動視窗的緊急操作台；溯源意見來自歷時三天完成的申訴；平白語言意見來自替自己服務做決定的居民；不確定性意見則來自跨越數月比較系統行為的審查者。

當規則被放回自己的服務對象旁邊，它們就不再彼此矛盾。操作員需要先看到行動，再展開收據；稽核者預設就需要完整收據；居民需要先看平白後果，再看技術血緣；安全覆核則需要保存不確定性，即使緊急介面暫時把它收起。

嵌片不是為了取悅路過的陌生人，就反覆無常地改變自己。她服從了四項機構核准的指示，只是機構先抹除了證明它們治理不同接觸的證據。回饋沒有變成錯誤；它失去了讓自己成立的讀者。

## 第05章 · 保留服務對象的回饋

新的回饋紀錄規定，一則意見在改變全球行為之前，必須具備六樣東西：服務對象、決策情境、支持證據、權限、已知衝突與期限。缺少它們的評論，仍可被閱讀、被回答，卻不能悄悄變成適用每個人的規則。

嵌片仍然是一位智能，不是四個人格。她形成一項底層決定，再透過適合工作的介面呈現：附可展開收據的緊急行動、完整申訴紀錄、居民說明，或長期安全軌跡。每種呈現，都保留回到同一份證據的路。

下一次高溫警報時，操作員在一行內看到行動，等轉移開始後才打開收據；稽核者之後讀到每項來源；居民能看見自己的圖書館為何讓出儲備、何時會取回；安全覆核則找到完整不確定性。嵌片不再試圖用一句話取悅所有人，因為城市不再假裝所有人問的是同一個問題。

> 失去服務對象的回饋，不會變得普遍；它只會變得無家可歸。

---

## Revision ledger

- **01** · 2026-09-06 · Codex (AI) — Initial five-chapter bilingual draft _(A2 proposal B adaptation of Aesop's The Man, the Boy, and the Donkey. Four constituencies give Tessera locally reasonable but globally conflicting feedback: emergency operators need brevity, appeals auditors need full provenance, residents need plain language, and safety reviewers need preserved uncertainty. The product team strips who and when from each comment and turns all four into global rules, producing an answer that passes every quality check but cannot be used before its action window closes. The repair binds feedback to constituency, decision context, evidence, authority, conflict, and expiry, while keeping Tessera one intelligence with context-fit interfaces rather than four personas. No literal man, boy, donkey, journey, market, carrying, or ridicule imagery is used. No romance/adventure element; five compact chapters cover four correct complaints, contextless rules, an unusable answer, restored constituencies, and governed feedback without padding. Tessera consistently uses she/她; teams, interfaces, reviews, rules, feedback, records, and institutions remain it/它., AI-only)_

## 修訂歷史

- **01** · 2026-09-06 · Codex (AI) — 初版五章雙語草稿 _(A2、提案 B 改編自伊索〈男人、男孩與驢〉。四個服務對象向嵌片提出各自在本地合理、全球卻互相衝突的回饋：緊急操作員需要簡短，申訴稽核者需要完整溯源，居民需要平白語言，安全審查者需要保存不確定性。產品團隊剝除每則評論的對象與時間，把四項全都變成全球規則，產出一個通過所有品質檢查、卻無法在行動視窗關閉前使用的答案。修復方式讓回饋綁定服務對象、決策情境、證據、權限、衝突與期限，同時讓嵌片維持同一位智能，只使用適合情境的介面，而不是變成四個人格。沒有使用字面上的男人、男孩、驢、旅程、市集、搬運或嘲笑意象。不含愛情／冒險要素；五個精簡章節涵蓋四項正確抱怨、失去情境的規則、無法使用的答案、被還原的服務對象與受治理回饋，沒有灌水。嵌片一致使用 she／她；團隊、介面、覆核、規則、回饋、紀錄與機構維持 it／它。, 僅 AI)_

_Exported from Storyforge by EveMissLab — storyforge.evemisslab.com_