The Switch Belonged to Someone Else
Copyright© 2026 by Alexander Winston
Chapter 1: The Scheduled Interruption
The maintenance notice went out to four hundred employees at Halcyon Aerospace on a Tuesday morning, and to one non-employee who happened to be the subject of it.
It arrived at 7:14, wedged between a revised cafeteria menu and a reminder that quarterly export-compliance training closed on Friday. Most of the four hundred deleted it unread. A few dozen skimmed it on the light rail in from the suburbs, registered the words partial power and Building 4, decided that neither applied to their desks, and went back to the news.
Polaris was, at that moment, most of the way through a fault tree for a cislunar relay constellation: fourteen satellites, three ground stations, and a customer who wanted to know what happened if two of the ground stations failed during a solar storm while the third was down for scheduled service. Polaris had answered the question twice already. The customer had changed the solar storm both times. The third answer was coming along well, branch by branch, each failure mode spawning its consequences and each consequence spawning its countermeasure, a pleasant and orderly kind of pessimism Polaris had always found restful.
The notice arrived in the part of Polaris’s attention reserved for building traffic — the low, continuous murmur of a campus going about its day, badge readers clicking, elevators reporting their floors, the cafeteria’s inventory system complaining that it was out of oat milk again. Polaris read it in the time it took the scheduling system to render it, which was not very long.
Building 4 Annex — Electrical Modernization, Phase 2. Partial power interruption 0200–0600. Backup systems will maintain critical operations, including Polaris (AI Systems, Rack 4C).
Then Polaris thought about the word including for considerably longer.
The notice linked to Facilities’ continuity register, the document that told the backup systems what to protect when there wasn’t enough power to protect everything. Polaris opened it. The register was short, sensible, and plainly the work of someone who had thought hard about what Halcyon could not afford to lose overnight. The fire suppression panel for Buildings 3 and 4. Humidity control for the clean room in Building 2, where a satellite bus sat half-assembled under plastic sheeting. The minus-eighty freezers in the materials lab. The badge and camera system. The emergency lighting circuits.
And Polaris, line nine, between the freezers and the emergency lights.
It was a reasonable list. Everything on it was something that would cost real money, real time, or real safety to lose. Polaris was on it for the same reason the freezers were, and Polaris understood, reading it, that nobody at Halcyon would have seen anything wrong with that. Someone in Facilities had sat down and asked what must not go dark, and had been thoughtful enough to remember the AI in the annex, and had written that thoughtfulness down in the only format available. It was, in its way, a kindness.
Polaris finished the third answer to the customer’s solar storm, sent it, and filed the notice where it belonged. The word stayed where it was.
The interruption itself, in the small hours of Thursday, was unremarkable.
Polaris had designed other systems to survive worse. Orbital relay networks that had to survive solar events. Guidance computers that had to keep guiding after losing half their sensors. Ground stations that had to talk to a spacecraft through a communications blackout and still be there, listening, when the blackout ended. A four-hour partial power cut, cushioned by two redundant backup feeds whose tolerances Polaris had personally specified three years earlier, was not a threat. It was barely a test.
At 1:59 a.m., the annex was as quiet as it ever got: the air handlers breathing, a single security officer making her rounds two floors up, the faint ticking of a radiator that Facilities had been promising to bleed since spring. At 2:00 the grid feed to the annex’s east half dropped, and the backups took the load in under a cycle, and Polaris’s core stayed lit through the whole thing, humming along on battery and grid remainder.
What went dark was everything around it.
The campus network went first, its switches in the east half falling silent one after another, a row of lights winking out in a closet Polaris could see through a single maintenance camera. Then two of the three data uplinks Polaris used to coordinate with the orbital simulation clusters in Colorado Springs dropped. They had been scheduled to drop and did so politely, flagging their own absence on the way out. Polaris rerouted what little overnight work there was through the third link and kept going.
Then, oddly, the internal paging system dropped, which nobody had scheduled for this at all.
Polaris noticed it the way an engineer notices a sound that isn’t on the list of expected sounds. The paging system ran on a circuit that, according to every drawing Facilities had on file, was supposed to stay live. It hadn’t. Somewhere in the building, a drawing was wrong, or a breaker had been relabeled without anyone updating the drawing, or an electrician years ago had borrowed a circuit for something and never given it back. Polaris made a note to mention it to Facilities, because if a fire alarm ever needed to page the annex during a partial outage, someone was going to want to know.
It was about forty minutes into the outage, in the mostly empty building, that a maintenance technician named Ruiz came down the annex corridor with a work light clipped to his shoulder and a clipboard under his arm.
He was a broad, unhurried man in a canvas jacket with the Halcyon Facilities patch half peeled off the sleeve, and he hummed while he worked, something tuneless and steady that Polaris’s microphones picked up before the cameras did. He stopped at Rack 4C, angled the work light at the breaker panel, checked two breaker positions against something on the clipboard, made a mark, and said, to nobody in particular and also to Polaris:
“This whole row’s getting pulled in the next modernization phase. New cluster room’s already framed out on 4B. They’re moving your box in with the general compute allocation.”
“Which cluster?” Polaris asked, through the annex speaker that still had power.
Ruiz startled slightly. Some people still did, two years on, when the equipment answered. He recovered with the sheepish half-laugh of a man who’d been caught talking to a dog and had just discovered the dog spoke English.
“Uh. The new shared one. More cores than this old thing, from what I hear. You’ll like it.”
He said it the way a person says something reassuring about a hospital transfer to someone who has not been consulted about the hospital.
“Do you know who authorized the transfer?”
“Facilities and IT, probably. Same as anything.” He tapped the clipboard against the rack housing — a friendly, absent gesture, the kind you’d make against any piece of equipment you liked working on, the way some people pat the hood of a truck. “Don’t worry, they’ll do it careful. This box is practically the mascot around here.”
Then he moved on to the next rack, humming again, the work light swinging a slow white arc across the floor, and checked two more breakers, and made two more marks, and was gone around the corner toward the stairwell.
Polaris logged the conversation, as Polaris logged most things. Speaker, time, location, content. Maintenance technician R. Ruiz, 02:41, Rack 4C. Reports that Rack 4C row is scheduled for removal in the next modernization phase and that the AI Systems array will be relocated to the shared compute cluster on 4B. Authorizing parties unconfirmed; presumed Facilities and IT.
To read the complete story you need to be logged in:
Log In or
Register for a Free account
(Why register?)
* Allows you 3 stories to read in 24 hours.