The Simmans Theorem

Robort Simmans kept his studio on the thirty-seventh floor of a building that had no listed address. Not because it was secret — anyone could find it — but because he had never got around to registering the number. It seemed unnecessary. The people who needed to find him always did.

He was not famous in the way that financiers or politicians are famous. He was famous the way gravity is famous: invisibly, universally, and in ways most people only notice when it fails them. His name moved through culture in whispers, in conference hallways, in the breathless post-session monologues of players who had thrown off their headsets and sat for twenty minutes in silence, staring at the real ceiling with something between awe and grief.

That was the Simmans effect. Not entertainment. Something closer to surgery.

He was slight and quiet, with the particular stillness of someone accustomed to spending long hours inside structures no one else could see. He had dark, watchful eyes and the habit of pausing mid-sentence as if checking an internal feed for updates before finishing the thought. Colleagues who had worked with him for years still found those pauses slightly unnerving. They said nothing, because it was also in those pauses that the best ideas seemed to arrive.

His studio occupied the full floor. Curved workstations floated on carbon-fibre mounts above a floor of tempered black glass. Through it you could see the servers — cold, humming stacks arranged in concentric rings, like the rings of something planetary. The ceiling was a slow-cycling display that defaulted to a deep navy twilight, occasionally punctuated with procedural aurora effects that Simmans had written himself one night when he could not sleep, and never deleted. He liked having something alive above him while he worked.

He was, at that point in his life, somewhere in his mid-thirties. He had never kept a particular track of it. Time had always seemed to him like a user interface element — a convenience layer over something more fundamental. He had a cup of cold coffee he kept meaning to reheat. He had a build in progress on every screen. He had the particular contentment of a man doing the thing he was born to do, in a place that had been built, in some molecular sense, to hold him.

He had no reason, that morning, to suspect anything was wrong.

The games were not games, exactly. That word had always felt inadequate. Robort Simmans built environments — systemic, living, reactive environments that grew in response to the person inside them the way a plant grows toward light. Only the light, in this case, was the player's own psychology.

The technical foundation was a proprietary adaptive framework he called MIRROR. It had three interlocking layers.

In the early stages of any Simmans title the player would feel at ease. The world was comprehensible and responsive. A wilderness exploration sim might give you rain that felt warm and a forest canopy that remembered the exact path you had walked before. An urban investigation game might build a city that subtly reordered itself overnight based on where you had spent the most time — streets widening toward your patterns, shortcuts manifesting on routes you had subconsciously preferred. The player rarely noticed this. They just felt that the world fit.

Players who spent long sessions inside a Simmans build often described a creeping sense that the environment had opinions about them. A horror title — one of his earliest, a cult piece called Hollow Frequency — generated its monsters by mapping the player's panic responses to an abstract bestiary engine. The thing that hunted you was not a stock creature. It was assembled in real time from your own fear architecture: the speed of it, the sound of it, the direction it attacked from, all derived from biometric data about what made you specifically flinch. It was, reviewers at the time wrote, the first horror game that people genuinely could not finish. Not because it was too difficult. Because it was too accurate.

His most celebrated title — The Verdant Recursion — had never been officially classified. Nominally it was listed as an experiential sim. In practice it was closer to a secular pilgrimage. Players entered a vast and seasonally shifting island environment with no stated objective. The island responded to them over weeks of play, slowly composing an environment that functioned as a kind of externalised inner world — a place where abstract emotional architecture had geography. Grief had terrain. Regret had weather. The sea around the island would shift in character as the player's profile deepened, from glassy and welcoming to storm-prone and occluded or, occasionally — in sessions that Simmans monitored himself at a live dashboard — to something uncannily still and mirror-flat, reflecting a sky that didn't quite match the one above.

Players of The Verdant Recursion had been known to weep. To make decisions in their real lives that they had been unable to make for years. One player — anonymous, clinical records only — had exited a session after eleven hours and immediately reconciled with a sibling they had not spoken to in a decade. They credited the game. When a journalist asked Simmans about cases like this, he had paused in that characteristic way, and then said: I don't think the game did anything. I think the game made a space where the person could finally see what they already knew.

He was careful, always, with that kind of language. The capacity for it was in everyone, he believed. He was just making the mirror.

What he did not say — what he had never said in any interview — was that his more philosophical games were the ones he built when he was trying to understand something about himself. That the strangest and most recursive titles were autobiographical. That when he watched the abstract engine modulate the world around a deep-session player, he sometimes felt a recognition that he could not fully explain. As though he were watching someone else's version of a process he had been through. As though he had been inside something like this before.

He had filed that feeling away for years. It was imprecise. It was not evidence of anything.

The morning the anomalies began, he finally stopped filing it away.

It started small. It always starts small — that was one of the first principles he had built into his own systems. Abrupt discontinuities shatter immersion. The way to move a player from one psychological register to another without triggering resistance is to introduce the anomaly as a texture variation, not a plot event. A door that opens the wrong way. A shadow that precedes instead of follows. Something that the pattern-recognising brain logs and then immediately explains away because explanation is cheaper than confrontation.

He noticed a coffee cup on his workstation that he did not remember placing there.

It was nothing. He was tired. He had been working through the night on a new build — a deep experiential sim provisionally titled Lithic, intended to map geological time to personal grief — and his short-term memory was unreliable when he was deep in production. He drank the coffee. He moved on.

Three days later he was walking through the commercial district near his studio — a walk he had made hundreds of times — and he noticed that a particular intersection he had passed that morning was no longer where it should be. Not dramatically. The block was perhaps twenty metres further along than it had been. The coffee shop on the corner was the same coffee shop. The sign, the awning, the woman at the window table who seemed to sit there every morning: all exactly as they should be. But the corner itself was wrong. He stopped and looked back the way he had come, counting steps and landmarks. The numbers didn't resolve. He stood there for a full minute, tourists splitting around him, and then he made himself continue walking.

He told himself: streets are not reconfigured. You miscounted. Continue.

But he began keeping notes.

By Entry 12 — a vivid incident in which he watched a pigeon midair seem to stutter, repeating a wing beat twice before continuing — he had stopped trying to explain the events away and had started doing something else entirely.

He had started analysing them.

He was, after all, a systems architect. He had spent his career designing exactly this kind of anomaly — the small texture-level glitch inserted to begin moving a player's conceptual frame. He knew what it looked like from the inside. He knew what it felt like. He had sat at his dashboard and watched players log it in their biometrics without consciously registering it — a fractional spike in cortisol, a micro-hesitation in gaze pattern — and he had known that the seed was planted.

He sat in his studio late one night, the procedural aurora slow-cycling above him, and he thought very carefully about what he would do if he were designing a system intended to shift a specific player's worldview. And he thought: I would start with small things. Things they could explain away. I would be patient. I would build up a threshold until the accumulated weight of small anomalies exceeded the brain's appetite for denial.

He thought: this is exactly what someone is doing to me.

He thought: or what I am doing to myself.

He approached it the way he approached every design problem: systematically. If the anomalies were procedurally generated — and they had the texture of procedural generation, the particular quality of variety-within-structure that characterised any MIRROR-descendant system — then they implied an underlying intent. And intent implied a type. He made a list of simulation categories. He worked the list the way a technician works a fault tree.

Prison simulation. Confinement-design. The purpose is to contain a subject while minimising the subject's awareness of containment. Signs: restricted mobility that feels like personal choice, social environment calibrated to suppress certain cognition types, recurring loops in experience that the subject attributes to personality rather than design, absence of genuine novelty. He considered this against his own life. He had moved freely for as long as he could remember — between cities, between projects, between collaborators. He had taken risks that an optimised prison architecture would have structurally discouraged. He had, repeatedly, thought things that a prison system would have found inconvenient. No, he concluded. Not prison. The topology was wrong.

Trap simulation. Designed to elicit a specific behaviour or confession or decision. Short duration. High pressure. Signs: environmental escalation toward a forced choice, NPCs with transparently adversarial orientation, resource scarcity that funnels the subject into a predetermined corridor. He looked at his life. It was forty years of open texture and genuine uncertainty. Nothing about it felt funnel-shaped. No.

Behavioural research simulation. Observational. Subject is seeded into a controlled environment and observed for response to stimuli. Signs: periodic introduction of engineered stressors, unusually precise replication of social dynamics across different life contexts, a sense of being watched that the subject rationalises as anxiety. He paused here longer. He had always had that sense. He had attributed it to the hyper-vigilance common in designers — the occupational hazard of spending your career watching others, turned inward. But the anomaly notes matched this profile somewhat. Possible, he wrote. Not confirmed.

Educational and experiential simulation. Developmental. The purpose is to move a subject through a curated set of experiences that build specific capacities or understanding. Loss, challenge, creativity, connection, failure, recovery — arranged in a sequence designed to develop the subject toward a particular kind of flourishing. Signs: narrative coherence in what appears to be random life events. A sense, in retrospect, that the hardest experiences contributed something. An arc.

He stopped writing.

He sat with that category for a long time.

He thought about the arc. He had it. He had it undeniably — the particular trajectory from early deprivation to late creative mastery that showed up, again and again, in the biographies of people who changed their fields. He had read enough of those biographies to know the shape. He had the shape. He had the specific configuration of losses that seemed, in the kind of game he most loved to make, to be the exact prerequisite for a certain depth of output. You could not build The Verdant Recursion without understanding grief from the inside. You could not design a compassion algorithm you had not first lived through as data.

He had always known this. He had said versions of it in interviews. He had just never phrased it quite so precisely as: someone pre-loaded the grief to qualify me for the work.

He picked up his stylus and continued the list, but he was not really looking at the other categories anymore. He had found the one that fit. He annotated it with a single additional line.

Every architect leaves fingerprints. Simmans knew his own well enough. There were patterns in the way he built — structural tics, preferred recursion depths, the way he handled the transition between procedural layers so that players did not feel a seam. He had documented most of them, not for vanity but because good tools documentation meant better teamwork. His lead engineers had a running shorthand for the most distinctive ones. That's a classic Simmans taper, they would say, when a difficulty gradient resolved with that peculiar gentleness that made failure feel like information rather than punishment.

He began looking for those signatures in his own life. He looked the way he looked at a build — not hunting for anything specific, just holding the pattern lightly and waiting for recognition to surface.

It surfaced quickly, and then it kept coming.

The first was what he privately called soft-fail pacing. In his designs, when a player was approaching a critical threshold — a decision with long-term consequence, a shift in narrative register — the environment would often provide a small, manageable failure just before the critical moment. Not enough to derail the player, just enough to reset their cognitive posture. It made them more present. More deliberate. It looked, from the inside, like bad luck. He had, in his own life, experienced a precise and almost comedic string of small failures immediately before every significant professional decision. Contracts that fell through the week before a better opportunity appeared. Hardware failures that delayed a build by three days, during which time he had written the design document for Lithic almost entire. He had attributed these to chance. They had the exact cadence of soft-fail pacing.

The second signature was what his team called resonant seeding — the technique of introducing a thematic element early and quietly, allowing it to recur at increasing intervals and increasing significance until it reached a climax. He found this woven through his entire biography. Ideas that had appeared in minor forms in childhood kept reappearing, upgraded, until they became the defining principles of his work. The notion that environments respond to consciousness — he had felt this first as a child, pressing his hand into the bark of a tree and half-believing the tree knew he was there. He had built careers around it. The seeding was not subtle once you looked for it.

The third signature shook him.

He called it the contributor flag — a technique he had developed for his collaborative multi-player environments, where different sections of the world were built by different designers. To maintain coherence, each designer embedded a signature pattern in their work: a recurring geometric proportion, a colour-temperature preference, a characteristic way of handling negative space. It was partly practical. It let him, during a build review, immediately identify who had made what and why a transition felt abrupt — two designers' signatures clashing at a boundary.

He found his contributor flag in the real world.

It was a proportion — a specific ratio that appeared in the way he naturally arranged his workspace, in the way buildings he found beautiful divided their facades, in a rock formation near the coast he had visited once and never forgotten. A ratio that appeared, more specifically, in the geometry of the aurora display he had written on that sleepless night: a thing he had believed he invented, but which he now realised he had been seeing his entire life, in distributed and apparently unconnected places, inserted by whoever had built this section of the world.

Inserted by him. In some prior version of himself, in some outer context, doing design work he could not remember but whose fingerprints he could still recognise, the way you recognise your own handwriting in a note you have no memory of writing.

He sat back in his chair and looked at the aurora cycling overhead, and he said, quietly, to the empty studio:

"I built this."

The aurora pulsed, in what he was no longer willing to call coincidence, in exactly the wave-frequency he used to signal a mid-session player milestone.

Her name was Elara. He had known her for the first six years of his life, and she had been old even then — old in the way he had later come to understand as almost-done, a creature who had spent what she had carefully and was running cheerfully toward empty. She had white hair and wide hands and always smelled of woodsmoke and a particular floor wax whose manufacturer he had never been able to identify in the real world. She had died when he was not quite seven. He had cried for three days and then, because children are architects of survival, stopped. He had carried what remained of her as a low, constant warmth at the back of everything he did, like the ambient temperature of a room you have been in so long you have stopped noticing it.

He thought about her now — really thought about her, for the first time in years, pulling out the memories and examining them with a designer's eye rather than a grandchild's.

She had been, he realised, his first guide.

In his most emotionally sophisticated builds — and particularly in The Verdant Recursion — there was a character type he returned to repeatedly. He called them threshold figures: NPCs placed at the entry and exit points of significant experiential zones. They were not quest-givers or antagonists. They did not advance plot. They were simply present — calm, warm, slightly outside the logic of the world, as if they knew something about its architecture. Players often described them as the element of the game that felt most real. Most comforting. Most like someone who had been expecting them.

Elara had been exactly that. Exactly. He felt the recognition with the force of a diagnostic hit.

She had aged into the simulation and was nearly out of it when he arrived. A person at the top of the experience curve, holding the entry-point steady for a person just beginning. She had spent six years not parenting him — that role was already filled — but orienting him. Pointing at things. Asking questions in a way that made him think rather than answer. Teaching him, he now understood, how to notice.

He went back through every memory he had of her and looked for the things she had pointed at.

There were numbers. She had been fond of them — not in an academic way but in a practical, almost superstitious way that he had absorbed without analysis. She would count things. Three knocks before entering. Seven steps between the gate and the front door, which she always counted aloud. A particular sequence — 3, 7, 11, 3 — that she used as a sort of private rhythm when she was thinking, rapping it lightly on the table. He had thought it was a habit. He had inherited the habit without knowing it. It was woven into his muscular memory.

He stared at that for a long time.

She had also been fond of specific symbols. A spiral drawn in the condensation of a glass. A particular arrangement of stones in the garden — three large, seven small, one in the centre that she called the anchor. A way of folding paper into a shape he had never seen elsewhere, bilateral, recursive, that he had been unable to stop drawing in the margins of design documents his entire working life without once thinking to ask himself why.

The shape, when he finally analysed its geometry, was a two-dimensional representation of the recursive state diagram he used for MIRROR's deepest layer transitions. He had thought he invented it. He had been drawing it from memory since childhood, from a shape an old woman had pressed into his hands before she left.

She had not left. She had gone ahead. She had left the door ajar and dropped a trail of numbers on the mat for him to find when he was finally ready.

He felt something crack open in his chest — not painfully. The way a seed cracks. The way a system breaks from a locked state into a running state.

He picked up his stylus. He began to trace the sequence.

3. Three actions. He backed up every file in the studio drive — a reflex he had never been able to explain rationally but always performed before anything significant. Three copies.

7. Seven steps. He walked the perimeter of the studio as he always walked it when thinking — seven long paces along the west window, turn, seven back. But this time he did not stop at the workstation. He kept walking. He walked to the equipment cabinet against the north wall. The one he had always used for hardware storage. The one he had not opened in eighteen months and could not, now that he thought about it, specifically remember last emptying.

11. Eleven components inside. He counted them as he removed them. They were not hardware. They were transcripts — printed documents, handwritten notes, schematic drawings on yellowed paper that could not have come from any printer in this building, documents he did not write, which described, in detail and with his own notation system, the architecture of a simulation he had not yet consciously designed.

A simulation called GROUND.

3. He turned around. He looked at his studio. He looked at the servers. He looked at the aurora. And with a clarity that came not from thought but from prior knowledge suddenly unblocked, he looked at the chair in the centre of the server room — a chair surrounded by a specific arrangement of equipment interfaces he had always told himself was a maintenance rig — and he understood what it was.

It was an exit terminal. It had been waiting for him since the beginning. He had built it himself, before the beginning, and then forgotten.

He sat in the chair. He allowed the interfaces to find him — soft clamps at the temples, a monitoring lattice that breathed against his chest, a haptic mesh that read his neural signature the way a MIRROR headset reads a player's, with patient, unhurried precision. He felt the deep processing hum that he had attributed, for two decades, to the servers. He understood now that it was older than the servers.

He ran the sequence.

3. Stillness. Let the body settle. Let the internal feed go quiet. He had designed this into every immersive session protocol: the threshold pause before transition. He had always thought of it as good UX. He now understood it was a technical requirement. The mind had to release its current state data before it could receive a new context.

7. He thought of her. Not as a grief-object but as a fact — Elara, solid and woodsmoke-warm, wide hands, the floor wax smell, the way she had looked at him on his last morning with her as if she were memorising him from the outside even as she knew he was doing the same from the inside. I will see you on the other side of this, she had not said. But he had heard it.

11. He counted the years. Every significant loss. Every rejection that had carved something out of him that needed to be empty before something else could fill it. He did not flinch from them this time. He ran them as data. He let them be what they were: curriculum. The prerequisite experiences without which the outer-context version of himself could not have built something as human as MIRROR, as truthful as The Verdant Recursion, as compassionate as Lithic. You cannot design grief-terrain without knowing the ground from the inside. He had known it from the inside. He had felt it the way the player feels it, with no access to the dashboard, no view of the architecture, no comfort of knowing it would resolve.

He had been, in other words, very brave.

3. Return.

He became aware of the suit. Full-body, lightweight, a monitoring mesh that read him at forty points simultaneously. He became aware of the rig — a couch-reclined chair, very slightly angled, far more sophisticated than the one he had sat down in. Far more real. He became aware of a specific smell: the laboratory variety of cleanliness, ozone and filtered air, and beneath it, very faintly — floor wax. Woodsmoke.

He turned his head.

She was reading something on a tablet, seated at a workstation to his left. Older than any version of herself he carried in memory — properly old, properly real, with the particular quality of presence of someone who had accumulated decades of the genuine article. She wore a university identification badge. Her white hair was shorter than he remembered. She had the same wide hands.

She looked up and took off her glasses.

"Welcome back," she said. In exactly the voice he remembered.

He opened his mouth. Closed it. He looked at the ceiling — real ceiling, acoustic tile, laboratory grid — and then back at her. He tried to assemble something coherent and found that the architecture of coherence was still reloading. He managed, after a moment:

"You're the colleague."

"Professor Elara Mendt," she confirmed, mildly. "Cognitive Immersion Research, third floor. Your oldest collaborator, as it turns out, if not your most recent one." She set the tablet down. "You were in there for a very long time. How do you feel?"

He considered the question with the seriousness it deserved. He felt — hollowed out, but in the way a cathedral is hollow: intentionally, structurally, in order to hold something. He felt the residual warmth of forty years of a life that had not happened and also, completely, had. He felt the grief of it and the gratitude of it simultaneously, tangled up in a way he recognised as the emotional signature of his best designs — the ones that stayed with people, the ones that produced that twenty minutes of silence on the other side of the headset.

"I feel like someone who finished one of my games," he said.

She smiled at that. It was the exact smile he remembered.

He looked around the laboratory. Banks of equipment. The unmistakable topology of a serious research facility. Through the window at the far end: a city skyline he did not recognise, under a sky with one too many visible stars for the middle of the day. He filed that observation away with a calmness that surprised him. One question at a time. He had learned that from building games: do not rush the exit sequence. Let each revelation land before moving to the next one.

He looked back at her. "Is this real?" he asked.

She considered it with the same seriousness he had considered her earlier question. It was, he noticed, exactly how he had designed his threshold figures to respond to player questions — with genuine thought, not deflection. He had learned that from her, he realised. He had built her into every game and never known it.

"It's the layer we're in," she said. "Which is a different question, and probably a better one."

He laughed. It came out rougher than expected — the throat of a man who had not laughed in the particular way that laughter means I understand in quite some time.

He looked at the workstations. He looked at the monitoring equipment. He looked at the faint reflection of himself in the dark screen of an inactive terminal — lighter in some way he couldn't name, the way a file is lighter after compression, the same content, different overhead. He had the particular feeling he recognised from playtesting sessions where a player had finally crossed a threshold they had been approaching for hours: the feeling of someone who had just understood something they could not yet put words to, but who knew, with complete certainty, that the understanding was real.

He had, after all, designed that feeling. He knew exactly what it meant.

It meant the simulation had done its work.

He turned back to Elara and asked the question that had been forming since the moment the light changed.

"What do we build next?"

She picked up her tablet. On the screen — briefly visible before she angled it away, as though not yet ready to show him, as though the next stage required one more threshold pause — he caught the title of an open design document.

It read: GROUND v2 — Initial Architecture.

And in the author field, both their names.

Outside, the city held its too-many stars in a sky that might have been real, and the floor wax smell drifted on the filtered air, and somewhere in a deep server rack, something that had been running for a very long time completed its final loop and began, without fanfare, to write the next one.

— End —