Data Recovery Damnation
Added 2024-07-01 16:43:08 +0000 UTCRay had logged into the local cyber-brothel with the intent to illegally record the sensory output from the Mesh-Puppets who worked there. He would use the recordings to “flesh out” the smutty “Feelies” he was making to sell on the porn-chip market. To accomplish this, he uploaded his sentience and disguised it as just another stored personality belonging to the women who allowed their minds to be temporarily over written for customer use. Once inside the system, Ray began to search when he accidentally triggered a data cascade.
Warning: Node unstable…fatal data corruption probability high…Initiate emergency data dump..suitable storage capacity identified in node designated “Maya K Oslow”...
Data dump? Maya K? Oh, NO WAIT!
Dump initiated!
By contract, stored personalities codes (perks) had data recovery priority over all other concerns, including locality. In an emergency ,stored “Perks” were dumped into the memory reciever with the fastest link.
Ray had remoted in, his body was multiple hops and high latency away. At the same time, a Mesh Puppet named Maya had just started her shift and slotted in for upload.
WARNING: Dual Command structures detected!
Maya’s perk was still present and in control, but her brain had the capacity to host Ray as well.
Legacy command priority! Voluntary Neural link default retained.
Recognizing Maya’s right to her body, Ray was given no access to the body’s motor cortex. He is a passenger in Maya’s body with no way to communicate or act. As Ray’s Perk was not inventoried in the brothel’s system, no data recovery was ever attempted. Ray lived on as a helpless passenger in a sex-puppet from that day forward.
