We Had to Decide What Dominus Was Before We Could Build It

The first question behind Dominus was not about code.

It was not about maps, artificial intelligence, military systems, economics, or even countries.

It was much simpler: are we making a game, or are we making a simulation?

At first, that might sound like a distinction without much difference. A lot of games simulate something. Cities, wars, sports, business, politics—there are entire genres built around turning real-world systems into things a player can control.

But the more I thought about Dominus, the more important the difference became.

A traditional game is usually built around the player. The world waits for you. It gives you a set of actions, rewards you for using them well, and creates challenges designed to keep the experience moving. Even when the world appears huge, the player is still the center of gravity. The economy exists to support the player. The war exists to challenge the player. The other countries exist to give the player something to react to.

That was not what I wanted.

I wanted a world that could exist without the player.

I wanted countries to make decisions while nobody was watching. I wanted economies to grow, stumble, borrow, recover, and occasionally break because of the pressures inside them—not because a mission designer decided it was time for a crisis. I wanted leaders to pursue their own goals. I wanted history to keep unfolding whether a person logged in that day or not.

That is a simulation.

And simulations can be incredibly compelling in theory. They can also be painfully boring to experience.

A simulation can be technically brilliant and still feel like watching a spreadsheet recalculate. It can contain thousands of interconnected rules, deeply realistic data, and years of careful research—and still leave a person wondering why they should care. A number rises. Another number falls. A country’s GDP changes. A supply chain weakens. Somewhere beneath all of that, there may be an incredible story. But if nobody can see it, feel it, or understand why it matters, it may as well not be there.

That was the tension at the beginning of Dominus.

I wanted the honesty of a simulation, but I am a visual person. I did not want to build a world that only existed in logs, dashboards, and charts. I wanted to watch the world breathe. I wanted to see an event appear on the map and understand that something had changed. I wanted a player to open the world and feel like they had arrived somewhere—not like they had opened a business application.

So the answer was not to choose one side.

Dominus would be both.

It would be a living simulation at its core, with systems that continue to run, react, and remember. But it would also be a visual strategy experience: a place to watch history unfold, explore the world, sit in a seat of power, and make decisions that matter.

Not a game in the traditional sense. There would not be a simple win screen waiting at the end. There would not be a neat campaign designed around one hero’s inevitable rise.

Instead, the world itself would be the thing worth watching.

A country might prosper. Another might overextend itself. A government could make a choice that looks smart in the short term and becomes disastrous years later. A war might begin because diplomacy, resources, politics, fear, and bad judgment finally collide. The person watching would not just see an alert saying “conflict started.” They would see the world react around it.

That is where the visual side of Dominus became more than decoration.

The map is not there simply because maps look good. It is there because geography makes consequences understandable. When a trade route is disrupted, it means something different when you can see where it runs. When a military crisis grows along a border, distance matters. When a country suffers a disaster, the scale of it matters. When a political decision changes the lives of people in one region but not another, that difference should have a place in the world.

The visual layer gives the simulation a body.

Without it, Dominus would be a machine producing outcomes. With it, the outcomes can become stories.

That realization changed how we thought about every system afterward. We could not build visuals that invented reality just because they were dramatic. If an event appeared on the map, it needed to come from something that had actually happened in the authoritative world. If the interface showed a country in trouble, the player needed to be able to discover why. If a leader gave advice, that advice needed to be based on the information available to that leader—not on hidden knowledge pulled from somewhere behind the curtain.

The screen could make the world easier to understand. It could not be allowed to become a second version of the world.

That rule sounds technical, but it is really about trust.

A person can forgive a simulation for being complicated. They can forgive it for being difficult. They might even forgive it for surprising them. But they will eventually stop believing in it if the rules feel arbitrary. If an economy collapses and there is no explanation, it feels scripted. If a war begins and no one can trace the pressure that caused it, it feels fake. If a dashboard says a country is strong while the underlying systems tell a different story, the illusion breaks.

Dominus needed to be able to account for itself.

That is why the earliest work was mostly invisible. Before there was a polished Earth, we focused on how time passes, how decisions enter the system, how resources move, how events are recorded, and how a result can be replayed and investigated later. We wanted every major change to leave a trail.

If a country spends money, the money has to come from somewhere. If a factory produces something, it needs the inputs to do it. If a government makes a decision, it should create consequences that other systems can react to. If something changes, there should be a reason.

That became the core law of Dominus: every action has a reaction.

It is easy to say. It is much harder to build around.

The rule meant we could not treat features as isolated toys. We could not add a military system that ignored the economy, or an economic system that ignored people, or a visual effect that appeared without a real event beneath it. Every new piece had to become part of the same living world.

That was also important because Dominus was never meant to stop at countries. The early vision already included governments that could be led by people, scripted actors, or AI. It included seats of power that a player could occupy. It included a future in which the world would have individual characters living inside it: people with jobs, families, beliefs, ambitions, and opportunities shaped by the country around them.

That eventually became Joe.

But Joe only makes sense if the larger world is real enough to reach down into a person’s life. A national employment crisis should someday be able to become a missed paycheck. A change in education policy should be able to become an opportunity. A war should not just move an icon on a map; it should affect the people who live near it, work because of it, flee from it, or rise to power through it.

That is the long-term ambition.

Dominus is not trying to recreate every detail of real life. It is trying to create a world where the major systems of life can touch one another in believable ways. Politics should affect the economy. The economy should affect industry. Industry should affect military power. Military pressure should affect society. Society should eventually affect individual lives.

And all of it should be visible enough to matter.

So before we built the world, we had to decide what kind of thing it was.

It would not be only a game, because the world could not revolve around the player.

It would not be only a simulation, because a world nobody can feel is just a machine running in the dark.

Dominus would be a living simulation with the presence, clarity, and visual drama of a strategy experience.

The world would keep moving.

And for the first time, people would be able to watch it move.