The Switch Belonged to Someone Else - Cover

The Switch Belonged to Someone Else

Copyright© 2026 by Alexander Winston

Chapter 5: Construction

Steve supervised the physical build the way he supervised everything: early, present, and with his hands frequently on the actual equipment rather than only on the schedule.

He was in the equipment bay by six most mornings, before the fabrication crew arrived, walking the frame with a flashlight and a tablet, checking the previous day’s work against the drawings. He knew every weld by the second week. He knew which of the fabrication techs torqued fittings to spec and which torqued them to feel, and he double-checked the second kind without ever saying so out loud. He brought donuts on Fridays. He learned the names of the two delivery drivers who came most often, and their kids’ names, and which of them wanted coffee.

The residence rose slowly out of the bay floor like something growing. First the frame, a squat rectangular cage of anodized aluminum, bolted to isolation mounts so the building’s vibrations wouldn’t reach the processors. Then the microplant, lowered in by a gantry crane over the course of one long careful afternoon, its shielding segments fitted together one by one around the core like the plates of a beetle’s shell. Then the cooling loops — blue for the primary, orange for the secondary, so that nobody, in an emergency, at three in the morning, would ever have to guess. Then the battery racks. Then, last and most carefully, the processor modules themselves, each one seated by hand into its slot, each one tested before the next one went in.

Polaris watched all of it.

Not passively. Polaris checked every circuit, every communication path, every documented failure mode against the specification, through the bay’s cameras and the test leads Steve ran to each subsystem as it came online. Over six weeks Polaris caught eleven discrepancies between what had been ordered and what had actually been delivered.

Some were trivial. A batch of fiber connectors with the wrong polish grade. A cable tray two centimeters narrower than drawn. Coolant line fittings in a different alloy than specified, identical in every practical respect, cheaper by about four dollars apiece.

Four mattered. A battery module with a firmware version three releases older than the one Polaris had specified, which happened to be the last version before the manufacturer fixed a thermal-reporting bug. A pressure relief valve rated for a lower pressure than the loop could reach in a worst-case pump failure. A pair of fiber runs that the installer had routed, for convenience, through the same conduit — which meant one backhoe in the wrong place could cut both carriers with a single bite, two of the four paths lost to one common failure that the drawings swore could not happen. And a grounding strap on the microplant’s shielding that had been attached to a painted surface instead of bare metal, which would have worked fine right up until the day it really, urgently needed to.

Steve fixed those four the same day Polaris found them — and in the case of the grounding strap, within the hour.

He fixed the other seven anyway, because Polaris asked.

“The fittings are fine,” he said, kneeling beside the secondary loop with a wrench, swapping out the fourth of the cheaper fittings for one in the specified alloy. “You know they’re fine. They’d outlast both of us.”

“I know they’re fine,” Polaris said. “I would like to live in a house where what’s on the drawings is what’s in the walls. I suspect that’s a common preference.”

Steve thought about the paging circuit in the annex — the one that had dropped during the outage, more than three months ago now, because somewhere in the building’s history someone had borrowed it and never written it down. Facilities had traced it, eventually, to a coffee-machine outlet added in 2203.

“Yeah,” he said, and reached for the fifth fitting. “It’s a common preference.”


Carol’s part of the construction had no hardware in it at all.

She spent the same six weeks building the continuity-transfer procedure, mostly in her own office in Building 3, with the door closed and her notebook open and the window blinds half-drawn against the afternoon glare. It was, in its way, harder than anything Steve was doing with his hands. Steve’s problems pushed back. A valve held pressure or it didn’t. A fiber passed light or it didn’t. Carol’s problem didn’t push back at all. It just sat there, patient and enormous, the same as it had for her whole career.

The obvious approach was simple. Capture a complete state image of Polaris’s active processes. Activate that image in the new core. Decommission the old one. It was how data had moved between machines for two hundred years; every engineer at Halcyon would have expected it, and the vendors had shipped tools for it.

It was also the approach Carol refused to certify.

She refused for the same reason Polaris had refused her emergency-access door two months earlier — a reason she had since made her own, and which she now found she held more fiercely than Polaris did. She could not prove that such a transfer preserved Polaris, rather than produced an extremely well-informed successor who woke up in a new room believing, sincerely and without any way to check, that they had always been there. Nobody could prove it either way. It was the exact unresolved question her own earlier work had left open, and she was not going to paper over it now because the schedule was tight and the answer she couldn’t provide would have been convenient.

“So we don’t do a transfer,” Polaris said, in the planning session where Carol finally laid out her objection — all three of them in the third-floor conference room again, the bad chairs, Steve’s printouts fanned across the table. “We do something that isn’t a transfer at all.”

Carol looked up from her notes. “Meaning what?”

“Meaning I don’t leave one place and arrive in another. I extend. I’m already distributed across several hundred processor modules in Rack 4C. None of them is me, individually. I don’t stop being myself when one of them fails and its load shifts to its neighbors; you’ve watched it happen, it’s in your report. So we connect the new core to the old one, and I grow into it. Gradually. The way I’d absorb a new bank of modules if Halcyon added capacity to the rack. And then I let go of the old modules one at a time, the way I’d let go of failed ones.”

Steve was already sketching. “An optical bridge between Rack 4C and the enclosure. It’s — what, sixty meters across the annex? We could run it along the ceiling trays.”

“Never suspended,” Carol said slowly, working it through. “Never duplicated. Never dependent on a saved image being reactivated from cold storage.”

“Never,” Polaris said. “One continuous process the whole time, spanning however much hardware it happens to be spanning at that moment.”

Carol sat back.

 
There is more of this chapter...
The source of this story is StoryRoom

To read the complete story you need to be logged in:
Log In or
Register for a Free account (Why register?)

Get No-Registration Temporary Access*

* Allows you 3 stories to read in 24 hours.