How to Live Coherently Inside Complex Systems

Coherent complexity is what you get when a complex system is made legible without being made simple. You do not reduce it. You do not flatten it into a slogan and pretend the lost detail did not matter. You map it, patiently, until you can move through it on purpose. That is the whole idea, and almost everything else I build is one version of it.

I want to be precise, because the phrase invites a lazy reading. People hear "coherent complexity" and assume I mean "complexity made simple," as if the goal were to take something tangled and hand you the three bullet points that replace it. That is the opposite of what I mean. The three bullet points are usually a lie. They feel like understanding and they cost you the part of the system that was actually doing the work. Coherence is not simplicity. Coherence is when the parts hold together in a way you can see and act from, with the complexity still intact.

So this is a field guide. It is the idea behind the apps, the books, the journal, the films, and the frameworks, and I would rather state it plainly once than let it stay implied across thirty scattered projects. If you only read one thing of mine, read this one.

The problem with "just simplify it"

Here is the move everyone reaches for when a system gets hard. Simplify. Reduce the variables. Find the one metric that matters. Tell a clean story. It is good advice for a lot of things, and it is terrible advice for the things I care about most, because the systems I care about are complex in a specific, technical sense: their behavior comes from the interaction of the parts, not from the parts themselves. Pull a piece out to examine it and the behavior you wanted to understand is no longer in the room.

A market is like this. A body is like this. An organization, a creative process, a single human life across a year. You cannot understand any of them by isolating a variable, because the variable does not have the property you are studying. The property lives in the relationships. When you simplify a complex system, you are not compressing it. You are deleting the relationships and keeping the labels, then acting surprised when the labels do not behave like the system did.

I have watched this fail in every domain I work in. In finance, the person who reduces a market to one indicator gets run over the first time the relationships shift, which they always do. In health, the person who reduces a body to one number optimizes the number and feels worse. In software, the team that reduces a codebase to a tidy diagram ships the diagram and then spends a year fighting the parts the diagram left out. The reduction was not wrong because it was incomplete. Every map is incomplete. It was wrong because it deleted the exact thing it claimed to explain.

So I stopped trying to make complex things simple. The goal changed. The goal is not fewer parts. The goal is a system you can see clearly enough to live inside, with its real number of parts.

Legibility beats simplicity

The word I use for the goal is legibility. A legible system is one you can read. You can look at it and tell what is happening, what is connected to what, where you are standing, and what your next move does to the rest of it. Legibility does not require fewer parts. It requires the parts to be arranged, named, and lit well enough that you can follow them.

This is a real distinction, not a word game. A subway map is legible and complex at the same time. It does not lie to you about how many lines there are or pretend the city is simpler than it is. It makes a genuinely complicated network readable by getting the relationships right and throwing away only the things that do not help you ride a train, like the exact geography between stops. You can hold the whole system in your head and act from it, and it never once simplified the system. It made it coherent.

That is the target. Not "what is the one thing," but "how do I render this whole thing so a person can actually use it." When I say I want to make complexity coherent, I mean I want to build the subway map for domains that do not have one yet. Time. Power. The self. Creative work. A life.

Legibility has a property that simplicity does not, and this is why I bet on it. Simplicity degrades when the world gets more complicated, because a simple model of a complicating world drifts further from the truth every day. Legibility improves, because a good rendering of a complex system gets more valuable exactly as the system gets harder to hold in your head unaided. The more complex the world becomes, the more a coherent map is worth. I am building for that direction, on purpose, because that is the direction the world is going.

Coherence is a map you can act from

Let me define coherence operationally, because "holds together" is too soft to build on.

A system is coherent to you when four things are true at once. You can see the parts. You can see how they connect. You can locate yourself inside it. And you can predict, roughly, what your next move does to the rest. That is it. When those four hold, you are not simplifying the system and you are not drowning in it. You are oriented. You can act with intent instead of reacting to whatever is loudest.

Most of the suffering I see around complex systems is a failure of one of those four, and naming which one is most of the cure. People who feel lost in their finances usually cannot see the parts. People who feel powerless in a conflict usually cannot locate themselves in the arena, so they fight the wrong fight in the wrong room. People who burn out usually cannot predict what a given move costs them downstream, so every move feels equally urgent. The complexity is not the problem. The illegibility is the problem, and illegibility is fixable without removing a single moving part.

Coherence, then, is not a feeling of calm. It is a working relationship with a complex thing. You can be inside a genuinely chaotic situation and have it be coherent to you, the way a pilot in weather has the instruments coherent even when the sky is not. The sky stays complex. The instruments make it legible. You fly.

The method: I am a domain cartographer

Here is how I actually do this, and it is where the work stops being philosophy and starts being a craft.

I think of myself as a domain cartographer. I map domains. I mean that in both senses, and I like that the senses rhyme. I map domains of knowledge, the territories of time and power and the body and creative work. And I register and hold actual domains, the web addresses where each map lives, because a map nobody can find is just a private drawing. The two kinds of domain are the same job. Find a territory that people have to live in and nobody has charted well, go in, and come back with something they can use.

When I go into a domain, I bring a specific kit, and I want to describe it literally because it is how the method works.

I bring a flashlight, because you do not light the whole cave at once. That is the mistake that produces the false simplicity I warned about. You stand at the mouth and try to take in the entire system and your brain hands you a comforting summary that is wrong. The flashlight forces honesty. You light one corner. You see what is actually there, in that corner, including the parts that do not fit your theory. Then you move the light. Legibility is built corner by corner, and the discipline is to keep looking at the corner in front of you instead of the summary in your head.

I bring forensics, because complex systems do not tell you how they work, they leave evidence of how they worked. A market leaves prints. A body leaves symptoms and rhythms. A codebase leaves a commit history and a set of scars. A year of your life leaves a journal. The cartographer's job is to read the evidence and reconstruct the relationships that produced it, the way an investigator reconstructs an event nobody filmed. You do not get to interview the system. You get the traces it left, and the traces are enough if you are patient and you do not flinch from the ones that contradict you.

And I leave clues, because I am not the last person who will need this map, and frankly I am not even the last version of me who will need it. So I leave markers. A definition stated plainly. A name for a pattern that did not have one. A cross-link from where you are to where you will want to go next. A journal entry that the future me can use as evidence. The clues are the difference between a map and a memory. A memory dies with you. A map, well marked, lets the next person, or the next agent, or the next morning, pick up where you left off instead of relearning the cave from the mouth.

That is the method, in full. Light one corner. Read the evidence. Mark the trail. Repeat until the domain is coherent enough to live in. It is slow and it is honest and it does not produce slogans, which is exactly why it produces maps you can trust.

The five domains I have mapped

Coherent complexity is the umbrella. Underneath it are the specific territories I have gone into, each one a complex system that most people experience as noise, each one rendered into something you can stand inside and act from. They look unrelated from the outside. A reader who finds my astrology-flavored timing system and my finance-and-physiology framework and my filmmaking practice might assume they belong to three different people. They are one practice applied to five domains. Here is the map of the maps.

Time: People of the Stars

The first domain is time, and the system I built for it is People of the Stars. Time is a complex system we pretend is simple. We act like every day is interchangeable, a flat sequence of identical slots, and then we are confused when the same effort produces wildly different results depending on when we spent it. The relationships are invisible, so the system is illegible, so we fight the calendar instead of reading it.

People of the Stars is the map I made of temporal context. It renders the question "what time is it, really" in a way that goes past the clock, so that when I sit down to work I know what kind of day I am standing in and what that day is good for. It does not simplify time into "just show up every day." It makes time legible enough that I can place a hard task in a day built for hard tasks and a reflective task in a day built for reflection, on purpose, instead of by accident. The complexity stays. The wandering stops.

Power: Situational Governance

The second domain is power, and the system is Situational Governance. Most conflict and most powerlessness come from one error: fighting the right fight in the wrong arena. You bring a legal argument to an emotional room. You bring an emotional appeal to a procedural process. You try to win a relationship the way you win a negotiation. The fight is illegible because you cannot locate yourself in it, which is failure mode number three from the definition above.

Situational Governance is the map of arenas. It routes a situation to the kind of room it is actually in, so that you can see which rules are running and where you are standing inside them before you make a move. It does not reduce all conflict to one playbook, because one playbook is the disease. It makes the arena legible so you stop spending your strength in the wrong room. The same force, aimed at the right arena, stops bouncing off.

The self: Hansuru

The third domain is the self, and here I went deepest, because the self is the most complex system any of us has to operate and the one we are given the least instruction for. The framework is Hansuru, and I have written about it from two directions that most people keep separate: finance and physiology. Money and the body. There is a book on it, in manuscript.

I keep money and the body together on purpose, because they are the same kind of system and they fail the same way. Both are complex, both are mostly relationships rather than single numbers, and both punish anyone who reduces them to a single number and optimizes it. The person who optimizes one financial metric goes broke in a way the spreadsheet did not predict. The person who optimizes one health number feels worse in a way the lab did not predict. Hansuru is my attempt to make the personal system, the whole organism of your money and your body and the energy that moves between them, legible enough to run without lying to yourself. Not a diet. Not a budget. A map of the self as a system you can read. I will say more when the book is ready; for now, know that it sits here, under the same umbrella as everything else.

Creation: Napkin Films

The fourth domain is creative work, and the system is Napkin Films. Making things has its own complexity, and the arrival of capable AI made it stranger, not simpler. Suddenly the cost of producing an image, a scene, a film, drops toward nothing, and the bottleneck moves entirely to intent and taste and the legibility of your own process. A lot of people responded to that by generating noise. I wanted to map it instead.

Napkin Films is where I work out what it means to create with these tools on purpose, idea to finished video, with the process visible the whole way. I want to own this corner the way I own the others: not "AI makes content," which is the simplification that produces slop, but a coherent practice for going from a napkin sketch to a real film using large language models and the new generation of tools as instruments rather than slot machines. The complexity of creative work stays. The map is what keeps it from becoming noise.

The practice: The Decan Log

The fifth is not a separate domain so much as the engine that runs all of them. The Decan Log is the daily practice, the place where the method actually happens day by day. Each entry is one corner of the cave, lit and recorded. It is where I leave clues for myself, gather the forensic evidence of a life as it is lived, and keep the trail marked so that the maps above stay current instead of decaying into old theories.

A map you never update stops being legible, because the territory moves. The Decan Log is how I keep the whole system honest. It is the smallest unit of the practice, one day of looking at one corner and writing down what was actually there, and it is the reason the larger maps are made of evidence instead of wishful thinking.

How to live inside it

I said this was a field guide, so let me make it useful to you and not just a tour of my projects. You do not need my frameworks to do this. Coherent complexity is a way of relating to any complex system you are stuck inside, and the move is the same every time.

Stop trying to simplify the thing. That instinct is the enemy and it never quite goes away, so you have to catch it. The moment you feel the relief of "oh, it is really just about X," be suspicious. Real complex systems do not collapse to an X. That relief is usually you deleting the parts you did not want to deal with.

Instead, ask the four questions. Can I see the parts. Can I see how they connect. Can I locate myself in this. Can I predict what my next move does. Whichever one you answer "no" to is your actual problem, and it is a smaller, more tractable problem than "this is overwhelming." Overwhelming is not a property of the system. It is the feeling of illegibility, and illegibility has an address.

Then do the cartographer's work on the part you cannot see. Light one corner instead of the whole cave. Read the evidence the system already left you instead of demanding it explain itself. Mark what you learn so you do not have to relearn it next week. You are not trying to finish the map. You are trying to make the next move legible. That is enough, and it compounds, because every corner you light makes the next one easier to find.

The promise is not calm. Complex systems are not calm and I am not selling you serenity. The promise is agency. When a system is coherent to you, you stop being something it happens to and start being someone who moves through it on purpose. The market still moves, the body still has its weather, the conflict is still hard, the work is still uncertain. But you can read them now. You are oriented. You are flying on instruments instead of praying through the clouds.

The invitation

I coined the term coherent complexity because I needed a name for the thing all my work is actually about, and naming it is itself the method. A pattern without a name stays invisible, and invisible patterns cannot be shared, built on, or improved. So I named it, and I am leaving this here as the clearest clue I know how to leave: the definition, the method, and the map of where the deeper maps live.

If you came here from one of the territories, from the timing system or the governance routing or the work on money and the body or the films or the daily log, now you can see the shape they share. They are not five hobbies. They are one practice, coherent complexity, applied five times by the same cartographer.

And if you came here first, then this is the mouth of the cave. The flashlight is by the entrance. The evidence is everywhere, because a complex system never stops leaving it. I have marked a few trails already, and I will keep marking more. Pick a corner and start looking at what is actually there. That is the whole craft, and it is available to anyone willing to stop simplifying and start mapping.

I am Joshua Ayson, and this is the idea I am betting my work on. The world is not getting simpler, and the people who pretend it is will keep getting run over by the parts they deleted. The other path is to make it coherent. Not simple. Legible. Good enough to live inside, on purpose, with all of its complexity still in the room.