Back to Details

thinking-thought-experiment

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Thought Experiment

思想实验

When empiricism is out of reach, run a disciplined counterfactual: one isolated change, fixed conditions, step-by-step mechanism, and a hard bound on implications.
当经验主义方法不可行时，开展严谨的反事实分析：仅做一处孤立变更、固定条件、逐步追踪机制，并严格限定隐含结论的范围。

When to Use

适用场景

  • You need behavior under failure, scale, or policy you cannot cheaply trigger or measure (region outage, 100x load, one-way architecture).
  • A decision is expensive or irreversible and a mental trace can surface break points before commit.
  • Edge cases are too costly to stage, but a mechanistic chain can still expose missing controls.
  • 你需要了解系统在故障、高负载或特定策略下的表现，但无法低成本触发或测量这些场景（如区域故障、100倍负载、单向架构变更）。
  • 某项决策成本高昂或不可逆转，通过推演机制可在执行前发现潜在断点。
  • 边缘场景的搭建成本过高，但通过机制链推演仍能发现缺失的控制环节。

When NOT to Use

不适用场景

  • A cheap real test exists (load test, flag, query, spike) → run the test; do not substitute imagination.
  • Adversarial security attack-path work → use red-team structure, not free-form scenarios.
  • You already know the mechanism and only need a decision under known facts → decide; do not dramatize.
  • Vague "what if everything" brainstorming without a single isolated variable → tighten or stop.
  • 存在低成本真实测试（如负载测试、功能开关、查询验证、流量突增测试）→ 直接开展测试，不要用想象替代。
  • 对抗性安全攻击路径分析 → 使用红队架构，而非自由场景推演。
  • 你已明确机制，仅需基于已知事实做决策 → 直接决策，无需刻意推演。
  • 模糊的“如果一切都变了”式头脑风暴，未聚焦单个孤立变量 → 明确变量或停止推演。

Procedure

操作流程

  1. State the question and isolation. Name exactly one primary variable or counterfactual change. Freeze all other conditions as the control world. Reject multi-variable "and also" scenarios.
  2. Fix initial conditions. Specify system state, load, configuration, actors, and what is not changed. Write values concrete enough that another agent could replay the setup.
  3. Trace the mechanism step by step. From t0, record what fails, queues, retries, or adapts next—and why—using known components and policies only. No hand-wavy "then everything collapses"; each step needs a causal link.
  4. Extract invariants and break points. Note what still holds (invariants) and the first step where the system violates a requirement (capacity, correctness, safety, UX). Mark assumptions that, if false, void the chain.
  5. Bound implications. Map insights only to actions or checks justified by the chain (limits, guards, monitoring, redesign). Label speculative leaps beyond the isolation as out of bound.
  6. Name a discriminating real check, then stop. For the weakest link, state the cheapest observation or experiment that would confirm or kill it. Stop after one controlled chain with bounded implications; if a link is cheaply testable now, exit to that test instead of further imagination.
  1. 明确问题与隔离变量：精准定义一个核心变量或反事实变更。将所有其他条件固定为基准状态。拒绝包含多个变量的“同时变更”场景。
  2. 固定初始条件：明确系统状态、负载、配置、参与角色，以及所有保持不变的内容。设定的数值需足够具体，确保其他Agent可复现该场景。
  3. 逐步追踪机制链：从初始时刻（t0）开始，记录后续出现的故障、队列堆积、重试或自适应行为——以及背后的原因——仅使用已知组件和策略。避免模糊的“然后系统全面崩溃”；每一步都需要因果关联。
  4. 提取不变量与断点：记录仍保持正常的部分（不变量），以及系统首次违反需求（容量、正确性、安全性、用户体验）的环节。标记若不成立则会使整个推演链失效的假设条件。
  5. 限定隐含结论范围：仅将推演链所支撑的行动或检查（如限制措施、防护机制、监控方案、重新设计）纳入结论。超出隔离变量范围的推测需标注为超出边界。
  6. 确定鉴别性真实检查，然后停止：针对最薄弱环节，说明可验证或推翻该环节的最低成本观测或实验。完成一条受控推演链并限定结论范围后即停止；若某环节当前可低成本测试，则停止推演并开展测试。

Output

输出内容

Emit a thought-experiment record:
  • question
    : what behavior or decision is under test
  • isolated_variable
    : single change vs control world
  • initial_conditions
    : frozen state and non-changes
  • consequence_chain
    : ordered mechanistic steps
  • invariants
    : what still holds
  • break_points
    : first requirement failures and critical assumptions
  • implication_bound
    : actions/checks justified by the chain only
  • discriminating_check
    : cheapest real observation to confirm or kill the weak link
生成一份思想实验记录，包含：
  • question
    ：待测试的行为或决策
  • isolated_variable
    ：相对于基准状态的单一变更
  • initial_conditions
    ：固定状态与未变更内容
  • consequence_chain
    ：按顺序排列的机制步骤
  • invariants
    ：仍保持正常的部分
  • break_points
    ：首次需求失效环节与关键假设
  • implication_bound
    ：仅由推演链支撑的行动/检查
  • discriminating_check
    ：验证或推翻薄弱环节的最低成本真实观测

Verification

验证标准

  • Isolation check: more than one free variable without a stated control → invalid; reset.
  • Mechanism check: any step without a causal link to a known component/policy → rewrite or drop.
  • Implication bound: recommendations not entailed by the chain are out of scope.
  • Empiricism override: if a real test became available mid-analysis, stop the thought experiment and test.
  • Over-application guard: do not use this skill for ordinary debugging you can reproduce, or as a substitute for red-team threat modeling.
  • Stop: one isolated counterfactual → full chain → bounded implications + discriminating check; no scenario sprawl.
  • 隔离性检查：存在多个未明确控制的自由变量 → 无效，重新设定。
  • 机制性检查：任何步骤未关联到已知组件/策略的因果关系 → 重写或删除该步骤。
  • 结论范围检查：推演链未支撑的建议属于超出范围。
  • 经验主义优先：若分析过程中出现可开展的真实测试，立即停止思想实验并进行测试。
  • 过度应用防护：不要将此方法用于可复现的常规调试，或替代红队威胁建模。
  • 停止准则：完成一个孤立反事实场景的完整推演链，得出限定范围的结论与鉴别性检查；避免场景蔓延。