There’s no triumph in his voice. No heat. Just certainty. For the first time since stepping into that consultation room, my pulse slows.
“Rowan,” he adds, softer now.
“Yes?”
“You’re not facing this alone.”
I close my eyes.
“I know,” I say quietly. “And neither are you.”
And that changes everything.
21
KIREN
The preliminary summaries sit in my inbox, organized, cross-referenced, and stripped down to conclusions. Polina condensed them into a format designed for speed. Mikel already read them twice. I ignore both.
If someone reached into Rowan’s world and altered it from the inside, I need to see the structure myself.
The private conference room at Sovarin Biomedical is quiet at this hour. Floor-to-ceiling glass overlooks Charlotte’s skyline, the city lights diffused through a low winter haze. The table in front of me is clean except for my laptop and a stack of printed logs I requested instead of viewing everything digitally. I want paper. Paper forces attention.
I open the hospital access records first and move through them line by line. Badge scans align with scheduled shifts. Entry timestamps match routine traffic. Internal routing betweendepartments follows normal workflow patterns. IT authentication confirmations show no irregular flags or override errors. There’s no evidence of forced entry, no broken locks, and no corrupted system logs buried beneath the surface. Every credential was properly validated. Every access point was authorized.
The fabricated consultation that rerouted Rowan into that restricted corridor originated from a verified internal login. The badge belonged to a real employee. The credentials weren’t stolen through a crude breach. There was no foreign IP trace or external override.
I scroll through camera timestamps next. The corridor outside the surgical wing shows nothing unusual. A nurse passes at 18:42. A tech pushes equipment at 18:47. Rowan walks through at 18:49, following the consultation instructions that pulled her off her scheduled rotation.
I replay the segment twice, studying her posture. She’s not cautious, she’s focused. She trusts the system she works inside. That trust is what makes this possible.
The override trail is clean. The consultation was entered from a terminal located two floors above, then accessed through Rowan’s department workflow. It appears routine. The same routine that occurs dozens of times a day inside a hospital of that size.
There’s no sloppiness, no stray anomalies, and no digital fingerprints left behind for someone careless enough to overlook. The logs confirm what I already suspected. Thiswasn’t an impulsive move from the outside. It was a breach from within.
I square the stack of papers in front of me, aligning the edges until they sit perfectly flush, then pull up the previous incidents side by side on my laptop. The accident, the EMS dispatch reroute, and the fabricated hospital consultation sit aligned on the screen in chronological order. Three separate events in three different environments, yet built on the same underlying framework.
The accident that nearly killed Rowan was planned carefully. The brake failure was engineered without obvious tampering. There was no visible sabotage. Whoever handled it understood mechanical systems well enough to avoid leaving behind clear signs of interference.
The EMS reroute was subtle. A dispatch reassignment that sent the nearest unit elsewhere for four minutes. Not long enough to draw scrutiny, but long enough to create vulnerability.
The hospital lock required authenticated credentials and familiarity with procedures.
Each incident demanded patience and layered access, built on the assumption that Rowan would respond predictably within her professional role.
This isn’t Ivan. Ivan acts when opportunity presents itself. He pushes forward when he’s within reach. He enjoys inserting himself into environments where charm does the work before force becomes necessary. His ambition is direct. Visible.
This sequence isn’t direct. It’s orchestrated.
I slide the three timelines into alignment, studying the overlap in dates and communication spikes between known associates. Polina has already highlighted several nodes for me. One name appears consistently near decision points, though never at the center.
Arkady Voronin.
He doesn’t appear in the execution logs at all. His name shows up around the planning stages, then disappears before anything actually happens. He keeps himself removed and lets other people carry out the work.
The room feels colder despite the heat humming softly. I rest my forearms on the table and study the timestamps again, not because I expect new information, but because going over them more than once sharpens my judgment.
All three events required coordination across systems that don’t normally intersect, including traffic control, emergency response routing, and hospital workflow access. That level of coordination doesn’t happen by accident. It reflects planning by someone who understands how systems are built and how to use them without drawing attention.
