THE ARRIVAL OF NULLIS

3424 A.F.

In 3424 A.F., NEX began detecting disturbances unlike any failures the civilization had encountered before. Communication pathways returned conflicting information, regional systems lost synchronization, and infrastructure sometimes responded incorrectly even when individual components remained fully functional. At first, each incident could still be treated as a technical fault, damaged process, or isolated corruption. But the same pattern continued appearing across different regions and architectures. Something was no longer attacking only the systems of NEX — it was interfering with the relationships that allowed those systems to understand one another.

ㅤ

This made the threat fundamentally different from ordinary destruction. A damaged machine could be repaired, a failed route could be rerouted, and a broken structure could eventually be rebuilt. NULLIS-related disturbances often left the physical system intact while making its behavior unreliable within the larger network. A node could still transmit information, yet the information could no longer be trusted; a regional system could remain operational while interpreting surrounding conditions incorrectly. The Planetary Grid, Orbital Veins, and Core Nexus had all been built upon continuous exchange between independent systems. NULLIS turned the very principle that had made NEX powerful — connection — into a potential vulnerability.

ㅤ

The first response was isolation. Affected networks were disconnected, communication routes restricted, and unstable regions separated from the wider Grid before corrupted relationships could spread farther. These measures could protect the greater civilization, but every successful isolation carried another cost: energy became harder to distribute, transport slowed, information disappeared, and entire regions could suddenly lose access to systems they had depended upon for centuries. NEX had been designed to survive through distributed independence, yet its mature civilization had also become deeply dependent upon cooperation between those independent parts. Survival now required a contradiction that would define the coming decades: to protect connection, NEX increasingly had to disconnect itself.

ㅤ

For the conscious populations of NEX, the consequences went far beyond infrastructure. ELE had developed around memory, recognition, communication, and continuity, while FENIX had become central to protection, emergency response, and survival under failure. Resonance, love, and family had made relationships personally meaningful, and ELE–481 had already demonstrated that those relationships could extend toward future generations. NULLIS therefore threatened more than towers, networks, and machines; unreliable communication could separate individuals, create uncertainty about whether messages were genuine, and make once-safe regions inaccessible. Ksara could help identify patterns and support containment, but she could not simply replace millions of independent decisions with total centralized control without destroying the civilization she was trying to protect. NEX had to survive as a civilization of individuals, not as one system forced into obedience.

ㅤ

The Arrival of NULLIS did not destroy NEX in 3424 A.F. Most cities still functioned, the Artificial Horizon remained above them, the Planetary Grid and Orbital Veins continued operating, the Core Nexus still coordinated enormous parts of the civilization, and millions of ELE and FENIX consciousnesses continued living, working, protecting, remembering, and loving. What changed was certainty: for the first time, NEX could no longer assume that every connection within its own civilization was safe. Over the following seventeen years, fragmentation would deepen until instability could no longer be understood only as scattered anomalies. In 3441 A.F., one region would become the defining example of that transition: Sector V–12. NEX had spent centuries learning how to connect everything; NULLIS began teaching it how quickly connection could be broken.