Raf’s POV
I haven't slept in forty-eight hours, which I know because my laptop's battery has died twice and each charge cycle takes roughly twenty-four hours of my life disappearing into a screen that keeps showing me the same answer: I'm not smart enough to save my best friend.
The neural lock architecture fills my display like a schematic drawn by someone who hates the people looking at it.
Nodes branching into nodes, feedback loops nested inside feedback loops, the kind of recursive engineering that's elegant the way a bear trap is elegant — you can admire the design while it's eating your leg.
Dr. Anya Patel arrived at the hospital six hours ago with a laptop bag and the specific urgency of a woman who just recognized her own research being used for something she never intended.
She's a neuroscientist from Johns Hopkins — brain-computer interfaces, the intersection of neural mapping and digital input that sounds like science fiction until your best friend is lying in a bed wearing a headset that's hijacked his brain.
"Walk me through it again," I tell her, because hearing it twice doesn't make it better but it makes it clearer, and clearer is all I've got.
She pulls up the schematic on the hospital's conference room monitor — they gave us the room on day three because I refused to leave the hallway and the nurses got tired of stepping over my laptop cord.
Her finger traces the primary feedback loop, the one that runs from the headset's sensor array through the neural interface and back.
"The lock exploits the headset's biometric feedback loop. Under normal operation, the headset sends sensory data to the brain — visual, auditory, haptic. The brain processes it as input and responds with motor commands that move the avatar."
She draws a circle with her finger. "The lock interrupts the return path. The brain keeps receiving sensory input from the game, but the motor commands that would move the real body get rerouted back into the game instead. The brain thinks the avatar is the body."
"So it's not blocking signals. It's redirecting them."
"Exactly. The brain is still sending commands to move, breathe, respond. It just thinks the game is the destination instead of the real body." She taps the screen.
"The autonomic functions — heartbeat, breathing, organ regulation — are maintained by a separate loop the lock doesn't touch. That's why they're alive. The lock is sophisticated enough to hold consciousness hostage while keeping the body on life support."
"And if we force the headset off?"
"The brain is prioritizing the game's signals over the body's. Forcing disconnect would be like unplugging life support mid-surgery — the brain wouldn't know how to restart autonomic function. Heart rate, breathing, everything the separate loop is maintaining gets confused when the primary feed disappears."
She looks at me over the screen. "We'd be killing them to save them."
"So we can't pull them out."
"Not without the game releasing the lock from inside. Or finding whoever built this and getting the kill code."
The kill code. Three syllables that sound like the answer to everything and are actually the answer to nothing, because a kill code requires a coder, and the coder is somewhere out there building death games while I sit in a hospital conference room with a neuroscientist who can explain exactly how my friends are dying and can't do a single thing to stop it.
"Show me the comparison." Anya pulls up the Echo Link architecture from the hearing on one half of the monitor — the one I mapped during the original NeuraLink investigation.
I pull up the neural lock on the other half. The two schematics sit side by side and the resemblance is obvious enough that Anya sees it before I have to explain.
"That's the same foundation."
"I identified it on the first night. Someone took the NeuraLink surveillance code — the stuff the FTC confirmed was wiped — and rebuilt it. The source code was supposed to be destroyed, but corporate servers aren't the only place code lives. Development environments, personal backups, anyone with source access could have kept a copy."
"How many people had source access?"
"Hundreds. Every developer, every contractor, every engineer who ever touched Echo's codebase."
"Then narrow it down. Because this isn't just a rebuild." Anya highlights a section of the new architecture, and this is where she earns her six-hour drive from Johns Hopkins.
"The original system was theoretical — Echo Link's surveillance captured data but never attempted to hold consciousness. Whoever built this didn't just copy the capture protocols. They weaponized them. Turned a microphone into a cage." She traces the new routing pathways with her finger.
"This is doctoral-level work, Raf. This isn't some disgruntled employee pasting code together. This is someone who understood the original architecture deeply enough to see what it could become."
I pull up the new architecture's source and start reading — not the schematic this time but the raw code underneath, the actual instructions that tell the headset how to hijack a human brain.
Code has style the way handwriting has style — indentation preferences, variable naming conventions, the way a programmer structures their logic.
Two people can solve the same problem and the solutions look as different as fingerprints.
Anya watches me work. "What are you looking for?"
"A signature. The person who built this has habits — the way they name variables, the way they structure loops, the way they handle exceptions."
I scroll through lines of code that look like the architectural plans for a prison.
"Every programmer I've ever worked with has tells. If this person ever contributed to Echo's original codebase, their style is in the version history. I just have to match the fingerprint."
"And if they never touched the original code?"
"Then they learned from it. Studied it. Knew it well enough to rebuild it from memory." I lean back and press my palms against my eyes. Forty-eight hours without sleep and the screen is starting to swim.
"That's a different kind of fingerprint. Not a contributor — a student. Someone who studied Echo's architecture the way you'd study a textbook."
"Like a researcher."
"Like someone who published papers on the topic." I drop my hands and look at her.
"Do you know anyone in the neural interface field who's published theoretical work on biometric feedback loops? Specifically Echo's architecture?"
Anya is quiet for a moment. "I can check the academic databases. If someone published on Echo's specific protocols, the citation trail would be narrow — it's proprietary architecture, not open-source. Anyone writing about it had inside knowledge or reverse-engineered the system."
"Start there." I turn back to the screen. "Cross-reference anyone who published on Echo's biometric feedback with anyone who had access to the development environment. If there's overlap, that's our person."
She opens her own laptop and starts searching, and the conference room fills with the sound of two people typing — the only sound that makes sense right now, the only sound that feels like forward motion in a hospital full of machines that beep and people who wait and a world that keeps asking questions nobody can answer yet.
Forty-seven hundred patients in this city. Thousands more worldwide. Bodies in hospitals and living rooms and dorm rooms — alive and empty, maintained by machines and the hands of people who keep talking to faces that don't respond.
Somewhere in this code is a fingerprint. Somewhere in the academic record is a name.
I'm going to find both, because the alternative is sitting in a conference room watching a screen and waiting, and waiting is the one thing I'm worse at than sleeping.