DEVLOG #5 — WHAT YOU CANNOT DO

The EQUILIBRIUM terminal accepts anything you type.

That doesn't mean your government can do it.

This is the distinction we spent the longest working on, and it's what separates a government simulator from an engine that executes orders. A head of government isn't an administrator with root access: they're a person seated inside a system of constraints — constitutional, judicial, international — that the system doesn't let them bypass by writing the right sentence.

THE REASONED REFUSAL

When you submit a command your government cannot carry out, EQUILIBRIUM doesn't answer with an error.

It explains why it can't, and proposes what it can do instead.

Try dismissing an official who doesn't report to you. The game doesn't pretend to obey, and it doesn't leave you facing a wall: it tells you which power you lack, and puts in front of you the roads that remain open — slower, more expensive, or politically more exposed, but passable.

It's a deliberate design choice. A flat refusal teaches the player to stop trying. A reasoned refusal teaches them how the power in their hands actually works.

AND THEN THERE ARE THE TREATIES

The hardest layer to simulate isn't the constitutional one. It's the international one.

A nation inside the European Union has ceded pieces of sovereignty it cannot take back with a decree. On state aid. On the free movement of goods. On budget parameters. These are constraints that don't live in your constitution: they live in agreements signed by previous governments, which you inherit the day you take office.

In the game this produces a category of commands unlike the others. These aren't actions you can't afford — they're actions that are no longer yours to take.

Rescuing a struggling national company with public money is an obvious political decision, and it's exactly the kind of decision a treaty holds you accountable for. Closing a trade border to protect a sector is a governing instinct as old as the State, and it's precisely what the single market rules out.

The game doesn't stop you from wanting it. It shows you the constraint, tells you where it comes from, and leaves you the choice a government really has: respect it and pay in effectiveness, or force it and pay another way — later, and with interest.

WHY WE CHOSE THIS

It would have been far simpler to build a game that executes.

Type "nationalize," the game nationalizes. Type "close the borders," the game closes the borders. It's a design that works, takes a fraction of the time to program, and delivers a clean power fantasy.

But that isn't governing. Governing is discovering every day how many of the things you'd like to do don't depend on you, and learning to get results inside that narrow space.

The surprise, on your first playthrough, isn't what the game allows. It's what it doesn't allow, and the way it explains that to you.

IN SHORT

— Commands the government cannot execute: a reasoned refusal, never a flat error

— Workable alternatives offered alongside the refusal

— Constraints distinct by nature: fiscal, constitutional, international

— Treaties as a real limit on executive power, not background text

EQUILIBRIUM launches into Early Access on September 10, 2026. If the project interests you, adding it to your wishlist is the most concrete way to help — it helps me get it in front of more people.

The next devlog arrives next week.

— Andrea, Obliquon Corporation