Chapter 40: GAVIN PARK OPENS THE FILE
The dead-drop contained three pages.
I retrieved them from the Koreatown gym locker at 6 AM, three weeks after the wine cellar massacre. Tomas's handwriting was precise, economical—intelligence broker shorthand that compressed complex institutional movements into sentences I could process while walking to my car.
"W&H file transfer: complete. New owner: Gavin Park. Methodology change: significant."
I sat in the parking lot and read the full report.
Park had made three additions to the file in his first weeks of ownership. The first was a classification upgrade: "Subject demonstrates survival capability through methods that should be lethal. Recovery mechanism unknown but consistent across multiple incidents. Designation: Revival-class ability."
"Revival-class. He named it."
The second addition was technical. The parking structure Revival burst from the wine cellar night had been partially detected by an automated magical sensor in the building's infrastructure. The reading was incomplete—angle, distance, partial spectrum only—but it gave Park something Holland had never had: a technical profile of what happened when I came back.
The third addition was the problem.
Park had reclassified the file from "investigation" to "acquisition target."
I drove back to my room and ran the threat assessment.
"Investigation vs. acquisition. Different resolution states. Different tactical approaches."
Investigation had a clear endpoint: identify the subject, take action. The action could be neutralization, recruitment, or simple observation, but it resolved the investigation. You found your answer and you moved on.
Acquisition target was different. Acquisition target meant W&H wanted to extract me, contain me, and study me indefinitely. They didn't want to kill me—they wanted to understand the ability source, the mechanism, the replication potential. A Revival-class ability in W&H's hands would be worth years of research and potentially unlimited applications.
"Tactical shift: elimination to capture-and-hold. Trap-and-capture methodology. Proxy pressure on known associates."
I ran the probability analysis. Direct W&H engagement in the next twelve months: 35%. They wouldn't move on me directly until they had a capture methodology that could contain the Revival. That required research, resources, planning.
Proxy pressure on known associates: 55%.
Maya was a known associate in the pattern analysis.
I sat with the Maya calculation for an hour.
The operational logic was clear. She was in my pattern. W&H's behavioral analysis had almost certainly identified her as a recurring contact—someone who appeared in proximity to my operational movements more often than chance would explain. If Park decided to apply proxy pressure, she would be a target.
"Option: Sever connection. Give her clean departure. Reduce her profile in my pattern."
I knew what I would decide before I finished the calculation.
I had made this decision twice already. Once when she identified the Revival cycle and I said nothing—when I let her continue operating in my proximity knowing she understood what I was. Once when I told her to reduce operational activity and she complied without question, without friction, without resentment.
She had chosen to stay both times. She would choose again now.
"This is the clearest expression yet of choosing cost over operational logic."
The operational logic said: protect the asset by removing the asset from the threat environment. The cost calculation said: Maya is not an asset. Maya is a person who has chosen proximity to me knowing what that proximity costs. She deserves to make that choice again with full information.
I called her.
"The threat profile has changed."
We were at the coffee shop two blocks from my room. She'd arrived within twenty minutes of my call, no questions about why, no hesitation about the timing.
"W&H has reclassified their investigation," I said. "They're not trying to identify me anymore. They're treating me as an acquisition target. That means capture methodology, containment protocols, study parameters."
She listened without interrupting.
"It also means proxy pressure. People in my pattern become leverage points. You're in my pattern."
"I know."
"I'm telling you so you can choose. The risk to people in my proximity has materially changed. If you want to step back—"
"I know," she said again.
She picked up her coffee and took a drink. The gesture was unhurried, deliberate—the kind of pause that meant she was considering her response, not her decision. The decision was already made.
"You're telling me what you said you would tell me. Last time, when the file got reclassified to person-hunt, you said you would tell me if the risk changed. You're telling me."
"Yes."
"And you're asking if I want to leave."
"I'm giving you the option."
She set down the coffee. "The option was always there. I could have left when I figured out the Revival cycle. I could have left when you told me to reduce operational activity. I could have left any time in the past two years."
"Two years. She's been counting."
"I stayed," she said. "I'm staying. The risk profile changing doesn't change the choice. It just means I know more about what I already chose."
I didn't have a response that fit the moment. What I had was the specific recognition that she had just made her third unconditional choice—and that I was going to log it that way, even though the logging felt increasingly inadequate to describe what was happening.
"Okay," I said.
"Okay."
We finished our coffee. She asked about the eastern district—routine courier logistics, nothing operational, just the normal business that kept her legitimate work running. I answered. The conversation was ordinary in a way that felt strange after what we'd just discussed.
When she left, she touched my shoulder briefly. Not a gesture with operational meaning. Just contact.
Back in my room, I wrote in the operational log: "Maya — informed, chose. Cost: confirmed and accepted."
I wrote nothing more about this. The logging felt inadequate, but I didn't know what else to do. I had been keeping operational records for twenty-six months. The records were how I processed information, how I tracked state changes, how I maintained continuity across the chaos of trying to shape events I couldn't fully control.
Maya didn't fit the logging system. She hadn't fit it for months. I was going to keep logging anyway, because stopping felt like giving up something I couldn't afford to give up.
I opened the Sahjhan file.
Connor's birth was approximately six weeks away. The Holtz disruption glyph net had forced Sahjhan to re-engage with his operative directly—I'd tracked the temporal signature movements for three weeks, watching the pattern shift as the glyph-delayed infrastructure forced Sahjhan to make personal adjustments he'd normally delegate.
The engagement window would open in the next three to five weeks.
I had one chance.
I reviewed my preparation for the last time: five Granok resistance stacks, functional AIM field interference, Ashen Command with confirmed Granok susceptibility from my research, Pyre Lexicon binding configuration ready for deployment. Forty deaths worth of accumulated capability, focused on a single target.
The preparation was adequate. Whether adequate was enough—I would find out in less than a month.
To supporting Me in Pateron.
with exclusive access to more chapters (based on tiers more chapters for each tiers) on my Patreon, you get more chapters if you ask for more (in few days), plus new fanfic every week! Your support starting at just $6/month helps me keep crafting the stories you love across epic universes.
By joining, you're not just getting more chapters—you're helping me bring new worlds, twists, and adventures to life. Every pledge makes a huge difference!
Join now at patreon.com/TheFinex5 and start reading today!
if you've been waiting for a translation — it's up.
unwrittenrealm.com has this story in 14 languages and more free chapters than here.