Chapter 29 : THE EXPANSION PLAN
[SRD Planning Room — Level 25 — Day 30, 0900 Hours]
Martouf's intelligence map covered the conference table in blue-lit holographic projection — Tok'ra technology that Carter had interfaced with the SGC's display system three days ago, creating a visual hybrid that looked like someone had spilled alien starlight across military-grade hardware.
Three worlds glowed amber against the blue field. Three gate addresses. Three opportunities.
"P5C-353." Martouf touched the first marker, expanding it into a terrain overlay. "Abandoned Goa'uld mining complex, similar to your P3X-797 operation but with deeper naquadah seams and evidence of trinium co-deposits. Last Goa'uld activity: approximately forty years ago. Current threat assessment: minimal — one patrol circuit passes within two light-years every thirty-eight days."
"P2X-887." Second marker. "Agricultural world with strategic position relative to three known gate routes. Defensible terrain — mountain valley with natural chokepoints. No Goa'uld infrastructure, but the soil composition suggests terraforming potential consistent with the work you've begun on P4X-221."
"P6Y-112." Third marker, pulsing differently — gold instead of amber. "This one is... unusual. Tok'ra scouts reported Ancient ruins on the northern continent. Pre-Lantean era, possibly dating to the earliest period of gate network construction. Our analysts believe it may contain intact technology or data repositories."
The room held five people and one hologram. Kawalsky sat at the table's head, arms crossed, assessing each target through the lens of security requirements and personnel costs. Walter monitored from his laptop, cross-referencing the Tok'ra data against his gate traffic database for corroborating signals. Rothman — two days into his new position and already buried in artifact reclassification — had been pulled from his crystal analysis to provide archaeological perspective on P6Y-112. Martouf stood beside the display, the professional composure of a diplomat masking whatever Lantash was thinking beneath the surface.
I stood at the whiteboard, dry-erase marker in hand, mapping the three targets against resource availability.
"Current resource status." I wrote the numbers. "Naquadah stockpile: four hundred twenty units. Trinium: eighty-four. Daily generation from two territories: fifteen NQ, three TR, ten food. Personnel: SRD has six members plus Martouf and Teal'c in advisory roles. SGC has eighteen operational SG teams — down from twenty-two after the attack, four teams rebuilding from casualties."
The numbers sat on the whiteboard like a budget review. Which was exactly what they were — the same kind of resource allocation analysis Andrew Callahan had performed for Raytheon's project portfolio, adapted for interstellar territory management.
"Claiming all three brings us to five territories," I continued. "That's halfway to the network bonus threshold — at five connected territories, the system enables resource sharing across nodes, increasing efficiency by ten percent."
I didn't mention the broadcast threshold. At ten territories, the system would initiate a galactic recognition broadcast — effectively announcing Earth's territorial claims to every faction with the technology to receive it. That was a bridge I'd cross when the foundation was solid enough to support the attention.
Kawalsky leaned forward.
"We can claim them. The question is whether we can hold them." His voice carried the practical weight of a man who'd spent his career translating strategic ambitions into tactical realities. "Each territory needs a minimum security rotation — four-person team, two-week cycles. That's twelve additional personnel for three territories. Plus engineering support for development, logistics for supply, and contingency for emergencies."
"We don't have twelve people," Walter said from his laptop. "Not without pulling from existing SG team rotations, which O'Neill won't authorize without Hammond's direct order."
"Then we need to grow." I tapped the whiteboard. "The attack demonstrated what happens when we're undermanned. But it also demonstrated what happens when we're organized — eighty-three people evacuated successfully because we had a second territory to send them to. Hammond understands that. He approved the division because he saw the value of what we've built."
"Seeing value and authorizing personnel are different conversations," Kawalsky said.
He was right. The gap between strategic vision and operational reality was the same gap I'd navigated at Raytheon — the distance between what the project needed and what the budget allowed. The solution there had been phased execution: deliver results in stage one, use those results to justify resources for stage two.
"Phased approach." I wrote three columns on the whiteboard. "Phase one: P5C-353. Mining world, closest analog to P3X-797, proven operational model. We use existing SRD personnel plus one borrowed SG team for the claim mission. Once the territory is generating resources, we use those resources to justify personnel expansion for phase two."
"Phase two: P2X-887. Agricultural-strategic. By then, the P5C-353 yields should demonstrate enough value that Hammond approves dedicated security personnel — not SG teams on loan, but permanent territorial defense assignments."
"Phase three: P6Y-112. Research priority. This one requires Rothman's expertise and Daniel's collaboration for the Ancient ruins assessment. We time it for when the other territories are self-sustaining enough to free up engineering and security resources."
"Timeline?" Martouf asked.
"Six weeks for all three. Two weeks per claim, staggered to allow resource and personnel reallocation between phases."
Rothman raised his hand — the gesture of a man still accustomed to academic seminars rather than operational briefings.
"The Ancient ruins on P6Y-112. If they contain intact data repositories, the archaeological value alone justifies priority over the mining and agricultural targets. We could learn more from one functioning Ancient database than from—"
"Fifty years of naquadah extraction?" Kawalsky's voice wasn't unkind, but it carried the specific authority of a soldier who'd learned that knowledge didn't stop staff weapons. "The ruins aren't going anywhere, Doc. The personnel shortage is happening now."
Rothman deflated slightly. I stepped in.
"Robert's right about the potential value. But Kawalsky's right about the sequencing. We mine first because mining pays for everything else — security, development, research. P6Y-112 gets the resources it deserves precisely because we funded those resources through P5C-353 and P2X-887."
Rothman nodded. The practical logic reached him through the academic disappointment — the look of a researcher learning that organizational priorities weren't about what mattered most but about what made everything else possible.
"Walter, I need a proposal document for Hammond by end of day. Resource requirements, personnel requests, timeline, risk assessment. Standard format — the general reads bullet points, not essays."
"On it, sir."
"Kawalsky, tactical assessment for each target. Security requirements, threat profiles, extraction contingencies. Coordinate with Martouf for Tok'ra intelligence integration."
"Already started." Kawalsky pulled a notepad from his desk — I caught a glimpse of handwritten tactical notes in the same military shorthand I'd been learning to read over four weeks. He'd been planning this before I asked.
"He's ahead of me. He's anticipating the mission before the order. That's not a subordinate — that's a partner."
The thought caught me. Kawalsky's loyalty sat at forty-eight percent on the system's assessment — two points from the formal recruitment threshold. Two points from the moment when conditional trust became genuine commitment. And he'd just demonstrated the behavior of a man who'd already crossed that line in every way except the formal declaration.
"Martouf, coordinate with the Tok'ra for updated threat assessments on all three targets. If any of those patrol circuits shift, I want to know before we commit personnel."
"Understood. I will contact the High Council through the subspace relay."
The meeting dissolved into working groups — Kawalsky and Martouf at the tactical table, Walter at his laptop composing the Hammond proposal, Rothman gathering his files to continue the P3X-403 crystal analysis that might provide test data for the P6Y-112 approach.
I stood at the whiteboard and looked at the three columns. P5C-353. P2X-887. P6Y-112. Three worlds, each one a node in a growing network that would eventually — if everything held — become something capable of defending a planet.
"Andrew Callahan managed project portfolios worth ten to twenty million dollars. Drew Ramsey manages territorial expansion across light-years with a budget measured in alien minerals and a team of six people who still don't fully understand what I am."
"Same skill set. Different scale."
I caught myself using "we" again — in my head, not just in speech. The shift from singular to plural had happened without permission, the way organizational identity always formed when the work became bigger than any one person's capacity.
The whiteboard marker squeaked as I added the timeline: Week 1-2: P5C-353 claim and development. Week 3-4: P2X-887 claim and development. Week 5-6: P6Y-112 survey and assessment.
Below the timeline, I added a fourth line: Personnel expansion proposal — Hammond meeting, Day 32.
Five territories by month's end. Then ten. Then the broadcast, and everything that came after it.
The planning board on the wall — the one from P3X-797, my first territory, still marked with Siler's drill repair notes and extraction schedules from a lifetime ago — caught the overhead light. Twenty-three days between that board and this one. Between a supply closet and a division. Between one man with an alien headache and a team building something that might matter.
I pinned the three world designations to the planning board beside the P3X-797 operations notes.
The door opened. Janet stood in the corridor, white coat over scrubs, the particular expression of a woman who'd decided something and was executing the decision with the same clinical precision she applied to surgery.
"Drew. Are you free for dinner? Somewhere that isn't the cafeteria this time."
Kawalsky's pen paused mid-stroke. Walter's typing stopped for exactly one second before resuming. Siler didn't look up, but the corner of his mouth twitched.
"I'd like that."
"Saturday. 1900. I'll text you the address." She paused. "You do have a phone, right?"
"I'll get one."
She disappeared down the corridor. The office resumed its rhythm — pens moving, keys clicking, the quiet machinery of an organization in motion.
Kawalsky's voice carried across the room, dry and deliberate: "You don't have a phone."
"I'll get one."
"You've been living in this mountain for a month without a phone."
"I've been busy."
"Get a phone, Ramsey."
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