He did not take off his jacket. He placed the open laptop beside him, its screen still cycling through remote monitoring displays, and was asleep before he had decided to be. The restart executed at 12:47 in the afternoon, during the early peak of the business day's second trading window. In the first minutes, there was a misleading improvement. Queue times dropped.
Congestion patterns smoothed. The supervisor exhaled. Then the authentication tokens went asynchronous. It happened in waves. The first sign was a cluster of transaction sessions reporting unexpected state mismatches, payments showing as uninitialized, as if they had never begun.
The token synchronization service lost its connection to the primary routing pathway the moment the restart cleared the memory state where Andrew's temporary logic had been running. The isolation barriers collapsed. The dormant trigger fired. What followed was quiet, technical, and deeply frightening to anyone who understood the numbers on screen. Outbound transaction routing began redirecting a subset of traffic toward endpoints outside Aurelius Pay's verified network.
Reconciliation for a category of corporate transfers failed silently. Several high-value payment instructions entered a suspended state that was neither completed nor cleanly reversible. The monitoring systems, missing the bridging logic Andrew had built, could not correctly assess whether the anomalies were internal errors or active manipulation. Engineers worked at a pace that was fast enough to be impressive and not fast enough to keep up with the deterioration. They attempted rollbacks.
The rollbacks did not anchor correctly because the system state they were targeting had never been formally documented. It had been a functional construction built live, under pressure, by a single person who was no longer present. They attempted to isolate the affected nodes, but the interdependencies Andrew understood intuitively were not mapped anywhere accessible. Someone pulled up his repository notes and read them aloud to the group gathered around the primary console. The notes described the current failure mode with remarkable precision.
Understanding them fully enough to reverse what was happening was a different matter entirely. Olivia was called down from the executive floor. She walked into the operations center for the second time that day and found a room that had been transformed. The monitors were overwhelmingly red. Engineers moved between stations with the tight urgency of people who know exactly how serious something is and are afraid to name it plainly.
Calls from enterprise clients were already coming in. She asked what was happening. A senior engineer turned from his console, face pale and composed in the way of someone who has decided to say the true thing. "It looks like he was holding the entire system together by hand for two days." "We just deactivated all the defensive layers he built."
The phrase he used did not require a name. Everyone in the room knew. Olivia asked if they could fix it. She asked who understood Andrew's patch logic. She asked where the CTO was and what the CTO's working knowledge of the legacy infrastructure looked like.