Chapter 9
TOMMY
Something changed after the gym. The shift is small enough that someone who doesn't monitor behavioral data for a living would miss it entirely. I do monitor behavioral data for a living. The delta between pre-gym Dar and post-gym Dar is registering across every sensor I have.
She started using my coffee mug. Not asking.
Not acknowledging. Just picking it up from my workstation, refilling it from the pot, and drinking from it while she works.
The mug is ceramic, dark blue, with a ring stain that has become permanent through years of neglect, and it is mine in the way that objects in a shared space become proprietary through sustained use. She knows it's mine.
She uses it anyway.
The transgression is so small, so deliberately casual, that calling attention to it would reveal more about my reaction than her intention.
The vulnerability she exploited to deliver the warning is now sealed, reinforced with a verification layer that accounts for the exact load distribution technique she used.
The new protocol is better, tighter, more resilient, and if I'm honest about the design process, which I should be given that honesty is apparently the currency of 1 AM gym conversations, the protocol is built to withstand the way Dar approaches a system.
I'm designing against her mind. Learning the shape of her thought process and building defenses calibrated to it, which means I'm learning her, and the learning is happening through the medium I understand best, and the intimacy of studying someone through their code is something I should probably examine more carefully and absolutely will not.
The banter has sharpened. Where the first days were adversarial, all sharp edges and territorial markers, the verbal sparring has developed texture.
Dar's humor surfaces more frequently now, dry and unexpected and usually aimed at herself, and when it meets mine at speed, the collision produces something that makes Sarah glance sideways and pretend she didn't hear.
She's been at her station since before I arrived this morning, and the evidence is written in the details.
Three empty Mountain Dew cans lined up with military precision.
A hoodie sleeve pushed to her elbow, exposing the tendons in her forearm.
The faint indentation on her cheek from resting it against her fist while she worked through a problem.
I cataloged each detail as I sat down, the same way I catalog environmental variables during a systems check, automatic and thorough.
The warmth that accompanied the cataloging was neither automatic nor thorough.
It was specific and inconvenient and aimed entirely at the woman drinking from my coffee mug.
"Your variable naming conventions are an act of war.
" Dar says this without looking up from her screen, deep into a session that started before dawn and shows no signs of stopping.
The workspace hums with the combined output of both our systems, and the air between our stations carries the mixed scent of cold coffee and Mountain Dew and the ozone signature of hardware running hot.
"My variable naming conventions are poetry. You're just not literate."
"You named a sorting function 'Gandalf' because it, quote, shall not pass bad data. That's not poetry. That's a cry for help."
"It's a perfectly functional naming convention that communicates intent while maintaining developer morale. Gandalf is a reference the whole team understands. If I named it 'optimal_recursive_sort_v3,' Stryker would think I was having a stroke."
"Stryker doesn't read your code."
"Stryker doesn't read anything that doesn't come with a caliber rating, but that's not the point. The point is accessibility. Code should communicate with the people who maintain it."
"Code should communicate with the machines that run it. People are temporary. Machines are infrastructure."
"That's the bleakest thing you've ever said, and yesterday you described sunlight as 'an unnecessary environmental variable.'"
Her mouth does the thing, the almost-imperceptible lift at one corner that isn't a smile but is the closest she comes when she's not trying. A micro expression that lasts less than a second and rewires something in my chest every time I cause it.
She's leaning back in her chair with one boot propped on the edge of her desk, and the position shows the line of her throat above the collar of her hoodie.
I track the line before I can stop myself and store the image alongside every other image of Dar that's been accumulating in a folder my brain created without authorization: the gym doorway with her hand gripping the frame, the server room with the cold light on her cheekbones, the communal area where she sat alone at the edge of my team's table and didn't know I was memorizing the exact way loneliness sits on her shoulders.
She catches me looking. Her fingers, which have been tapping a rhythm against her boot, go still for a fraction of a second, then resume.
The pause is her tell, and the fact that I read it and she knows I read it and neither of us says anything about it creates a tension in the workspace that has weight and texture and a temperature significantly higher than the thermostat setting.
I adjust the workspace lighting. The overheads are set to a warm spectrum that I modified days ago because I noticed Dar squinting under the standard cool whites, and the adjustment is subtle enough that she hasn't mentioned it but significant enough that her eye strain has visibly decreased.
I leave a Mountain Dew at the edge of her workstation. I position the dark chocolate within reach of both our stations, a shared resource that serves as a neutral territory marker.
I tell myself these are efficiency optimizations, environmental adjustments designed to maximize productivity during a critical development phase, and the lie gets thinner every day.
The truth is that I'm engineering her environment. Building a space around her that accounts for her preferences and anticipates her needs and keeps her comfortable in ways she didn't ask for and hasn't noticed.
The lighting is for her. The Mountain Dew is for her. The temperature I adjusted in the workspace yesterday because I noticed goosebumps on her forearms when the ventilation kicked into its cooling cycle, that was for her.
I am constructing a system designed to make Dar's life easier, and the system is invisible, and the invisibility is the point, because visible care requires a conversation I'm not ready to have, and invisible care lets me keep building without anyone asking why.
The darker truth underneath the lie: I like it. The engineering. The quiet control of shaping her space without her permission. Every adjustment is a small claim, a tiny territorial marker that says I was here, I saw what you needed, I handled it.
The Mountain Dew is a twelve-ounce act of possession disguised as a caffeinated beverage, and the fact that she takes it without thanking me, the fact that she drinks from my coffee mug without asking, the fact that she occupies the workspace I designed around her as if she belongs there, creates a feedback loop that satisfies something in me I didn't know was hungry.
Victoria's intel about the Committee's retaliatory strategy has been sitting in my chest for two days, the pressure of knowing this weapon is personal compounding with the pressure of Dar's proximity and the marathon work sessions and the fact that my defenses need to be rebuilt from scratch against a weapon designed to destroy them.
Webb aimed at me. At my systems. At the thing I contribute to a team full of people who contribute with their bodies and their tactical capability and the physical courage to walk through doors I've never walked through.
Webb decided the way to break Echo Ridge was to break the one thing I built, and the targeting is as personal as a letter addressed by name.
The workspace is quiet except for our keyboards when Dar's fingers stop.
Not a pause but a full stop, the dead stillness that I've been learning to read as the absence of signal rather than the signal itself.
"Tommy."
I look up. Her face is different, the color consolidated inward, leaving her skin tight across the cheekbones and her eyes fixed on her screen with the intensity of someone who is reading something they wish they hadn't found.
"What."
"Come here."
I roll my chair to her station. Her screen displays a code analysis window, dense with highlighted blocks and dependency trees and the visual representation of the Committee weapon's internal structure that we've been mapping for days.
She's isolated a new component, something neither of us has seen before, highlighted in red because her analysis flagged it as critical.
"This is the framing module." Dar's voice is flat, clinical, stripped of everything except the information. "The weapon isn't just designed to attack your systems. It's designed to replicate your coding signature while it does it."
The words take a moment to resolve. I lean closer to her screen, close enough to see the code she's isolated, and the code is familiar in a way that makes my stomach drop because I recognize elements of it.
Variable naming patterns. Structural choices. The way I nest conditional logic and the spacing I use between function blocks. The code reads like mine.
It isn't mine, but it reads like mine with a fidelity that suggests someone spent considerable time studying my actual output.
"A frame job."
"A sophisticated one. When this weapon deploys, the evidence trail leads back to your station.
Your encryption keys. Your access credentials.
The logs will show that your systems initiated the breach, and the coding style in the attack payload will match yours closely enough that forensic analysis would take weeks to distinguish it from authentic output. "
"Someone studied my code."