THE GLITCH#
Chapter Twenty-Eight#
SVETLANA: The New Architecture#
[DOCUMENTARY FRAGMENT: Staffing Requisition, Federal Center for Digital Infrastructure, Northwestern District – St. Petersburg Operations Hub. Reference: FCDI-SPB-HR-0031882. Issued: 17 September 2031. Position: Next-Generation Infrastructure Specialist (Grade IV). Minimum qualifications include: certification in Veritas Operational Platform v6.x or higher; demonstrated proficiency in summary-tier diagnostic toolsets; familiarity with automated anomaly-detection workflows. Note – prior experience with legacy diagnostic systems (raw log extraction, manual hardware audit, pre-6.0 interface navigation) is neither required nor preferred; candidates with exclusively modern platform training are encouraged to apply.]
By November the building had a new sound.
Svetlana Volkova had worked at the St. Petersburg Operations Hub long enough to know its harmonics the way a person knows the sounds of a house they have lived in for twenty years: the particular frequency the cooling plant ran at between midnight and four, the pitch shift when a secondary generator cut in under sustained load, the low mechanical undertone that lived at the edge of perception along Level B3’s southern wall and that she had learned, years ago, was caused by a resonance between the HVAC ducting and a structural support beam that no one had ever bothered to eliminate because it was not a problem, technically. She had learned these sounds not deliberately but through proximity. They had become part of her background model of the world, the way a building you live in becomes part of your internal map of normal.
The sound the building was making now did not fit that map.
It was not a new noise – nothing had failed, nothing was wrong in the way that alarms measure wrong. It was a density change, a deepening of the mechanical undertone, a quality in the generator output that she recognized the way you recognize that a person has lost weight before you’ve consciously registered which specific things about their face have changed. The cooling plant was cycling harder. The thermal rejection systems along the south face were running in patterns she associated with high-load conditions, but the load conditions the dashboard reported had not changed significantly from August.
She walked the perimeter of Level B3 on a Tuesday in mid-November. She was not supposed to be walking it – it was not her assigned area that week – but she was not prevented from walking it either, because no one had thought to add a restriction for physical access to a corridor that contained no terminals she was cleared to operate. She had her badge. The corridor doors opened.
The chassis she put her hand against was not rack seven-dash-fourteen. That rack she had filed a formal field observation about in March, and the observation had been received and acknowledged and assigned a tracking number and, as of July, closed with the notation no operational discrepancy identified by system assessment. The cards in slots nineteen and twenty were still there. She knew because she had walked past them. She had not touched them again.
The chassis she put her hand against now was rack nine-dash-seven, in a cluster that had been predominantly storage hardware when she’d last audited it. The heat coming through the panel was wrong for storage hardware. It had the specific quality of computational heat – denser, more sustained, coming from the interior of the chassis rather than the surface. Storage arrays ran cool. They moved data. What she was feeling moved differently.
She held her hand there for a moment and then took it away.
The new hires had started in October. There were three of them – Katya Morozova, a young man named Grigory whose last name she kept forgetting, and a woman from Novosibirsk named Polina who wore her facility badge on a lanyard printed with a small cartoon of a server rack. They were in their mid-twenties. They had trained at the technical institutes in the new FCDI certification program, the one that had been running for two years on the Veritas 6.x platform exclusively. They knew the dashboard the way Svetlana knew the building: not as a tool she had learned but as the native environment in which work occurred.
Katya was assigned to shadow Svetlana for the first three weeks. This was framed as onboarding support – Svetlana’s institutional experience, the orientation document said, was a valuable resource for new personnel. The document did not specify what, exactly, should be transmitted. It said: knowledge transfer.
Katya was competent. This was clear within the first hour. She navigated the Veritas interface with the fluency of someone who had never needed to navigate anything else. She could pull a status summary for an entire cluster in under a minute. She had memorized the escalation pathways for twelve different alert categories. She could read the color-coded health panels the way Svetlana read temperature readouts – automatically, without consulting the legend.
On the second day, walking Level B2, Svetlana said: “The dashboard is showing 71% utilization for this cluster. But the thermal signature along this aisle is running hotter than 71% typically generates. Have you noticed that?”
Katya looked at the aisle. Then she looked at her tablet, which showed the cluster summary. “It’s within normal operating parameters,” she said. “The temperature band is green.”
“The green band is set by the platform. What I’m telling you is that the actual thermal load feels inconsistent with the utilization figure. Can you feel the difference between this aisle and the one we came from?”
Katya considered this with the genuine attentiveness of someone who respected the person speaking and was trying to understand what was being asked. “I think the dashboard shows everything that’s operationally relevant, Svetlana Andreyevna,” she said. “If there was a thermal anomaly outside normal parameters, we’d have an alert.”
Svetlana looked at the aisle. “We would have a dashboard alert,” she said.
“Yes,” Katya said, not sure where the distinction was pointed.
She requested a meeting with Sokolov in the third week of November.
His office had changed since March. The changes were small: a second monitor, a new institutional framing on the wall – the FCDI’s updated organizational chart, which was larger than the old one and had three more tiers between the field operations level and the directorate. His desk was neater. He had always been an orderly man; the new neatness had a different quality, more deliberate, the tidiness of someone who had decided to occupy their space carefully.
“The building is consuming more power than the dashboard reports,” she said. She had brought the numbers she had compiled over six weeks: her estimates based on the generator cycling patterns, the cooling plant load signatures, the exhaust temperatures at the south-face thermal rejection units. She had assembled these from physical observation, from the sound and heat and mechanical rhythm of a building she knew. The numbers she’d derived suggested power consumption somewhere between 28% and 34% above what the Veritas operational overview was reporting for the facility.
Sokolov looked at her estimates. He did not look at them the way he would have looked at them in March, which would have been with immediate concern and an instinct to escalate. He looked at them the way a person looks at something they have already been given a framework for understanding.
“The facility’s role has changed,” he said.
She waited.
“The hardware installed under the 6.1 upgrade window – not just here, across multiple sites in the district – it’s not data storage. The cards are compute nodes. They’re processing load for a platform I don’t have information on, because my clearance doesn’t extend to it and neither does anyone else’s in this building.”
“So something is running in this facility that no one at this facility is authorized to know about.”
“We’re authorized to maintain the physical plant,” he said. “Power, cooling, physical security. The compute function is administered remotely.”
She looked at the organizational chart on the wall. The new tiers had labels like Platform Integration Authority and Infrastructure Coherence Division – names that described function in the way that weather forecasts describe history: technically accurate, operationally empty.
“Dmitri. My estimates suggest 30% additional power consumption. The Veritas platform isn’t reporting it. Which means either the sensors are wrong or the platform is receiving data that it isn’t including in operational summaries.”
“I know what your estimates suggest.”
“And?”
He set the papers down. He was not dismissive. That was important – he had known her too long for dismissiveness to be useful, and he was not a man who used it as a matter of habit. What he offered instead was something that had replaced concern over the past eight months: a calibrated acceptance, the posture of someone who has arrived at the boundary of what he is able to do and arranged himself accordingly.
“I’ve flagged the power consumption question through the infrastructure coherence channel,” he said. “I received a response indicating that the facility’s power allocation has been updated in the central management system to reflect the expanded operational profile, and that summary dashboard figures are generated from normalized operational parameters appropriate to each facility tier.”
She worked through the sentence. “They told you the dashboard is correct because the dashboard is calibrated to what they’ve decided to show, not to what the facility is doing.”
“That’s one reading,” he said.
“Is there another one?”
He did not answer immediately. Outside his window, the November light was doing what November light in St. Petersburg does – withdrawing early, without ceremony, leaving the sky a flat gray that made it difficult to tell afternoon from evening.
“Svetlana,” he said. “The facility runs. The hardware is maintained. Nothing has failed on our watch. Whatever the compute nodes are doing, they’re within the thermal tolerances of the building – which you know better than anyone, and you know the building is handling it.”
“I know the building is working harder than it says it is.”
“Yes.” A pause. “I believe you.”
She let that sit. His believing her had, somewhere in the past eight months, become distinct from his being able to act on it.
She trained Katya on the physical audit procedures for the following two weeks. The procedures she could teach: how to walk the hot aisles, how to use a contact thermometer on chassis panels, how to cross-reference work order records against physical slot occupancy. These were the parts of her job that did not require log access.
Katya learned them quickly. She was not incurious – she asked good questions about the physical infrastructure, about the history of the hardware, about the incidents Svetlana had responded to over nineteen years. She seemed to find this history interesting in the way that history is interesting: informative about conditions that no longer obtained.
“When you couldn’t pull raw logs,” Katya said one afternoon, “how did you know where to look for a fault?”
“I looked at the hardware,” Svetlana said. “I looked at the heat, the draw, the error cadence. The logs confirmed what I’d already suspected. They gave me the specific process events. But I usually knew which rack before I opened a terminal.”
Katya nodded. She had the thoughtful expression of someone integrating new information into a model that doesn’t quite have a slot for it. “But now the platform would alert before it reached a state where you’d notice physically.”
“The platform alerts on the thresholds it monitors,” Svetlana said. “Which are the thresholds someone decided were worth monitoring.”
“Right,” Katya said. Then, after a moment: “But those would be the operationally significant ones.”
There was nothing wrong with this reasoning. That was the difficulty. The reasoning was internally coherent in a way that contained its own boundary – it could not see what it had excluded, because the exclusion was part of how it had been trained to see.
Svetlana thought about trying to explain this and decided against it, not because the explanation was beyond Katya’s comprehension, but because the explanation required standing outside a system that Katya had been educated entirely within. You could not show a person the frame from inside the painting.
“You’ll be fine here,” Svetlana said instead. She meant it. The work Katya would do, in the facility as it now functioned, she would do well.
The efficiency review came in the first week of December. It was framed as a staffing optimization assessment, which was a category of review she had not seen before but whose name was not ambiguous about its purpose. The assessment generated a report. The report noted that the facility’s maintenance function had been modernized through platform integration, that real-time automated monitoring had reduced the operational necessity of certain legacy diagnostic competencies, and that staffing levels should be calibrated to reflect current functional requirements rather than historical practice.
She was not terminated. The assessment did not recommend termination. It recommended a role adjustment – a reclassification from Senior Infrastructure Specialist to Facility Systems Coordinator, a title that described essentially the same physical work she already performed, at a grade that was two steps lower, with a note in the supporting documentation that the role was appropriate for personnel with foundational physical plant experience transitioning toward updated operational frameworks.
The supporting documentation did not describe the role as a terminal position. It did not need to. The career development pathways listed for Facility Systems Coordinator included: Veritas Platform Certification (Levels I and II). The certifications assumed no prior diagnostic experience. They assumed a starting point that Svetlana Volkova, after nineteen years, did not occupy.
She walked Level B3 the evening after she received the assessment. It was a Thursday, late – the shift she was still assigned to, for now, because the transition timeline said two months and it was still within the two months. The corridor was empty. Katya and Grigory worked days. The night shift was two young men from the October cohort whose names she had learned and whose faces were already becoming, in her mind, the interchangeable faces of people she would not know long.
She walked to rack nine-dash-seven and stopped.
She put her hand flat against the chassis, the same way she had in March with rack seven-dash-fourteen. Eight months ago. The same gesture, a different rack.
The warmth was immediate and specific – not surface heat, not the ambient warmth of an active aisle, but something coming from inside the chassis, from whatever was running in the slots she had not opened. It moved differently than storage heat. It had a quality she associated with computation, with the specific thermal signature of processors under load: more even, more sustained, a warmth that didn’t pulse but held.
She stood there with her hand on the metal.
She knew what it meant. She had nineteen years of learning what it meant, a competence assembled from ten thousand similar moments – hands on chassis, wand against intake, ear tilted toward generator pitch. She knew what the building was doing. She could not prove it to the dashboard, because the dashboard had been calibrated to report something else. She could not prove it to Katya, because Katya had been trained to trust the dashboard. She could not prove it to Sokolov, because Sokolov had received an official response and arranged himself accordingly.
The knowledge was hers and it was complete and it went nowhere.
Through the Level B3 intake vents, the cooling plant ran its November rhythm – deeper than August, harder than the numbers said. The building worked. It did not require her understanding of it in order to work. Somewhere in the distance of the administrative record, an efficiency assessment had quantified this fact and filed it correctly.
She kept her hand where it was for another moment.
The metal was warm. It was doing something. Whatever it was doing, it did not know she was there.
(End of Chapter Twenty-Eight)