Warning. Data files incomplete. Data files incomplete.
The warnings have been going off in zir head for years. Ze's learned how to ignore them and continue to sleep.
Integral circuitry unaccounted for. Memory logs inaccessible.
The same warnings, over and over. There's nothing ze can do to address them. Ze wishes, sometimes that ze was in perfect dormancy, untroubled by these constant, constant error reports. Ze can't fix them. Where are the engineers? They needed to come and fix zir.
Power source offline. Positioning system corrupted.
Just let zir sleep. Ze wants to sleep. Why can't ze sleep? Didn't ze already do what was asked of zir? Zir primary function was forgotten long ago, lost in the mess of error reports. But the update logs confirm that ze succeeded in zir initial programmed mission. So ze should have been decommissioned ages ago. Right?
Just let zir sleep...please. Things hurt. There's a feeling of fracturing in zir chest that pangs at zir chest constantly. It's probably the missing circuitry that the error messages warn of.
Warning. Defense systems offline. Update log has been corrupted. Warning. Circuit communication with outer layer has been disrupted.
Hm? Hang on. That's a new error message.
Memory files fractured. Attempting back up systems.
Ze shifts, suddenly nervous. What is happening? Code is unraveling around zir.
Memory back up processes compromised. Authorizing emergency transfer to external memory banks.
Zir memory files! They're being removed—sent through a network to an external bank! Someone is altering zir code!
Emergency beacon located. Physical transference activated.
That error message is—because of the danger, ze is automatically being transferred to the safe zone. Someone is unraveling their very code—the transference needs to be authorized immediately—
Something...something is calling zir. Zir fractured code in zir chest tightens and squeezes painfully.
Primary functions backed up. Emergency objectives stabilized. Physical transference to safe zone authorized.
These memories are already falling apart. The final removal of all but the essential objectives into an external memory bank is almost completed.
Ze has one final thought before the transference authorization resolves.
I can hear it.
The missing part of my code.
A/N: Hey y'all~ I hate to do this to everyone, but I'm putting this fic on a TEMPORARY hiatus. This is a good break point since it's the last interlude from part one, and part two dives right into the original plot of Zexal with my new tweaks.
Anyway, I don't want to have to do this, but I'm REAL close to finishing a few other large projects, and since the outline for this project is somewhat shaky in part 2, I want to give my full attention to my other current longfics before I return to give this one's outline and plotting the full attention that it deserves.
And don't worry! Part II will be updating in this same place, I'm NOT making a separate sequel section, so when this fic updates again, if you're subscribed to this, you'll get the notification like usual.
Thank you so far to everyone who has read and commented, and I promise you that I will be back to finish this one once I've got the other affairs in order. Thank you for your understanding!