Chapter 11: What Holland Manners Notices
The cold arithmetic of being noticed looks like a single line in someone else's documentation.
"Anomalous pattern noted in case-adjacent locations — three separate incidents, possible external interference. Assigning review."
Tomas read the line to me from a contact's transcription. His storage unit felt smaller than usual, the fluorescent light buzzing with the particular frequency of bad news delivered in neutral tones.
"Holland Manners," Tomas said. "Senior Special Projects. He's the one who signed off on the review notation."
I took the information and filed it. Holland Manners. The man who would die in a wine cellar when Angel chose not to save him. The man who had orchestrated Darla's resurrection. The man who was now, apparently, noticing patterns in case files that should have looked unremarkable.
"What's the classification level?"
"Review item. One level below actionable investigation." Tomas closed the folder he'd been reading from. "My source says he's methodical. Doesn't escalate unless the data supports it. But he's also patient. If the pattern continues, he'll wait until he has enough to make a formal case."
"Three incidents. Echo Park, the industrial district vampires, and one I considered too minor to track."
The realization landed with the specific weight of an intelligence failure. I had underestimated Wolfram & Hart's documentation sensitivity. The incident I'd dismissed as noise had registered in their system as signal.
"How long until the review becomes an investigation?"
"Depends on whether you give him more data." Tomas's amber eyes were evaluating, the way they always were when he was calculating the value of a client. "Three weeks to six weeks if nothing else triggers. Faster if you keep operating in his coverage zones."
I nodded. "Understood."
"Is this going to affect our arrangement?"
"No." I stood. "But I need to adjust my operational parameters. Which means I'll be buying less local intelligence for the next month."
Tomas accepted this with the professionalism of someone who understood that clients had their own calculations. We concluded the transaction, and I walked out into the Boyle Heights night with a new entry for my threat log.
Four hours later, I had the counter-analysis complete.
The three flagged incidents shared a common feature I should have identified earlier: all three had occurred within 48 hours of a Doyle vision-driven case in the same district. From Wolfram & Hart's analytical perspective, this created a correlation pattern.
If Holland Manners identified the correlation, he would reach one of two conclusions. Either Angel Investigations had a second operative — easily ruled out, since W&H's surveillance confirmed the team's size and composition. Or an independent external actor had foreknowledge of Angel's movements.
"The foreknowledge implication is the dangerous one."
I wrote the assessment in my operational log and then wrote the solution underneath it:
48-HOUR BREAK RULE Constraint: No adjacent operations within 48 hours of a Doyle vision-trigger in the same district. Rationale: Breaks temporal correlation pattern in W&H analysis. Cost: Approximately 30-40% of potential adjacent operations become timing-impossible.
The percentage sat on the page like a verdict. Thirty to forty percent of Season 1's cases were tight-window situations — threats that required intervention within hours of the vision, not days. By implementing the 48-hour break rule, I was accepting that roughly a third of the people I could potentially help would fall outside my operational ceiling.
"This is the first explicit acknowledgment that my ability to reduce harm has an institutional ceiling."
The thought was accurate and uncomfortable. I had known, abstractly, that I couldn't save everyone. But there was a difference between the abstract knowledge and the specific calculation: this many cases, this percentage miss rate, this many people I would choose not to help in order to maintain operational security.
I closed the log and opened it again.
The numbers hadn't changed.
The phone number had been in my pocket for eleven weeks.
I pulled it out, looked at it, put it back. Then pulled it out again.
Maya Reyes. Courier. The woman who had witnessed my Revival in a Koreatown alley and chosen silence. The woman who had offered me a contact number without asking what I was or why I kept coming back from death.
I needed a piece of local knowledge that Tomas's network didn't cover — a neighborhood in the valley that his contacts had no presence in. Maya's courier work took her through parts of Los Angeles that the formal underworld economy didn't reach.
"This is operational."
The thought was accurate. It was also incomplete.
I dialed the number.
Three rings. Then:
"Yeah?"
Her voice was exactly as I remembered it from Tomas's storage unit — steady, professional, calculated.
"It's Kael."
A pause. Two seconds. "The alley guy."
"Yes."
"You kept the number."
"You said it was good for six months."
"I did." Another pause. "What do you need?"
"Local knowledge. The valley — Sherman Oaks, Studio City, that area. I need to know if there's supernatural activity in the residential corridors."
"Business or personal?"
"Business."
"Forty-eight hours. I can have something for you."
"That works."
"Same dead drop as Tomas's secondary?"
"Yes."
She hung up without saying goodbye. Professional. Efficient. The specific brevity of someone who understood that phone conversations were traces and traces were liabilities.
I put the phone away and added a notation to my relationship log:
MAYA REYES — FIRST DIRECT CONTACT Date: February 8, 2000 Type: Phone call, operational Content: Intelligence request (valley neighborhoods) Response: Professional. No questions asked. Assessment: Good instincts about what not to ask.
Below that, in smaller script:
Note: First call in 11 weeks. Initiated for operational need. Not personal.
The notation was accurate. It was also the kind of accuracy that was more about convincing myself than documenting facts.
The operational log's threat section got a new entry that night.
HOLLAND MANNERS — ACTIVE THREAT Status: Review file opened. Not yet actionable. Pattern identified: Doyle-vision temporal correlation (48-hour window) Counter-measure: 48-hour break rule implemented Escalation timeline: 3-6 weeks if no additional incidents Assessment: Additional incidents are inevitable. Adjust accordingly.
I looked at the final line for a long moment.
Additional incidents were inevitable. The 48-hour rule would reduce the correlation data, but it wouldn't eliminate my operational footprint entirely. Holland Manners was patient and methodical. He would wait. He would accumulate. And eventually, he would have enough to move from review to investigation.
"His timeline for escalation from review to investigation: 3-6 weeks if no additional incidents. Additional incidents: inevitable. Adjust accordingly."
The words sat on the page like a countdown.
I resolved to run no adjacent operations in Wolfram & Hart coverage zones for the next three weeks. No exceptions. No rule-breaking. Strict operational discipline until the Holland Manners situation either escalated beyond my control or cooled to the point where I could resume operations.
Three weeks.
I made it twelve days.
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!