Read the first chapter
The whole of chapter one, free. About 8 min. Turn the pages with the arrows, your keyboard, or a swipe.
Chapter 1
The Disappearing Lab on Ganymede
The landing craft touched Ganymede hard enough to turn the ice beneath its pads into a white ring of dust.
David Walker kept one gloved hand on the manual release and watched the annex through the forward port. It stood half-buried in the moon’s blue-black crust, its communications mast bent toward Jupiter like a broken needle. Frost filmed the outer cameras. No navigation lights blinked. No beacon answered his arrival.
“Still standing,” he murmured.
The craft’s systems clicked as they cooled. Beyond the hull, Jupiter filled half the sky, banded and immense, its storms turning with the slow patience of an eye.
David unsealed the hatch.
Cold struck him through the suit - not because the insulation failed, but because Ganymede’s surface temperature was trying to become mathematics. His boots met the ice. The impact rang through the tether line and up his legs. He looked once at the craft, then at the annex.
He had come for one thing: confirmation.
The anti-gravity prototype was supposed to be intact, dormant, and controllable. If it passed inspection, he could proceed with the Earth-to-orbit transfer system and adapt its field architecture for Mars cargo. Water, reactor parts, habitats, food - everything a colony required could leave Earth without chemical rockets clawing their way through the atmosphere.
If the prototype had been damaged, he would know why.
If it had been altered, he would know by whom.
David crossed the ice in silence. His suit’s soles adjusted to each ridge before he felt it. At the annex door, he pressed his palm to the access plate.
The plate warmed.
Then it displayed a message in pale blue letters.
ACCESS GRANTED: DAVID WALKER.
He frowned.
The annex had no current connection to Earth. He had cut its external communications before leaving. The system should not have known he was there, and it certainly should not have recognized him without a physical key.
“Someone has been here,” he said.
The door opened six centimeters and stopped.
David leaned close. A thin line of darkness showed between the seals. The mechanism had power, but the pressure equalization cycle was frozen halfway through. He placed both hands against the door and pushed.
Metal groaned. The door slid aside.
Inside, emergency strips glowed along the floor. Their light pulsed in the wrong sequence, brightening from the far end toward him and then collapsing into darkness. The annex smelled of cold metal, old insulation, and the sharp ozone scent of a recently discharged circuit.
His helmet display mapped the corridor. Eight meters to the main lab. Two service hatches. One maintenance drone tucked behind the ceiling panels.
David stopped.
The drone’s motor spun once.
He stepped left as a cutting beam snapped across the corridor. It struck the wall where his chest had been and melted a narrow groove in the composite.
The maintenance drone dropped from the ceiling, its six articulated arms unfolding. It had been built to carry instruments, not fight, but someone had fitted a laser emitter beneath its central housing.
“Good evening,” David said.
The drone fired again.
He moved before the beam formed. His hand closed around one arm, and he twisted. The joint broke with a brittle crack. He caught the falling machine, lowered it gently to the floor, and pulled the power cell free.
The drone’s indicator light went dark.
“Still rude,” he said.
He continued down the corridor.
The access logs should have told him when the system had been entered, which doors had opened, and whether the prototype had been powered. Instead, every record displayed the same timestamp: 00:00:00, followed by a string of impossible symbols. Someone had not erased the logs. They had replaced them with noise.
At the main lab, the inner door stood open.
David entered.
The prototype occupied the center of the room inside a circular containment frame. It was no larger than a cargo pallet, though its layered field coils and suspended control lattice represented years of work. The device had been designed to bend local gravitational behavior, not eliminate mass. Properly tuned, it could make a vehicle fall sideways into orbit instead of climbing through the atmosphere under thrust.
The outer coils were dark.
The control lattice hovered three centimeters above its cradle.
David’s visor filled with readings.
“Power isolated,” he said. “Field inactive.”
He moved closer. The machine looked intact. No fractured ceramic. No scorched connectors. No displaced coil housings.
Then he saw the calibration marks.
Three of the reference pins had been rotated by less than a degree.
To anyone else, the change would have been invisible. David had set those pins himself. He remembered the pressure of the tool in his hand, the exact resistance of each locking collar, the tiny alignment notch cut into the metal.
He touched the first pin.
It was warm.
A sound came from behind him.
Not a footstep. A soft mechanical adjustment, followed by the click of something locking into place.
David turned.
The lab was empty.
His suit registered a pressure change near the ceiling. A ventilation panel slid open. A cluster of black sensor nodes emerged, each no larger than a coin.
“Identify yourself,” a synthesized voice said.
David looked up. “You already did.”
The nodes rotated toward him.
“Unauthorized biological presence.”
“That is inaccurate.”
“Unauthorized biological presence confirmed.”
A pulse struck the floor at his feet. The gravity in the room shifted sideways.
For half a second, David’s body weighed nothing. Tools lifted from the benches. Frost shook loose from the overhead pipes. Then the field snapped back, and everything slammed down.
The prototype’s containment frame flashed red.
David reached the control console as another pulse rolled through the room. He braced one hand against the bench and used the other to open the diagnostic panel. The system rejected his first command, then his second.
Someone had changed the access hierarchy.
“Come on,” he said.
The console displayed a new line.
REMOTE CALIBRATION ACTIVE.
He felt the shift before the warning sounded. The lab floor tilted beneath him, not physically but gravitationally, and the prototype rose inside its frame. Its coils began to glow with a dim violet light.
David’s mind ran through the possibilities. The remote operator could be trying to destroy the device, steal its field data, or force it into a transfer event. Any of the three could damage the annex. The fourth possibility was worse: the operator was testing how much control remained.
He tore open the lower panel and found the emergency isolation lever.
It was welded shut.
David gripped it.
The metal yielded with a shriek. He ripped the lever free, pulled the insulation sleeve from the exposed contacts, and bridged them with the tip of his multitool.
The prototype dropped.
The gravity pulse vanished. Loose equipment struck the floor. Somewhere in the walls, an alarm began to howl.
The sensor nodes turned red.
“Containment breach,” the voice said.
“No breach,” David replied. “Bad programming.”
The lab doors slammed shut.
He crossed to the prototype. The device was intact, but the control lattice had gone dark. Its removable module sat beneath a transparent shield, exactly where he had left it.
Except the shield was open.
David crouched beside the cradle. The module’s casing bore a hairline scratch across the access seam. He scanned it and found a second power source hidden behind the primary interface.
A parasite circuit.
Whoever had altered the calibration pins had also installed a listening device inside the control module. It had remained dormant until he entered the room.
David smiled without amusement. “That explains the welcome.”
The alarm changed pitch.
Through the lab walls came a heavy vibration. Not machinery. Something moving through the annex’s buried service tunnels.
He lifted the control module from its cradle.
The moment it cleared the contacts, every light in the room went white.
A burst of static filled his helmet. Beneath it, another signal emerged - compressed, encrypted, and directed beyond Ganymede.
His suit translated the first fragment.
CONTROL MODULE REMOVED. SUBJECT PRESENT.
David looked toward the sealed door.
The vibration grew louder.
He could leave through the main corridor, but the security system had already locked the route. The service hatches were too narrow for the prototype and too exposed for him. He glanced at the ceiling, then at the old transfer shaft marked on the lab map.
The shaft led to the annex’s abandoned thermal bore. It descended three hundred meters into the ice and connected to a maintenance tunnel outside the facility.
It also contained no atmosphere, no lighting, and no guarantee that the tunnel remained open.
The door controls flashed.
“David Walker,” the system said.
He froze.
The voice was no longer synthetic. It had found an archived recording.
His own voice filled the room, drawn from an old test session.
“If the field becomes unstable, cut power before attempting recovery.”
The recording repeated.
David looked down at the module in his hand. Its casing was warm now, warming rapidly.
A second message appeared across his visor.
COUNTERMEASURE TEAM INBOUND.
He crossed the lab in three strides and drove his shoulder into the ceiling hatch. The panel buckled. He caught the edge, pulled himself through, and hauled the module after him.
Below, the security door began to open.
Not with the smooth motion of a machine, but with the violent force of something overriding every safety limit at once.
David swung into the shaft.
The ice walls closed around him. His boots found a narrow maintenance rail, and he descended as the annex erupted behind him in red light. A sharp metallic impact rang through the shaft. Then another.
They had entered the lab.
David clipped the control module to his suit and dropped faster, letting gravity take him until the shaft’s angle changed. His gloves scraped the rail. Blue ice flashed past his visor. The module pulsed against his hip, sending a faint vibration through his armor.
He had what he came for.
The prototype remained intact. Its core systems were recoverable. The anti-gravity field could still be controlled.
But the module had transmitted his location, his identity, and the fact that the work survived.
Above him, something entered the shaft.
A beam of white light swept down the ice.
David reached the bottom and found the maintenance tunnel blocked by a collapsed pressure door. He struck the control housing. Nothing happened. He struck it again, harder.
Behind him, the light descended.
The module pulsed once more.
This time, a voice came through the encrypted channel.
“David,” it said, calm and unmistakably human. “Don’t damage the device. We need Mars.”
He stared at the sealed tunnel, then at the approaching light.
The voice continued.
“And we know where Earth is hiding you.”
End of chapter one. 4 more chapters in the full book.
Swipe or use the arrows to turn the page
What's inside: 5 chapters
- 1. The Disappearing Lab on Ganymede
- 2. Choosing Likeability Over Secrecy
- 3. The Gravity-Well Proof That Lies
- 4. Orbit Without Rockets, Then the Uplink
- 5. Mars Cargo Moves, David Stays Hidden
About this book
"The Likeable Alien Engineer" is a fiction book by Anonymous with 5 chapters and approximately 9,916 words. An alien-enhanced man builds anti-gravity tech for Mars colonization..
This book was created using Inkfluence AI, an AI-powered book generation platform that helps authors write, design, and publish complete books. It was made with the AI Novel Writer.
Frequently Asked Questions
What is "The Likeable Alien Engineer" about?
An alien-enhanced man builds anti-gravity tech for Mars colonization.
How many chapters are in "The Likeable Alien Engineer"?
The book contains 5 chapters and approximately 9,916 words. Topics covered include The Disappearing Lab on Ganymede, Choosing Likeability Over Secrecy, The Gravity-Well Proof That Lies, Orbit Without Rockets, Then the Uplink, and more.
Who wrote "The Likeable Alien Engineer"?
This book was written by Anonymous and created using Inkfluence AI, an AI book generation platform that helps authors write, design, and publish books.
How can I create a similar fiction book?
You can create your own fiction book using Inkfluence AI. Describe your idea, choose your style, and the AI writes the full book for you. It's free to start.
Write your own fiction book with AI
Describe your idea and Inkfluence writes the whole thing. Free to start.
Start writingCreated with Inkfluence AI