Back to Details

thinking-map-territory

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Map Territory

地图与领地

Docs, tests, diagrams, metrics, comments, and mental models are maps. Running code and actual data are the territory. When they disagree, verify territory and update the model — never force reality to match the description.
文档、测试、图表、指标、注释和思维模型都是‘地图’。运行中的代码和实际数据才是‘领地’。当两者不一致时，验证‘领地’并更新模型——绝不要强迫现实去匹配描述。

When to Use

适用场景

  • Observed behavior contradicts a doc, test expectation, diagram, comment, dashboard, or prior assumption.
  • A claim about the system rests on a secondary source rather than current code or data.
  • Tests pass but production or manual behavior is wrong.
  • You are about to theorize why something happens before inspecting what happens.
  • A decision depends on whether a model, schema, or metric is still current.
  • 观察到的行为与文档、测试预期、图表、注释、仪表盘或先前假设相矛盾。
  • 关于系统的声明基于二手资料而非当前代码或数据。
  • 测试通过但生产环境或手动操作的行为存在问题。
  • 你在检查实际发生的情况之前，就开始推测问题原因。
  • 决策依赖于模型、schema或指标是否仍为最新状态。

When NOT to Use

不适用场景

  • The map is the artifact you are asked to edit (doc, diagram, spec) — that artifact is the task territory.
  • Same path already verified this session — reuse that observation.
  • Map is authoritative and generative (codegen types, derived schema) with no claimed drift.
  • The mismatch cannot change the decision — note and move on.
  • Competing causal hypotheses after territory is confirmed — switch to scientific-method.
  • Security exploit construction — use red-team; this skill only settles model-versus-observation.
  • 你被要求编辑的对象就是‘地图’本身（文档、图表、规范）——该对象即为当前任务的‘领地’。
  • 本次会话中已验证过相同路径——可复用之前的观察结果。
  • ‘地图’是权威且生成性的（如代码生成的类型、派生schema），且无证据表明存在偏差。
  • 这种不一致不会影响决策——记录后继续推进。
  • 确认‘领地’后存在相互矛盾的因果假设——改用科学方法处理。
  • 构建安全漏洞利用方案——使用红队方法；本方法仅用于解决模型与观察结果的矛盾。

Procedure

执行步骤

  1. Name the map. State the exact representation trusted: which doc, test, metric, diagram, comment, or assumption. Quote the claim, not a paraphrase.
  2. Name the territory check. Specify the observation that would prove or disprove the claim: code path, runtime value, query, reproduction, recent change, or live metric.
  3. Verify source and freshness. Confirm origin of the map (author, generator, last update) and whether it could be stale relative to deploy, config, or data change. Prefer primary current sources over summaries.
  4. Observe the territory. Read the real code path, run or instrument it, query real data, or reproduce the behavior. Do not predict from signatures or names alone.
  5. Record the delta and update. If territory contradicts the map, territory wins for shipped behavior. Document the gap, revise the model, then decide the fix (code, map, or both). Note unmapped paths — likely next failure sites.
  6. Stop when settled. Once the claim is confirmed or overturned with a concrete observation, stop re-checking the same path.
  1. 明确‘地图’：说明所依赖的具体载体：哪份文档、测试、指标、图表、注释或假设。直接引用声明原文，而非转述。
  2. 确定‘领地’验证方式：明确能够证实或证伪该声明的观察手段：代码路径、运行时数值、查询操作、复现步骤、近期变更或实时指标。
  3. 验证来源与时效性：确认‘地图’的来源（作者、生成器、最后更新时间），以及它是否可能因部署、配置或数据变更而过时。优先选择当前的一手资料而非汇总信息。
  4. 观察‘领地’：查看真实的代码路径，运行或调试代码，查询真实数据，或复现行为。不要仅凭签名或名称进行预测。
  5. 记录差异并更新：如果‘领地’与‘地图’矛盾，对于已上线的行为，‘领地’具有最终决定权。记录两者的差距，修正模型，然后决定修复方案（修改代码、更新‘地图’，或两者都改）。标记未被‘地图’覆盖的路径——这些很可能是下一个故障点。
  6. 问题解决即停止：一旦通过具体观察确认或推翻了声明，停止重复检查同一路径。

Output

输出格式

text
Map: <claim + source + freshness>
Territory check: <what was inspected/run/queried>
Observation: <concrete result, not interpretation>
Delta: <aligned | map wrong | territory incomplete>
Updated model: <corrected understanding>
Action: <fix code | update map | no decision impact>
Uncovered: <paths no map covers>
text
Map: <claim + source + freshness>
Territory check: <what was inspected/run/queried>
Observation: <concrete result, not interpretation>
Delta: <aligned | map wrong | territory incomplete>
Updated model: <corrected understanding>
Action: <fix code | update map | no decision impact>
Uncovered: <paths no map covers>

Verification

验证要点

  • Falsify if you reasoned from the map without a territory observation, trusted a stale secondary source, or forced code to match a wrong doc without checking either.
  • Stop when the contradiction is resolved or irrelevant to the decision.
  • Over-application guard: do not re-verify the whole system when editing the map, when the map is the generative source of truth, or when the gap cannot change the next action.
  • 若你未观察‘领地’就基于‘地图’进行推理、信任过时的二手资料，或未做检查就强迫代码匹配错误的文档，则判定为不符合要求。
  • 当矛盾已解决或与决策无关时，停止验证。
  • 过度应用防范：编辑‘地图’时、‘地图’是生成式可信来源时，或差距无法改变下一步行动时，不要重新验证整个系统。