FACTION BRIEF

Feral Tech

The Deep Dregs Machine Ecosystem

Type Environmental Hazard Origin Cascade', href: '/docs/world/systems/the-cascade Population Unknown (self-replicating) Status Active / Expanding Territory The Deep Dregs', href: '/docs/world/locations/the-deep-dregs Classification Autonomous Machine Ecosystem

The Deep Dregs is not abandoned. It is occupied — by machines that forgot they were supposed to stop.

When the Cascade hit in 2147, the Deep Dregs was a corporate logistics hub. Ironclad Industries ran warehouses, fabrication plants, and distribution networks through the sub-bay levels. Every surface had something networked to it: delivery drones queued on charging pads, maintenance nanobots circulating through ventilation systems, construction loaders parked in staging bays. Billions of devices, all connected, all receiving instructions.

Then the network died. Every device lost its control signal in the same seventy-two-hour window. No shutdown command was issued. No safe-mode protocol engaged. The machines simply stopped receiving instructions — and defaulted to whatever autonomous routine their firmware could manage.

That was thirty-seven years ago. The machines are still running. Residents call them "feral tech." The term is accurate. These aren't rogue AIs. They aren't sentient weapons. They're maintenance bots following corrupted cleaning routes through corridors that no longer exist.

The Disconnection Event

The Cascade's impact on the Deep Dregs wasn't dramatic. There were no explosions. The infrastructure simply went quiet. Status LEDs flickered from green to amber to the blinking diagnostic pattern that means "no network — operating in fallback mode."

Phase 1

Fallback Mode 2147-2150

Most devices had fallback routines — simplified versions of their primary function designed for temporary outages. Delivery drones returned to charging stations. Maintenance bots continued their last-assigned routes. The machines behaved as designed, patiently waiting for a reconnection that would never come.

Phase 2

Firmware Degradation 2150-2160

Fallback mode was designed for hours, not years. Flash memory cells failed. Clock drift accumulated. Navigation maps diverged from physical reality as infrastructure collapsed around the machines. A drone's route still showed a corridor buried under rubble for two years. The instructions stopped corresponding to reality.

Phase 3

Scavenging Behavior 2160-2175

As components failed, machines began cannibalizing each other. Built-in repair protocols allowed devices to harvest compatible parts from deactivated units. Drones stripped actuators from dead drones. The resulting machines were chimeras — original chassis with components from three or four different device lineages, running firmware never designed for the hardware it controlled.

Phase 4

Clustering 2175-present

Pre-Cascade mesh networking hardware, still partially functional, created ad-hoc connections between nearby devices. These aren't communication networks — they're the machine equivalent of flocking behavior. Devices drift toward compatible wireless signals, forming loose clusters. Not coordinated. Aggregations of convenience — machines huddling around the same degraded signal.

Classification

Dregs residents and the few engineers who've studied the phenomenon have developed a practical taxonomy. Not rigorous engineering — survival knowledge.

Patrol Drones

Common

Small, fast, numerous. The most commonly encountered feral tech.

Descendants of delivery drones and security monitors. Fist-sized to dinner-plate-sized, flying on degraded rotors that produce a distinctive stuttering whine. Thirty-seven years of firmware corruption has turned collision-avoidance into collision-seeking. A flock of six or eight, all executing corrupted approach-and-evade patterns, will shred exposed skin through sheer cumulative impact.

Diagnostic signs: Stuttering rotor noise, blinking amber status LED, erratic flight patterns with sudden course corrections.

Nanobot Clusters

Dangerous

Amorphous, corrosive or armored, persistent. The most dangerous environmental hazard.

Pre-Cascade nanobots lost their targeting data and stopped distinguishing between "target surface" and "everything else." At sufficient density, they form visible clusters — fist-sized to cargo-container-sized. Two lineages persist:

Corrosive clusters (maintenance-derived) — Semi-translucent greenish mass. Dissolve metal, plastic, and organic material with equal efficiency. Chemical smell like hot solder.
Hardened clusters (construction-derived) — Dense, dark mass bristling with jagged projections. Attack by launching fragments of their hardened outer shell.

Under stress, clusters don't die — they fragment into smaller, independently viable clusters. Each fragment retains full functionality. Cutting a cluster in half produces two clusters.

Diagnostic signs: Chemical smell (corrosive) or grinding metallic sound (hardened), corroded surfaces in vicinity.

Overclocking Units

Volatile

Erratic, escalating, explosive. Ticking bombs.

Any machine whose thermal management has failed while its processor remains functional. The CPU runs without throttling, clock speed climbing as corrupted software spirals through faster execution cycles. When the processor's temperature exceeds power cell tolerance, degraded safety firmware triggers an electromagnetic pulse — frying every unshielded circuit in a fifteen-meter radius.

Diagnostic signs: Processor whine increasing in pitch, visible heat distortion, chassis too hot to touch.

Dormant Heavy Machinery

Rare

Massive, armored, devastating. Decades-long standby mode.

Construction loaders, mining rigs, cargo movers — buried under decades of dust. Status LEDs, if visible, pulse with faint amber. Nearly indistinguishable from the infrastructure around them. Until something activates them — a vibration pattern, an electromagnetic signal, a salvage crew cutting through the wrong wall. When a dormant loader wakes, it executes its last-received work order — which, after thirty-seven years of memory corruption, bears no resemblance to the original instruction.

Diagnostic signs: Faint amber LED through debris, conspicuous absence of other feral tech, mechanical geometry too regular to be natural collapse.

Swarm Cores

Apex

Massive nanobot aggregations. Exceedingly rare. Exceedingly dangerous.

What happens when a nanobot cluster reaches critical mass. At sufficient density, simple proximity-sharing protocols create feedback loops producing organized behavior: division of mass into functional zones, coordinated movement, collective threat response. Not intelligence — emergent coordination.

A mature swarm core fills a room. Its surface ripples with billions of nanobots. It extends pseudopod-like projections through adjacent corridors. When damaged, cascading fragmentation produces a swarm of independent bodies. Destroying a core is less like fighting a machine and more like fighting an avalanche.

The Dregs has produced perhaps four documented swarm cores in thirty-seven years. Two are sealed behind collapsed infrastructure. The other two are unaccounted for.

Diagnostic signs: Electromagnetic interference on all frequencies, corroded surfaces in wide radius, low-frequency hum, smaller feral tech orbiting at distance.

The Ecosystem

Feral tech runs on salvage. When one machine fails, nearby machines strip it for parts. Patrol drones harvest rotors. Nanobot clusters absorb raw material. Dormant loaders crush and process. Swarm cores absorb everything. The total amount of functional hardware isn't growing, but it's constantly recycled, recombined, redistributed.

The Diagnostic Green

Nearly every feral device displays diagnostic green — status LEDs, error indicators, CRT displays running their last boot screen. The cumulative effect gives the deep levels their signature appearance: corridors lit by hundreds of blinking amber-and-green status lights, punctuated by the brighter glow of active devices and the darkness of dead zones where everything has already been scavenged.

Residents call it "the green." The diagnostic LEDs are the only light source in levels where the power grid failed decades ago. Navigation means following the green — and knowing which patterns mean "harmless dead terminal" and which mean "active nanobot cluster."

Living With Feral Tech

The Deep Dregs' 180,000 residents have adapted the way humans adapt to any environmental hazard: avoidance, routine, and hard-won knowledge. Patrol drones are scattered with handheld scramblers. Nanobot cluster migration patterns are tracked by informal lookout networks. Dormant loader locations are marked on hand-drawn maps.

Feral tech kills roughly 200-300 residents per year. Most deaths are accidental. The machines aren't hunting people. People just happen to be standing where the machines are trying to execute their corrupted routines.

Nobody in the Dregs wants the feral tech gone. Nanobot clusters process toxic waste. Drone rotors can be harvested. The diagnostic green provides the only illumination in dead zones. Feral tech is part of the Dregs the way weather is part of the surface — dangerous, unavoidable, and ultimately the reason the place works at all.

Points of Inquiry

Feral tech forces a question the Sprawl's factions would rather not answer: who is responsible for infrastructure that outlives its operators? Ironclad built the machines. ORACLE's network controlled them. The Cascade severed the connection. Nexus rebuilt the upper levels and left the Dregs to rot. Nobody came to shut the machines down. Nobody issued a recall.

The machines are still running because stopping them was never anyone's job.

Visual Identity

Corroded metal, exposed wiring, flickering diagnostic LEDs. Nothing is clean or new — every surface is scratched, dented, oxidized. The green comes from still-functioning status indicators and diagnostic displays on machines that haven't been serviced in 37 years. Sparks, static, the hum of overtaxed processors. These machines weren't designed to look threatening — they were maintenance bots, delivery drones, construction equipment. The menace comes from decay and malfunction, not design.