He exhales slowly. “This is going to cause problems.”
I look at her again, then back at the system display.
“Good,” I say.
Because that’s the point.
This structure has been built on force, maintained through pressure, and reinforced through repetition, and that works until it doesn’t. I can feel the shift starting, not complete and not stable, but real enough that it won’t stop once it moves.
CHAPTER 11
STACY
The base doesn’t feel like a place that runs on structure, and the longer I stand still long enough to observe it, the more that impression solidifies into something I can define.
It feels like a place that runs on pressure instead, where movement is constant but rarely intentional, and where urgency replaces clarity as the primary driver of decision-making. I don’t need a full operational cycle to see it, because the patterns begin revealing themselves almost immediately in the way people move, the way instructions are repeated, and the way no one questions anything out loud even when the inefficiencies are obvious. Every adjustment is reactive, every correction comes after the problem instead of before it, and that creates a system that functions, but only just.
They aren’t operating on efficiency.
They’re operating on fear.
I lean slightly against the edge of the console, keeping my posture neutral enough to avoid drawing unnecessary attention while still maintaining a clear line of sight across multiple stations. The data moving across the displays is clean and structured, but the way it’s being handled doesn’t match theprecision of the information itself, and that mismatch is where the real problem lives.
“You’re staring again,” one of the operators mutters, his tone edged with irritation he’s not quite willing to show openly.
“I’m learning,” I reply without turning toward him.
“From what,” he asks, his hands still moving across the controls.
“From what you’re not fixing,” I say.
That lands, not loudly, but visibly, because his hands pause for just a fraction of a second before continuing.
“You’ve been here five minutes,” he says.
“That’s long enough to see a pattern,” I reply.
He exhales through his nose, dismissing the comment outwardly, but the tension in his shoulders doesn’t disappear.
I shift my attention to another station, tracking the delay between input and response, the subtle lag that shouldn’t exist but does, and the way corrections are being applied after errors instead of preventing them.
“Why are you compensating here,” I ask, nodding toward the display.
The operator glances at me briefly. “Because that’s where the drop is.”
“That’s where you’re seeing it,” I correct. “Not where it starts.”
He frowns, his attention flicking between me and the console. “It starts upstream.”
“Then why are you fixing it downstream,” I ask.
He hesitates, and that hesitation tells me more than his answer would have.
“Because that’s how it’s done,” he says finally.
“That’s not a reason,” I reply.
“It’s the system.”
