Chapter 33 : THE ATTENTION
[SRD Office — Room 114, Level 25 — Day 35, 0900 Hours]
Martouf's expression was the one I'd learned to read as the Tok'ra version of we have a problem — composed, professional, with Lantash's deeper harmonic surfacing beneath the words like a bass note under a melody.
"Three minor System Lords have independently noted Earth's territorial claims." He stood at the conference table, data crystal projecting a political overlay across the tactical map. "Moloc, Yu, and Zipacna. Each maintains passive monitoring of gate network activity in their respective spheres. Your claims on P3X-797, P4X-221, and P5C-353 have generated detectable patterns in the network's transit logs."
Walter sat at his laptop, already cross-referencing the Tok'ra data against his own gate traffic database. The correlation appeared on his screen in overlapping datasets — SGC gate activations mapped against the timestamps when System Lord monitoring systems would have registered those activations.
"We dial specific addresses repeatedly," Walter said, adjusting his glasses with the push that meant he'd found something he didn't like. "P3X-797 gets three to four activations per week for crew rotations and supply shipments. P4X-221 averages two. P5C-353 has had six in the past five days during the claiming and survey operations. From a signals intelligence perspective, those patterns are—"
"Obvious." The word tasted like a mistake I should have caught. "We've been optimizing for operational efficiency. Direct routes, regular schedules, predictable transit windows."
"Standard military logistics," Kawalsky said from his desk. He'd been listening with the specific attention of a soldier hearing tactical intelligence that affected his team's safety. "Nobody optimizes for stealth when they're trying to build infrastructure. That's a different operational doctrine."
"It's the doctrine we should have been using from the beginning."
The admission cost more than it should have. Thirty-five days of building, planning, executing — and I'd missed a fundamental operational security principle that any intelligence analyst would have flagged in the first week. The system hadn't flagged it either. AURORA-7 understood Ancient technology and territorial development. It didn't understand twentieth-century signals intelligence because it had been designed for a civilization that had owned the gate network, not one that was trying to use it covertly.
"This is what happens when you're moving too fast. You optimize for speed and miss the threat you're building toward."
Martouf continued. "The System Lords are not yet concerned. Three territorial outposts are insignificant in galactic terms — minor powers claim and lose territory constantly. But pattern analysis among the more sophisticated intelligence operations — Yu's, specifically — could identify Earth as the common origin point for these claims within weeks."
"What's the threshold for concern?"
"Ten territories would trigger formal assessment by any System Lord with competent intelligence. Twenty would invite military response. The more immediate danger is that your gate traffic patterns allow someone to extrapolate your expansion rate and project future claims. If they calculate that Earth is systematically building a territorial network rather than claiming random targets of opportunity, the response comes faster."
I picked up the red dry-erase marker from the whiteboard tray. The word OPERATIONAL SECURITY went up in capital letters, underlined twice, positioned directly above the three-phase expansion timeline I'd drawn with such confidence six days ago.
"Walter, how quickly can we modify our gate protocols?"
Walter's fingers were already moving across his keyboard, the gate traffic database reorganizing itself under his touch.
"I can implement indirect routing within twenty-four hours. Instead of dialing P3X-797 directly, we route through two intermediate addresses — the transit adds eleven minutes per trip but masks the destination from passive network monitoring." He pulled up a routing diagram. "Same principle for all territorial addresses. We never dial the same intermediate twice in sequence. The pattern becomes noise instead of signal."
"Do it."
"There's a cost." Walter looked up from the screen. "Indirect routing increases gate activation count. More activations means more power consumption, more scheduling conflicts with standard SG team operations, and more data points for anyone monitoring the gate network's total activity rather than specific addresses."
"Trade-offs. Always trade-offs."
"What's the minimum additional activation load?"
"Approximately forty percent increase in total gate operations for territorial support. We can partially offset by consolidating supply runs — instead of three trips to P3X-797 per week, we run one larger shipment through a randomized route."
Kawalsky leaned forward. "Consolidated shipments mean larger material loads. Larger loads mean more personnel per trip. More personnel means—"
"More people exposed per transit event." I finished the chain. "If a shipment gets intercepted, we lose more per incident."
The operational security problem was a hydra — cut one vulnerability and two more emerged. Every solution created new trade-offs. Every trade-off required decisions about acceptable risk. This was the cost of growing, and it was a cost I hadn't budgeted for because I'd been building like a project manager instead of thinking like an intelligence operative.
"Martouf, can the Tok'ra provide counter-surveillance on the System Lord monitoring systems? If we know which addresses are being watched, we can route around them specifically rather than randomizing everything."
Martouf consulted with Lantash — the brief internal pause, the slight unfocus. "The Tok'ra can provide periodic intelligence on monitoring patterns. We cannot guarantee real-time coverage — our operatives have other responsibilities. But a weekly assessment of active surveillance on known gate routes is achievable."
"Weekly is enough. Walter, build the routing protocol around Tok'ra intelligence cycles. We update routes every seven days based on fresh assessment data."
"On it."
I stood at the whiteboard and erased the original expansion timeline. The optimistic six-week plan — three territories, sequential claiming, each financing the next — dissolved under the dry-erase cloth. In its place, I redrew the plan with security checkpoints built into each phase.
Phase one: complete. P5C-353 claimed, but restricted pending ECHO investigation. Phase two: P2X-887, but approached through indirect routing with counter-surveillance coordination. Timeline extended from two weeks to three. Phase three: P6Y-112, the Ancient ruins site — the one that required the most preparation and the most stealth, because Ancient technology would attract exactly the kind of attention they were trying to avoid.
Total revised timeline: nine weeks instead of six. Slower. Survivable.
"One more thing." I capped the marker and turned to face the room. The SRD office — five desks now, plus conference table, plus whiteboard, plus the P3X-797 operations board that still hung on the wall like a founding document — held the people I'd spent thirty-five days building into an organization. Kawalsky, steady and watchful. Walter, precise and purposeful. Siler, practical and competent. Rothman's empty desk — he was in the lab, dissecting ECHO's containment data.
Martouf, standing between them, the Tok'ra liaison who'd accepted an alliance because Earth offered ground to stand on.
"We made a mistake," I said. "I made a mistake. Moving too fast, optimizing for efficiency when we should have been optimizing for security. The expansion plan was good strategy and bad tradecraft. From now on, every operational decision goes through a security filter before it goes through an efficiency filter."
The room absorbed the admission. Kawalsky's expression shifted — not surprise, but the particular respect a soldier showed when a commander acknowledged an error without qualification or excuse.
"Mistakes happen," he said. "Good leaders catch them before they get people killed."
"This one almost did." The System Lord attention hadn't translated to military action yet, but it could. If Yu's intelligence apparatus traced the gate traffic patterns to Earth before the routing changes took effect, the next fleet that showed up wouldn't be Apophis with three ships. It would be a coordinated System Lord response with enough firepower to overwhelm even the Asgard's protected planet designation.
I wrote the revised timeline on the whiteboard. Below it, the security protocol framework. Below that, a single line:
We don't hide forever. We hide until we're strong enough to be seen.
The marker went back in the tray. The room returned to work — Walter building the routing protocol, Martouf composing a Tok'ra intelligence request, Kawalsky updating the tactical assessment for P2X-887's revised approach.
My phone buzzed. The Nokia brick, still new enough that the notification sound surprised me. A text from Janet:
"Got assigned to next offworld medical survey. Your territory. P4X-221. Coincidence?"
It wasn't a coincidence. Janet's medical expertise was needed on the agricultural territory to assess food safety protocols for the crops P4X-221 would eventually produce. I'd requested the medical survey two weeks ago. I just hadn't expected Hammond to assign Janet specifically.
"The woman I'm building a relationship with is about to visit a territory I claimed while fighting to hide those territories from alien empires that could destroy us."
"Compartmentalization is getting harder."
I typed back: "Not a coincidence. Bring sunscreen. Different star."
The reply came twelve seconds later: "Professional capacity only. But I expect the tour to include whatever passes for scenery on your alien farm."
I pocketed the phone and looked at the whiteboard. Revised timelines. Security protocols. An Ancient AI waking up beneath my mining operation. System Lords watching from the shadows.
And a doctor who'd kissed my cheek in a parking lot, heading to a world I'd claimed while an empire I'd provoked learned my name.
The office hummed with quiet industry. The mountain held its secrets. The gate waited below.
Drew Ramsey picked up the routing protocol Walter had drafted and began reviewing the first set of indirect transit calculations, because the next mission to P2X-887 couldn't afford the kind of mistake that had put them on three System Lords' radar.
The work continued. It always did.
Author's Note / Support the Story
Your Reviews and Power Stones help the story grow! They are the best way to support the series and help new readers find us.
Want to read ahead? Get instant access to more chapters by supporting me on Patreon. Choose your tier to skip the wait:
Noble ($7): Read 10 chapters ahead of the public.
Royal ($11): Read 17 chapters ahead of the public.
Emperor ($17): Read 24 chapters ahead of the public.
Weekly Updates: New chapters are added every week. See the pinned "Schedule" post on Patreon for the full update calendar.
Join here: patreon.com/Kingdom1Building