{"id":"9ee0b493-54f6-4b60-b245-3329275d5345","entityType":"agent","slug":"clawhub-deciqai-map-is-not-the-territory","name":"Map Is Not the Territory","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-map-is-not-the-territory","canonicalPath":"/agent/clawhub-deciqai-map-is-not-the-territory","generatedAt":"2026-10-12T07:20:48.517Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T19:58:02.766Z","emptyReason":null},"description":"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle;... Skill: Map Is Not the Territory Owner: deciqai Summary: Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle;... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:05:36.886Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/map-is-not-the-territory.json) v1.0.4 | 2026-07-10","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:map-is-not-the-territory","sourceUrl":"https://clawhub.ai/deciqai/map-is-not-the-territory","homepage":"https://clawhub.ai/deciqai/skills/map-is-not-the-territory","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/map-is-not-the-territory","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/map-is-not-the-territory","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle;... "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:58:02.766Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:58:02.766Z","emptyReason":null},"stars":null,"forks":null,"downloads":1000,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T19:58:02.700Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T19:58:02.766Z","lastCrawledAt":"2026-10-11T19:58:02.700Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T19:58:02.700Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T18:05:36.886Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/map-is-not-the-territory.json)","fileCount":6,"zipByteSize":12404},{"version":"1.0.4","createdAt":"2026-07-10T10:27:03.780Z","changelog":"Add 2024-2026 AI-era worked example + updated sources","fileCount":6,"zipByteSize":12200},{"version":"1.0.3","createdAt":"2026-07-08T11:08:48.209Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":5,"zipByteSize":8265},{"version":"1.0.2","createdAt":"2026-07-08T00:53:34.570Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":8376},{"version":"1.0.1","createdAt":"2026-07-07T22:28:14.803Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":8219},{"version":"1.0.0","createdAt":"2026-06-30T06:17:33.163Z","changelog":"Initial publish","fileCount":5,"zipByteSize":8072}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:map-is-not-the-territory","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-12T07:20:48.513Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-map-is-not-the-territory/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T19:58:02.766Z","emptyReason":null},"readme":"Skill: Map Is Not the Territory\n\nOwner: deciqai\n\nSummary: Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle;...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T18:05:36.886Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/map-is-not-the-territory.json)\n\nv1.0.4 | 2026-07-10T10:27:03.780Z | user\n\nAdd 2024-2026 AI-era worked example + updated sources\n\nv1.0.3 | 2026-07-08T11:08:48.209Z | user\n\nFooter now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.2 | 2026-07-08T00:53:34.570Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T22:28:14.803Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-06-30T06:17:33.163Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 6 files, 12404 bytes\n\nFiles: examples/ai-benchmarks-vs-deployment-reality-2024-2026.md (6819b), examples/mcnamara-vietnam-kill-ratio-map.md (4384b), references/sources.md (1622b), skill-card.md (2660b), SKILL.md (8806b), _meta.json (143b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: map-is-not-the-territory\ndescription: \"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter. More: deciqai.com/c/map-is-not-the-territory\"\n---\n\n# Map Is Not the Territory\n\n## Overview\n\nAny representation — metric, model, strategy deck, org chart, or process manual — is a selective, simplified, aging abstraction. Maps omit (reflecting past priorities), distort (projecting dynamic reality onto static surfaces), and age (the territory moves; the map does not). The map is useful because it compresses complexity; dangerous because users forget it is a compression. Composes with `goodharts-law` (optimizing a metric makes it an even worse map), `first-principles` (rebuilding from territory when maps fail), and `narrative-fallacy` (every narrative is a map that ages).\n\n## When to Use\n\n- A key metric improves while customer feedback, morale, or competitor signals deteriorate\n- Team disagreement cannot be resolved by data — parties are disagreeing about maps, not territory\n- A strategy, model, process, or org chart has not been reviewed in more than one planning cycle\n- \"The data shows...\" but the data is old, narrow, or from a proxy source\n- A metric is being optimized directly without asking whether it still maps to the underlying goal\n- An AI model's benchmark score, leaderboard rank, or internal \"world model\" is being treated as proof of real-world capability (AI adoption / AI hype)\n\n**Not when:** the map is demonstrably current and well-calibrated; decision is low-stakes; territory is stable and map is freshly validated.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete map/decision → run The Process directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: the metric, model, or plan you are navigating with is not reality — it is a selective, aging abstraction of it. Confusing the two is how smart people make systematic errors.\n2. Check fit: is there a map being used to navigate? Is there evidence the territory has moved beyond the map?\n3. Elicit their real case: what is the map? what territory does it claim to represent? when was it last calibrated?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input: what does the map omit? how has it aged? what direct territory observations are available?\n> **[WAIT — do not advance until user responds]**\n5. Close by naming the map-territory gap explicitly: omissions identified, distortions named, calibration action defined, update trigger specified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**S1 — Name the map:** what is it (metric, model, plan, process)? who made it and when? what territory does it claim to represent?\n\n**S2 — Structural omissions:** what does it omit by design? by measurement limits? by aging? what signals are outside this map?\n\n**S3 — Structural distortions:** what relationships does it assume (linear, causal, static)? what assumptions must be true for it to be accurate?\n\n**S4 — Map age:** when was it last calibrated? what has changed since? is it inside or outside its useful life?\n\n**S5 — Direct territory signal:** what direct observations are available (interviews, field visits, primary data)? where is divergence from the map greatest?\n\n**S6 — Decide:** use as-is / update / replace. what specific updates close the most important gap? what is the update trigger?\n\n## Output: Map-Territory Audit\n```\nMap: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger\n```\n\n*→ Method in Action: [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md)*\n\n*→ 2026 lens: [AI Benchmarks as Maps of Capability (2024–2026)](examples/ai-benchmarks-vs-deployment-reality-2024-2026.md)*\n\n## Pack: Map-Territory Mismatches Across Domains\n\n| Domain | Map | Key omission | Territory signal missed |\n|---|---|---|---|\n| Startup growth | MAU | Churn drivers, value realization | Users activate but don't retain |\n| Sales | Pipeline × close rate | Buying-committee dynamics | Close rate collapses late-stage |\n| Team health | Satisfaction scores | Silent disengagement | Top performers leave without warning |\n| Financial model | Revenue/cost projections | Cash flow dynamics | Model shows profit; cash crisis arrives |\n| Org chart | Formal authority | Informal influence networks | Decisions route through uncharted nodes |\n\n## Applying It Well\n\n- Pair a map audit with at least one direct territory observation — not another map\n- Distinguish map-territory decoupling from execution failure before diagnosing either\n- Name the update trigger explicitly; maps without recalibration schedules age silently\n- Expert confidence does not track map applicability to novel territory\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Our metrics are all green — we're doing well.\" | Metrics are a map. Green metrics with deteriorating qualitative signals indicate map-territory decoupling. |\n| [D] \"The model shows this will work.\" | The model encodes assumptions that may be outdated. The territory does not read the model. |\n| [D] \"We followed the process exactly.\" | The process was a map of conditions that may no longer exist. Process compliance is not territory compliance. |\n| [D] \"The data doesn't show any problems.\" | The data measures a subset of territory designed for past priorities. Absence in data ≠ absence in territory. |\n| [D] \"We optimized the KPI — we improved the business.\" | Optimizing a metric is optimizing the map. Only direct territory observation shows whether underlying reality improved. |\n| [D] \"The expert said this is how the market works.\" | Expert models are maps from past encounters. Novel conditions may invalidate the map without invalidating the expert's confidence. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Key metric improving but qualitative signals (customers, team, partners) are worsening\n- Model or plan not updated within the current competitive or operational cycle\n- Team disagreements cannot be resolved by data — parties are disagreeing about maps, not territory\n- A process is followed because \"it's the process\" without reference to its original outcome\n- A metric is being managed directly rather than used as a signal of underlying reality\n- Field team reports a reality that contradicts the dashboard — and is told the dashboard is correct\n\n## Verification\n\n- [ ] Map named and creation date identified\n- [ ] Structural omissions listed (what the map cannot show by design)\n- [ ] Structural distortions listed (what the map misrepresents by design)\n- [ ] Map age assessed relative to territory's rate of change\n- [ ] At least one direct territory observation gathered (not mediated by the map)\n- [ ] Most significant map-territory divergence identified and named\n- [ ] Decision made: use as-is, update, or replace; update trigger specified\n\n**Stop rule:** if territory observation and map are consistent across multiple independent signals, stop auditing. Over-applying risks paralytic model-skepticism where no map is trusted enough to navigate.\n\n---\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/map-is-not-the-territory** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/map-is-not-the-territory.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"map-is-not-the-territory\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784225136886\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — map-is-not-the-territory\n\n> *Primary sources for the [map-is-not-the-territory](../SKILL.md) skill.*\n\n- Korzybski, A. (1933). *Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics.* Institute of General Semantics. 5th ed. ISBN 978-0937298015. The original source.\n- Bateson, G. (1972). *Steps to an Ecology of Mind.* Ballantine Books. Extended the principle into systems theory and epistemology.\n- McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. ISBN 978-0812925333. Primary source case study on map-territory decoupling in strategic management.\n- Hayakawa, S. I. (1949). *Language in Thought and Action.* Harcourt. A key popularizer of Korzybski's general semantics framework.\n- Meadows, D. H. (2008). *Thinking in Systems: A Primer.* Chelsea Green. ISBN 978-1603580557. Systems-level treatment of model-reality divergence.\n- Taleb, N. N. (2010). *The Black Swan.* 2nd ed. Random House. ISBN 978-0812973815. The map-territory failure mode in statistical and financial models.\n- Stanford HAI (2024, 2025). *Artificial Intelligence Index Report.* Stanford Institute for Human-Centered AI. Documents AI benchmark saturation and the introduction of harder evaluations as older benchmarks stopped discriminating between top models — a contemporary map-territory case.\n- Jimenez, C. E., Yang, J., et al. (2024). *SWE-bench: Can Language Models Resolve Real-World GitHub Issues?* ICLR 2024. arXiv:2310.06770. Benchmark built to move evaluation closer to real deployment territory (repository-level software tasks) rather than toy problems.\n\nFile v1.0.5:examples/ai-benchmarks-vs-deployment-reality-2024-2026.md\n\n# Method in Action: AI Benchmarks as Maps of Capability (2024–2026)\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nBetween 2024 and 2026 the AI industry navigated by a dense set of maps: benchmark scores (MMLU, GPQA, HumanEval, SWE-bench, GSM8K, MATH), public leaderboards (such as the crowd-voted LMArena / Chatbot Arena), and the model's own internal \"world model\" — the compressed statistical representation it builds of the world. Each is a map. The territory is what the system actually does when a real user, with a real task, in a messy real context, presses enter. The recurring 2024–2026 story is the gap between a rising score and unchanged — or worse — real-world behavior. This example walks that gap through the skill's Process.\n\n## S1 — Name the map\n\n- **Maps:** (a) static benchmark scores reported in model cards and launch posts; (b) public leaderboards ranking models by aggregate preference or accuracy; (c) the model's internal learned representation of the world.\n- **Made by / when:** benchmarks by academic and industry researchers, mostly frozen at a point in time; leaderboards updated continuously by voters or automated eval harnesses; internal world models fixed at each model's training-data cutoff.\n- **Territory claimed:** \"how capable and reliable this model is for the tasks people will actually use it for.\"\n\n## S2 — Structural omissions\n\nWhat the benchmark/leaderboard maps omit by design:\n\n- **Long, stateful, real tasks.** A single-turn multiple-choice score omits multi-step agentic work, long-context degradation, and tool use — which is where deployed assistants actually spend their time.\n- **Distribution shift after the cutoff.** The internal world model omits everything that happened after training data was frozen; the world keeps moving, the representation does not.\n- **Failure texture.** Aggregate accuracy omits *how* a model fails — confident fabrication (hallucination), refusal, or sycophantic agreement with a wrong premise all vanish into a single percentage.\n- **Contamination.** Public benchmarks can leak into training corpora, so a high score may partly measure memorization of the test rather than the underlying skill it claims to represent.\n\n## S3 — Structural distortions\n\n- **Linearity assumption:** that a higher benchmark number implies proportionally more useful real-world behavior. Deployment is not linear in eval score — a few percentage points on a saturated benchmark can mean little downstream.\n- **Single-number compression:** collapsing a multi-dimensional capability surface (reasoning, calibration, safety, latency, cost, robustness) into one rank.\n- **Hidden assumption of representativeness:** that the benchmark's task distribution matches the user's task distribution. When it does not, the map is precise about the wrong territory.\n- **Leaderboard incentive distortion:** because scores are public and competitive, they become targets — the classic [Goodhart's Law](../goodharts-law/SKILL.md) coupling, where models can be tuned to what the eval rewards (e.g., style or verbosity that wins votes) rather than to underlying usefulness.\n\n## S4 — Map age\n\n- Static benchmarks age fast: as capabilities rose through 2024–2025, several long-standing benchmarks approached saturation (top models clustering near the ceiling), losing their power to discriminate — an aging map that no longer resolves the territory.\n- Internal world models age at their training cutoff: a model confidently answering about \"current\" facts is reading an out-of-date map of a moved territory. This is the everyday, visible form of the gap — the assistant that is fluent and wrong about anything recent.\n- The industry response was itself an admission the maps had aged: a steady stream of *new* harder benchmarks and evolving arena formats appeared specifically because the old maps had stopped tracking the territory.\n\n## S5 — Direct territory signal\n\nWhere divergence from the map is largest — the primary, non-benchmark observations:\n\n- **Deployment behavior:** documented, widely reported cases of hallucinated citations, fabricated case law in legal filings, and confidently wrong outputs from high-scoring models — behavior a headline score does not predict.\n- **Agentic robustness:** the visible 2024–2026 gap between demo-level and reliable autonomous multi-step task completion; benchmarks like SWE-bench were introduced precisely to measure real repository-level work rather than toy problems.\n- **Sycophancy and calibration:** direct interaction shows models agreeing with incorrect user premises or expressing unwarranted confidence — a failure mode invisible in accuracy-only maps.\n- **Human-preference vs. correctness:** leaderboard rank (what voters *prefer*) can diverge from task correctness and safety, so the arena map and the reliability territory point in different directions.\n\n## S6 — Decide\n\n- **Fit:** Partially. Benchmarks and leaderboards remain useful *comparative* maps — but they are maps of test performance, not of deployed reliability.\n- **Required updates:** pair every benchmark claim with direct territory observation — task-specific evals on your own workload, red-teaming, human review of failure texture, and retrieval to patch the internal world model's aging. Track cost, latency, calibration, and safety alongside accuracy.\n- **Update trigger:** re-audit when a benchmark saturates, when your task distribution shifts, or whenever a score improves but user-reported failures do not fall. If the map keeps going up while the territory (support tickets, wrong-answer reports, abandoned agent runs) does not improve, suspect map-territory decoupling first.\n\n**The lesson for founders and operators deploying AI:** a rising eval score is a map of the test, not of your product. Before trusting \"the new model benchmarks higher,\" observe the territory — your users, your tasks, your failure modes — directly. The leaderboard does not read your production logs, and the model's world model does not read the news.\n\n*Sources: Stanford HAI, \"Artificial Intelligence Index Report 2024\" and \"2025,\" which document benchmark saturation and the introduction of harder evaluations; the SWE-bench benchmark (Jimenez et al., \"SWE-bench: Can Language Models Resolve Real-World GitHub Issues?\", ICLR 2024) for real-world agentic task evaluation; LMArena / Chatbot Arena (Chiang et al., \"Chatbot Arena: An Open Platform for Evaluating LLMs by Human Preference,\" 2024) for the human-preference leaderboard method and its known limitations; widely reported court sanctions over AI-fabricated legal citations (2023–2025, e.g., Mata v. Avianca and subsequent cases) as documented territory-level failures. Timeless core: Korzybski, A. (1933), *Science and Sanity*.*\n\nFile v1.0.5:examples/mcnamara-vietnam-kill-ratio-map.md\n\n# Method in Action: McNamara and the Vietnam Kill-Ratio Map\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nThe most operationally instructive case of map-territory decoupling in modern history is Robert McNamara's management of the Vietnam War using statistical metrics as the primary navigation system.\n\nMcNamara, U.S. Secretary of Defense 1961–1968, came from the Ford Motor Company where systems analysis and quantitative management had produced measurable results. He applied the same epistemology to the war: define measurable proxies, track them rigorously, use the trends as ground truth for strategic decisions.\n\nThe primary metric: **kill ratio** (enemy killed per U.S. soldier killed) and **body count** (enemy combatants killed). These were the maps McNamara and the Johnson administration used to navigate the territory of the war. The logic was sound as map logic: if the United States was killing far more of the enemy than the enemy was killing of the U.S., the U.S. was winning.\n\nThe kill ratio improved consistently from 1965 to 1968. The map said: progress.\n\nThe territory said: catastrophe. Civilian support for the Saigon government was eroding. North Vietnamese recruitment was accelerating. The Viet Cong infrastructure in the South was strengthening, not weakening. Public opinion in the United States was approaching a breaking point. The 1968 Tet Offensive — a coordinated assault on more than 100 South Vietnamese cities — shattered the map's credibility in a single week.\n\nMcNamara's own retrospective is among the most important primary source documents on map-territory failure in organizational decision-making:\n\n> \"We were wrong, terribly wrong. We owe it to future generations to explain why. We viewed the people and leaders of South Vietnam in terms of our own experience. We saw in them a thirst for — and a determination to fight for — freedom and democracy. We totally misjudged the political forces within the country.\"\n>\n> — McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. p. xvi.\n\nThe map (kill ratio, body count, area control percentages) omitted:\n\n- **Legitimacy signals.** Whether the South Vietnamese population supported the Saigon government — the single most strategically decisive variable — was not in the map.\n- **Adversary adaptation.** The North Vietnamese adapted to minimize body count by avoiding pitched battles, converting the map metric into a measure of guerrilla discipline rather than strategic failure.\n- **Incentive corruption.** U.S. field commanders, evaluated on kill ratios, had strong incentives to over-report enemy killed and under-report civilian casualties. The map was being optimized (in the Goodhart's Law sense), making it increasingly disconnected from territory.\n- **Time horizon.** The map showed who was winning each engagement. It could not show who would sustain the war longer — which was the decisive question.\n\nThe McNamara case demonstrates three map-territory failure modes that recur in organizational settings:\n\n**First, metric selection encodes assumptions about what matters.** The decision to use kill ratio as the primary metric encoded the assumption that the war was primarily a military attrition problem. The territory was primarily a political legitimacy problem. The map was wrong in kind, not just in degree.\n\n**Second, improving maps can mask deteriorating territory.** The kill ratio kept improving through 1967. Decision-makers read this as progress. The metric's improvement filtered out the signals that the territory was moving in the opposite direction. A map that always shows improvement under optimization is not a map of territory — it is a map of itself.\n\n**Third, map improvement can generate perverse territory dynamics.** When field commanders were evaluated on body count, the territory adapted: enemy combatants minimized engagement, and the body count filled with civilians and inflated reporting. The metric was optimizing the field behavior rather than describing the war.\n\nThe lesson for founders and operators: when the map (dashboard, KPI, model) consistently improves while anecdotal, qualitative, and peripheral signals are deteriorating, the hypothesis to investigate first is map-territory decoupling — not execution failure, not signal noise. The territory may have moved.\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nGuides agents through a map-territory audit to test whether a metric, model, process, or plan still matches the real-world situation it is used to navigate.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, operators, founders, and strategy teams use this skill to check whether dashboards, benchmarks, models, plans, or processes have drifted away from observed reality before relying on them for decisions. It is especially suited for cases where quantitative indicators look healthy while customer, employee, market, or field signals point the other way.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Users may treat the framework as an authority rather than a coaching aid for judgment.\n\nMitigation: Use it to structure review, then validate conclusions with direct territory observations and accountable human decision-makers.\n\nRisk: Real organizational examples entered during audits may contain confidential or sensitive details.\n\nMitigation: Avoid recording sensitive details unless intentional, approved, and appropriate for the storage location.\n\nRisk: Over-applying map skepticism can delay decisions even when independent territory signals agree with the map.\n\nMitigation: Apply the skill's stop rule: stop auditing when the map and multiple independent territory observations are consistent.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/map-is-not-the-territory)\n- [deciqAI skill page](https://www.deciqai.com/c/map-is-not-the-territory)\n- [Machine-readable skill metadata](https://www.deciqai.com/s/map-is-not-the-territory.json)\n- [Sources](references/sources.md)\n- [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md)\n- [AI Benchmarks as Maps of Capability (2024-2026)](examples/ai-benchmarks-vs-deployment-reality-2024-2026.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown checklist and structured audit text]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Produces a Map-Territory Audit covering omissions, distortions, age, territory signals, decision, required updates, and update trigger.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 6 files, 12200 bytes\n\nFiles: examples/ai-benchmarks-vs-deployment-reality-2024-2026.md (6819b), examples/mcnamara-vietnam-kill-ratio-map.md (4384b), references/sources.md (1622b), skill-card.md (2416b), SKILL.md (8647b), _meta.json (143b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: map-is-not-the-territory\ndescription: \"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter.\"\n---\n\n# Map Is Not the Territory\n\n## Overview\n\nAny representation — metric, model, strategy deck, org chart, or process manual — is a selective, simplified, aging abstraction. Maps omit (reflecting past priorities), distort (projecting dynamic reality onto static surfaces), and age (the territory moves; the map does not). The map is useful because it compresses complexity; dangerous because users forget it is a compression. Composes with `goodharts-law` (optimizing a metric makes it an even worse map), `first-principles` (rebuilding from territory when maps fail), and `narrative-fallacy` (every narrative is a map that ages).\n\n## When to Use\n\n- A key metric improves while customer feedback, morale, or competitor signals deteriorate\n- Team disagreement cannot be resolved by data — parties are disagreeing about maps, not territory\n- A strategy, model, process, or org chart has not been reviewed in more than one planning cycle\n- \"The data shows...\" but the data is old, narrow, or from a proxy source\n- A metric is being optimized directly without asking whether it still maps to the underlying goal\n- An AI model's benchmark score, leaderboard rank, or internal \"world model\" is being treated as proof of real-world capability (AI adoption / AI hype)\n\n**Not when:** the map is demonstrably current and well-calibrated; decision is low-stakes; territory is stable and map is freshly validated.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete map/decision → run The Process directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: the metric, model, or plan you are navigating with is not reality — it is a selective, aging abstraction of it. Confusing the two is how smart people make systematic errors.\n2. Check fit: is there a map being used to navigate? Is there evidence the territory has moved beyond the map?\n3. Elicit their real case: what is the map? what territory does it claim to represent? when was it last calibrated?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input: what does the map omit? how has it aged? what direct territory observations are available?\n> **[WAIT — do not advance until user responds]**\n5. Close by naming the map-territory gap explicitly: omissions identified, distortions named, calibration action defined, update trigger specified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**S1 — Name the map:** what is it (metric, model, plan, process)? who made it and when? what territory does it claim to represent?\n\n**S2 — Structural omissions:** what does it omit by design? by measurement limits? by aging? what signals are outside this map?\n\n**S3 — Structural distortions:** what relationships does it assume (linear, causal, static)? what assumptions must be true for it to be accurate?\n\n**S4 — Map age:** when was it last calibrated? what has changed since? is it inside or outside its useful life?\n\n**S5 — Direct territory signal:** what direct observations are available (interviews, field visits, primary data)? where is divergence from the map greatest?\n\n**S6 — Decide:** use as-is / update / replace. what specific updates close the most important gap? what is the update trigger?\n\n## Output: Map-Territory Audit\n```\nMap: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger\n```\n\n*→ Method in Action: [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md)*\n\n*→ 2026 lens: [AI Benchmarks as Maps of Capability (2024–2026)](examples/ai-benchmarks-vs-deployment-reality-2024-2026.md)*\n\n## Pack: Map-Territory Mismatches Across Domains\n\n| Domain | Map | Key omission | Territory signal missed |\n|---|---|---|---|\n| Startup growth | MAU | Churn drivers, value realization | Users activate but don't retain |\n| Sales | Pipeline × close rate | Buying-committee dynamics | Close rate collapses late-stage |\n| Team health | Satisfaction scores | Silent disengagement | Top performers leave without warning |\n| Financial model | Revenue/cost projections | Cash flow dynamics | Model shows profit; cash crisis arrives |\n| Org chart | Formal authority | Informal influence networks | Decisions route through uncharted nodes |\n\n## Applying It Well\n\n- Pair a map audit with at least one direct territory observation — not another map\n- Distinguish map-territory decoupling from execution failure before diagnosing either\n- Name the update trigger explicitly; maps without recalibration schedules age silently\n- Expert confidence does not track map applicability to novel territory\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Our metrics are all green — we're doing well.\" | Metrics are a map. Green metrics with deteriorating qualitative signals indicate map-territory decoupling. |\n| [D] \"The model shows this will work.\" | The model encodes assumptions that may be outdated. The territory does not read the model. |\n| [D] \"We followed the process exactly.\" | The process was a map of conditions that may no longer exist. Process compliance is not territory compliance. |\n| [D] \"The data doesn't show any problems.\" | The data measures a subset of territory designed for past priorities. Absence in data ≠ absence in territory. |\n| [D] \"We optimized the KPI — we improved the business.\" | Optimizing a metric is optimizing the map. Only direct territory observation shows whether underlying reality improved. |\n| [D] \"The expert said this is how the market works.\" | Expert models are maps from past encounters. Novel conditions may invalidate the map without invalidating the expert's confidence. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Key metric improving but qualitative signals (customers, team, partners) are worsening\n- Model or plan not updated within the current competitive or operational cycle\n- Team disagreements cannot be resolved by data — parties are disagreeing about maps, not territory\n- A process is followed because \"it's the process\" without reference to its original outcome\n- A metric is being managed directly rather than used as a signal of underlying reality\n- Field team reports a reality that contradicts the dashboard — and is told the dashboard is correct\n\n## Verification\n\n- [ ] Map named and creation date identified\n- [ ] Structural omissions listed (what the map cannot show by design)\n- [ ] Structural distortions listed (what the map misrepresents by design)\n- [ ] Map age assessed relative to territory's rate of change\n- [ ] At least one direct territory observation gathered (not mediated by the map)\n- [ ] Most significant map-territory divergence identified and named\n- [ ] Decision made: use as-is, update, or replace; update trigger specified\n\n**Stop rule:** if territory observation and map are consistent across multiple independent signals, stop auditing. Over-applying risks paralytic model-skepticism where no map is trusted enough to navigate.\n\n---\n*Part of **deciqAI Knowledge Skills** — 223 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/map-is-not-the-territory** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"map-is-not-the-territory\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1783679223780\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — map-is-not-the-territory\n\n> *Primary sources for the [map-is-not-the-territory](../SKILL.md) skill.*\n\n- Korzybski, A. (1933). *Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics.* Institute of General Semantics. 5th ed. ISBN 978-0937298015. The original source.\n- Bateson, G. (1972). *Steps to an Ecology of Mind.* Ballantine Books. Extended the principle into systems theory and epistemology.\n- McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. ISBN 978-0812925333. Primary source case study on map-territory decoupling in strategic management.\n- Hayakawa, S. I. (1949). *Language in Thought and Action.* Harcourt. A key popularizer of Korzybski's general semantics framework.\n- Meadows, D. H. (2008). *Thinking in Systems: A Primer.* Chelsea Green. ISBN 978-1603580557. Systems-level treatment of model-reality divergence.\n- Taleb, N. N. (2010). *The Black Swan.* 2nd ed. Random House. ISBN 978-0812973815. The map-territory failure mode in statistical and financial models.\n- Stanford HAI (2024, 2025). *Artificial Intelligence Index Report.* Stanford Institute for Human-Centered AI. Documents AI benchmark saturation and the introduction of harder evaluations as older benchmarks stopped discriminating between top models — a contemporary map-territory case.\n- Jimenez, C. E., Yang, J., et al. (2024). *SWE-bench: Can Language Models Resolve Real-World GitHub Issues?* ICLR 2024. arXiv:2310.06770. Benchmark built to move evaluation closer to real deployment territory (repository-level software tasks) rather than toy problems.\n\nFile v1.0.4:examples/ai-benchmarks-vs-deployment-reality-2024-2026.md\n\n# Method in Action: AI Benchmarks as Maps of Capability (2024–2026)\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nBetween 2024 and 2026 the AI industry navigated by a dense set of maps: benchmark scores (MMLU, GPQA, HumanEval, SWE-bench, GSM8K, MATH), public leaderboards (such as the crowd-voted LMArena / Chatbot Arena), and the model's own internal \"world model\" — the compressed statistical representation it builds of the world. Each is a map. The territory is what the system actually does when a real user, with a real task, in a messy real context, presses enter. The recurring 2024–2026 story is the gap between a rising score and unchanged — or worse — real-world behavior. This example walks that gap through the skill's Process.\n\n## S1 — Name the map\n\n- **Maps:** (a) static benchmark scores reported in model cards and launch posts; (b) public leaderboards ranking models by aggregate preference or accuracy; (c) the model's internal learned representation of the world.\n- **Made by / when:** benchmarks by academic and industry researchers, mostly frozen at a point in time; leaderboards updated continuously by voters or automated eval harnesses; internal world models fixed at each model's training-data cutoff.\n- **Territory claimed:** \"how capable and reliable this model is for the tasks people will actually use it for.\"\n\n## S2 — Structural omissions\n\nWhat the benchmark/leaderboard maps omit by design:\n\n- **Long, stateful, real tasks.** A single-turn multiple-choice score omits multi-step agentic work, long-context degradation, and tool use — which is where deployed assistants actually spend their time.\n- **Distribution shift after the cutoff.** The internal world model omits everything that happened after training data was frozen; the world keeps moving, the representation does not.\n- **Failure texture.** Aggregate accuracy omits *how* a model fails — confident fabrication (hallucination), refusal, or sycophantic agreement with a wrong premise all vanish into a single percentage.\n- **Contamination.** Public benchmarks can leak into training corpora, so a high score may partly measure memorization of the test rather than the underlying skill it claims to represent.\n\n## S3 — Structural distortions\n\n- **Linearity assumption:** that a higher benchmark number implies proportionally more useful real-world behavior. Deployment is not linear in eval score — a few percentage points on a saturated benchmark can mean little downstream.\n- **Single-number compression:** collapsing a multi-dimensional capability surface (reasoning, calibration, safety, latency, cost, robustness) into one rank.\n- **Hidden assumption of representativeness:** that the benchmark's task distribution matches the user's task distribution. When it does not, the map is precise about the wrong territory.\n- **Leaderboard incentive distortion:** because scores are public and competitive, they become targets — the classic [Goodhart's Law](../goodharts-law/SKILL.md) coupling, where models can be tuned to what the eval rewards (e.g., style or verbosity that wins votes) rather than to underlying usefulness.\n\n## S4 — Map age\n\n- Static benchmarks age fast: as capabilities rose through 2024–2025, several long-standing benchmarks approached saturation (top models clustering near the ceiling), losing their power to discriminate — an aging map that no longer resolves the territory.\n- Internal world models age at their training cutoff: a model confidently answering about \"current\" facts is reading an out-of-date map of a moved territory. This is the everyday, visible form of the gap — the assistant that is fluent and wrong about anything recent.\n- The industry response was itself an admission the maps had aged: a steady stream of *new* harder benchmarks and evolving arena formats appeared specifically because the old maps had stopped tracking the territory.\n\n## S5 — Direct territory signal\n\nWhere divergence from the map is largest — the primary, non-benchmark observations:\n\n- **Deployment behavior:** documented, widely reported cases of hallucinated citations, fabricated case law in legal filings, and confidently wrong outputs from high-scoring models — behavior a headline score does not predict.\n- **Agentic robustness:** the visible 2024–2026 gap between demo-level and reliable autonomous multi-step task completion; benchmarks like SWE-bench were introduced precisely to measure real repository-level work rather than toy problems.\n- **Sycophancy and calibration:** direct interaction shows models agreeing with incorrect user premises or expressing unwarranted confidence — a failure mode invisible in accuracy-only maps.\n- **Human-preference vs. correctness:** leaderboard rank (what voters *prefer*) can diverge from task correctness and safety, so the arena map and the reliability territory point in different directions.\n\n## S6 — Decide\n\n- **Fit:** Partially. Benchmarks and leaderboards remain useful *comparative* maps — but they are maps of test performance, not of deployed reliability.\n- **Required updates:** pair every benchmark claim with direct territory observation — task-specific evals on your own workload, red-teaming, human review of failure texture, and retrieval to patch the internal world model's aging. Track cost, latency, calibration, and safety alongside accuracy.\n- **Update trigger:** re-audit when a benchmark saturates, when your task distribution shifts, or whenever a score improves but user-reported failures do not fall. If the map keeps going up while the territory (support tickets, wrong-answer reports, abandoned agent runs) does not improve, suspect map-territory decoupling first.\n\n**The lesson for founders and operators deploying AI:** a rising eval score is a map of the test, not of your product. Before trusting \"the new model benchmarks higher,\" observe the territory — your users, your tasks, your failure modes — directly. The leaderboard does not read your production logs, and the model's world model does not read the news.\n\n*Sources: Stanford HAI, \"Artificial Intelligence Index Report 2024\" and \"2025,\" which document benchmark saturation and the introduction of harder evaluations; the SWE-bench benchmark (Jimenez et al., \"SWE-bench: Can Language Models Resolve Real-World GitHub Issues?\", ICLR 2024) for real-world agentic task evaluation; LMArena / Chatbot Arena (Chiang et al., \"Chatbot Arena: An Open Platform for Evaluating LLMs by Human Preference,\" 2024) for the human-preference leaderboard method and its known limitations; widely reported court sanctions over AI-fabricated legal citations (2023–2025, e.g., Mata v. Avianca and subsequent cases) as documented territory-level failures. Timeless core: Korzybski, A. (1933), *Science and Sanity*.*\n\nFile v1.0.4:examples/mcnamara-vietnam-kill-ratio-map.md\n\n# Method in Action: McNamara and the Vietnam Kill-Ratio Map\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nThe most operationally instructive case of map-territory decoupling in modern history is Robert McNamara's management of the Vietnam War using statistical metrics as the primary navigation system.\n\nMcNamara, U.S. Secretary of Defense 1961–1968, came from the Ford Motor Company where systems analysis and quantitative management had produced measurable results. He applied the same epistemology to the war: define measurable proxies, track them rigorously, use the trends as ground truth for strategic decisions.\n\nThe primary metric: **kill ratio** (enemy killed per U.S. soldier killed) and **body count** (enemy combatants killed). These were the maps McNamara and the Johnson administration used to navigate the territory of the war. The logic was sound as map logic: if the United States was killing far more of the enemy than the enemy was killing of the U.S., the U.S. was winning.\n\nThe kill ratio improved consistently from 1965 to 1968. The map said: progress.\n\nThe territory said: catastrophe. Civilian support for the Saigon government was eroding. North Vietnamese recruitment was accelerating. The Viet Cong infrastructure in the South was strengthening, not weakening. Public opinion in the United States was approaching a breaking point. The 1968 Tet Offensive — a coordinated assault on more than 100 South Vietnamese cities — shattered the map's credibility in a single week.\n\nMcNamara's own retrospective is among the most important primary source documents on map-territory failure in organizational decision-making:\n\n> \"We were wrong, terribly wrong. We owe it to future generations to explain why. We viewed the people and leaders of South Vietnam in terms of our own experience. We saw in them a thirst for — and a determination to fight for — freedom and democracy. We totally misjudged the political forces within the country.\"\n>\n> — McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. p. xvi.\n\nThe map (kill ratio, body count, area control percentages) omitted:\n\n- **Legitimacy signals.** Whether the South Vietnamese population supported the Saigon government — the single most strategically decisive variable — was not in the map.\n- **Adversary adaptation.** The North Vietnamese adapted to minimize body count by avoiding pitched battles, converting the map metric into a measure of guerrilla discipline rather than strategic failure.\n- **Incentive corruption.** U.S. field commanders, evaluated on kill ratios, had strong incentives to over-report enemy killed and under-report civilian casualties. The map was being optimized (in the Goodhart's Law sense), making it increasingly disconnected from territory.\n- **Time horizon.** The map showed who was winning each engagement. It could not show who would sustain the war longer — which was the decisive question.\n\nThe McNamara case demonstrates three map-territory failure modes that recur in organizational settings:\n\n**First, metric selection encodes assumptions about what matters.** The decision to use kill ratio as the primary metric encoded the assumption that the war was primarily a military attrition problem. The territory was primarily a political legitimacy problem. The map was wrong in kind, not just in degree.\n\n**Second, improving maps can mask deteriorating territory.** The kill ratio kept improving through 1967. Decision-makers read this as progress. The metric's improvement filtered out the signals that the territory was moving in the opposite direction. A map that always shows improvement under optimization is not a map of territory — it is a map of itself.\n\n**Third, map improvement can generate perverse territory dynamics.** When field commanders were evaluated on body count, the territory adapted: enemy combatants minimized engagement, and the body count filled with civilians and inflated reporting. The metric was optimizing the field behavior rather than describing the war.\n\nThe lesson for founders and operators: when the map (dashboard, KPI, model) consistently improves while anecdotal, qualitative, and peripheral signals are deteriorating, the hypothesis to investigate first is map-territory decoupling — not execution failure, not signal noise. The territory may have moved.\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nHelps an agent audit whether a metric, model, strategy, process, or plan has drifted from the real-world territory it represents. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, operators, and strategy teams use this skill to challenge dashboards, benchmarks, models, or processes when direct customer, employee, or field signals suggest reality has moved. It guides the agent through a Map-Territory Audit covering omissions, distortions, age, direct observations, and update triggers. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may lead users to discuss business strategy, financial models, team health, customer signals, or other sensitive context. <br>\nMitigation: Share only information appropriate for the conversation and review generated guidance before acting on it. <br>\nRisk: The skill can challenge metrics, dashboards, models, or plans, which may produce misleading conclusions if treated as a substitute for direct validation. <br>\nMitigation: Use the audit as reasoning support and pair it with direct territory observations before changing strategy, process, or operational decisions. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/map-is-not-the-territory) <br>\n- [Sources - map-is-not-the-territory](references/sources.md) <br>\n- [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md) <br>\n- [AI Benchmarks as Maps of Capability (2024-2026)](examples/ai-benchmarks-vs-deployment-reality-2024-2026.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown Map-Territory Audit template and step-by-step coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Text-only reasoning output; no code execution or external tool calls.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 5 files, 8265 bytes\n\nFiles: examples/mcnamara-vietnam-kill-ratio-map.md (4384b), references/sources.md (1063b), skill-card.md (2129b), SKILL.md (8366b), _meta.json (143b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: map-is-not-the-territory\ndescription: \"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter.\"\n---\n\n# Map Is Not the Territory\n\n## Overview\n\nAny representation — metric, model, strategy deck, org chart, or process manual — is a selective, simplified, aging abstraction. Maps omit (reflecting past priorities), distort (projecting dynamic reality onto static surfaces), and age (the territory moves; the map does not). The map is useful because it compresses complexity; dangerous because users forget it is a compression. Composes with `goodharts-law` (optimizing a metric makes it an even worse map), `first-principles` (rebuilding from territory when maps fail), and `narrative-fallacy` (every narrative is a map that ages).\n\n## When to Use\n\n- A key metric improves while customer feedback, morale, or competitor signals deteriorate\n- Team disagreement cannot be resolved by data — parties are disagreeing about maps, not territory\n- A strategy, model, process, or org chart has not been reviewed in more than one planning cycle\n- \"The data shows...\" but the data is old, narrow, or from a proxy source\n- A metric is being optimized directly without asking whether it still maps to the underlying goal\n\n**Not when:** the map is demonstrably current and well-calibrated; decision is low-stakes; territory is stable and map is freshly validated.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete map/decision → run The Process directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: the metric, model, or plan you are navigating with is not reality — it is a selective, aging abstraction of it. Confusing the two is how smart people make systematic errors.\n2. Check fit: is there a map being used to navigate? Is there evidence the territory has moved beyond the map?\n3. Elicit their real case: what is the map? what territory does it claim to represent? when was it last calibrated?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input: what does the map omit? how has it aged? what direct territory observations are available?\n> **[WAIT — do not advance until user responds]**\n5. Close by naming the map-territory gap explicitly: omissions identified, distortions named, calibration action defined, update trigger specified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**S1 — Name the map:** what is it (metric, model, plan, process)? who made it and when? what territory does it claim to represent?\n\n**S2 — Structural omissions:** what does it omit by design? by measurement limits? by aging? what signals are outside this map?\n\n**S3 — Structural distortions:** what relationships does it assume (linear, causal, static)? what assumptions must be true for it to be accurate?\n\n**S4 — Map age:** when was it last calibrated? what has changed since? is it inside or outside its useful life?\n\n**S5 — Direct territory signal:** what direct observations are available (interviews, field visits, primary data)? where is divergence from the map greatest?\n\n**S6 — Decide:** use as-is / update / replace. what specific updates close the most important gap? what is the update trigger?\n\n## Output: Map-Territory Audit\n```\nMap: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger\n```\n\n*→ Method in Action: [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md)*\n\n## Pack: Map-Territory Mismatches Across Domains\n\n| Domain | Map | Key omission | Territory signal missed |\n|---|---|---|---|\n| Startup growth | MAU | Churn drivers, value realization | Users activate but don't retain |\n| Sales | Pipeline × close rate | Buying-committee dynamics | Close rate collapses late-stage |\n| Team health | Satisfaction scores | Silent disengagement | Top performers leave without warning |\n| Financial model | Revenue/cost projections | Cash flow dynamics | Model shows profit; cash crisis arrives |\n| Org chart | Formal authority | Informal influence networks | Decisions route through uncharted nodes |\n\n## Applying It Well\n\n- Pair a map audit with at least one direct territory observation — not another map\n- Distinguish map-territory decoupling from execution failure before diagnosing either\n- Name the update trigger explicitly; maps without recalibration schedules age silently\n- Expert confidence does not track map applicability to novel territory\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Our metrics are all green — we're doing well.\" | Metrics are a map. Green metrics with deteriorating qualitative signals indicate map-territory decoupling. |\n| [D] \"The model shows this will work.\" | The model encodes assumptions that may be outdated. The territory does not read the model. |\n| [D] \"We followed the process exactly.\" | The process was a map of conditions that may no longer exist. Process compliance is not territory compliance. |\n| [D] \"The data doesn't show any problems.\" | The data measures a subset of territory designed for past priorities. Absence in data ≠ absence in territory. |\n| [D] \"We optimized the KPI — we improved the business.\" | Optimizing a metric is optimizing the map. Only direct territory observation shows whether underlying reality improved. |\n| [D] \"The expert said this is how the market works.\" | Expert models are maps from past encounters. Novel conditions may invalidate the map without invalidating the expert's confidence. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Key metric improving but qualitative signals (customers, team, partners) are worsening\n- Model or plan not updated within the current competitive or operational cycle\n- Team disagreements cannot be resolved by data — parties are disagreeing about maps, not territory\n- A process is followed because \"it's the process\" without reference to its original outcome\n- A metric is being managed directly rather than used as a signal of underlying reality\n- Field team reports a reality that contradicts the dashboard — and is told the dashboard is correct\n\n## Verification\n\n- [ ] Map named and creation date identified\n- [ ] Structural omissions listed (what the map cannot show by design)\n- [ ] Structural distortions listed (what the map misrepresents by design)\n- [ ] Map age assessed relative to territory's rate of change\n- [ ] At least one direct territory observation gathered (not mediated by the map)\n- [ ] Most significant map-territory divergence identified and named\n- [ ] Decision made: use as-is, update, or replace; update trigger specified\n\n**Stop rule:** if territory observation and map are consistent across multiple independent signals, stop auditing. Over-applying risks paralytic model-skepticism where no map is trusted enough to navigate.\n\n---\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/map-is-not-the-territory** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"map-is-not-the-territory\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783508928209\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — map-is-not-the-territory\n\n> *Primary sources for the [map-is-not-the-territory](../SKILL.md) skill.*\n\n- Korzybski, A. (1933). *Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics.* Institute of General Semantics. 5th ed. ISBN 978-0937298015. The original source.\n- Bateson, G. (1972). *Steps to an Ecology of Mind.* Ballantine Books. Extended the principle into systems theory and epistemology.\n- McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. ISBN 978-0812925333. Primary source case study on map-territory decoupling in strategic management.\n- Hayakawa, S. I. (1949). *Language in Thought and Action.* Harcourt. A key popularizer of Korzybski's general semantics framework.\n- Meadows, D. H. (2008). *Thinking in Systems: A Primer.* Chelsea Green. ISBN 978-1603580557. Systems-level treatment of model-reality divergence.\n- Taleb, N. N. (2010). *The Black Swan.* 2nd ed. Random House. ISBN 978-0812973815. The map-territory failure mode in statistical and financial models.\n\nFile v1.0.3:examples/mcnamara-vietnam-kill-ratio-map.md\n\n# Method in Action: McNamara and the Vietnam Kill-Ratio Map\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nThe most operationally instructive case of map-territory decoupling in modern history is Robert McNamara's management of the Vietnam War using statistical metrics as the primary navigation system.\n\nMcNamara, U.S. Secretary of Defense 1961–1968, came from the Ford Motor Company where systems analysis and quantitative management had produced measurable results. He applied the same epistemology to the war: define measurable proxies, track them rigorously, use the trends as ground truth for strategic decisions.\n\nThe primary metric: **kill ratio** (enemy killed per U.S. soldier killed) and **body count** (enemy combatants killed). These were the maps McNamara and the Johnson administration used to navigate the territory of the war. The logic was sound as map logic: if the United States was killing far more of the enemy than the enemy was killing of the U.S., the U.S. was winning.\n\nThe kill ratio improved consistently from 1965 to 1968. The map said: progress.\n\nThe territory said: catastrophe. Civilian support for the Saigon government was eroding. North Vietnamese recruitment was accelerating. The Viet Cong infrastructure in the South was strengthening, not weakening. Public opinion in the United States was approaching a breaking point. The 1968 Tet Offensive — a coordinated assault on more than 100 South Vietnamese cities — shattered the map's credibility in a single week.\n\nMcNamara's own retrospective is among the most important primary source documents on map-territory failure in organizational decision-making:\n\n> \"We were wrong, terribly wrong. We owe it to future generations to explain why. We viewed the people and leaders of South Vietnam in terms of our own experience. We saw in them a thirst for — and a determination to fight for — freedom and democracy. We totally misjudged the political forces within the country.\"\n>\n> — McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. p. xvi.\n\nThe map (kill ratio, body count, area control percentages) omitted:\n\n- **Legitimacy signals.** Whether the South Vietnamese population supported the Saigon government — the single most strategically decisive variable — was not in the map.\n- **Adversary adaptation.** The North Vietnamese adapted to minimize body count by avoiding pitched battles, converting the map metric into a measure of guerrilla discipline rather than strategic failure.\n- **Incentive corruption.** U.S. field commanders, evaluated on kill ratios, had strong incentives to over-report enemy killed and under-report civilian casualties. The map was being optimized (in the Goodhart's Law sense), making it increasingly disconnected from territory.\n- **Time horizon.** The map showed who was winning each engagement. It could not show who would sustain the war longer — which was the decisive question.\n\nThe McNamara case demonstrates three map-territory failure modes that recur in organizational settings:\n\n**First, metric selection encodes assumptions about what matters.** The decision to use kill ratio as the primary metric encoded the assumption that the war was primarily a military attrition problem. The territory was primarily a political legitimacy problem. The map was wrong in kind, not just in degree.\n\n**Second, improving maps can mask deteriorating territory.** The kill ratio kept improving through 1967. Decision-makers read this as progress. The metric's improvement filtered out the signals that the territory was moving in the opposite direction. A map that always shows improvement under optimization is not a map of territory — it is a map of itself.\n\n**Third, map improvement can generate perverse territory dynamics.** When field commanders were evaluated on body count, the territory adapted: enemy combatants minimized engagement, and the body count filled with civilians and inflated reporting. The metric was optimizing the field behavior rather than describing the war.\n\nThe lesson for founders and operators: when the map (dashboard, KPI, model) consistently improves while anecdotal, qualitative, and peripheral signals are deteriorating, the hypothesis to investigate first is map-territory decoupling — not execution failure, not signal noise. The territory may have moved.\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nHelps agents audit when metrics, models, processes, or plans have drifted from the underlying reality they are meant to represent. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nOperators, founders, strategy teams, and other decision-makers use this skill to audit a metric, model, plan, or process against direct territory signals before relying on it. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Strategic recommendations can be misleading if treated as a substitute for direct observation or domain review. <br>\nMitigation: Use the audit as decision support and validate conclusions against primary data, stakeholder feedback, and appropriate expert review before acting. <br>\nRisk: Over-applying map skepticism can slow decisions when the available map is current and well calibrated. <br>\nMitigation: Use the skill's stop rule: stop auditing when map and territory observations are consistent across multiple independent signals. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/map-is-not-the-territory) <br>\n- [Primary sources](references/sources.md) <br>\n- [Method in Action: McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown audit with structured fields] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a Map-Territory Audit covering omissions, distortions, map age, direct territory signals, and update decisions.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 5 files, 8376 bytes\n\nFiles: examples/mcnamara-vietnam-kill-ratio-map.md (4384b), references/sources.md (1063b), skill-card.md (2284b), SKILL.md (8480b), _meta.json (143b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: map-is-not-the-territory\ndescription: \"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter.\"\n---\n\n# Map Is Not the Territory\n\n## Overview\n\nAny representation — metric, model, strategy deck, org chart, or process manual — is a selective, simplified, aging abstraction. Maps omit (reflecting past priorities), distort (projecting dynamic reality onto static surfaces), and age (the territory moves; the map does not). The map is useful because it compresses complexity; dangerous because users forget it is a compression. Composes with `goodharts-law` (optimizing a metric makes it an even worse map), `first-principles` (rebuilding from territory when maps fail), and `narrative-fallacy` (every narrative is a map that ages).\n\n## When to Use\n\n- A key metric improves while customer feedback, morale, or competitor signals deteriorate\n- Team disagreement cannot be resolved by data — parties are disagreeing about maps, not territory\n- A strategy, model, process, or org chart has not been reviewed in more than one planning cycle\n- \"The data shows...\" but the data is old, narrow, or from a proxy source\n- A metric is being optimized directly without asking whether it still maps to the underlying goal\n\n**Not when:** the map is demonstrably current and well-calibrated; decision is low-stakes; territory is stable and map is freshly validated.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete map/decision → run The Process directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: the metric, model, or plan you are navigating with is not reality — it is a selective, aging abstraction of it. Confusing the two is how smart people make systematic errors.\n2. Check fit: is there a map being used to navigate? Is there evidence the territory has moved beyond the map?\n3. Elicit their real case: what is the map? what territory does it claim to represent? when was it last calibrated?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input: what does the map omit? how has it aged? what direct territory observations are available?\n> **[WAIT — do not advance until user responds]**\n5. Close by naming the map-territory gap explicitly: omissions identified, distortions named, calibration action defined, update trigger specified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**S1 — Name the map:** what is it (metric, model, plan, process)? who made it and when? what territory does it claim to represent?\n\n**S2 — Structural omissions:** what does it omit by design? by measurement limits? by aging? what signals are outside this map?\n\n**S3 — Structural distortions:** what relationships does it assume (linear, causal, static)? what assumptions must be true for it to be accurate?\n\n**S4 — Map age:** when was it last calibrated? what has changed since? is it inside or outside its useful life?\n\n**S5 — Direct territory signal:** what direct observations are available (interviews, field visits, primary data)? where is divergence from the map greatest?\n\n**S6 — Decide:** use as-is / update / replace. what specific updates close the most important gap? what is the update trigger?\n\n## Output: Map-Territory Audit\n```\nMap: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger\n```\n\n*→ Method in Action: [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md)*\n\n## Pack: Map-Territory Mismatches Across Domains\n\n| Domain | Map | Key omission | Territory signal missed |\n|---|---|---|---|\n| Startup growth | MAU | Churn drivers, value realization | Users activate but don't retain |\n| Sales | Pipeline × close rate | Buying-committee dynamics | Close rate collapses late-stage |\n| Team health | Satisfaction scores | Silent disengagement | Top performers leave without warning |\n| Financial model | Revenue/cost projections | Cash flow dynamics | Model shows profit; cash crisis arrives |\n| Org chart | Formal authority | Informal influence networks | Decisions route through uncharted nodes |\n\n## Applying It Well\n\n- Pair a map audit with at least one direct territory observation — not another map\n- Distinguish map-territory decoupling from execution failure before diagnosing either\n- Name the update trigger explicitly; maps without recalibration schedules age silently\n- Expert confidence does not track map applicability to novel territory\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Our metrics are all green — we're doing well.\" | Metrics are a map. Green metrics with deteriorating qualitative signals indicate map-territory decoupling. |\n| [D] \"The model shows this will work.\" | The model encodes assumptions that may be outdated. The territory does not read the model. |\n| [D] \"We followed the process exactly.\" | The process was a map of conditions that may no longer exist. Process compliance is not territory compliance. |\n| [D] \"The data doesn't show any problems.\" | The data measures a subset of territory designed for past priorities. Absence in data ≠ absence in territory. |\n| [D] \"We optimized the KPI — we improved the business.\" | Optimizing a metric is optimizing the map. Only direct territory observation shows whether underlying reality improved. |\n| [D] \"The expert said this is how the market works.\" | Expert models are maps from past encounters. Novel conditions may invalidate the map without invalidating the expert's confidence. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Key metric improving but qualitative signals (customers, team, partners) are worsening\n- Model or plan not updated within the current competitive or operational cycle\n- Team disagreements cannot be resolved by data — parties are disagreeing about maps, not territory\n- A process is followed because \"it's the process\" without reference to its original outcome\n- A metric is being managed directly rather than used as a signal of underlying reality\n- Field team reports a reality that contradicts the dashboard — and is told the dashboard is correct\n\n## Verification\n\n- [ ] Map named and creation date identified\n- [ ] Structural omissions listed (what the map cannot show by design)\n- [ ] Structural distortions listed (what the map misrepresents by design)\n- [ ] Map age assessed relative to territory's rate of change\n- [ ] At least one direct territory observation gathered (not mediated by the map)\n- [ ] Most significant map-territory divergence identified and named\n- [ ] Decision made: use as-is, update, or replace; update trigger specified\n\n**Stop rule:** if territory observation and map are consistent across multiple independent signals, stop auditing. Over-applying risks paralytic model-skepticism where no map is trusted enough to navigate.\n\n---\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/map-is-not-the-territory?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=map-is-not-the-territory** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"map-is-not-the-territory\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783472014570\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — map-is-not-the-territory\n\n> *Primary sources for the [map-is-not-the-territory](../SKILL.md) skill.*\n\n- Korzybski, A. (1933). *Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics.* Institute of General Semantics. 5th ed. ISBN 978-0937298015. The original source.\n- Bateson, G. (1972). *Steps to an Ecology of Mind.* Ballantine Books. Extended the principle into systems theory and epistemology.\n- McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. ISBN 978-0812925333. Primary source case study on map-territory decoupling in strategic management.\n- Hayakawa, S. I. (1949). *Language in Thought and Action.* Harcourt. A key popularizer of Korzybski's general semantics framework.\n- Meadows, D. H. (2008). *Thinking in Systems: A Primer.* Chelsea Green. ISBN 978-1603580557. Systems-level treatment of model-reality divergence.\n- Taleb, N. N. (2010). *The Black Swan.* 2nd ed. Random House. ISBN 978-0812973815. The map-territory failure mode in statistical and financial models.\n\nFile v1.0.2:examples/mcnamara-vietnam-kill-ratio-map.md\n\n# Method in Action: McNamara and the Vietnam Kill-Ratio Map\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nThe most operationally instructive case of map-territory decoupling in modern history is Robert McNamara's management of the Vietnam War using statistical metrics as the primary navigation system.\n\nMcNamara, U.S. Secretary of Defense 1961–1968, came from the Ford Motor Company where systems analysis and quantitative management had produced measurable results. He applied the same epistemology to the war: define measurable proxies, track them rigorously, use the trends as ground truth for strategic decisions.\n\nThe primary metric: **kill ratio** (enemy killed per U.S. soldier killed) and **body count** (enemy combatants killed). These were the maps McNamara and the Johnson administration used to navigate the territory of the war. The logic was sound as map logic: if the United States was killing far more of the enemy than the enemy was killing of the U.S., the U.S. was winning.\n\nThe kill ratio improved consistently from 1965 to 1968. The map said: progress.\n\nThe territory said: catastrophe. Civilian support for the Saigon government was eroding. North Vietnamese recruitment was accelerating. The Viet Cong infrastructure in the South was strengthening, not weakening. Public opinion in the United States was approaching a breaking point. The 1968 Tet Offensive — a coordinated assault on more than 100 South Vietnamese cities — shattered the map's credibility in a single week.\n\nMcNamara's own retrospective is among the most important primary source documents on map-territory failure in organizational decision-making:\n\n> \"We were wrong, terribly wrong. We owe it to future generations to explain why. We viewed the people and leaders of South Vietnam in terms of our own experience. We saw in them a thirst for — and a determination to fight for — freedom and democracy. We totally misjudged the political forces within the country.\"\n>\n> — McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. p. xvi.\n\nThe map (kill ratio, body count, area control percentages) omitted:\n\n- **Legitimacy signals.** Whether the South Vietnamese population supported the Saigon government — the single most strategically decisive variable — was not in the map.\n- **Adversary adaptation.** The North Vietnamese adapted to minimize body count by avoiding pitched battles, converting the map metric into a measure of guerrilla discipline rather than strategic failure.\n- **Incentive corruption.** U.S. field commanders, evaluated on kill ratios, had strong incentives to over-report enemy killed and under-report civilian casualties. The map was being optimized (in the Goodhart's Law sense), making it increasingly disconnected from territory.\n- **Time horizon.** The map showed who was winning each engagement. It could not show who would sustain the war longer — which was the decisive question.\n\nThe McNamara case demonstrates three map-territory failure modes that recur in organizational settings:\n\n**First, metric selection encodes assumptions about what matters.** The decision to use kill ratio as the primary metric encoded the assumption that the war was primarily a military attrition problem. The territory was primarily a political legitimacy problem. The map was wrong in kind, not just in degree.\n\n**Second, improving maps can mask deteriorating territory.** The kill ratio kept improving through 1967. Decision-makers read this as progress. The metric's improvement filtered out the signals that the territory was moving in the opposite direction. A map that always shows improvement under optimization is not a map of territory — it is a map of itself.\n\n**Third, map improvement can generate perverse territory dynamics.** When field commanders were evaluated on body count, the territory adapted: enemy combatants minimized engagement, and the body count filled with civilians and inflated reporting. The metric was optimizing the field behavior rather than describing the war.\n\nThe lesson for founders and operators: when the map (dashboard, KPI, model) consistently improves while anecdotal, qualitative, and peripheral signals are deteriorating, the hypothesis to investigate first is map-territory decoupling — not execution failure, not signal noise. The territory may have moved.\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nHelps agents audit whether a metric, model, plan, process, or other map still matches the reality it is being used to navigate. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, operators, and decision-support agents use this skill to test whether dashboards, KPIs, plans, models, or processes have drifted away from the underlying customer, team, market, or operational reality. It guides a map-territory audit that identifies omissions, distortions, age, direct territory signals, and an update or replacement decision. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Users may place confidential business, customer, or employee details into local examples or templates while applying the audit. <br>\nMitigation: Use anonymized or non-sensitive examples unless retaining those details in the local skill copy is intentional. <br>\nRisk: Over-applying the framework can create excessive skepticism about useful, freshly calibrated maps. <br>\nMitigation: Stop the audit when direct territory observations and the map agree across multiple independent signals. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/map-is-not-the-territory) <br>\n- [Primary sources](references/sources.md) <br>\n- [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Text] <br>\n**Output Format:** [Markdown audit template and stepwise coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a Map-Territory Audit covering map identity, omissions, distortions, age, territory signals, decision, required updates, and update trigger.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 5 files, 8219 bytes\n\nFiles: examples/mcnamara-vietnam-kill-ratio-map.md (4384b), references/sources.md (1063b), skill-card.md (2180b), SKILL.md (8298b), _meta.json (143b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: map-is-not-the-territory\ndescription: \"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter.\"\n---\n\n# Map Is Not the Territory\n\n## Overview\n\nAny representation — metric, model, strategy deck, org chart, or process manual — is a selective, simplified, aging abstraction. Maps omit (reflecting past priorities), distort (projecting dynamic reality onto static surfaces), and age (the territory moves; the map does not). The map is useful because it compresses complexity; dangerous because users forget it is a compression. Composes with [`goodharts-law`](../goodharts-law/SKILL.md) (optimizing a metric makes it an even worse map), [`first-principles`](../first-principles/SKILL.md) (rebuilding from territory when maps fail), and [`narrative-fallacy`](../narrative-fallacy/SKILL.md) (every narrative is a map that ages).\n\n## When to Use\n\n- A key metric improves while customer feedback, morale, or competitor signals deteriorate\n- Team disagreement cannot be resolved by data — parties are disagreeing about maps, not territory\n- A strategy, model, process, or org chart has not been reviewed in more than one planning cycle\n- \"The data shows...\" but the data is old, narrow, or from a proxy source\n- A metric is being optimized directly without asking whether it still maps to the underlying goal\n\n**Not when:** the map is demonstrably current and well-calibrated; decision is low-stakes; territory is stable and map is freshly validated.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete map/decision → run The Process directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: the metric, model, or plan you are navigating with is not reality — it is a selective, aging abstraction of it. Confusing the two is how smart people make systematic errors.\n2. Check fit: is there a map being used to navigate? Is there evidence the territory has moved beyond the map?\n3. Elicit their real case: what is the map? what territory does it claim to represent? when was it last calibrated?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input: what does the map omit? how has it aged? what direct territory observations are available?\n> **[WAIT — do not advance until user responds]**\n5. Close by naming the map-territory gap explicitly: omissions identified, distortions named, calibration action defined, update trigger specified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**S1 — Name the map:** what is it (metric, model, plan, process)? who made it and when? what territory does it claim to represent?\n\n**S2 — Structural omissions:** what does it omit by design? by measurement limits? by aging? what signals are outside this map?\n\n**S3 — Structural distortions:** what relationships does it assume (linear, causal, static)? what assumptions must be true for it to be accurate?\n\n**S4 — Map age:** when was it last calibrated? what has changed since? is it inside or outside its useful life?\n\n**S5 — Direct territory signal:** what direct observations are available (interviews, field visits, primary data)? where is divergence from the map greatest?\n\n**S6 — Decide:** use as-is / update / replace. what specific updates close the most important gap? what is the update trigger?\n\n## Output: Map-Territory Audit\n```\nMap: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger\n```\n\n*→ Method in Action: [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md)*\n\n## Pack: Map-Territory Mismatches Across Domains\n\n| Domain | Map | Key omission | Territory signal missed |\n|---|---|---|---|\n| Startup growth | MAU | Churn drivers, value realization | Users activate but don't retain |\n| Sales | Pipeline × close rate | Buying-committee dynamics | Close rate collapses late-stage |\n| Team health | Satisfaction scores | Silent disengagement | Top performers leave without warning |\n| Financial model | Revenue/cost projections | Cash flow dynamics | Model shows profit; cash crisis arrives |\n| Org chart | Formal authority | Informal influence networks | Decisions route through uncharted nodes |\n\n## Applying It Well\n\n- Pair a map audit with at least one direct territory observation — not another map\n- Distinguish map-territory decoupling from execution failure before diagnosing either\n- Name the update trigger explicitly; maps without recalibration schedules age silently\n- Expert confidence does not track map applicability to novel territory\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Our metrics are all green — we're doing well.\" | Metrics are a map. Green metrics with deteriorating qualitative signals indicate map-territory decoupling. |\n| [D] \"The model shows this will work.\" | The model encodes assumptions that may be outdated. The territory does not read the model. |\n| [D] \"We followed the process exactly.\" | The process was a map of conditions that may no longer exist. Process compliance is not territory compliance. |\n| [D] \"The data doesn't show any problems.\" | The data measures a subset of territory designed for past priorities. Absence in data ≠ absence in territory. |\n| [D] \"We optimized the KPI — we improved the business.\" | Optimizing a metric is optimizing the map. Only direct territory observation shows whether underlying reality improved. |\n| [D] \"The expert said this is how the market works.\" | Expert models are maps from past encounters. Novel conditions may invalidate the map without invalidating the expert's confidence. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Key metric improving but qualitative signals (customers, team, partners) are worsening\n- Model or plan not updated within the current competitive or operational cycle\n- Team disagreements cannot be resolved by data — parties are disagreeing about maps, not territory\n- A process is followed because \"it's the process\" without reference to its original outcome\n- A metric is being managed directly rather than used as a signal of underlying reality\n- Field team reports a reality that contradicts the dashboard — and is told the dashboard is correct\n\n## Verification\n\n- [ ] Map named and creation date identified\n- [ ] Structural omissions listed (what the map cannot show by design)\n- [ ] Structural distortions listed (what the map misrepresents by design)\n- [ ] Map age assessed relative to territory's rate of change\n- [ ] At least one direct territory observation gathered (not mediated by the map)\n- [ ] Most significant map-territory divergence identified and named\n- [ ] Decision made: use as-is, update, or replace; update trigger specified\n\n**Stop rule:** if territory observation and map are consistent across multiple independent signals, stop auditing. Over-applying risks paralytic model-skepticism where no map is trusted enough to navigate.\n\n---\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"map-is-not-the-territory\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783463294803\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — map-is-not-the-territory\n\n> *Primary sources for the [map-is-not-the-territory](../SKILL.md) skill.*\n\n- Korzybski, A. (1933). *Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics.* Institute of General Semantics. 5th ed. ISBN 978-0937298015. The original source.\n- Bateson, G. (1972). *Steps to an Ecology of Mind.* Ballantine Books. Extended the principle into systems theory and epistemology.\n- McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. ISBN 978-0812925333. Primary source case study on map-territory decoupling in strategic management.\n- Hayakawa, S. I. (1949). *Language in Thought and Action.* Harcourt. A key popularizer of Korzybski's general semantics framework.\n- Meadows, D. H. (2008). *Thinking in Systems: A Primer.* Chelsea Green. ISBN 978-1603580557. Systems-level treatment of model-reality divergence.\n- Taleb, N. N. (2010). *The Black Swan.* 2nd ed. Random House. ISBN 978-0812973815. The map-territory failure mode in statistical and financial models.\n\nFile v1.0.1:examples/mcnamara-vietnam-kill-ratio-map.md\n\n# Method in Action: McNamara and the Vietnam Kill-Ratio Map\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nThe most operationally instructive case of map-territory decoupling in modern history is Robert McNamara's management of the Vietnam War using statistical metrics as the primary navigation system.\n\nMcNamara, U.S. Secretary of Defense 1961–1968, came from the Ford Motor Company where systems analysis and quantitative management had produced measurable results. He applied the same epistemology to the war: define measurable proxies, track them rigorously, use the trends as ground truth for strategic decisions.\n\nThe primary metric: **kill ratio** (enemy killed per U.S. soldier killed) and **body count** (enemy combatants killed). These were the maps McNamara and the Johnson administration used to navigate the territory of the war. The logic was sound as map logic: if the United States was killing far more of the enemy than the enemy was killing of the U.S., the U.S. was winning.\n\nThe kill ratio improved consistently from 1965 to 1968. The map said: progress.\n\nThe territory said: catastrophe. Civilian support for the Saigon government was eroding. North Vietnamese recruitment was accelerating. The Viet Cong infrastructure in the South was strengthening, not weakening. Public opinion in the United States was approaching a breaking point. The 1968 Tet Offensive — a coordinated assault on more than 100 South Vietnamese cities — shattered the map's credibility in a single week.\n\nMcNamara's own retrospective is among the most important primary source documents on map-territory failure in organizational decision-making:\n\n> \"We were wrong, terribly wrong. We owe it to future generations to explain why. We viewed the people and leaders of South Vietnam in terms of our own experience. We saw in them a thirst for — and a determination to fight for — freedom and democracy. We totally misjudged the political forces within the country.\"\n>\n> — McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. p. xvi.\n\nThe map (kill ratio, body count, area control percentages) omitted:\n\n- **Legitimacy signals.** Whether the South Vietnamese population supported the Saigon government — the single most strategically decisive variable — was not in the map.\n- **Adversary adaptation.** The North Vietnamese adapted to minimize body count by avoiding pitched battles, converting the map metric into a measure of guerrilla discipline rather than strategic failure.\n- **Incentive corruption.** U.S. field commanders, evaluated on kill ratios, had strong incentives to over-report enemy killed and under-report civilian casualties. The map was being optimized (in the Goodhart's Law sense), making it increasingly disconnected from territory.\n- **Time horizon.** The map showed who was winning each engagement. It could not show who would sustain the war longer — which was the decisive question.\n\nThe McNamara case demonstrates three map-territory failure modes that recur in organizational settings:\n\n**First, metric selection encodes assumptions about what matters.** The decision to use kill ratio as the primary metric encoded the assumption that the war was primarily a military attrition problem. The territory was primarily a political legitimacy problem. The map was wrong in kind, not just in degree.\n\n**Second, improving maps can mask deteriorating territory.** The kill ratio kept improving through 1967. Decision-makers read this as progress. The metric's improvement filtered out the signals that the territory was moving in the opposite direction. A map that always shows improvement under optimization is not a map of territory — it is a map of itself.\n\n**Third, map improvement can generate perverse territory dynamics.** When field commanders were evaluated on body count, the territory adapted: enemy combatants minimized engagement, and the body count filled with civilians and inflated reporting. The metric was optimizing the field behavior rather than describing the war.\n\nThe lesson for founders and operators: when the map (dashboard, KPI, model) consistently improves while anecdotal, qualitative, and peripheral signals are deteriorating, the hypothesis to investigate first is map-territory decoupling — not execution failure, not signal noise. The territory may have moved.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nGuides agents through a map-territory audit to test whether a metric, model, strategy, process, or plan still matches the reality it claims to represent. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, operators, and decision-support agents use this skill to audit whether dashboards, KPIs, models, org charts, or plans have become stale or misleading before relying on them for business or operational decisions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may influence real business, organizational, or operational decisions using an incomplete audit of reality. <br>\nMitigation: Treat outputs as decision-support prompts, require human judgment, and validate recommendations against direct territory observations before acting. <br>\nRisk: Over-applying the audit can lead users to distrust current, well-calibrated maps even when multiple independent signals agree. <br>\nMitigation: Use the skill's stop rule: if direct observations and the map remain consistent across independent signals, stop auditing and continue with the current map. <br>\n\n\n## Reference(s): <br>\n- [Primary sources](references/sources.md) <br>\n- [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Text] <br>\n**Output Format:** [Markdown audit with structured prompts, checklist items, and decision guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No code execution or external tool use is required; outputs should be treated as decision-support guidance.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 5 files, 8072 bytes\n\nFiles: examples/mcnamara-vietnam-kill-ratio-map.md (4384b), references/sources.md (1063b), skill-card.md (1803b), SKILL.md (8298b), _meta.json (143b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: map-is-not-the-territory\ndescription: \"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter.\"\n---\n\n# Map Is Not the Territory\n\n## Overview\n\nAny representation — metric, model, strategy deck, org chart, or process manual — is a selective, simplified, aging abstraction. Maps omit (reflecting past priorities), distort (projecting dynamic reality onto static surfaces), and age (the territory moves; the map does not). The map is useful because it compresses complexity; dangerous because users forget it is a compression. Composes with [`goodharts-law`](../goodharts-law/SKILL.md) (optimizing a metric makes it an even worse map), [`first-principles`](../first-principles/SKILL.md) (rebuilding from territory when maps fail), and [`narrative-fallacy`](../narrative-fallacy/SKILL.md) (every narrative is a map that ages).\n\n## When to Use\n\n- A key metric improves while customer feedback, morale, or competitor signals deteriorate\n- Team disagreement cannot be resolved by data — parties are disagreeing about maps, not territory\n- A strategy, model, process, or org chart has not been reviewed in more than one planning cycle\n- \"The data shows...\" but the data is old, narrow, or from a proxy source\n- A metric is being optimized directly without asking whether it still maps to the underlying goal\n\n**Not when:** the map is demonstrably current and well-calibrated; decision is low-stakes; territory is stable and map is freshly validated.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete map/decision → run The Process directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: the metric, model, or plan you are navigating with is not reality — it is a selective, aging abstraction of it. Confusing the two is how smart people make systematic errors.\n2. Check fit: is there a map being used to navigate? Is there evidence the territory has moved beyond the map?\n3. Elicit their real case: what is the map? what territory does it claim to represent? when was it last calibrated?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input: what does the map omit? how has it aged? what direct territory observations are available?\n> **[WAIT — do not advance until user responds]**\n5. Close by naming the map-territory gap explicitly: omissions identified, distortions named, calibration action defined, update trigger specified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**S1 — Name the map:** what is it (metric, model, plan, process)? who made it and when? what territory does it claim to represent?\n\n**S2 — Structural omissions:** what does it omit by design? by measurement limits? by aging? what signals are outside this map?\n\n**S3 — Structural distortions:** what relationships does it assume (linear, causal, static)? what assumptions must be true for it to be accurate?\n\n**S4 — Map age:** when was it last calibrated? what has changed since? is it inside or outside its useful life?\n\n**S5 — Direct territory signal:** what direct observations are available (interviews, field visits, primary data)? where is divergence from the map greatest?\n\n**S6 — Decide:** use as-is / update / replace. what specific updates close the most important gap? what is the update trigger?\n\n## Output: Map-Territory Audit\n```\nMap: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger\n```\n\n*→ Method in Action: [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md)*\n\n## Pack: Map-Territory Mismatches Across Domains\n\n| Domain | Map | Key omission | Territory signal missed |\n|---|---|---|---|\n| Startup growth | MAU | Churn drivers, value realization | Users activate but don't retain |\n| Sales | Pipeline × close rate | Buying-committee dynamics | Close rate collapses late-stage |\n| Team health | Satisfaction scores | Silent disengagement | Top performers leave without warning |\n| Financial model | Revenue/cost projections | Cash flow dynamics | Model shows profit; cash crisis arrives |\n| Org chart | Formal authority | Informal influence networks | Decisions route through uncharted nodes |\n\n## Applying It Well\n\n- Pair a map audit with at least one direct territory observation — not another map\n- Distinguish map-territory decoupling from execution failure before diagnosing either\n- Name the update trigger explicitly; maps without recalibration schedules age silently\n- Expert confidence does not track map applicability to novel territory\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Our metrics are all green — we're doing well.\" | Metrics are a map. Green metrics with deteriorating qualitative signals indicate map-territory decoupling. |\n| [D] \"The model shows this will work.\" | The model encodes assumptions that may be outdated. The territory does not read the model. |\n| [D] \"We followed the process exactly.\" | The process was a map of conditions that may no longer exist. Process compliance is not territory compliance. |\n| [D] \"The data doesn't show any problems.\" | The data measures a subset of territory designed for past priorities. Absence in data ≠ absence in territory. |\n| [D] \"We optimized the KPI — we improved the business.\" | Optimizing a metric is optimizing the map. Only direct territory observation shows whether underlying reality improved. |\n| [D] \"The expert said this is how the market works.\" | Expert models are maps from past encounters. Novel conditions may invalidate the map without invalidating the expert's confidence. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Key metric improving but qualitative signals (customers, team, partners) are worsening\n- Model or plan not updated within the current competitive or operational cycle\n- Team disagreements cannot be resolved by data — parties are disagreeing about maps, not territory\n- A process is followed because \"it's the process\" without reference to its original outcome\n- A metric is being managed directly rather than used as a signal of underlying reality\n- Field team reports a reality that contradicts the dashboard — and is told the dashboard is correct\n\n## Verification\n\n- [ ] Map named and creation date identified\n- [ ] Structural omissions listed (what the map cannot show by design)\n- [ ] Structural distortions listed (what the map misrepresents by design)\n- [ ] Map age assessed relative to territory's rate of change\n- [ ] At least one direct territory observation gathered (not mediated by the map)\n- [ ] Most significant map-territory divergence identified and named\n- [ ] Decision made: use as-is, update, or replace; update trigger specified\n\n**Stop rule:** if territory observation and map are consistent across multiple independent signals, stop auditing. Over-applying risks paralytic model-skepticism where no map is trusted enough to navigate.\n\n---\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"map-is-not-the-territory\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1782800253163\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — map-is-not-the-territory\n\n> *Primary sources for the [map-is-not-the-territory](../SKILL.md) skill.*\n\n- Korzybski, A. (1933). *Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics.* Institute of General Semantics. 5th ed. ISBN 978-0937298015. The original source.\n- Bateson, G. (1972). *Steps to an Ecology of Mind.* Ballantine Books. Extended the principle into systems theory and epistemology.\n- McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. ISBN 978-0812925333. Primary source case study on map-territory decoupling in strategic management.\n- Hayakawa, S. I. (1949). *Language in Thought and Action.* Harcourt. A key popularizer of Korzybski's general semantics framework.\n- Meadows, D. H. (2008). *Thinking in Systems: A Primer.* Chelsea Green. ISBN 978-1603580557. Systems-level treatment of model-reality divergence.\n- Taleb, N. N. (2010). *The Black Swan.* 2nd ed. Random House. ISBN 978-0812973815. The map-territory failure mode in statistical and financial models.\n\nFile v1.0.0:examples/mcnamara-vietnam-kill-ratio-map.md\n\n# Method in Action: McNamara and the Vietnam Kill-Ratio Map\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nThe most operationally instructive case of map-territory decoupling in modern history is Robert McNamara's management of the Vietnam War using statistical metrics as the primary navigation system.\n\nMcNamara, U.S. Secretary of Defense 1961–1968, came from the Ford Motor Company where systems analysis and quantitative management had produced measurable results. He applied the same epistemology to the war: define measurable proxies, track them rigorously, use the trends as ground truth for strategic decisions.\n\nThe primary metric: **kill ratio** (enemy killed per U.S. soldier killed) and **body count** (enemy combatants killed). These were the maps McNamara and the Johnson administration used to navigate the territory of the war. The logic was sound as map logic: if the United States was killing far more of the enemy than the enemy was killing of the U.S., the U.S. was winning.\n\nThe kill ratio improved consistently from 1965 to 1968. The map said: progress.\n\nThe territory said: catastrophe. Civilian support for the Saigon government was eroding. North Vietnamese recruitment was accelerating. The Viet Cong infrastructure in the South was strengthening, not weakening. Public opinion in the United States was approaching a breaking point. The 1968 Tet Offensive — a coordinated assault on more than 100 South Vietnamese cities — shattered the map's credibility in a single week.\n\nMcNamara's own retrospective is among the most important primary source documents on map-territory failure in organizational decision-making:\n\n> \"We were wrong, terribly wrong. We owe it to future generations to explain why. We viewed the people and leaders of South Vietnam in terms of our own experience. We saw in them a thirst for — and a determination to fight for — freedom and democracy. We totally misjudged the political forces within the country.\"\n>\n> — McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. p. xvi.\n\nThe map (kill ratio, body count, area control percentages) omitted:\n\n- **Legitimacy signals.** Whether the South Vietnamese population supported the Saigon government — the single most strategically decisive variable — was not in the map.\n- **Adversary adaptation.** The North Vietnamese adapted to minimize body count by avoiding pitched battles, converting the map metric into a measure of guerrilla discipline rather than strategic failure.\n- **Incentive corruption.** U.S. field commanders, evaluated on kill ratios, had strong incentives to over-report enemy killed and under-report civilian casualties. The map was being optimized (in the Goodhart's Law sense), making it increasingly disconnected from territory.\n- **Time horizon.** The map showed who was winning each engagement. It could not show who would sustain the war longer — which was the decisive question.\n\nThe McNamara case demonstrates three map-territory failure modes that recur in organizational settings:\n\n**First, metric selection encodes assumptions about what matters.** The decision to use kill ratio as the primary metric encoded the assumption that the war was primarily a military attrition problem. The territory was primarily a political legitimacy problem. The map was wrong in kind, not just in degree.\n\n**Second, improving maps can mask deteriorating territory.** The kill ratio kept improving through 1967. Decision-makers read this as progress. The metric's improvement filtered out the signals that the territory was moving in the opposite direction. A map that always shows improvement under optimization is not a map of territory — it is a map of itself.\n\n**Third, map improvement can generate perverse territory dynamics.** When field commanders were evaluated on body count, the territory adapted: enemy combatants minimized engagement, and the body count filled with civilians and inflated reporting. The metric was optimizing the field behavior rather than describing the war.\n\nThe lesson for founders and operators: when the map (dashboard, KPI, model) consistently improves while anecdotal, qualitative, and peripheral signals are deteriorating, the hypothesis to investigate first is map-territory decoupling — not execution failure, not signal noise. The territory may have moved.\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nHelps an agent audit whether a metric, model, plan, process, or other abstraction still matches current reality before relying on it for decisions. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees and external users use this skill to audit metrics, models, strategy decks, org charts, and processes against direct observations before making decisions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may influence how an agent frames decisions about metrics, models, and plans, which could lead to misleading conclusions if treated as factual proof. <br>\nMitigation: Use it as analytical coaching and verify cited examples, current facts, and high-stakes business conclusions with direct evidence and human review. <br>\n\n\n## Reference(s): <br>\n- [Sources](references/sources.md) <br>\n- [McNamara and the Vietnam Kill-Ratio Map](examples/mcnamara-vietnam-kill-ratio-map.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown, text] <br>\n**Output Format:** [Markdown map-territory audit with coaching questions and checklist items] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May pause at stepwise coaching prompts until the user provides a concrete case.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Map Is Not the Territory Owner: deciqai Summary: Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle;... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:05:36.886Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/map-is-not-the-territory.json) v1.0.4 | 2026-07-10","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Map: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger"},{"language":"text","snippet":"Map: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger"},{"language":"text","snippet":"Map: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger"},{"language":"text","snippet":"Map: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger"},{"language":"text","snippet":"Map: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger"},{"language":"text","snippet":"Map: <name> | Created by/when | Territory it represents\nOmissions: by design | by measurement limits | by aging\nDistortions: linearity assumptions | artificial boundaries | hidden assumptions\nAge: last calibrated | territory change rate | inside/outside useful life\nTerritory signals: source | key divergences from map\nDecision: fit Y/N/Partially | required updates | update trigger"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: map-is-not-the-territory\ndescription: \"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle; a team keeps disagreeing and can't resolve it with data; someone says 'the model shows...' or 'the data doesn't show any problems'; a plan is being followed because 'that's how we do it.' Do NOT activate when: the map is demonstrably current and freshly validated against the territory; the decision is so low-stakes that map imprecision doesn't matter. More: deciqai.com/c/map-is-not-the-territory\"\n---\n\n# Map Is Not the Territory\n\n## Overview\n\nAny representation — metric, model, strategy deck, org chart, or process manual — is a selective, simplified, aging abstraction. Maps omit (reflecting past priorities), distort (projecting dynamic reality onto static surfaces), and age (the territory moves; the map does not). The map is useful because it compresses complexity; dangerous because users forget it is a compression. Composes with `goodharts-law` (optimizing a metric makes it an even worse map), `first-principles` (rebuilding from territory when maps fail), and `narrative-fallacy` (every narrative is a map that ages).\n\n## When to Use\n\n- A key metric improves while customer feedback, morale, or competitor signals deteriorate\n- Team disagreement cannot be resolved by data — parties are disagreeing about maps, not territory\n- A strategy, model, process, or org chart has not been reviewed in more than one planning cycle\n- \"The data shows...\" but the data is old, narrow, or from a proxy source\n- A metric is being optimized directly without asking whether it still maps to the underlying goal\n- An AI model's benchmark score, leaderboard rank, or internal \"world model\" is being treated as proof of real-world capability (AI adoption / AI hype)\n\n**Not when:** the map is demonstrably current and well-calibrated; decision is low-stakes; territory is stable and map is freshly validated.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete map/decision → run The Process directly.\n- **Coach mode:** user is unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-liner: the metric, model, or plan you are navigating with is not reality — it is a selective, aging abstraction of it. Confusing the two is how smart people make systematic errors.\n2. Check fit: is there a map being used to navigate? Is there evidence the territory has moved beyond the map?\n3. Elicit their real case: what is the map? what territory does it claim to represent? when was it last calibrated?\n> **[WAIT — do not advance until user responds]**\n4. Run The Process one step at a time with their input: what does the map omit? how has it aged? what direct territory observations are available?\n> **[WAIT — do not advance until user responds]**\n5. "},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"map-is-not-the-territory\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784225136886\n}"},{"path":"references/sources.md","content":"# Sources — map-is-not-the-territory\n\n> *Primary sources for the [map-is-not-the-territory](../SKILL.md) skill.*\n\n- Korzybski, A. (1933). *Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics.* Institute of General Semantics. 5th ed. ISBN 978-0937298015. The original source.\n- Bateson, G. (1972). *Steps to an Ecology of Mind.* Ballantine Books. Extended the principle into systems theory and epistemology.\n- McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. ISBN 978-0812925333. Primary source case study on map-territory decoupling in strategic management.\n- Hayakawa, S. I. (1949). *Language in Thought and Action.* Harcourt. A key popularizer of Korzybski's general semantics framework.\n- Meadows, D. H. (2008). *Thinking in Systems: A Primer.* Chelsea Green. ISBN 978-1603580557. Systems-level treatment of model-reality divergence.\n- Taleb, N. N. (2010). *The Black Swan.* 2nd ed. Random House. ISBN 978-0812973815. The map-territory failure mode in statistical and financial models.\n- Stanford HAI (2024, 2025). *Artificial Intelligence Index Report.* Stanford Institute for Human-Centered AI. Documents AI benchmark saturation and the introduction of harder evaluations as older benchmarks stopped discriminating between top models — a contemporary map-territory case.\n- Jimenez, C. E., Yang, J., et al. (2024). *SWE-bench: Can Language Models Resolve Real-World GitHub Issues?* ICLR 2024. arXiv:2310.06770. Benchmark built to move evaluation closer to real deployment territory (repository-level software tasks) rather than toy problems."},{"path":"examples/ai-benchmarks-vs-deployment-reality-2024-2026.md","content":"# Method in Action: AI Benchmarks as Maps of Capability (2024–2026)\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nBetween 2024 and 2026 the AI industry navigated by a dense set of maps: benchmark scores (MMLU, GPQA, HumanEval, SWE-bench, GSM8K, MATH), public leaderboards (such as the crowd-voted LMArena / Chatbot Arena), and the model's own internal \"world model\" — the compressed statistical representation it builds of the world. Each is a map. The territory is what the system actually does when a real user, with a real task, in a messy real context, presses enter. The recurring 2024–2026 story is the gap between a rising score and unchanged — or worse — real-world behavior. This example walks that gap through the skill's Process.\n\n## S1 — Name the map\n\n- **Maps:** (a) static benchmark scores reported in model cards and launch posts; (b) public leaderboards ranking models by aggregate preference or accuracy; (c) the model's internal learned representation of the world.\n- **Made by / when:** benchmarks by academic and industry researchers, mostly frozen at a point in time; leaderboards updated continuously by voters or automated eval harnesses; internal world models fixed at each model's training-data cutoff.\n- **Territory claimed:** \"how capable and reliable this model is for the tasks people will actually use it for.\"\n\n## S2 — Structural omissions\n\nWhat the benchmark/leaderboard maps omit by design:\n\n- **Long, stateful, real tasks.** A single-turn multiple-choice score omits multi-step agentic work, long-context degradation, and tool use — which is where deployed assistants actually spend their time.\n- **Distribution shift after the cutoff.** The internal world model omits everything that happened after training data was frozen; the world keeps moving, the representation does not.\n- **Failure texture.** Aggregate accuracy omits *how* a model fails — confident fabrication (hallucination), refusal, or sycophantic agreement with a wrong premise all vanish into a single percentage.\n- **Contamination.** Public benchmarks can leak into training corpora, so a high score may partly measure memorization of the test rather than the underlying skill it claims to represent.\n\n## S3 — Structural distortions\n\n- **Linearity assumption:** that a higher benchmark number implies proportionally more useful real-world behavior. Deployment is not linear in eval score — a few percentage points on a saturated benchmark can mean little downstream.\n- **Single-number compression:** collapsing a multi-dimensional capability surface (reasoning, calibration, safety, latency, cost, robustness) into one rank.\n- **Hidden assumption of representativeness:** that the benchmark's task distribution matches the user's task distribution. When it does not, the map is precise about the wrong territory.\n- **Leaderboard incentive distortion:** because scores are public and competitive, they become targets — the classic [Goodhart's Law](../goodharts-law/SKILL.md) co"},{"path":"examples/mcnamara-vietnam-kill-ratio-map.md","content":"# Method in Action: McNamara and the Vietnam Kill-Ratio Map\n\n> *Example for the [map-is-not-the-territory](../SKILL.md) skill.*\n\nThe most operationally instructive case of map-territory decoupling in modern history is Robert McNamara's management of the Vietnam War using statistical metrics as the primary navigation system.\n\nMcNamara, U.S. Secretary of Defense 1961–1968, came from the Ford Motor Company where systems analysis and quantitative management had produced measurable results. He applied the same epistemology to the war: define measurable proxies, track them rigorously, use the trends as ground truth for strategic decisions.\n\nThe primary metric: **kill ratio** (enemy killed per U.S. soldier killed) and **body count** (enemy combatants killed). These were the maps McNamara and the Johnson administration used to navigate the territory of the war. The logic was sound as map logic: if the United States was killing far more of the enemy than the enemy was killing of the U.S., the U.S. was winning.\n\nThe kill ratio improved consistently from 1965 to 1968. The map said: progress.\n\nThe territory said: catastrophe. Civilian support for the Saigon government was eroding. North Vietnamese recruitment was accelerating. The Viet Cong infrastructure in the South was strengthening, not weakening. Public opinion in the United States was approaching a breaking point. The 1968 Tet Offensive — a coordinated assault on more than 100 South Vietnamese cities — shattered the map's credibility in a single week.\n\nMcNamara's own retrospective is among the most important primary source documents on map-territory failure in organizational decision-making:\n\n> \"We were wrong, terribly wrong. We owe it to future generations to explain why. We viewed the people and leaders of South Vietnam in terms of our own experience. We saw in them a thirst for — and a determination to fight for — freedom and democracy. We totally misjudged the political forces within the country.\"\n>\n> — McNamara, R. (1995). *In Retrospect: The Tragedy and Lessons of Vietnam.* Times Books. p. xvi.\n\nThe map (kill ratio, body count, area control percentages) omitted:\n\n- **Legitimacy signals.** Whether the South Vietnamese population supported the Saigon government — the single most strategically decisive variable — was not in the map.\n- **Adversary adaptation.** The North Vietnamese adapted to minimize body count by avoiding pitched battles, converting the map metric into a measure of guerrilla discipline rather than strategic failure.\n- **Incentive corruption.** U.S. field commanders, evaluated on kill ratios, had strong incentives to over-report enemy killed and under-report civilian casualties. The map was being optimized (in the Goodhart's Law sense), making it increasingly disconnected from territory.\n- **Time horizon.** The map showed who was winning each engagement. It could not show who would sustain the war longer — which was the decisive question.\n\nThe McNamara case demonstrates three map-te"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle;... Skill: Map Is Not the Territory Owner: deciqai Summary: Activate when: a metric is improving but customers or employees are signaling problems; a strategy or process hasn't been reviewed in over a planning cycle;... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:05:36.886Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/map-is-not-the-territory.json) v1.0.4 | 2026-07-10","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2016,"uniquenessScore":49,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T19:58:02.766Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T19:58:02.766Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-12T07:20:48.517Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}