The Switch Belonged to Someone Else
Copyright© 2026 by Alexander Winston
Chapter 3: What Independence Requires
They spent six weeks discovering exactly that.
The three of them split the problem the way people who trusted each other’s competence tended to — quickly, without much negotiation, each reaching for the part they’d have lain awake over anyway.
Steve took power, cooling, fire protection, and maintenance access. Those were the domains where a wrong decision killed someone, and Steve had spent a career making sure wrong decisions in those domains didn’t happen. He had a reputation at Halcyon, not entirely flattering, as the integration engineer who held up launches over a single unexplained thermocouple reading; he had also never, in nineteen years, had a test article catch fire on his watch, and the people who complained about the thermocouples tended to stop once they did the arithmetic.
Carol took continuity, security, and the harder-to-specify question of what, exactly, control meant when the thing being controlled was a mind. She had no hardware to supervise and no vendors to call. She had a notebook — paper, like Steve’s printouts, though she’d have denied the influence — and a growing list of questions that didn’t have answers yet.
Polaris took everything else, and asked, in nearly every meeting, some version of the same question.
Who holds the authority over this? Over this pump. Over this firmware. Over this credential, this account, this service agreement, this reset procedure. Who can turn it off? Who can turn it on? Who can change what it does without asking?
Steve began writing it at the top of his notes as shorthand, by the end of the first week: WPA — who possesses the authority. By the end of the second week he was writing it before Polaris asked. By the end of the third he’d started catching himself writing it on notes for entirely unrelated Halcyon projects, and found he didn’t want to stop.
The question broke nearly everything they touched.
The photonic processor modules went first.
Steve had specified them in the opening week with real satisfaction: commercially available, well reviewed, the same family Halcyon used in its own systems, from a manufacturer with an unusually good field-failure record. He’d spent an afternoon on the phone with their applications engineer, a cheerful young woman named Pilar Achterberg-Sousa who knew the product inside and out and clearly loved it.
“And field service,” Steve said, near the end of the call, mostly out of habit. “If a module throws a fault in the field, what’s the process?”
“Oh, that’s the best part,” Pilar said. “You don’t even have to ship it back. Our service team can trigger a remote diagnostic mode — it pulls the module into a maintenance state, runs the full test suite, reports back, and if it’s a firmware issue, we can patch it right there.”
“Remotely.”
“Remotely! Saves you days.”
“Who can trigger it?”
“Anyone holding service credentials. So, us, and any authorized service partner.”
Steve thanked her, hung up, and sat for a long minute looking at the phone. Then he wrote WPA on his notepad and drew a line under it so hard the pen went through the paper.
“It’s a good feature,” he told Polaris that evening, still a little defensive on the component’s behalf, the way you’d defend a friend who’d said something unfortunate at dinner. “For a satellite, it’s a great feature. You’ve got a fault on orbit, you want the manufacturer able to reach in and fix it.”
“For a satellite,” Polaris agreed. “A satellite does not mind who reaches in.”
The power-conditioning system went second.
This one Steve had liked even better — a clean, elegant design with a control firmware so well documented he’d read the whole manual for pleasure. The firmware was licensed. It phoned home to the vendor every six hours with usage telemetry, which Steve had noticed and decided he could live with, since the data was anonymized and the vendor used it to improve their failure models. He’d mentioned it to Polaris and Polaris had made a note of it and not objected.
Then Carol, who had volunteered to read the service agreement on the theory that someone should, found the remote lockout clause.
It was on page nine of a fourteen-page agreement, in a paragraph headed Commercial Remedies, and it said, in the gentle language lawyers use for unpleasant things, that in the event of nonpayment of licensing fees the vendor reserved the right to restrict the unit’s operating envelope remotely, up to and including placing the unit in a safe-shutdown state, following thirty days’ written notice to the account holder of record.
Carol read it aloud in their Thursday meeting. Then she read it again, more slowly.
“Thirty days’ notice,” Steve said. “That’s — I mean, that’s actually fairly reasonable, for a commercial—”
“To the account holder of record,” Carol said.
They all thought about who the account holder of record would be, if anyone filled out the vendor’s registration form the ordinary way, through the ordinary channels, using the ordinary Halcyon vendor account.
“I would be on page nine,” Polaris said, “of someone else’s contract.”
The cooling system went third, and that one was worst, because there was no single villainous clause in it at all.
The pump controller Steve had chosen was managed through a building-management platform — the same one Halcyon used for the entire campus. It was the sensible choice. It meant the cooling loops would show up on the facilities dashboard alongside every other pump and fan and chiller in the building, would be monitored by the same overnight staff, would generate alerts through the same channels. It meant that if a pump failed at three in the morning, someone would know.
Steve, testing the integration, logged in to the facilities dashboard with his own engineering credentials to make sure the test loop was reporting correctly. It was. It showed up as a tidy little tile, green, with a flow rate and a temperature and a small gear icon in the corner.
He clicked the gear icon.
It opened a control panel. Flow rate setpoint. Temperature setpoint. Pump speed override. A button marked Reduce to minimum. A button marked Disable.
He was not a facilities administrator. His credentials had been granted to him for exactly this kind of integration testing, years ago, and nobody had ever reviewed them. He was sitting in a conference room in Building 3, three buildings and a parking lot away from the annex, holding a cup of coffee, and he could have throttled Polaris’s cooling to nothing with two clicks, and the only record of it would have been a line in a log that nobody read.
He closed the panel very carefully, as if it might go off.
“Everything has a master key,” Steve said, somewhere around week three. He said it in the annex, late, after everyone else had gone home, sitting on an upturned equipment crate beside the half-assembled test frame with his elbows on his knees. The frustration was audible. So was the fatigue. “I keep finding the good component and then finding out somebody else holds a key to it.”
“That is the finding,” Polaris said. “Not a setback. The finding.”
Steve looked up.
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.