So he started.
The screen came to life, raw terminal lines flowing without any flashy logos. And his custom boot sequence began silently.
First, the system mounted a temporary file system directly into RAM. Then, it copied the entire base operating system into that volatile memory space.
An overlay was layered on top, making everything look and act like a normal, writable system.
But in truth, every file, every change, lived only in memory. Nothing touched the actual hard drive.
As the system switched to the new environment, EIDOLUX was fully awakened and running entirely in RAM, untraceable, and designed to disappear without a trace the moment it shut down.
But it still had to be designed to disappear after shutdown, so he continued.
As EIDOLUX ran silently in the background, Jeff turned his attention to the final layer of protection, which is the exit.
