noveltoon logo noveltoon
Love at First Login

Chapter 210

Ch. 210 / 255 May 14, 2026

Raf's POV

The match comes through at 11:42 PM on a Tuesday, and the match is one hundred percent.

Not ninety-two. Not close-but-not-definitive. One hundred. The subpoena results included the student's full thesis code — not the published papers, the raw work, the unpolished version that carries every habit and preference and structural fingerprint the published versions were cleaned of.

The indentation and the variable naming. The nested logic structures that build like sentences, clause inside clause, the specific architecture of a mind that thinks in layers and codes the way it thinks.

The neural lock's architecture matches the thesis code the way a signature matches a signature. The student didn't study the system. The student didn't build on the research. The student built the thing.

I sit in the conference room at 11:42 PM on a Tuesday and stare at a one-hundred-percent match and the one hundred feels like a door opening into a room I've been trying to reach for twenty-eight days and the room is darker than I expected.

But the match isn't the breakthrough.

The breakthrough is what I find when I turn from the code comparison to the active server logs Sophia subpoenaed alongside the enrollment records.

The neural lock's code — the architecture that holds nineteen thousand people in hospital beds — isn't static. It's being modified. In real time.

Tier parameters adjusted between challenges. Difficulty curves tweaked mid-session. The biometric thresholds that determine whether a player passes or fails recalibrated based on live data.

Someone is inside the system right now, writing code, adjusting variables, running the experiment the way a scientist runs a trial — hands on the controls, eyes on the data, the methodology alive and responsive.

I trace the modifications to their origin point. The code changes don't come from an external server. Don't come from a development terminal or a remote access point or any of the standard architectures I'd expect from someone operating the system from outside.

The modifications originate from a player-side connection. Someone logged into Echo as a player. Someone with system-level access disguised inside a standard login — admin privileges hidden behind a player interface, a control panel wearing a campfire's clothing.

The Architect is in the game.

Not monitoring from a server room. Not operating from a prison cell — Nora's Arthur theory dies in the server logs, though she won't know that for a while.

Not managing from any external position. The Architect is logged in. Playing. Sitting at campfires. Walking through Tiers. Standing beside the people they trapped and rewriting the rules from inside while the people sleep.

I call Anya. Three in the morning. She picks up on the second ring.

"The code changes are coming from inside the game."

Silence. Then: "That's not possible. Player-side connections don't have write access to the architecture."

"This one does. The student built a backdoor into the player interface — admin-level access disguised as a standard login. From the outside, it looks like any other connection. From the inside, it's a control panel."

"So the Architect is a player."

"It's worse than that." I pull up the connection logs — raw data, every login and logout event across all nineteen thousand active connections. The pattern is uniform: single continuous sessions.

One login, no logout, the connection held open for twenty-eight days because the neural lock doesn't let you disconnect. Twenty-eight days of unbroken signal. Every single player.

Except one.

"There's one connection that breaks the pattern. Same admin-level access. But the session isn't continuous." I stare at the data. "It disconnects and reconnects. Regularly. Sometimes for hours at a time."

"That means—"

"The Architect isn't trapped. They log in, they play alongside the people they locked inside, and then they log out. Take off the headset. Walk around. Eat dinner. Sleep in a real bed." I lean back in the chair and the leaning has the specific weight of a man who just found the thing he's been looking for and the thing is worse than he imagined. "Then they put the headset back on and walk back into the game like nothing happened."

"They're choosing to be there."

"Every single day. For twenty-eight days. They built a cage for nineteen thousand people and they visit it voluntarily. They sit at campfires with people who can't leave, and then they go home."

The conference room is dark except for the screen. Danny is three floors above me in a bed that's been breathing for him for twenty-eight days without a break.

Without a single disconnection. Without the option of taking off the headset and walking to the kitchen and eating something that isn't delivered through a tube.

The Architect has been taking breaks. Walking outside. Living a life between sessions while Danny and Nora and nineteen thousand other people lie in hospital beds with IVs in their arms and families in their waiting rooms.

I save the server logs. Label the file: ARCHITECT — ACTIVE PLAYER / FREE ACCESS. Send it to Sophia. Send it to Margaret. Send it to every address in my investigation folder.

The Architect has a code fingerprint. A dead fiancée. A thesis advisor who won't say their name. A one-hundred-percent match to a neural lock that holds nineteen thousand people in stasis. And a connection that logs in and out of a game that nobody else can leave.

I have everything except the face.

The university database query — the one I launched twenty-four hours ago, the progress bar I watched crawl from one percent — should have the student's enrollment photo in my inbox by morning.

By morning I'll have the face. By morning the invisible person who has been sitting at campfires and adjusting difficulty curves and walking through Tiers beside the people they trapped will have a face that matches a fingerprint that matches a thesis that matches a dead woman in the 47,000 dataset.

But right now, at 3 AM in a conference room that smells like twenty-eight days of cold coffee and obsession, all I have is a connection log that tells me the Architect is somewhere.

Maybe inside the game right now. Maybe outside it — sitting in an apartment, sleeping in a bed, walking a street in a city that isn't crumbling. Living the ordinary life that nineteen thousand people can't.

Danny is three floors up. The Architect is somewhere. And the distance between those two facts is the distance between a man in a bed and the person who put him there, and the person walks freely between the world that holds the beds and the world that holds the cage, and nobody on either side knows their face.

Not yet.