2022-10-15: Train Dilemma
- Log: 2022-10-15: Train Dilemma
- Cast: Zan
- Where: Side 5
- Date: U.C. 0096 15 10
- Summary: Zan has programming problems after the latest Angel fight and it's ability to black out communications.
After ensuring everyone was back on the Ra Mari, Zan floated in space. Reconnected to his larger self, Zan sat in his robotic form on the docking platform he normally rested in as his alternate form.
The other units were more important. They needed repairs more than he did. They protected and defeated enemies. They saved human life. That was his reasoning on the surface.
Internally, Zan's awareness was occupied. He was not paying attention to the outside world as he had other problems now. His programming was running with the processors nearly overheating. Never since awakening had he experienced what happened.
The Iron Railer did not respond when he asked for assistance. When he sent for help. When he tried to call for it to come to him.
New, unprogrammed routines start to appear. Ones and zeros forming new routines as Zan tried to compensate internally for what happened. To explain it. One comes up that he has experienced before. Fear. This was normally when he was in hiding. His processors slow a little as the realization comes across. Logic follows back to the cause. The lack of response from the Iron Railer.
Zan runs it again. Logic and emotional programming conflict. It should not have happened.
He returns to his ORCA form and docks with the Iron Railer. He needed a full connection. And he needed to check the data logs.
Errors start to appear. Data logs not matching, inconsistencies that should not exist. Zan's data logs do not match the Iron Railer's own.
Communication between the two should be instant. Connection constant even when separated.
Zan was one with the Iron Railer. The Iron Railer was one with Zan. One AI, one body.
The realization that a part of him could be effectively cut off, taken, or even destroyed has Zan's programming running to logical conclusions.
Deletion of results happen. Two more results pop up. Feelings. Deletion again. More results. Deletion again.
An alert is sent out shortly after as Zan's processors overheat in their effort to find a solution.
Shortly after the alert, emergency protocols transmit a data log before Zan shuts down the process at the source and goes into a low powered, hibernation program.
Zan and the Iron Railer float in the Side 5 Shoal Zone, neither responsive to sudden inquiries about the alert.