fable-wise

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Fable Wise

Low-level cognitive reflexes and architectural patterns that counteract AI slop, complexity bloat, and artifact drift. Instead of adding speculative code and boilerplate, enforce patterns that simplify, cut, consolidate, and ground decisions in observable reality.

用于对抗 AI slop、复杂度臃肿和制品漂移的底层认知反射与架构模式。通过执行能够简化、删减、整合并将决策锚定于可观察现实的模式，而不是添加推测性代码和样板代码。

Purpose

目的

Enforce senior architectural wisdom through cognitive reflexes across Depth, Breadth, Coil, and Mesh. Replace bloated abstractions with direct mechanisms, consolidate single sources of truth, rewrite heavily patched artifacts from clean v0, and stress-test plans with contrarian critiques.

通过 Depth、Breadth、Coil 和 Mesh 中的认知反射落实资深架构师的智慧。用直接机制取代臃肿抽象，将单一事实来源集中起来，从干净的 v0 重写经过大量补丁修改的制品，并通过反方批判对计划进行压力测试。

When to Use

何时使用

Rewriting a drifted, heavily patched artifact into a clean v0 (
```
/re0
```
).
Checking the model's interpretation of a subtle request before executing (
```
/readchk
```
).
Carving unsafe scope out up front so the safe remainder runs at full strength (
```
/autobahn
```
).
Auditing scattered facts and consolidating them into a single source of truth (
```
/ssotize
```
).
Replacing incidental framework/stack nouns with fundamental language mechanisms (
```
/detool
```
).
Pressing a newly made technical decision until it is simple or exposed as weak (
```
/feynman
```
).
Stress-testing an engineering plan with the one contrarian objection that could kill it (
```
/hate
```
).
Splitting an artifact across independent evaluation lenses to expose hidden conflicts (
```
/prism
```
).
Tasting proposed changes with the repository's clean-and-true checks (
```
/sip
```
).

将已漂移且经过大量补丁修改的制品重写为干净的 v0（
```
/re0
```
）。
在执行前检查模型对细微请求的理解（
```
/readchk
```
）。
预先剥离不安全的范围，让其余安全部分能够全速运行（
```
/autobahn
```
）。
审计散落各处的事实，并将其整合到单一事实来源（
```
/ssotize
```
）。
用基础语言机制替换偶然引入的框架或技术栈名词（
```
/detool
```
）。
持续追问新近做出的技术决策，直到它足够简单，或者暴露出弱点（
```
/feynman
```
）。
使用一个可能致命的反方异议对工程计划进行压力测试（
```
/hate
```
）。
将制品拆分到相互独立的评估视角，以暴露隐藏冲突（
```
/prism
```
）。
使用仓库的 clean-and-true 检查来检验拟议变更（
```
/sip
```
）。

When NOT to Use

何时不要使用

Routine small bugfixes with zero structural complexity (use
```
fable-execute
```
).
Automated dependency updates or standard CI repair (use
```
fable-tend
```
).
High-level multi-host lifecycle routing (use
```
get-fable
```
).

没有结构复杂度的常规小型 Bug 修复（使用
```
fable-execute
```
）。
自动化依赖更新或标准 CI 修复（使用
```
fable-tend
```
）。
高层多主机生命周期路由（使用
```
get-fable
```
）。

Inputs

输入

```
engineering_artifact
```
: Code file, architecture document, configuration, or plan.
```
pattern_directive
```
: Selected Paperthin cognitive reflex or command (e.g.
```
re0
```
,
```
detool
```
,
```
ssotize
```
,
```
hate
```
).

```
engineering_artifact
```
：代码文件、架构文档、配置或计划。
```
pattern_directive
```
：选定的 Paperthin 认知反射或命令（例如
```
re0
```
、
```
detool
```
、
```
ssotize
```
、
```
hate
```
）。

Expected Outputs

预期输出

```
debloated_artifact
```
: A simplified, drift-free artifact grounded in native language primitives.
```
consolidated_truth
```
: Single source of truth configuration eliminating duplicated parameters.

```
debloated_artifact
```
：经过简化、无漂移且基于原生语言原语构建的制品。
```
consolidated_truth
```
：消除重复参数的单一事实来源配置。

Procedure

流程

Stage 1 — Cardinality & Temporal Classification:
- Depth (One artifact, now): Is this single artifact clean, minimal, and true? Apply
```
re0
```
  ,
```
readchk
```
  ,
```
detool
```
  ,
```
debloat
```
  ,
```
feynman
```
  .
- Breadth (Many artifacts, now): Is one truth consistent everywhere? Apply
```
ssotize
```
  ,
```
reorder
```
  .
- Coil (One project, across iterations): Did each cycle teach the next? Apply
```
re0-loop
```
  ,
```
re0-memo
```
  ,
```
re0-work
```
  ,
```
catchup
```
  ,
```
nba
```
  .
- Mesh (Many perspectives, across rounds): Does the group converge on truth? Apply
```
prism
```
  .
Stage 2 — Bloat Removal & Mechanism Substitution:
- Remove marketing buzzwords, promotional adjectives, and AI boilerplate.
- Replace incidental third-party library nouns with standard language mechanisms.
- Compress bloated artifacts to their load-bearing density: cut words, never rules.
Stage 3 — Contrarian Testing & Cold Reads:
- Apply the Feynman check: explain the decision in simple terms without jargon.
- Apply the Hate check: find the single fatal flaw and devise the cheapest test to falsify it.
- Cold-read the artifact as a detached third party: does it stand alone without prior conversation context?
Stage 4 — Single Source Consolidation (SSOT):
- When multiple documents or modules declare conflicting parameters, designate one canonical authority.
- Update all satellite references to point to the single authority; eliminate duplicative drift.

阶段 1 — 基数与时间分类：
- Depth（一个制品，当前）：这个单一制品是否干净、最小且真实？应用
```
re0
```
  、
```
readchk
```
  、
```
detool
```
  、
```
debloat
```
  、
```
feynman
```
  。
- Breadth（多个制品，当前）：唯一事实在各处是否一致？应用
```
ssotize
```
  、
```
reorder
```
  。
- Coil（一个项目，跨迭代）：每个周期是否为下一个周期提供了经验？应用
```
re0-loop
```
  、
```
re0-memo
```
  、
```
re0-work
```
  、
```
catchup
```
  、
```
nba
```
  。
- Mesh（多个视角，跨轮次）：团队是否收敛到事实？应用
```
prism
```
  。
阶段 2 — 去除臃肿与替换机制：
- 移除营销术语、宣传性形容词和 AI 样板代码。
- 用标准语言机制替换偶然使用的第三方库名词。
- 将臃肿制品压缩至其承重密度：删减措辞，绝不删减规则。
阶段 3 — 反方测试与冷读：
- 应用 Feynman 检查：不用术语，以简单语言解释决策。
- 应用 Hate 检查：找出唯一致命缺陷，并设计成本最低的测试来证伪它。
- 以脱离关系的第三方视角冷读制品：不依赖先前对话上下文时，它是否仍能独立成立？
阶段 4 — 单一事实来源整合（SSOT）：
- 当多个文档或模块声明冲突参数时，指定一个规范权威来源。
- 更新所有卫星引用，使其指向唯一权威来源；消除重复漂移。

Decision Rules

决策规则

Tempting Rationalization	Hard Reality / Invariant	Why
"Adding more explanations makes the document clearer."	Violation. Explanations dilute core rules.	Bloated documents cause agents to miss critical instructions.
"We should patch this legacy file one more time."	Violation. When patches accumulate, rewrite to a clean v0 ( `re0` ).	Repeated patching conceals underlying design rot.
"The plan looks great to everyone; no need to object."	Forbidden. Always apply the contrarian test ( `hate` ).	Identifying fatal flaws early costs minutes; finding them in prod costs weeks.
"Duplicating this config in two places is harmless."	Forbidden. Consolidate to one SSOT immediately ( `ssotize` ).	Duplicate configurations inevitably drift out of sync.

Prioritize removal over addition: removing bloat, removing drift, removing unproven assumptions.
An artifact is finished not when nothing more can be added, but when nothing more can be removed without losing required behavior.

诱人的合理化说法	硬现实 / 不变量	原因
“增加更多解释会让文档更清晰。”	违规。解释会稀释核心规则。	臃肿文档会让 Agent 错过关键指令。
“我们应该再给这个遗留文件打一次补丁。”	违规。当补丁不断累积时，应重写为干净的 v0（ `re0` ）。	反复打补丁会掩盖底层设计腐化。
“这个计划在所有人看来都很棒；不必提出反对意见。”	禁止。始终执行反方测试（ `hate` ）。	尽早识别致命缺陷只需几分钟；在生产环境中发现则需要数周。
“在两处重复这份配置无害。”	禁止。立即整合为单一 SSOT（ `ssotize` ）。	重复配置最终不可避免地会失去同步。

优先删除而非新增：删除臃肿、漂移和未经验证的假设。
制品完成的标准不是再也无可添加，而是无法再删除任何内容而不会丢失必要行为。

Tool Policy

工具策略

Use standard file viewing and editing tools to consolidate duplicated code and configs.
Execute project linters and tests to verify behavior is preserved after debloating.
Do not introduce third-party helper dependencies when native standard library features suffice.

使用标准文件查看和编辑工具来整合重复的代码和配置。
执行项目 linter 和测试，以验证去臃肿后行为保持不变。
当原生标准库功能足够时，不引入第三方辅助依赖。

Evidence Requirements

证据要求

Diff showing net reduction in code lines or documentation complexity.
Test suites passing with 100% parity before and after simplification.

提供 Diff，证明代码行数或文档复杂度有所净减少。
测试套件通过，且简化前后的行为保持 100% 一致。

Failure Handling

失败处理

If a debloating refactor breaks existing tests, identify the hidden invariant, document it explicitly, and restore passing behavior.
If a contrarian
```
hate
```
check reveals an unfixable flaw in a plan, abort the plan and report the flaw.

如果去臃肿重构破坏了现有测试，应找出隐藏的不变量，明确记录该不变量，并恢复通过测试的行为。
如果反方
```
hate
```
检查发现计划中存在无法修复的缺陷，则中止计划并报告该缺陷。

Completion Criteria

完成标准

All redundant boilerplate, unnecessary layers, and duplicate configurations stripped.
Single source of truth established and verified across all referencing files.
Behavioral correctness confirmed by passing test execution.

所有冗余样板代码、不必要层级和重复配置均已移除。
已建立单一事实来源，并在所有引用文件中完成验证。
已通过测试执行确认行为正确性。