Raf's POV
The conference room smells like cold coffee and twenty-six days of someone who stopped noticing the air around day eight.
I have a cot in the corner, a bathroom down the hall, and a laptop with seventeen open tabs. The whiteboard I took from the nurses' station has Dr. Cross's name circled in red, connected by a line to "student — unnamed — enrollment records," connected by another line to the code fingerprint I pulled from the neural lock twenty days ago.
Twenty days of following a fingerprint through academic papers. Through published research.
Through the breadcrumb trail of a person careful enough to publish under initials but not careful enough to disguise their coding style. Tonight the trail led somewhere I wasn't prepared for.
The enrollment records came through at six this evening. Sophia Chen's subpoena — the one Margaret's testimony pushed through committee — cracked open Cross's department files from 2014 to 2019.
Student names, thesis topics, enrollment status. Most of it administrative noise — dozens of graduate students cycling through a neural interface lab across five years.
But I'm not looking for dozens. I'm looking for one. A student who co-authored three papers on biometric feedback architecture, who was listed by initials in the publications, whose coding style matches the neural lock with the precision of a signature.
I cross-reference the co-author dates with enrollment records. The overlap narrows the field. Three students were enrolled during all three publication windows.
One withdrew before completing their degree — the enrollment status listing "personal circumstances" as the reason, which is the academic version of we don't know or we know and we're not saying.
The withdrawn student. The one who was there for all three papers and then wasn't. I pull their file.
The file doesn't give me a name — the subpoena covered enrollment status and academic records, not identity documents. Privacy protections on student data.
Sophia is working a second subpoena for the full identification, but that's days away. What the file gives me is a thesis topic: "Biometric Feedback Loops in Persistent Virtual Environments: Emotional-State Translation and System-Level Response Architecture."
I read it twice. The thesis topic is the neural lock. Not adjacent to the neural lock — the neural lock itself, described in academic language, filed as a graduate research project under Dr. Vivian Cross's supervision.
The student wasn't building on published research. The student was building the thing. In a university lab. With their thesis advisor watching.
Cross knows. She's known since the beginning. The leftward glance Margaret caught at the hearing wasn't a tell — it was a confession, delivered in the one-second language of a woman who mentored the person who built the trap and has been protecting that person's identity with every careful, rehearsed, principled answer she's given.
I lean back. The chair creaks. The conference room holds its breath the way conference rooms do when the person sitting in them has found something that changes the shape of the search.
The next step is the 47,000.
The dataset sits on a server Sophia secured from the original NeuraLink case — the complete list of couples whose intimate data was collected by the surveillance system Danny and Nora exposed at the hearing.
Forty-seven thousand couples. Ninety-four thousand names. Biometric profiles, relationship data, the catalogued intimacy of people who never consented to being watched.
I search the withdrawn student's file for any connection to the dataset. Not the student's name — I don't have it. The student's academic affiliation, their enrollment dates, their department access.
Looking for overlap between a neural interface student and the couples whose data was collected.
The overlap appears at 11:47 PM.
Not the student. The student's emergency contact — listed in the enrollment file as "fiancée." A name. A name that appears in the 47,000 dataset.
I pull the fiancée's record from the NeuraLink data. The record loads and the loading takes three seconds and the three seconds are the last three seconds before the investigation stops being about code and becomes about a person.
She was twenty-six. Used Echo casually — social features, the way you'd use any platform without reading the terms of service. Her relationship data was captured automatically by the biometric system Danny's investigation exposed.
Heart rate correlations. Emotional-state patterns during shared virtual experiences. Two people in love, catalogued without consent by a system that was supposed to be entertainment.
She didn't survive the hearing.
Not the game — the hearing. The hearing that Danny and Nora's investigation triggered.
The public revelation that the data existed — that somewhere on a server, the most private moments of her relationship had been captured, stored, sorted into categories by a system that measured her love in data points.
I search further. The death record is public — connected to the hearing's aftermath, filed under a timestamp that places it three months after the federal testimony.
Cause of death listed in clinical language that says nothing and says everything. The woman didn't die from the data being leaked — the data was never released publicly. She died from the knowledge.
The awareness that the intimacy she shared with her partner had been watched. Recorded. Stored. That the private had never been private. That the moments she thought belonged to two people belonged to a server.
I stare at the screen. The conference room is dark except for the laptop's glow. Danny is three floors above me, trapped in the system that this student built. Nora is beside him.
Nineteen thousand people are in hospital beds. And the person who trapped them did it carrying the grief of a fiancée who died because a hearing revealed that privacy is a thing people believe in and systems don't.
I call Anya. She picks up because Anya stopped keeping normal hours the same week I did.
"I found the connection," I say. "Cross's student had a fiancée. The fiancée was one of the forty-seven thousand."
"Was?"
"She didn't survive the aftermath. Not the game — the hearing. The exposure. The knowledge that their intimate data existed on a server."
Silence on the line. Anya processing the way Anya processes — the pause that means the data is being integrated into a framework that just shifted.
"So we're looking for someone who lost the person they loved," she says. "Because a system collected their most private data without consent. And that someone responded by building a system that traps people inside the same kind of surveillance."
"The same architecture. Biometric monitoring. Emotional-state tracking. Intimate data used as a weapon." I look at the whiteboard. The circle around Cross's name. The line to the unnamed student.
The line now extending to a dead woman whose love was catalogued by a machine. "Whoever this student is, they watched the person they loved die from the knowledge that their privacy was never real. And they built a game that asks whether love survives when privacy is impossible."
"That's not a game, Raf. That's a question."
"It's a question that's killing people."
The conference room holds the sentence. Three floors up, a monitor beeps.
Somewhere inside a game, a student sits at a campfire carrying a grief that built a cage for nineteen thousand people, and the cage is the question and the question is the grief and nobody on this side of the screen knows the student's face.
Not yet.