thinking-map-territory

1# Map Territory
2 
3Docs, 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.
4 
5## When to Use
6 
7- Observed behavior contradicts a doc, test expectation, diagram, comment, dashboard, or prior assumption.
8- A claim about the system rests on a secondary source rather than current code or data.
9- Tests pass but production or manual behavior is wrong.
10- You are about to theorize why something happens before inspecting what happens.
11- A decision depends on whether a model, schema, or metric is still current.
12 
13## When NOT to Use
14 
15- The map is the artifact you are asked to edit (doc, diagram, spec) — that artifact is the task territory.
16- Same path already verified this session — reuse that observation.
17- Map is authoritative and generative (codegen types, derived schema) with no claimed drift.
18- The mismatch cannot change the decision — note and move on.
19- Competing causal hypotheses after territory is confirmed — switch to scientific-method.
20- Security exploit construction — use red-team; this skill only settles model-versus-observation.
21 
22## Procedure
23 
241. **Name the map.** State the exact representation trusted: which doc, test, metric, diagram, comment, or assumption. Quote the claim, not a paraphrase.
25…