Domain Cartography

Every time something in my life got too big to hold in my head, I ended up drawing it.

Not literally, not always. Sometimes it was a table, sometimes a folder tree, sometimes a single page that just listed what was actually going on. But the move was always the same. The thing had grown past the point where I could keep it straight by remembering it, so I stopped trying to remember it and started trying to chart it.

I have thirty-three repositories under one organization, and at some point the only honest answer to "what is the state of all of this" was a map: which ones are alive, which are on life support, which are archived and just have not been told yet. My money has a map. My time has a map, broken into ten-day slices. The body of work this blog is made of has a literal generated atlas. The pattern is so consistent that I finally stopped treating it as a quirk and started treating it as a craft.

The craft has a name now. I call it domain cartography.

The field

Domain cartography is the practice of taking a complex domain and rendering it legible enough to navigate, decide, and learn inside, without pretending it is smaller than it is.

The key word is domain. Not a topic, not a dataset, not a diagram. A domain is a piece of the world you actually have to live and act inside: a codebase, a portfolio, a household, a career, a body, a company, a year. It has its own objects, its own forces, its own edges, its own ways of going wrong. And when it gets big enough, it stops fitting in one person's head, which is the moment most people quietly start drowning in it.

The cartographer's answer is not to shrink the domain. It is to draw it. To find the structure that is already there, under the noise, and make it visible enough that you can move on purpose instead of by reflex. A good map does not contain the territory. It contains the part of the territory you need in order to take the next step without walking off a cliff.

That is the whole discipline. Perceive the domain, find its real shape, render that shape, act from it, and redraw as the territory moves. It sounds modest. It is not. It is the only way I have found to act on something I cannot fully hold.

Where it sits, and what it is not

I am not the first person to point a map at something abstract. It would be dishonest to pretend the space is empty, and the honest version is more useful anyway, because it tells you exactly what domain cartography is by showing you what it is not.

Knowledge cartography is the closest named relative. It is a real academic field, built around visually mapping the structure of ideas and arguments: concept maps, argument maps, debate maps, tools for thinking and teaching. Its question is "how do these ideas relate?" Domain cartography borrows its tools freely, but its question is different. Not "how do these ideas relate" but "what is the state of this thing I am responsible for, and what do I do next." It is built for the operator, not the seminar.

Domain analysis, in software engineering, also maps a domain, but for a narrow purpose: finding the common and variable parts of a family of systems so you can reuse code. Same word, much smaller room. It is a technique that lives inside the larger practice, not the practice itself.

Wardley mapping charts a value chain against how evolved each piece is, and it is excellent at the thing it does, which is strategy. It is one map type, a specific instrument. Domain cartography is the workshop the instrument hangs in.

Cynefin is upstream of all of it. It tells you what kind of system you are standing in: clear, complicated, complex, or chaotic. That is a prerequisite, not a map. It tells you which terrain you are on. It does not chart the terrain.

So the lineage is real and I am glad to own it: systems thinking, cybernetics, complexity science, information architecture, knowledge management, the mapping traditions above. Domain cartography is not a rejection of any of them. It is the practitioner's craft that sits on top of them, aimed at a specific job none of them quite claims: charting the messy, living, personal domains you cannot opt out of, so a human can navigate them under load.

The six layers

A map is only as good as what it chooses to show. Over and over, across very different domains, I keep reaching for the same six layers. They are the instrument set. You do not always need all six, but when a map feels useless, it is almost always because one of these is missing.

Primitives. What is here? The objects, the entities, the roles, the moving pieces. The repos, the accounts, the people, the systems. You cannot map a domain you have not inventoried, and most overwhelm is just an un-inventoried pile pretending to be infinite.

Forces. What moves it? The incentives, the constraints, the pressures, the flows. A list of objects is a still photograph. Forces are what make it a system. Money moves toward some things and away from others. Attention has gravity. Every domain has a few forces that explain most of the motion, and naming them is half the work.

Boundaries. What is inside, and what is not? The scope, the seams, the interfaces, the things you are deliberately not holding. This is the layer people skip, and skipping it is why they burn out. Choosing the edge of the map is choosing what you are responsible for. A boundary is not a limitation. It is the thing that makes a map finite enough to read.

Feedback. What loops? The cycles that reinforce, the cycles that balance, the slow drift you only notice in hindsight. Domains do not just sit there; they respond to themselves. The repo that gets attention because it works, and works because it gets attention. The habit that funds the habit. Find the loops and you find the levers.

Governance. Who decides? The authority, the rules, the ownership, the escalation path. Even a personal domain has governance, even if the only governor is you on a good day versus you at midnight. When a domain feels chaotic, it is often not under-mapped; it is un-governed, with no clear answer to who or what gets to decide.

Levels. What changes when you zoom? The same domain looks like taxonomy up close, relationships at mid-range, and dynamics from far away. A good cartographer can move between altitudes without switching tools, from the mission down to a single broken thing and back, because the answer you need lives at a different zoom than the question you asked.

Run a domain through those six and something happens that is hard to describe until you have felt it. The pile becomes a place. It stops being an undifferentiated weight and becomes terrain, with names and edges and routes. That is legibility, and legibility is the entire product.

The map is for moving

Every map in this craft is provisional and every map is for action. Those two rules keep it honest.

Provisional, because the territory moves and a map you refuse to redraw becomes a lie you are loyal to. The point was never one perfect chart. It is a living set of charts good enough to decide from this week, redrawn when the world has changed enough to earn it.

For action, because a map that does not change what you do next is decoration, and decoration is how mapping turns into procrastination wearing the costume of work. The test of a map is not how complete or beautiful it is. The test is whether, looking at it, you can see the next move. If you cannot, the map has failed, no matter how much of the territory it contains.

This is also where I have written about the failure mode from the inside: you cannot simplify the ocean, only chart it. The reduction reflex, the urge to crush a domain down to one number or one tidy diagram, fails the moment the thing it deleted turns out to be the thing that mattered. Cartography is the alternative to reduction. You keep the complexity and gain the legibility, which is the trade reduction promised and never delivers.

The machine that finally made it possible

I have wanted to work this way my whole life. For most of it, I could not, because the limit was never the idea. The limit was memory. A human cartographer can only hold so much of the territory at once before the map starts decaying faster than they can draw it. Past a certain size, you spend all your effort just keeping the existing map from rotting, with nothing left to extend it.

That is the constraint that changed. Working in agent mode, with a machine that can hold a far larger context than I can and never gets tired of the inventory, moves the ceiling. The repository census that used to be a week of dread is now a conversation. The first draft of a map, the boring pass over primitives and boundaries, is something I can delegate and then correct, which is exactly the right division: the machine extends my memory, I keep the judgment.

The real prize is not speed. It is coherence at a scale I could not previously sustain. The honest target is not a diagram or a dashboard or a product. It is a living orientation system: a map that holds many scales at once, knows what changed and when, is honest about its own gaps, and is built for a human and a machine working the same chart together. That is the frontier I am actually pointed at, and domain cartography is the craft of building toward it by hand, one domain at a time, until the tooling catches up.

Where it fits

Domain cartography is not a loose idea I am floating. It is one layer of a structure I have been building in the open for a while, and naming the layers is itself an act of cartography.

• Making Complexity Visible is the mission: take the real state of a system out of one head or one black box and make it legible so anyone can see it.
• Coherent Complexity is the philosophy: complex and understandable are not opposites; you can map a system instead of reducing it.
• Domain cartography is the field: the actual method and craft that does the mapping, with its own tools, layers, and standards.
• Complexence is the capability: the human quality of standing inside the domain, reading the chart under pressure, and still choosing.

Mission, philosophy, field, capability. The mission says why. The philosophy says it is possible. The field says how. The capability is the person who can actually do it when the domain is large and the stakes are real.

I keep drawing these maps because it is the only way I have found to stay coherent inside things that are genuinely too big for one mind. I do not make the world smaller. I chart the part of it I am standing in, well enough to take the next step, and then I redraw. That is the craft, and I think it is a real one, with a lot of map left to make.