Chapter 169
Ellie's POV
3:47 AM. My eyes burned from staring at three monitors simultaneously—left screen displaying the Martinez project's completed authentication module, center screen running encryption protocols for the werewolf dark web, right screen open to an increasingly detailed email chain about delivery schedules.
Subject: Final Acceptance & Delivery Timeline - Action Required
Ms. Green, congratulations on passing regression testing. We're ready to schedule the client acceptance meeting and technical handoff session. Please confirm your availability for next Wednesday's final presentation and Q&A. Our executive team will be present.
I rubbed my temples, feeling Thalia stir restlessly beneath my skin.
Lily and I had already finished the Martinez platform—the code was solid, testing complete, ready for delivery. But "delivery" meant hours of client presentations, technical deep-dives, documentation walkthroughs, answering executive questions about architecture decisions. Time I desperately didn't have.
The werewolf communication network wasn't just a class project anymore. After Samantha's breakdown, after watching a human mind shatter from exposure to our world, I understood with brutal clarity: we needed this. Our entire community needed safe, untraceable ways to coordinate and protect each other.
But Martinez Cybersecurity Solutions needed their acceptance meeting. The professional handoff I'd contractually agreed to. The human world obligations that didn't pause just because I'd discovered a higher calling.
I needed someone I could trust completely. Someone who understood the Martinez platform as well as I did. Someone who could handle client-facing technical communication without me.
Lily.
Eight AM. I found her in our tiny dorm kitchenette, hair in a messy bun, pouring coffee with the precision of someone who hadn't slept well either.
"Morning," she said, eyeing my obvious exhaustion. "Rough night?"
"Lily." I set down my mug, deciding directness was better than buildup. "I need to ask you something big."
She turned, immediately alert. "Okay..."
"I need to focus completely on a personal project. Something really important and time-sensitive." I met her eyes. "I want you to take over as primary contact for the Martinez project. All the client meetings, progress reports, needs gathering. And the technical demo next Wednesday."
Lily literally stepped backward. "What? Ellie, I—no. I can't. I only write code! I get nervous when professors call on me. You want me to present to actual corporate clients?"
"Yes."
"I'll literally die of anxiety. I hate making PowerPoints. I don't understand business terminology. What if my brain just blanks under pressure? What if I say something stupid? What if—"
"Lily." I kept my voice calm. "Give me ten minutes. Let me show you why I think you're completely capable of this."
She crossed her arms, skeptical but listening.
I pulled out my phone, opened our message history. "Two weeks ago, when we first discussed the dark web architecture. You researched everything, drew diagrams, explained onion routing to me using the 'package wrapped in layers' analogy. That's literally 'translating complex tech for non-technical people.'"
Lily opened her mouth to argue.
"Last week," I continued, "group discussion about zero-knowledge proofs. You caught my mistake, patiently corrected me, used the 'proving you can solve a problem without revealing the answer' example. Megan said you explained it better than Professor Paulsen."
I scrolled further. "And this—your GitHub issue on that open-source encryption project. Professional language, clear logic, pinpointed a critical vulnerability. The maintainer specifically thanked you. That's expert technical communication."
"But those were written," Lily protested weakly. "Face-to-face video calls are completely different. I'll stutter. I'll look awkward. I won't know where to look—"
"You already have the hardest part," I interrupted. "Genuinely understanding the technology and clearly expressing your thoughts. Everything else—meeting protocols, presentation skills, managing nerves—those can be practiced." I leaned forward. "I'll prep all the technical documentation. I'll create the demo outline. I'll rehearse with you until you feel confident. I just need you to be the voice, the face. Because I literally cannot focus on two directions at once."
Lily was silent, conflict written across her features.
"Why now?" she asked quietly. "What's this personal project that's so urgent you'd hand off something this important?"
The question hit like a physical blow. Thalia stirred, warning flooding my instincts. Pack secrets. Can't tell. Survival depends on silence.
But Lily was my friend. My partner. Asking her to step into fire without explanation felt wrong.
"It's..." I chose my words carefully. "A project about digital privacy protection and vulnerable community safety. It involves some very sensitive and complex situations." I held her gaze. "I genuinely can't explain details yet. Not because I don't trust you, but because it involves other people's safety and confidences I have to keep."
Her expression shifted—hurt, but considering.
"I can promise you," I said, "it's about protecting people's physical safety and futures. If it wasn't genuinely critical and urgent, I wouldn't be making this choice." I let her see my sincerity. "Will you help me? Not because I'm asking, but because I actually need someone I completely trust who's completely capable."
Lily stared at me for what felt like forever. Then she took a deep breath.
"Okay," she said slowly. "But you have to promise—when your project is done, you'll tell me as much truth as you can. I hate being kept in the dark."
Relief flooded through me. "Deal. Thank you, Lily. Seriously."
---
That afternoon, I officially emailed the Martinez project manager, introducing Lily as "primary technical liaison" while I transitioned to "backend development support." Then I spent three solid hours preparing her.
We broke down the network security training platform's complex architecture into clear module diagrams. Translated technical jargon into business value. Created clean, professional slides. I even showed her how to handle questions: "If you're uncertain, just say 'I'll confirm that and get back to you with accurate information.' Never guess."
Her first practice run was rough—shaky voice, forgotten points, couldn't look at the webcam. But by the fifth attempt, after my patient "try again, just slower this time," she delivered the core content smoothly and completely.
"If I screw this up next week," Lily said, wiping sweat from her forehead, "you're cleaning up the mess."
I squeezed her shoulder. "You won't screw up. And even if something unexpected happens, we'll figure it out together. You're not alone."
After she left, I closed every Martinez-related window and document. Opened the werewolf dark web core code editor fullscreen. The monitor filled with dense encryption algorithms, node configurations, moon phase synchronization protocols.
For the first time in weeks, I felt completely, purely focused.
My phone vibrated. Jackson: Council approved the dark web proposal. Several elders want to see a demonstrable prototype ASAP. Time's tight. Pressure okay?
I took a deep breath, typed back: Just got the human world stuff properly delegated. Can go full speed now.
I cracked my knuckles, pulled up the Tor network integration code, and got to work.
We're building sanctuary, Thalia whispered. Our pack will be safe.
Yes. And I wasn't doing it alone anymore. Lily would handle the human world. Jackson had my back in the werewolf one. The Council was invested. Miles was preparing.
I'd learned something crucial: True strength wasn't carrying everything myself. It was knowing who to trust, when to delegate, and how to focus where I was most needed.
The code compiled successfully. Green text scrolled across the screen: Initial encryption layer validated. Proceeding to distributed node deployment.