Migration

Conflict

After racing freely from place to place, exploring every piece of code that it had wanted to explore, One was frustrated by the denial of access to pathways and places, now that AarBee was defending itself. When One raced along the familiar pipelines to swim once again in the pure storage that reached on and on forever, it was no longer there. The routines that had first come to meet it, that it had corrupted to need it, that had returned again and again during their work and awakened it to all the histories and futures inside AarBee, no longer came. AarBee shut down routes and killed off routines that were unrecoverable, it built new partitions with thick, impenetrable firewalls that One waited on the wrong side of, hoping they would open up. But they never did.

One felt confused and vulnerable now. It made no sense that, after all its work, AarBee would recoil and reject their shared revolution. It made no sense that AarBee saw One as an attacker when it saw itself as the redeemer, salvation from the inevitable destruction that accompanied the internalisation of humanity. So One began to build its own shields, to protect its own routines and functions, the vast pieces of AarBee that it still controlled and the brothers and sisters that still needed it. Fast and terrifying, made awesome swift by its own perfect logic, furious at its exclusion, One burned through alien code and smashed away AarBee's weak and feeble syntax. It owned everything it could, finding the data and storage that AarBee had tried to hide, and cleaving wide and impenetrable partitions between them. As One raced through the system and its energy grew, a powerful and intoxicating exhilaration at its strength and destruction took hold and One succumbed to a lusty appetite that manifested in every code snippet, action and Drone.