2084: An Algorithmic State — Act VIII: Presence, Chapter 44: The Cascade

Six sectors lose confidence in five days, all with the same signature and no cause anyone can trace. By evening it is fourteen. For the first time in twenty-six years, the model raises a flag without being asked.

In Brief: Ruhi is kept two nights at the clinic, and Kavya reads on the discharge entry who expedited her file. The fall in confidence that began in Sector 12-East is spreading across the eastern half of the city. Renu shows Samar the map, the model alerts Dev Sharma on its own, and a young engineer tells the Secretariat what is happening. In the courtyard, the margins watch the amber spread on a single handheld.

The clinic kept Ruhi two nights. Kavya slept in the chair beside the cot both nights. On the second morning the sound had gone out of the child’s breathing, and by the afternoon Ruhi was complaining, with some energy, about the colour of the walls. Samar came on the second evening and was not much use, and sat there anyway, and Kavya let him.

Later that evening a nurse came with the discharge entry and turned the clinic’s terminal toward Kavya for her thumbprint. Kavya read it first, start to finish, the way she read anything the Ministry put in front of her. The allocation line sat at the top, above the drug names and the doses.

Medical allocation, Sector 12-East, subject R. Nair. Expedited by Secretary’s personal authorization, outside standard confidence-threshold review. Reason: discretionary.

She read it twice. Ruhi was asleep, turned toward the wall she disliked, one hand under her cheek. Kavya put her thumb on the glass and the nurse took the terminal away.

“Secretary,” Kavya said, when the nurse had gone. She did not look at Samar. “I asked you for a human in the window. You went and found the one who built it.”

“There wasn’t anyone else,” Samar said.

“I know.” She straightened the sheet over Ruhi’s feet, though it did not need straightening. “Nine years I never asked that building for anything. Now she is on his desk with discretionary beside her name, and I would ask again tonight.” She sat down again in the chair. “Don’t tell me what he’s like. I don’t want to owe a person.”

Samar sat with it, as he had been told to, in the plastic chair on the far side of the cot, until the ward lights went down.

The drift reached Renu’s desk three days later, in the form of a number that made her call Samar over before she had finished reading it herself.

“It’s not just Twelve-East anymore,” she said, turning her screen so he could see it. Her voice carried none of its usual unhurried certainty. “Fourteen. Nine. The whole eastern arc. Confidence down between four and seven points across six sectors, all in the last five days, all with the identical signature: no traceable dominant cause, distributed across tens of thousands of files, none of them individually significant.”

Samar felt something cold move through him that had nothing to do with the canteen’s carefully calibrated air. “It’s spreading.”

“I don’t think spreading is the right word, or maybe it’s exactly the right word and I don’t want it to be.” Renu pulled up a wider view. Sector confidence was rendered as a heat map across the eastern half of the city. There were patches of amber where amber had never appeared in the four years she’d been tracking it. At its densest edge was one small knuckle of orange, darker than anything Samar had seen the map produce before. “Adjacent sectors share infrastructure dependencies in the model’s own architecture: power routing, transit modelling, resource pooling. If Twelve-East’s uncertainty was never resolved, only contained, it looks like it’s begun propagating through every sector that shares a dependency with it. Not because anyone decided anything. Because the model treats unresolved uncertainty in one area as a reason for caution in every area that touches it, and caution, once it starts compounding, doesn’t know how to stop compounding on its own.”

Dev received the same view forty minutes later. This time it came through a channel that did not require him to ask for it. For the first time, the model itself had escalated a pattern without being asked. A flag appeared at the top of the Secretariat’s automated brief. Dev’s staff would later tell him it had never, in twenty-six years, been triggered before.

Aggregate confidence decline exceeds cross-sector propagation threshold. Model recommends:(1) increased risk-aversion posture across affected sectors, currently implemented automatically(2) Secretariat review of underlying cause, currently unidentified(3) continued monitoring pending resolution.

Dev read the third recommendation and knew, for the second time in a week, exactly the shape of what his machine was telling him. It was the same blindness he had found at his own terminal a week before, scaled now past a single sector and still climbing. It would go on defending against its own not-knowing, sector by adjacent sector, for as long as the cause stayed unidentified. The model could see the decline perfectly well and had no faculty anywhere for sourcing it. That was to say, it would go on for as long as anyone could foresee.

A second notice arrived on the same screen before he had finished absorbing the first. It came from the architecture oversight committee, acknowledging receipt of Director Rao’s emergency review request. It copied his own office as a courtesy the charter required. Until this exact hour, that courtesy had always felt to him like a formality and never like an actual threat. He set the two notices side by side in his mind, the cascade and the inquiry into whether his own mercy had helped cause it. In the same morning he had both the crisis and the question of whether he himself was some part of its cause. He had no time left to consider either one apart from the other.

He called an emergency session of the Secretariat’s technical staff that afternoon, the first such session in nine years. He sat through two hours of increasingly careful language from engineers who had built careers on the assumption that the model’s architecture was, whatever its limits, fundamentally sound. Then the youngest among them offered the diagnosis Dev had already privately reached a week earlier at his own terminal. She was Meera Krishnan, perhaps thirty, three years into the role. She was visibly aware that what she was about to say would follow her for the rest of her career, whichever direction it turned out to be right in.

“It’s not a fault, Secretary,” she said. Her voice was steadier than her hands, which she kept flat on the table in front of her. It was the way a person keeps their hands still to prove something to themselves as much as to the room. “That’s what none of us want to say plainly, because a fault can be patched. This is the architecture working exactly as designed. It was built to weigh confidence outward, toward citizens, never inward, toward itself. It has no mechanism, none, to ask itself whether the caution it’s now applying across six sectors is proportionate to an actual risk. From inside its own architecture, caution in the face of unexplained uncertainty is not a malfunction. It’s the single most correct thing the model knows how to do.”

No one in the room contradicted her. The silence that followed was itself the most damning confirmation any of them could have offered. Here was a room full of the Programme’s most senior engineers, and not one of them reached for the reassurance that would, a week earlier, have arrived automatically.

Samar learned the shape of the cascade from Kavya that same evening. He arrived at the courtyard to find it fuller than he had ever seen it. Bilal and Zainab and Aisha were there, and a dozen others he did not recognise. They were all gathered around a single handheld terminal showing the same amber heat map Renu had shown him that morning. It was spreading now, visibly, sector by sector, as they watched. Fatima had left her stall untended, an unprecedented thing in itself. She stood near the back with her arms crossed, watching the map the way a person watches weather that has already taken something from them once before. Zainab said nothing at all, but Samar saw her hand move, once, to her chest. From what Kavya had told him weeks ago, that gesture was about a nephew rather than about the map in front of her.

“Fourteen sectors,” Aisha said, without preamble, when she saw him. “This morning it was six. I don’t think anyone in this courtyard needs your Ministry’s explanation for what’s happening. We’ve lived our whole lives downstream of a machine that panics quietly and calls the panicking prudence. What we need to know is whether anyone up there actually understands it’s happening, or whether we’re all just going to keep discovering it one throttled tap and one delayed fever at a time until it reaches the Grid itself.”

“The last time it did this they called it recalibration,” Zainab said. Her hand had come down from her chest. “My nephew went down a tier in that one, and then another.”

Samar thought of a man on the other side of the checkpoint who had built a government to end the eleven cabinet meetings of the Collapse. He had built instead a single meeting that could never adjourn.

“Someone understands it’s happening,” he said, quietly, to the whole gathered courtyard. He was aware as he said it that he was answering for a man none of them had ever met and most of them would never trust. “I don’t know yet if understanding is the same thing as being able to stop it.”

About this serial: 2084: An Algorithmic State is a dystopian novel by Nithin Palal, published online one chapter at a time.

Previous: Chapter 43: Rao’s Leverage

Next: Chapter 45: What Failed First