Chapter 16 : THE GATEKEEP
[Gate Control Room — Level 28 — Day 15, 2000 Hours]
Walter Harriman's workstation was the nerve center of the most classified facility on Earth, and it looked like a tax accountant's cubicle.
Three monitors arranged in a tight semicircle. A keyboard worn smooth at the E, T, and A keys. A mug that read "World's Best Gate Tech" — someone's idea of a joke that Walter had adopted without apparent irony. Sticky notes in precise columns along the monitor bezels, each one a gate address or procedural reminder written in handwriting so uniform it could have been typeset.
I stood behind his chair while he walked me through the data set he'd compiled — and the more I saw, the more I understood that Walter Harriman was either the most underutilized asset in Cheyenne Mountain or the most dangerous one.
"Gate activation frequency over the past ninety days." He pulled up a spreadsheet that covered three screens. "Cross-referenced with mission outcome reports, resource expenditure logs, personnel deployment records, and medical post-mission assessments. I've been compiling this on my own time."
The data was immaculate. Every gate activation timestamped to the second. Every mission tagged with outcome classification — success, partial success, failure, abort, casualty event. Resource expenditure tracked per mission: ammunition, medical supplies, equipment, naquadah fuel for dialing. Personnel utilization rates calculated to decimal points I hadn't asked for and wouldn't have thought to request.
"Walter, this is—" I stopped. Restructured the sentence. "This is exactly the kind of integrated analysis I've been trying to build from incomplete departmental reports. How long have you been tracking this?"
"Fourteen months, sir." He adjusted his glasses — a quick push at the bridge with his index finger, precise and habitual. "Since the gate program expanded beyond the initial exploration phase. I sit at the dialing computer for every activation. I see every team go out. I see them come back. Or I see them not come back." He paused. "The data tells stories that the individual reports don't."
"What stories?"
He minimized the spreadsheet and opened a second file. A pattern analysis I recognized immediately — the same kind of correlation modeling I'd built at Raytheon for supply chain optimization, adapted for military operations through an alien portal.
"Mission casualty rates correlate with preparation time. Teams with less than four hours of pre-mission briefing have a seventeen percent higher casualty rate than teams with six or more hours. Equipment failure rates spike during weeks three and four of deployment rotations — maintenance cycles aren't aligned with operational tempo." He clicked through three more slides. "And resource allocation for gate operations is based on a formula from 1994 that assumes four active teams. We have twenty-two."
I leaned closer to the screen. The inefficiencies bloomed like bruises under Walter's analytical light — the same kind I'd been mapping with the system's holographic interface, but documented from the human side, with human data, in a format any military auditor would accept without question.
"He's been building an intelligence product in his spare time. Not because anyone asked him to. Because he's the kind of person who can't sit at the crossroads of information and not try to make sense of it."
The system text confirmed what I already knew:
[SGC PERSONNEL IDENTIFIED: SERGEANT WALTER HARRIMAN — GATE OPERATIONS CHIEF — HERO POTENTIAL: RATING C (INTELLIGENCE/ADMINISTRATION) — RECRUITMENT VIABILITY: HIGH]
"Sergeant." I straightened. The gate control room was quiet — the night shift technician sat forty feet away, monitoring standby protocols, earbuds in. Private enough. "What are you offering me?"
Walter's expression didn't change. The same mild, competent mask he wore for every gate activation, every off-world crisis, every routine dial-out. But his shoulders shifted — a fraction of an inch downward, the release of tension from muscles that had been carrying something for a long time.
"I'm offering you what I've been offering every department head who'll listen for the past year. Integrated operational intelligence. Pattern analysis that could save lives and resources. A communications hub that connects gate operations, mission planning, logistics, and medical into a single coordinated picture." He adjusted his glasses again. "Nobody's been interested. They see me as the man who pushes the button. Not the man who watches what happens after."
"I'm interested."
"I know, sir. That's why I brought you the data."
The words sat between us like a handshake neither of us had offered yet. I pulled the second chair from the adjacent workstation and sat down beside him.
"I'm building something, Walter. Not against SGC — for it. Better coordination, better intelligence, better outcomes. The extraction operation on P3X-797, the expansion proposals I've submitted to Hammond — they're all pieces of a larger framework. Strategic Resources Division. If Hammond approves it, it'll be the organizational structure that connects everything this base does into a coherent strategy."
"And you need someone at the center of the information flow."
"I need someone who sees what you see. Someone who sits at the crossroads and notices when the patterns shift." I met his eyes. "I need someone who's been waiting for someone to ask the right questions."
Walter was quiet for ten seconds. Not hesitating — processing. Running the proposal through the same analytical framework he applied to everything else. Cost-benefit. Risk assessment. Outcome projection.
"What would you need from me specifically?"
"Gate traffic monitoring with purpose. Mission outcome correlation fed to me in real time. Resource flow tracking across all SGC operations. Personnel deployment patterns flagged for inefficiency or risk." I leaned forward. "Nothing outside your existing duties. You already collect this data. I'm asking you to direct it."
"You're asking me to be your intelligence officer."
"I'm asking you to be what you already are. Just with someone who'll actually use what you produce."
His glasses caught the monitor light as he turned back to his screens. The gate activation log scrolled silently — addresses, timestamps, team designations, a river of data flowing past the man who'd been watching it for fourteen months and building a picture nobody else had bothered to look at.
"I'll need access to your reporting chain," he said. "If I'm feeding you intelligence, I need to understand what you're doing with it. Trust goes both ways, sir."
"Agreed. Full transparency on how I use your analysis. And if you ever see something that concerns you — anything that suggests I'm not operating in SGC's best interest — you go straight to Hammond. No hesitation."
"That was always going to be the case, sir." The ghost of something that might have been humor crossed his face. "With or without your permission."
We spent the next two hours sketching the framework on Walter's second monitor — information flows, reporting templates, priority flags, communication protocols. Nothing that would raise eyebrows if someone looked at Walter's workstation. Just a gate operations technician optimizing his own systems, the same way he'd been doing for over a year.
The night shift technician yawned and refilled his coffee. The Stargate stood dormant in the room below, visible through the control room window — dark metal, quiet potential.
[HERO UNIT WALTER HARRIMAN — RECRUITMENT INITIATED — LOYALTY: 30% — ROLE: INTELLIGENCE/COMMUNICATIONS HUB]
"Four people now. Kawalsky for tactics, Daniel for knowledge, Siler for engineering, Walter for intelligence. Not a team yet. But the skeleton of one."
Walter saved the framework files and locked his workstation with a ten-character alphanumeric password that his fingers typed from muscle memory.
"Sir. The SG-1 mission report from P3X-888." He pulled a printout from beneath his keyboard — flagged, highlighted, already analyzed. "Contact with a possible Tok'ra operative. The gate address cross-references with three other reports I've tagged as potential non-Goa'uld symbiote encounters over the past six months."
I took the report. Scanned the summary. Jolinar. The name triggered a cascade of meta-knowledge — the Tok'ra, the resistance, the alliance that would take years to build in the original timeline.
Or months, if I positioned it correctly.
"Get me everything SGC has on the Tok'ra," I said. "Intelligence files, mission reports, Teal'c's debriefings. Anything with the word 'symbiote' that doesn't end in 'Goa'uld.'"
Walter nodded. Opened a new search query. His fingers moved across the keyboard with the quiet efficiency of a man who'd found his purpose.
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