2084: An Algorithmic State — Act VIII: Presence, Chapter 43: Rao’s Leverage

The log entry says only this: subject minor, expedited by the Secretary, reason discretionary. Meghna Rao reads it eighteen hours later. Then she finds what a child saved outside the model leaves behind in its data.

In Brief: Meghna Rao, the Director who has promised to watch Dev Sharma’s private mercies, finds his intervention for a child in Sector 12-East in his office’s action log. Reading the system’s fine print, she begins to suspect that his twenty years of quiet exceptions may lie behind the sector’s falling confidence. She drafts a request for review.

Meghna Rao learned of the Ruhi Nair intervention within eighteen hours, not because anyone had told her. It was because she had done exactly what she had promised Dev Sharma she would do. She had built, in the week since their conversation, a standing query against his office’s own action log. It was set to surface anything touching Section 1, Subsection 9 the same day it occurred rather than the following quarter.

The entry, when it surfaced, told her almost nothing and everything at once.

Secretariat intervention, medical allocation, Sector 12-East, subject minor. Expedited by Secretary’s personal authorization, outside standard confidence-threshold review. Reason: discretionary.

No name. No file attached, because citizen privacy had closed that door to her, as it always did. There was only a timestamp, a week after her own conversation with him. It showed exactly how long the promise she’d extracted from him had lasted before he broke its spirit, if not, strictly, its letter. He had not concealed the intervention. He had logged it plainly, in a system that would have surfaced it to her regardless. He had simply gone ahead and done it anyway, the same day, without waiting to hear whether her office might have moved faster, or slower, or differently, given the chance.

She stayed with the entry a long time, Director of Personnel Integrity at a desk kept clear of everything but one tray. She understood that she now had, technically, the single clean example she had told him she hoped never to find. Alongside it came a second thought, which troubled her considerably more than the first.

Since their meeting, she had spent the days doing the reading she had not yet finished when she confronted him. She had pulled the full architecture documentation for the confidence-calibration subsystem. It was the same documentation Dev himself had presumably read decades ago and half-forgotten. He would have forgotten it the way anyone forgets the fine print of something they built with their own hands and trusted to hold. She read it now with the attention of a woman looking for a particular kind of answer. She found a line she had passed over the first time without registering its full weight. Manual overrides were logged and excluded from retraining data, yes, exactly as the charter promised. But the exclusion applied only to the override’s stated outcome. It did not apply to the downstream ripple of the citizen’s later behaviour, resource consumption, and interactions with a dozen other systems. None of those systems had been told to disregard the fact that this particular case had been handled outside the model’s own logic. A child saved by discretion did not vanish from the aggregate the moment the override closed. She went on existing, consuming resources the model had not predicted for her, in patterns the model would, eventually, quietly incorporate. The safeguard correctly excluded the override. But the model would take in forty small downstream facts about a life it had expected to look different than it now did.

Meghna did not yet know whether this was the actual mechanism behind Sector 12-East’s six-point drift. She suspected it, and the suspicion unsettled her more than certainty would have. There had been twenty years and two hundred and eighty-eight quiet exceptions. Each one had rippled forward through a decade of unmodelled downstream consequence. Together they might be exactly the kind of accumulated, untraceable micro-variance Dev’s own query had described to him three days ago. The query had never once suggested where the variance had actually come from.

She did not raise this with him directly, not yet. She did not have proof of it. She had only architecture and arithmetic, and a suspicion sharp enough to keep her awake past the hour she usually permitted herself. She had built a career on refusing to let belief substitute for evidence. She was not about to make an exception for her own half-formed hypothesis simply because of whom it was aimed at. Once already, she had told that man to his face that she did not consider him an enemy.

It was possible, and she made herself hold it fully. A mercy entirely unselfish and entirely well-intentioned could still be doing to Sector 12-East something not unlike what her father’s headmasters had done to him. Her father had been a schoolteacher, passed over three times for men with better uncles. It could do it simply by being a form of attention the model had never been built to account for. The model could therefore never absorb it without cost to somebody standing nearby who had asked for none of it.

This did not change what she intended to do. It changed how little comfort she expected to take in doing it.

She did the next thing her discipline required instead. She drafted a request to the Programme’s architecture oversight committee. This body answered to no Secretary, and so far as her own records showed, it had not been consulted about anything touching Section 1, Subsection 9 in over a decade.

Requesting emergency technical review of downstream propagation effects from historical discretionary overrides, Sector 12-East, with view to determining whether accumulated unmodelled interventions constitute a material contributing factor to current confidence instability.

She did not submit it immediately. She held the draft the way Dev, she suspected, held his own hardest determinations. She understood that submitting it would set in motion a process whose shape even she could not fully control once it began. A technical review answering to a committee outside the Secretary’s own authority was not merely an inquiry into a number. Whatever language she dressed it in, it was the first formal thread. It connected Dev Sharma’s twenty-six years of mercy to the very crisis he had spent a sleepless night beside his dog trying to name.

She read the request over four times before she let herself stop counting the readings. Each time she checked for a softer phrasing that would still be honest. Each time she found that the honest version and the soft version kept refusing to be the same document. She had spent a career believing that the honest version of anything was also, eventually, the kindest version, once enough time had passed for the kindness to become visible. She was less certain, sitting with this particular document, that either of them, herself or Dev Sharma, would live to see enough time pass.

She submitted it at eleven that night. She did not sleep well either, that night, a fact she noted with a discomfort adjacent to satisfaction. Whatever else was true of her and the Secretary, they had this much, at least, now unmistakably in common.

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

Previous: Chapter 42: Ruhi

Next: Chapter 44: The Cascade