Chapter 37
Coffee, Code, And Quiet Threats
~ADRIAN~
The Binary Grounds looks like any other coffee shop from the outside.
Exposed brick, industrial lighting, the obligatory chalkboard menu listing drinks with pretentious names and even more pretentious prices. Located three blocks from the main paddock, it caters to the racing crowd during competition season and tech workers year-round.
But I know better.
The basement houses one of the best unauthorized server farms in the city, run by a collective of hackers who maintain strict neutrality in exchange for access and protection.
The private booths upstairs have Faraday cage shielding and dedicated fiber connections.
And the owner—a former cyber security specialist who got tired of corporate politics—doesn't ask questions about what customers do on those connections.
It's perfect for what I have planned.
Aurora walks beside me, dressed in her usual baggy clothes and masculine presentation. Rory Lane to anyone watching, but I see Aurora underneath, the Omega who's comfortable in both presentations depending on context and safety.
"A coffee shop?" she asks, one eyebrow arched skeptically. "This is your idea of a date?"
"Trust me," I say, holding the door open. "Tesoro, this is going to be better than any fancy restaurant."
The endearment slips out in Italian—my mother's language, spoken when emotions run too close to the surface for English to contain them properly.
Aurora's lips quirk into a smile that she tries to hide, following me inside.
The smell hits immediately—fresh-ground coffee beans mixing with the electronic ozone scent of overworked servers. A few patrons scattered throughout, most hunched over laptops with the particular intensity of people doing work they'd rather not explain publicly.
I guide Aurora toward the back, where the private booths offer both seclusion and the technical infrastructure I arranged earlier.
The booth is exactly as I requested: multiple screens already set up, power strips, dedicated fiber connection, and a stack of vintage race strategy notebooks that cost me a small fortune to acquire at auction.
The leather seats are worn but comfortable, and someone has already delivered the espresso I pre-ordered—proper Italian, not the American swill most places try to pass off as coffee.
"Oh," Aurora breathes, taking in the setup. "Oh, this is perfect."
The genuine delight in her voice makes warmth bloom in my chest.
"Sit," I encourage, sliding into the booth beside her—close enough that our thighs touch, that I can smell her smoke-and-vanilla scent mixing with mine. "We're going to go through telemetry data and compare your gut-feel racing lines to what the numbers actually show."
Her eyes light up with the kind of excitement most people reserve for expensive gifts or romantic gestures.
But this is romance in my language.
Shared technical work, diving deep into the details that most people find tedious, finding intimacy in collaborative problem-solving.
I pull up the telemetry from her last race, overlaying it with the ideal racing line calculations that our AI systems generated.
"See here?" I point to Turn Seven. "Your instinct is to apex slightly earlier than optimal. But look—" I zoom in on the data, "—that early apex costs you about point-three seconds on corner exit because you can't get back on the throttle as aggressively."
Aurora leans in, studying the screens with focused intensity.
"But if I apex later, I risk running wide on exit and losing time on the following straight."
"Not with your driving style." I pull up comparative data from Luca's runs.
"He needs the later apex because he's more aggressive on initial turn-in.
But you're smoother, more progressive with your inputs.
You can hold a later apex without the exit issues because your throttle application is more gradual. "
We fall into easy rhythm—analyzing corners, discussing strategy, debating the merits of different approaches with the kind of technical detail that would bore most people to tears.
But Aurora is fully engaged, asking intelligent questions, challenging my assumptions, offering insights from the driver's perspective that raw data can't capture.
"Can we customize the steering and brake bias settings?" she asks after we've been at it for maybe an hour. "I feel like the car is fighting me slightly in high-speed direction changes."
"Absolutely." I pull up the configuration interface, making a mental note of the satisfaction coursing through me at her trust. "Talk me through exactly what you're feeling."
She describes the sensations with precision—the slight delay in response, the way the car wants to understeer before suddenly oversteering, the particular vibration through the wheel that suggests the front tires are working harder than the rears.
I translate her words into technical adjustments, tweaking parameters in real-time while explaining what each change will do.
"Try that next session," I say finally, saving the custom configuration. "If it's still not right, we'll keep adjusting until it feels perfect."
Aurora's smile is radiant.
"This is amazing. I've never had someone take the time to actually listen to what the car feels like and translate that into settings."
The comment makes something in my chest tighten.
Because this is what I love—using my technical knowledge to help drivers succeed, to eliminate the barriers between their instincts and the machine's capabilities. Making their jobs easier, safer, more successful through obsessive attention to details.
"I once caused a crash by missing a small data anomaly," I hear myself saying, the confession emerging before I can stop it.
Aurora's attention shifts from the screens to me, those storm-green eyes going soft with concern.
"It was three years ago. Different team, different driver.
" I take a sip of espresso, needing something to do with my hands.
"I was reviewing telemetry data from practice sessions, looking for optimization opportunities.
And I missed it—a tiny fluctuation in the suspension damping rates that suggested a mounting bolt was working loose. "
The memory is vivid despite my attempts to bury it. The sound of impact. The way the car disintegrated. The agonizing minutes waiting to hear if the driver survived.
"He lived," I continue quietly. "Broken ribs, concussion, ended his season but not his career. But it could have been so much worse. And it was my fault for not catching the anomaly when I had the data right in front of me."
Aurora's hand finds mine on the table, squeezing gently.
"Is that why you don't drive?" she says slowly, understanding dawning. "Even though you have the skill and competence."
"Sì." I turn my hand to interlace our fingers. "I'd rather sponsor and support drivers' dreams from the sidelines. Be the one ensuring their equipment is perfect, their data is accurate, their success is maximized. Especially in a field that crucifies people before giving them a chance."
I meet her eyes, letting her see the guilt and determination that drives me.
"The current sabotage secretly terrifies me," I admit.
"Because I don't want any driver to feel forced into actions beyond their control.
Someone sitting behind a computer, messing with them out of jealousy or spite or whatever fucked-up motivation they have.
It's cowardly. And if someone is smarter than me in code, we're dealing with a very serious opponent. "
I pause, considering.
"But I've always been able to figure things out eventually. Given enough time and resources, I can track anyone, break any encryption, find any digital footprint."
Aurora is quiet for a long moment, her thumb tracing circles on the back of my hand in soothing patterns.
"Maybe we're not looking at all the possibilities," she says finally.
I frown.
"What do you mean?"
"The obvious individuals are Richard and Dante," she explains, her voice dropping even though the booth is shielded. "But maybe that's the point. They're too obvious. Yeah, Marco too, but again—it could be someone we least expect."
The observation cuts through my assumptions with uncomfortable accuracy.
She's right.
I've been focusing on the apparent suspects, the people with clear motive and opportunity. But what if that's exactly what someone wants? What if the real threat is hiding in plain sight, using our focus on obvious targets as cover?
"Someone we trust," I say slowly, running through possibilities. "Someone with access who wouldn't raise suspicions."
"Or someone who seems incompetent. Or uninterested in racing politics." Aurora's expression is thoughtful. "Someone who—"
My phone buzzes in my pocket, cutting her off.
I pull it out reflexively, expecting a message from Elias or an update from one of my security consultants.
Instead, I find a text from an unknown number.
The first attachment loads before I can stop it—a screenshot showing our current location. The Binary Grounds, this specific booth, time-stamped from maybe five minutes ago.
We're being watched.
Right now.
The second attachment makes my blood run cold.
It's a photo of Aurora—unconscious, tied up in the back of a vehicle. The image quality is slightly blurred but unmistakable. From the kidnapping, hours before hitting heat, and being transported to god-knows-where before we intercepted.
Someone has photos from that incident.
Photos that should have been destroyed or secured by the Lane family's cleanup crew.
The accompanying message appears below the images:
"Omega drivers are easy to replace. Pack Alphas are easier to break."
The threat is clear. Explicit.
They're not just watching Aurora—they're willing to hurt her, willing to target the pack, willing to escalate beyond sabotage into actual violence.
And they have resources that suggest serious organization behind this.