Novel

Chapter 5: Shadows in the Bay

Kaelen decrypts the prototype's logs, discovering it is a beacon for a lethal academy purge. Before he can disable it, a technician and security drones raid his bay, triggering a lockdown and forcing Kaelen into a cornered survival scenario.

Release unitFull access availableEnglish
Full chapter open Full chapter access is active.

Shadows in the Bay

The air in Maintenance Bay 4 tasted of ozone and scorched copper—the scent of a machine pushed past its thermal limits. Kaelen Vane sat hunched over his terminal, the flickering light of the display casting long, jagged shadows against the rusted hull of his mech. His forearm, where the neural-link scar pulsed with a dull, rhythmic heat, throbbed in sync with the data stream he was desperately trying to scrub.

Dawn was four hours away. At dawn, the academy’s automated diagnostic suite would initiate a full-system sync. If the suite detected the prototype module’s signature, the remote-purge protocol would trigger, turning his mech into a tomb.

Kaelen’s fingers moved in a blur, bypassing the final layer of black-ice encryption. The module resisted, sending a white-hot spike of feedback through his neural tether. He gritted his teeth, forcing his own sensory processing to act as a heat sink for the digital surge. He didn't pull back; he couldn't afford to. He pushed his will into the machine’s logic gate, sacrificing his physical stability to anchor the connection.

Crack.

The encryption shattered.

Data flooded his HUD, not as mission reports, but as a forensic timeline of a massacre. He watched, frame by frame, as a Ghost-Class prototype was systematically dismantled by academy drones. It wasn't a failure of combat; it was a targeted execution. The academy hadn't lost the prototype in a skirmish; they had purged it to bury the fact that their own systems were designed to consume their best hardware.

He traced the final line of code, his breath hitching. The module wasn't just storing data; it was broadcasting a beacon. It was a kill-switch. He was piloting a death sentence.

Before he could isolate the purge command, the heavy metal door of his bay groaned under a forceful override. A lead technician from the central office strode in, his uniform pressed with a razor-thin formality that felt like a death sentence. Behind him, two security drones hovered, their optical sensors pulsing a clinical, rhythmic blue.

"Open the access port, Vane," the technician commanded. "We’ve detected an unauthorized energy flux originating from this bay. Hand over the maintenance logs, or we initiate a hard-line override."

Kaelen’s heart hammered against his ribs. He had spent the last hour building a digital ‘ghost’—a looped data stream designed to mimic a standard engine signature. He stood, shielding the terminal with his body. "Diagnostic is scheduled for dawn, not midnight. My frame is offline for maintenance."

"The Director doesn't care for your schedule," the technician replied, stepping into the bay. His boots clicked against the metal grating, a sound that echoed like a countdown. He pushed past Kaelen, his fingers hovering over the diagnostic port.

Kaelen watched, paralyzed, as the technician plugged a high-tier override cable into the Rust-Bucket’s chassis. The terminal screen shrieked—a high-frequency pulse that vibrated through the marrow of Kaelen’s teeth. On the screen, a red progress bar stalled at 88%. Beneath it, a line of cascading error codes flooded the feed: Unauthorized Hardware Signature. Recursive Data-Loop Detected. Integrity Threshold: Critical.

"Damn it," Kaelen hissed, his fingers dancing across the haptic interface. He tried to sever the beacon’s handshake, but the module was fighting back, actively rerouting his frame’s power to bypass the security wall. Suddenly, the terminal screen flickered to a static-filled image: a war-torn landscape, jagged mountains of scrap, and a sky choked with orbital fire. Then, the connection snapped.

A cold, synthetic voice boomed through the bay’s overhead speakers, cutting through the hum of cooling fans.

“Alert. Unauthorized kernel modification detected in Bay 402. Initiating Level 5 Lockdown.”

The heavy, reinforced blast doors slid shut with a bone-jarring thud, sealing him inside. His HUD flickered, highlighting the entrance with a pulsing amber warning. Outside, the mechanical whine of high-tier security drones—the kind usually reserved for hazardous containment—echoed in the corridor. They were here. Halloway hadn't waited for dawn; he had sent a cleanup crew.

Member Access

Unlock the full catalog

Free preview gets people in. Membership keeps the story moving.

  • Monthly and yearly membership
  • Comic pages, novels, and screen catalog
  • Resume progress and keep favorites synced