Chapter 20: The First Machine
The Watcher rolled off the production line at 14:07 on day thirty-three, and Nakoa kicked it.
Not aggressively — a combat test. Her boot connected with the machine's flank at the joint between the forward leg assembly and the torso chassis, the precise point where field damage was most likely to occur. The Watcher stumbled, recalibrated, and resumed its patrol circuit without acknowledgment. No alarm. No aggression. The blue pulse of its scanning eye swept past Nakoa and continued across the Cauldron floor.
"Stable," she said. "Lighter than the wild ones. Faster, probably. Less armor." She crouched, examining the chassis where her boot had connected. "The joint reinforcement is thinner. A Scrapper could breach this in one good bite."
["The armor reduction was a deliberate trade-off,"] NEMEA-7's voice echoed through the production core. The Cauldron's internal speakers carried the AI's communication with a clarity that improved daily — each conversation refining its speech synthesis, the component sounds flowing more naturally. ["Patrol-optimized units prioritize speed, sensor range, and battery life over combat durability. The design philosophy is: detect and report, not engage and destroy."]
"Detection doesn't stop a war party."
["No. But twelve units providing continuous perimeter surveillance, coordinated through Beta's override network, create a detection web that makes surprise attack functionally impossible. The tactical advantage is information, not force."]
Nakoa straightened. Her assessment expression — the one I'd learned to read during weeks of sparring sessions where every failure was cataloged and returned as instruction — processed the AI's reasoning. Guerrilla thinking applied to machine capabilities.
"How fast can they relay an alert?"
["Speed of light through the communication network. Effectively instantaneous within a six-kilometer radius of the relay transmitter."]
Something shifted behind Nakoa's eyes. The tactical mind engaging with a new variable — not machines as weapons, which she'd been skeptical of, but machines as scouts. Mobile, tireless, immune to boredom and distraction, capable of maintaining watch through conditions that would degrade human sentries.
"Cavalry," she said.
"What?"
"In the old wars — the ones my clan's elders told stories of — cavalry wasn't about charging. It was about screening. Riding the flanks, probing enemy positions, falling back before contact. Mobile harassment." She touched the Watcher's chassis — the first time she'd voluntarily touched one of the machines. "These don't charge. But they screen. They probe. They fall back and report. Machine cavalry."
The warrior who'd been uncomfortable with machine allies just found the tactical framework that makes them make sense. Not by accepting them as equals, but by fitting them into a doctrine she already understood.
["The term is... evocative,"] NEMEA-7 said. ["I have not previously considered production output in equestrian terminology. This is a new preference."]
---
Eight days compressed into a blur of production, coordination, and the kind of logistical improvisation that no strategy game had prepared me for.
NEMEA-7's production line ran continuous cycles — the printer unit humming overhead, assembly arms working in coordinated sequences, each Watcher taking approximately eighteen hours from raw material intake to functional deployment. The capacity was limited by damage to the secondary fabrication line and the supply of specific alloys that the Cauldron couldn't synthesize from available materials. Twelve units in ten days. Not twenty. Not the overwhelming force that would make the Tenakth war party irrelevant.
In the game, machine production was a queue. Click, wait, deploy. In reality, each Watcher is a logistical puzzle: materials sourced from the Cauldron's diminishing reserves, programming loaded through Beta's override protocols, patrol routes designed by my strategic overlay and stress-tested by Nakoa's combat assessment. Every machine that rolls off the line represents hours of coordinated effort by five people and one AI.
Beta lived in the Cauldron for three days straight. Her Focus interfaced with NEMEA-7's production systems through the bridge she'd built during the partition, programming each Watcher with patrol algorithms, identification protocols, and the emergency response sequences that would determine how the machines behaved when fifty warriors arrived at the perimeter.
"The override architecture is holding," she reported on day thirty-five, her voice carrying the ragged edge of someone who'd been sleeping in two-hour increments on a Cauldron floor. "Each unit carries a base behavioral package — patrol, detect, report, evade. Combat engagement requires a direct command from the overlay or from my Focus. They won't attack autonomously."
"Why not?"
"Because autonomous combat machines are what HEPHAESTUS built, and we're not HEPHAESTUS." She rubbed her eyes — the exhaustion visible in the shadows beneath them, the slight tremor in her hands that three days of caffeine-free technical work had produced. "These machines serve us. They don't decide who dies."
The ethical constraint she'd built into the code — machines as tools, not weapons. The same principle that had governed her water system design: function in service of human choice, not function replacing it.
I pulled her away from the console at hour sixty-four. Literally — took her hand, closed the Focus, and walked her to the storehouse where a bedroll and a meal of smoked fish waited. She protested with the specific indignation of an engineer interrupted mid-calibration, then fell asleep before finishing the fish.
The settlement's needs didn't pause for the Cauldron operation. Geras managed Redhorse in my absence — the intelligence chief stepping into an administrative role that tested capabilities he'd spent twenty years suppressing in favor of tradecraft. He handled it with the quiet competence of a man discovering that organizing a settlement wasn't fundamentally different from running a network of informants: tracking resources, managing personalities, ensuring that the right information reached the right people at the right time.
"The food situation is manageable but not comfortable," he reported through the long-range Focus link on day thirty-four. "Jenna's gathering crews are efficient, but twenty-seven mouths and shrinking rations require either trade or expanded foraging range. We're two weeks from rationing if nothing changes."
"Carja trade?"
"Tavan's consortium won't cycle back for another month. We could send a delegation south to meet them, but that pulls people from construction."
Tradeoffs. Always tradeoffs. Feed the population or finish the walls. Build machines or stockpile food. Every resource allocated to defense is a resource not allocated to sustainability.
"Split it. Send two of Jenna's crew south with machine parts for emergency trade. The rest continue local foraging. And tell Marek to prioritize the southwestern wall section — that's the Tenakth approach vector."
"Already done." A pause. "I anticipated your priorities."
He's learning to lead. Not because I taught him — because the necessity taught him, the way it teaches everyone who stays long enough.
Nakoa's contribution was the doctrine. She spent the days between production runs designing patrol routes, response protocols, and the formation of machine-human coordination that she'd dubbed "cavalry screening." The concept was elegant: Watchers on the perimeter provided continuous surveillance, relaying position data through the overlay to Nakoa's command post. Human fighters, positioned at key defensive points, responded to machine alerts with targeted force. The machines detected; the humans decided.
"Twelve machines cover the primary approach corridors," she briefed on day thirty-six, using charcoal on stone to illustrate the patrol patterns. "Four overlapping circuits on the eastern ridge, where the Tenakth will approach. Four on the flanks. Four in reserve, cycling between positions to prevent pattern recognition."
"The Tenakth will adapt."
"The Tenakth will see twelve machines and wonder how many more are behind the walls." She tapped the positions. "The display matters as much as the function. Fifty warriors who expect to overrun a settlement of outcasts will recalculate when they find machine sentries coordinating like a military formation."
The first Watcher to patrol Redhorse's perimeter deployed on the evening of day thirty-five. I stood on the watchtower platform and watched it cross the ridgeline in the fading light — a machine I'd helped build, following routes I'd designed, serving a settlement I'd founded. Blue scanning light swept the valley floor. The mechanical chirp — once the sound of danger in a dark forest — was now the sound of security.
Something I built from nothing, following my orders. In the old life, the closest I got to this feeling was watching a city grow in Civilization. This is different. This machine is real. The valley it patrols is real. The people it protects are real.
[Settlement development: 45%]
[Machine garrison: 8 (deployed) + 4 (in production)]
[Tenakth war party: estimated arrival in 4 days]
Twelve machines. Four humans. One AI. Against fifty warriors led by a marshal with decades of combat experience and a captain with a personal vendetta.
The arithmetic wasn't encouraging. But arithmetic didn't account for machine cavalry, thermal deception, intelligence operations, and the strategic creativity of a transmigrator who'd spent a lifetime winning unwinnable scenarios in games that had suddenly become real.
Nakoa joined me on the watchtower. She watched the Watcher complete its first circuit — the machine crossing the ridge with the measured stride of a purpose-built sentinel.
"Machines don't panic," she said. The words she'd spoken in the Cauldron, the observation that had transformed her skepticism into tactical appreciation. "They don't hesitate. They don't get scared or tired or distracted."
"No."
"That makes them better than most warriors I've commanded." She looked at me. The crossed-out clan marks on her forearms — loyalty burned out, replaced by something chosen — caught the last light. "And worse. Because a warrior who's scared still fights. A machine that's overwhelmed just stops."
"Then we make sure they're never overwhelmed."
"That's what I'm designing for." She pulled a stone from her belt — one of the patrol route diagrams — and held it up. "Four days. I need every machine operational and programmed. And I need you to stop sleeping more than four hours."
"Deal."
Four days. The countdown had started.
Want more? The story continues on Patreon!
If you can't wait for the weekly release, you can grab +10, +15, or +20 chapters ahead of time on my Patreon page. Your support helps me keep this System running!
Read ahead here: [ patreon.com/system_enjoyer ]