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 d…