Raf's POV
The code fingerprint and the academic writing style are ninety-two percent match.
Ninety-two. I've been staring at the comparison for three hours, running the analysis through every tool I have, and the number won't move.
The indentation preferences align — the student's published papers use a four-space indent with nested comments in a style I've seen exactly once before, inside the neural lock's architecture.
The variable naming conventions match: lowercase with underscores, descriptive but compressed, the specific shorthand of someone who writes code the way poets write sonnets — formally, within constraints, the constraints becoming the style.
But ninety-two isn't one hundred. The eight percent gap is the difference between a fingerprint and a smudge, and a smudge doesn't hold up in a legal proceeding or in the specific court of my own certainty, which has higher standards than most courtrooms because my best friend is three floors above me in a bed and I can't afford to be wrong.
"The eight percent could be evolution," Anya says on speakerphone. She's at her own desk across town, running the same analysis on a different screen, the parallel processing we've been doing since week two because two sets of eyes catch things one set misses.
"The student published those papers in 2017, 2018. The neural lock was built in 2024 or 2025. Seven years of coding experience would change someone's style — smoother, faster, more confident. The core architecture stays the same but the execution matures."
"So the gap is growth, not difference."
"That's my read. The ninety-two percent is the skeleton. The eight percent is the muscle someone built on top of it over seven years. Same person. Better at what they do."
I lean back. The whiteboard has grown since last week — the circle around Cross expanding into a web of connections that looks like a conspiracy wall from a movie Kai would reference.
The student's file sits at the center: withdrawn, personal circumstances, thesis on biometric feedback loops in persistent virtual environments. The fiancée's name branching off to the right, connected by a line to the 47,000 dataset and another line to a death record dated three months after the hearing.
The profile is almost complete. I can describe this person without naming them: graduate-level researcher in neural interface design. Studied under Dr. Vivian Cross at one of the top programs in the country.
Published three papers on the exact architecture the neural lock uses — not adjacent work, not foundational research, the thing itself described in academic language and filed as a thesis project.
Had a fiancée whose intimate data was collected by the original Echo surveillance system. Lost the fiancée to the psychological aftermath of the hearing that exposed the data's existence.
Withdrew from their program under personal circumstances — the academic euphemism for a life that fell apart so completely the falling showed up in enrollment status.
And then, years later, built a trap. Not a random trap — a trap built from the exact technology they studied, aimed at the exact population whose data was collected, testing the exact question that their fiancée's death left unanswered: does love survive when privacy is destroyed?
"The motive makes sense," Anya says, reading the same profile. "Someone who studied the system that collected their partner's data. Who lost the person they loved because the data existed. Who had years to plan and the skill to execute."
"And a thesis advisor who knows their name and won't say it under oath."
"Cross is protecting them. Loyalty or complicity?"
"Loyalty. Cross's testimony was too clean for complicity — complicit people leave gaps because they're managing two versions of the truth. Cross is managing one version with one omission. The omission is the student's name." I tap the desk.
"She knows. She's known since the beginning. She sat at a hearing and watched senators ask questions that circled her student without landing, and she let the circles stay circles."
I pull up the university's archived student database portal. The screen loads the login page — institutional access only, student records protected under privacy regulations that Sophia has been chipping at for a week.
The database contains enrollment photos, full identification, and academic transcripts. Everything I need to put a face on the fingerprint.
"Sophia's second subpoena," I tell Anya. "The one for full student identification. She filed it four days ago. The university's legal team pushed back on privacy grounds. Sophia argued imminent danger — nineteen thousand people in hospital beds constitutes a compelling interest that overrides student privacy protections."
"And?"
"And I've been refreshing my email every eleven minutes since Tuesday." I check again. Eleven minutes since the last check. The inbox loads.
The email is there.
Subject line: SUBPOENA COMPLIANCE — Student Records, Neural Interface Laboratory, 2014-2019. From the university's general counsel.
Attachment: one encrypted file. The encryption key in a separate email from Sophia, sent thirty seconds later, the security protocol she insists on because Sophia treats digital evidence the way surgeons treat instruments — sterile, documented, every handoff logged.
I decrypt the file. The database access portal loads — full records, full identification, enrollment photos. The search interface accepts department, date range, enrollment status. I enter the parameters: Neural Interface Lab. 2014-2019. Withdrawn.
The search runs. The progress bar fills. The database processing the query through years of archived records, matching the criteria against thousands of student files, narrowing toward the one file I've been building toward for twenty-seven days.
"It's running," I tell Anya.
"How long?"
"The system says twenty-four hours for archived records retrieval. The photos are stored in a separate database that requires manual verification before release."
"Twenty-four hours."
"Twenty-four hours." I stare at the progress bar — one percent, the slowest percent I've ever watched, the kind of waiting that makes hospital waiting rooms feel efficient by comparison. "I have a code fingerprint, a motive, a thesis advisor, a dead fiancée, and a ninety-two percent match. In twenty-four hours, I'll have a face."
"And then what?"
"And then I find out if the face matches anyone inside the game."
The progress bar crawls. One percent becomes two. The conference room holds its dark, its cold coffee, its whiteboard covered in lines and circles and the shape of a person who has been invisible for twenty-seven days and is about to become visible in the time it takes a university server to process one archived query through one bureaucratic pipeline.
Danny is three floors up. Nora is beside him. The Architect is somewhere inside the game they're both trapped in. And in twenty-four hours, the Architect will have a face.
I watch the progress bar and wait.