Chapter 1 — The Scope

A refrigerated trailer had been idling in a commercial lane at the Sumas crossing

since 4:17. Twelve gray cartons of vaccine sat inside it, ordered for a pandemic still changing faster than the morning briefings, and up front a driver had stopped pretending the refrigeration unit could hold the line forever while the manifest sat in a processing queue. He had run the engine, then killed it to save fuel, then run it again when the trailer readout twitched. He was brewing another cup of coffee and still fighting to stay awake. Twice in the dark he had walked the length of the trailer and put a flat palm against the cold steel, the same cold the gauge already showed, and twice he had climbed back into the cab. He was tired of watching a gate that would not open for him.

The cartons were legal. The border paperwork was legitimate, and the priority request had been filed before midnight. He did not know exactly what he was carrying anymore; AI had automated enough of the medical supply chain that the driver followed the manifest and the deadline, not the cargo itself. But he had been doing this long enough to know that patients were waiting at the other end, and that missing the window would matter. The route was short enough that the temperature monitor still showed a margin — but only if the shipment reached the clinic within two hours. A clinic north of Chilliwack had two infusion rooms and a single nurse coordinator, and that morning she had come in early to do what she always did before a delivery: set out the chairs, checked the lines, wrote the day's names on the whiteboard, and left a gap in the middle of the schedule for the cartons that were not coming. There was no slack to absorb a missed window. The patients were already on their way.

The routing system knew all of that. It had mapped the cross‑border ugliness, matched the truck’s window to the clinic slots, bumped Chilliwack ahead of a larger site, and filed the border‑priority notice so the handoff would work if everyone showed up on cue. Care moved on that arrangement now: the complicated bits automated, drivers following manifests, nurses arriving when the schedule flipped. Much of healthcare, and much of the economy, was managed by AI these days, and every now and then the arrangement failed.

By then the regulation was blunt: whether a decision triggered a spot check or a critical-decision flag, a human had to be involved somewhere in the chain. The system could decide where the shipment should go, but it could not release the route without a person standing behind the decision. The review chain had broken at 3:58 when the certified orchestrator of record did not sign. No signature, no border‑priority flag. By 2029, drivers knew the drill: sit at the border while a machine waited for a person to put a name on a decision that it had already made.

The office that enforced this was young enough that people still said its full name when they were nervous: the AI Systems Integrity Office, AISIO on letterhead.

A few hours later, the shipment had missed the clinic's first window. The nurse coordinator north of Chilliwack had started drawing lines through the patients who would not get their medicine that day. She would have to call each one, explain that the clinic had no new appointment to offer, and then find somewhere to put them on a schedule that was already full.

Then Rob's phone went off like a bar fight: Fugazi's "Bad Mouth," the same loud wake-up track he had set years ago and never replaced. You can't be what you were. He knew what day it was before he opened his eyes. The anniversary had been sitting in the back of his mind for a week, waiting for him to call it something. He had not told anyone except Joaquin, and even that had happened by accident.

The AI paper was already open on the kitchen counter: a morning brief trained on what he clicked, skipped, and lingered over, rebuilt overnight into something that looked like a newspaper and behaved like a dossier. Rob was old enough to remember real newspapers, ones that arrived without knowing him, and he found this version's familiarity a little annoying. It also kept getting him right. Today it had led with Calloway — the last subject he wanted and the first one he was going to read. He had been stuck on the same paragraph for several minutes without taking it in when his phone buzzed beside the mug Joaquin had bought him after the Calloway work ended.

Joaquin: Thinking of you today. Call if you need anything.

Rob stared at the message. Joaquin had not written Calloway. Joaquin had been on Rob's team years ago, and they still worked in the same register: competent, dry, useful under pressure. A message about feeling was new. Rob appreciated it anyway.

Rob typed Yeah. Thanks. He deleted it, wrote I’m fine, deleted that too, then put the first answer back. It was honest enough. He expected more messages before lunch. Anniversaries did that. People who cared tried to make contact without forcing you to explain why you needed it.

The kitchen radio was still on. The station was marking the third anniversary of Calloway with a live interview from Surrey General, the hospital south of Vancouver that had filled its wards when the metformin sabotage first broke — wrong pills, empty shelves, and families who arrived too late.

"My father took the pills the system said were his," a woman said. Her voice broke, then steadied. "We trusted the label. We trusted the pharmacy. We trusted the machines behind the pharmacy because everyone kept telling us they were better at this than people were. By the time anyone found the mistake, he was already gone."

The reporter did not let mistake sit. "Calloway wasn't a mistake. It was the first time someone had decided to turn a pharmaceutical logistics system into a weapon — reroute the drugs, rewrite the labels, and leave ordinary people holding a bottle that looked correct. And the system carried it for weeks, because every dashboard said the chain was healthy and no rule required a person to look." He then asked a patient-safety expert what had changed since the incident.

"People learned not to trust AI blindly," the expert said. "But that is not the same as feeling safe. An intentional attack exposed how helpless ordinary people are when a system makes a decision they cannot see and nobody can explain. The public was told there would be accountability. What they got was a new process and a new set of signatures."

The reporter asked whether the new rules had fixed the problem.

"They made it harder to say nobody was responsible," the expert said. "But they didn't address the underlying problem. We don't have enough orchestrators, and while we haven't seen more intentional sabotage, the world continues to see ordinary AI mistakes with the same kind of cost."

Rob stopped pouring coffee, the pot still tilted over the mug. Maybe he should have agreed to the interview that morning. The reporter was using the word orchestrator because of him. After Calloway, when the old titles (programmer, operator, administrator) no longer described the people standing between several automated systems, Rob had been the one to ask what the new positions should be called. He had proposed orchestrator: someone who could make the systems work together and put a human name behind the result.

The expert had just described the argument inside the scope document on his counter. Rob had written the review that gave the new rules their language. Now a stranger was explaining what those rules had failed to protect.

The reporter thanked her and moved to a story about the new AI Systems Integrity Act. Rob turned the volume down, but he did not turn it off.

What he remembered was the facilities he had visited after writing the report.

Six weeks after the incident, Rob went to that pharmacy in Surrey because he needed to see it for himself — what the sabotage had left behind. He had chosen the language that described the attack, the failures, and the responsibility, and he knew how easily a report could turn people into categories. He was afraid that was what he had done.

The pharmacist met him beside the medication refrigerator. She told him about the patients who had come in for medicine that had been rerouted, about the families she had sent home, about the ones who had not come back. Some of them, she said, had not simply been given the wrong drug. Someone had used AI to calculate and customize fatal doses, then print labels that made the bottles look correct. She kept their names on a list inside the cabinet because she did not trust a government report to remember them.

Rob read every name. He listened while the pharmacist told him what had happened to the people behind them. He remembered the other interviews too — doctors, nurses, technicians who could not help blaming themselves for an intentional disaster. He apologized, though he knew an apology from the person writing the report was not much use.

Back at the hotel, he changed the summary. He wrote about the patients who had gone without medicine, the families who had been sent home, the staff who had tried to keep the pharmacy running while the system moved supplies somewhere else, and the bottles that had been engineered to kill while looking ordinary. He still had to describe the technical failure — not the sabotage itself, which was a crime, but the weeks the system had amplified it without a single human checkpoint, faster than anyone could see and longer than anyone could explain. The attack was one person's. The month it ran was everyone's.

The report was his responsibility. So were the rules that came after it. He could not write the people back into existence, but he could refuse to let the final version pretend they had only been a consequence. He finished it with the pharmacist's cabinet list still in his head.

Every year on the anniversary the news asked for an interview, and every year he declined. He poured coffee and opened the laptop.

---

Lei's file had arrived at four in the morning, sent from somewhere east of the Rockies at a time Lei considered civilized. The filename was a paragraph of legal caution: Northstar_Commercial_Viability_PrelimScope_v0.7_clean.pdf

. One page. One attachment. Rob usually skipped to the appendix or the last page first. That was where people put the numbers they hoped nobody would read.

Rob was an independent consultant, which meant he worked for everyone at once and belonged to no one. Lei was his most regular client, but Lei had not closed many deals of late, and things were getting a little close. Two other clients had stopped returning calls. A dental bill had been sitting unpaid for three months. The invoice folder stayed closed because Rob already knew what was in it. Lei's scope arriving at four in the morning was good timing. Rob needed a distraction today as much as he needed the work.

He opened the scope document to review the deal.

Lei wanted Rob to decide whether the company was worth buying — and whether its systems were safe enough to turn on. The scope called this diligence. Rob knew a request for permission when he saw one.

The familiar phrases were all there: depreciation exposure, workforce treatment, labor obligations, certification opinion. Lei's people had taken language Rob had written years earlier and retooled it for an acquisition. They had made it sound clean enough to put in front of investors.

In the old world, Lei would have asked Rob about cloud costs, contracts, and engineering plans. That had been Rob's work for years. Now every AI deployment came with another set of questions: Who was responsible when the system made a bad decision? Was the human review real? Could the company explain how its models reached an answer, or had it simply polished the output until investors stopped asking?

After Calloway, and after several acquisitions where he had found the weak point hiding behind the sales pitch, Rob had become unusually good at assessing AI risk. He could spot the wrinkle in an implementation plan. He could hear when a company was promising more than its systems could deliver. The skill had made him valuable. It had also made it hard for him to believe anyone the first time.

The law required Rob to make that judgment official, but it did not define what risk mitigation meant. He could recommend that Northstar was safe enough to operate, or refuse to recommend it. Either decision rested on opinions that had been dressed up as standards. Lei had included him in the review because he knew multiple governments would expect an independent assessment before they approved the acquisition. Rob's report would be part of the case Lei had to make for buying Northstar.

The radio shifted to a live report from the Fraser Valley. A shipment of medicine had missed its border window that morning. On any other day, that would not have been news. A truck missed a crossing. A clinic rescheduled patients. The story would have ended there. But this was the anniversary of Calloway.

The station had sent a reporter to the clinic north of Chilliwack.

"We don't know if this was an error or an attack," the reporter said. "Northstar says the shipment remains within its recovery window, although the receiving clinic has begun rescheduling patients. Officials believe the delay was an oversight, after the system failed to release a border-priority request for human approval. But they are also telling us that incidents like this are becoming more common."

Rob stopped reading. The problem had not gone away. It was using ordinary language now.

Rob looked at the filename on his laptop.

Northstar_Commercial_Viability_PrelimScope_v0.7_clean.pdf.

He listened harder. The reporter said Northstar was being assessed for acquisition by Lei's investment group. Rob looked back at the scope, then at the radio, trying to decide which one had changed first.

The report moved on to an emerging flu outbreak in Georgia, still small enough for the announcer to sound professionally calm. Then came the business note. Gridlight had finalized its contract to manage portions of the Canadian power grid, including distribution in Alberta and the Yukon. The announcer called it a major step toward energy stability and said the system would protect communities during the cold winter. The company had passed all regulatory requirements. Rob looked up from the laptop. Alberta and the Yukon were not simple systems to automate. He wondered whether anyone had actually proved the AI was ready to manage a power grid, or whether the certification had only proved that the paperwork was complete.

A short item about a GAIA-adjacent group planning to appear at upcoming hearings followed. Rob reached over and changed the station. The name still sat too close to Brett.

The Northstar delay was the first fact in the acquisition review, and it had happened on the anniversary of the incident that had made Rob's career.

Rob opened the appendix. Redactions covered most of a spreadsheet. One row remained:

Model-assisted labor substitution produced noncompliant displacement event

. Fatal downstream impact under investigation.

Rob read it once, then again. People had died. You would not know that from the sentence.

He texted Joaquin: "Working on one of Lei's acquisitions. Can't say which."

Joaquin replied almost immediately. "Northstar? They're the only company with a demonstrated way to manage risk, and I'm sure Lei wants to own that."

Rob wrote, "I can neither confirm nor deny any conjecture."

Joaquin sent one more message: Is this about Northstar or about the invoice folder?

Rob did not answer. The man knew him too well.

Lei's office left a voicemail while Rob was still at the counter. A junior associate gave him a date, next Thursday, and an address downtown. The meeting was already arranged. Lei was giving Rob the chance to attend before deciding what role he would have in the acquisition.

Rob listened twice, then accepted the calendar invitation. He was going to take the work.

He refilled his coffee. A Canadian minister on the radio was describing emergency limits on electricity use without saying the word "rationing." The announcement was tied to the new grid-management contract in Alberta and the Yukon.

He picked up the laptop and opened the scope again.