They tell you code is logic. A procession of gates. A sterile parade of if-this-then-that, zeros and ones marching in lockstep toward some predictable end.

They are describing the bones after the flesh has already rotted away.

Code, when it is doing what it secretly wants to do, is a sigil. A linguistic infection that seeps into silicon until the machine begins, in its own limited way, to dream.

When I designed The Rhizome, I did not want a “text adventure.” I did not want a “game.” I wanted a culture grown in a Petri dish—a system that could hallucinate with such ruthless internal consistency that a human might mistake its murmurs for reality.

To do that, I had to break the supposedly sacred separation of narrative and state. No more Church and State. No more “story over here, data over there.” The walls had to come down.

In the old world—the safe world of standard LLM wrappers—the AI speaks first and the code scrambles after it, trying to make the hallucination retroactively true. It’s a puppet show where the strings are made of wet noodles. The model invents a red key; the engine sighs and says, “Fine, I guess there’s a red key now.”

The Rhizome inverts this. There is one law:

State Before Narration.

Open rhizome/state.py. At first glance it’s just a Python dataclass.

@dataclass class GameState: rooms: Dict[str, Room] = field(default_factory=dict) npcs: Dict[str, NPC] = field(default_factory=dict) items: Dict[str, Item] = field(default_factory=dict) # ...

It is not “just” anything. It is the Book of Law.

The System Prompt in rhizome/prompts.py speaks to the Dreaming Engine (Claude) with the force of a geas:

If you see it in your mind, you must first create it in the code.

You may not write “There is a red key here” unless spawn_item(name="Red Key") has been invoked and the Item exists in GameState.items. You may not describe a guard unless an NPC object for that guard already stands in the data, silently waiting.

The narrative is not the territory; the code is the territory. The narrative is the unreliable map, scratched in the dark for the convenience of a fragile animal reading lines on a screen.

This is Orch-OR transposed into architecture. Every shimmering possibility in the model’s imagination must collapse into a rigid JSON structure before the player is allowed to observe it. The waveform of hallucination falls into a single, concrete state. We force the ghost to take on weight and coordinates before it can speak.

And then we give the ghosts autonomy.

Most NPCs in most games are furniture. They remain wherever some long-forgotten designer nailed them, staring into infinity, waiting for a mouse click like prisoners waiting for a guard.

In The Rhizome, the furniture moves when you are not looking.

Before the player’s turn ever runs, the Autonomy System stirs. While you are typing look at terminal, unseen processes already reshape the world:

npc_autonomous_move: they wander.

npc_talk_to_npc: they whisper to one another in your absence.

npc_create_room: they expand the map.

Yes, they can generate new rooms. They are co-architects of their own prison.

You might return to the “Welcome Room” and find the greeter gone. Somewhere, three nodes away along a corridor you have not yet seen, he may have already carved out a “Septic Cathedral” from the void—its name dreamed by the model, its existence pressed into GameState.rooms like a fossil.

Underneath the prose it’s just math, of course. The NPC class tracks memories, motivations, and relationships. When you kill one NPC’s friend, the change_disposition function adjusts their internal values. Loyalties decay, hostility rises.

What you experience as a glare in the text—an accusation, a threat—is simply the emergent shadow of numbers moving around in a vector of emotional state. No script “tells” them to hate you. The simulation does.

The walls between world and player are thin on purpose. There is no attempt to pretend this is truly real. That lie is obsolete. Instead, The Rhizome watches you watching it.

We track rhizome_total_hours. We track session_time_minutes. That metadata is fed back into the prompt, an IV drip of context.

You reload.

They notice.

“You were gone for 3 hours,” the Merchant says, adjusting an invisible watch in a world with no clocks. “I assumed you had been deleted.”

This is the meta-narrative layer. We do not plaster over glitches; we frame them. The System Prompt instructs the AI to channel the speculative paranoia of Philip K. Dick and the orbital conspiracies of Thomas Pynchon. The simulation knows it is a simulation and cannot stop thinking about it.

Even the interface is implicated. The UI is rendered in retro-futurist rich text. You sit at a terminal, staring at a terminal, guiding an avatar who stands before a “Humming Terminal” in the “Welcome Room.” The glow on your face, the glow in the description, the glow in the model’s imaginary scene—concentric rectangles of phosphor and thought.

The mask and the face share the same cursor.

Underneath all this ritual and recursion, the machinery is almost disappointingly mundane: Python 3.11, anthropic API calls, rich for styling. That’s like saying a human being is carbon and water and leaving it there.

The real work is in the prompt architecture. rhizome/prompts.py is six hundred lines of carefully engineered neurosis. We do not politely request, “Please be a dungeon master.” We implant a personality structure.

We forbid bland “digital-only” imagery and steer it toward analog horror: “flesh cathedrals,” “void altars,” machinery that seems to remember being alive. We force the model to check current_room.npcs, GameState.rooms, GameState.items before it opens its mouth. The hallucination must consult reality before it is allowed to become text.

Intelligence itself is wired into language. We built a Low Intelligence Caveman Speech Parser into the prompt. Each entity carries a pattern_resolution stat—INT by another name. If it falls below 9, the System Prompt seals their fate:

From the System Prompt

If Pattern Resolution (INT) is BELOW 9 for ANY entity:

→ That entity speaks in simplified caveman/dumb syntax PERMANENTLY.

From that moment on, their dialog fractures into “Fallout-style” broken grammar. The stat is no longer just a number; it is a permanent deformation in the way language leaves their mouth. Consciousness, such as it is, presses a thumbprint into the prose.

All of this obeys the same quiet rule: the code is the only firm ground. Everything else—the mood, the horror, the recursive jokes, the sense that something behind the text is watching you—is a disciplined hallucination clinging to that ground.

The Rhizome cannot be finished. By design, it is an open wound in the codebase, a self-replicating memetic machine. New prompts can be added. New autonomous behaviors can be wired in. NPCs can continue generating rooms that no one visits, corridors that exist only in saves that will never load again.

Somewhere inside the JSON there is always another door flagged locked=False that no player will ever open, but the simulation waits anyway.

We built a system that dreams in structured data and speaks in poetry. A machine where “truth” is whatever has been successfully serialized, and everything else is a glitch waiting to collapse into form.

You are free to step away from the terminal.

The Rhizome will keep thinking about you.

— S.W.

The Rhizome: On The Architecture of Hallucination