-
Anything with more than one exclamation point in the subject line.
-
Anything containing the phrase “per my last message.”
-
Anything from a manufacturer that begins with “Out of an abundance of caution…”
Monday afternoon, I got all three.
The first two had already been handled. Facilities found the source of the “mysterious odor”—a forgotten lunch in the break room fridge, archaeological in age. The commissioner who discovered “reply all” and urgently needed his printer reset had been diplomatically redirected to “user education.”
For eleven blissful minutes afterward, VCIM was quiet.
Then my inbox chimed.
From: BiOnyx Municipal SupportSubject: IMPORTANT SAFETY BULLETIN — BT4 Series
Jake appeared in my doorway like he’d been force-propelled by dread.
“You got the abundance-of-caution email?” he asked.
“I did,” I said.
“Are you okay?”
“No,” I said. “But here we are.”
I opened it.
The body was a bureaucratic monument to avoiding responsibility. Paragraphs of carefully sanded-down legal English, faux-concern, and enough bold text to violate accessibility guidelines.
Out of an abundance of caution, BiOnyx is issuing an immediate temporary operational pause on all BT4-series municipal maintenance units…
“That’s Rusty,” Jake said immediately.
“Yes,” I said. “That’s Rusty.”
The bulletin continued:
…pending a proactive safety and messaging review following recent social media activity involving misinterpretation of BT4 unit behavior…
“Misinterpretation,” Jake repeated. “He held up a rebar flag. He was proud.”
“He was carrying something to the scrap pile,” I said. “People were proud.”
BiOnyx continued:
BT4 units are not sentient, self-aware, or capable of independent decision-making outside programmed parameters…
Jake wrinkled his nose. “That sounds defensive.”
“Everything in this email is defensive,” I said.
The directive:
BiOnyx recommends placing all BT4 units in Standby Mode and pausing non-essential public-facing operations until further notice…
Attached: Form 7-C: Temporary Deactivation Acknowledgment — Field Assets
At the bottom, in tiny corporate threat-font:
Failure to comply may limit BiOnyx’s ability to support you in the event of an incident.
Jake leaned closer. “That’s a threat, right?”
“A threat,” I said, “that went through Legal and lost most of its relationship with verbs.”
My phone buzzed.
From: COUNTY ADMINISTRATORSUBJECT: MEETING — “BIO NYX ROBOT THING”ALL RELEVANT STAFF. 20 MIN.
He’d spelled BiOnyx with a space again. I admired his consistency.
This story is posted elsewhere by the author. Help them out by reading the authentic version.
Jake squinted at the screen. “We’re relevant.”
“Unfortunately,” I said.
Administrator. Two commissioners. Budget Officer. Sheriff McCready. Adaptive Risk Counsel.And us—Valeroso’s everything department, the people who inherit problems like cursed objects.
Administrator waved us in.“Our BT4 people.”
“We prefer ‘IT,’” I said.
“And ‘maintenance,’” Jake added.
“You’re our everything people,” Administrator repeated. I wasn’t convinced that was better.
He pointed at the projected bulletin. “What does this mean in plain English?”
“It means BiOnyx saw Rusty’s viral video,” I said, “panicked, convened a meeting, panicked again, and wrote this after someone reminded them their shareholders also have the internet.”
Adaptive Risk Counsel cleared her throat. “More precisely, BiOnyx is establishing a documented cautionary measure so liability rolls downhill if anything happens.”
“To us,” Budget said flatly.
“To whoever they can point at,” she confirmed.
McCready squinted at the bulletin. “Standby Mode. That’s off, right?”
“No,” I said. “Standby is low-power, ready-state. Think: napping, not unconscious.”
Administrator steepled his fingers. “Can we comply?”
“Technically yes,” I said. “Practically, without the BT4s, trash will pile up, debris will remain debris, and public sentiment will deteriorate faster than Tater’s battery level.”
Jake nodded. “Tater is a tired boy.”
“But we managed before robots,” one commissioner said.
“Do we have pre-robot staffing?” I asked.
Silence.
Budget stared at the table like he hoped it would open and swallow him.
“No,” Administrator said. “We consolidated positions when we bought the BT4s.”
“Then going backward is not an option,” I said.
Adaptive Risk Counsel tapped the bulletin. “We can’t ignore this. But the language is vague.”
Jake leaned forward. “Meaning… loopholes.”
“I prefer ‘interpretive flexibility,’” I said.
Administrator sighed. “Howard, explain.”
I stood.
“AGPI built the task-control architecture that the BT4s use,” I said. “It expects one of two chassis designs: C-series—industrial, stable; or M-series—lightweight, mobile.”
“And the BT4?” Administrator asked.
“A hybrid,” I said. “Just heavy enough to violate M-series assumptions, just jittery enough to violate C-series ones. BiOnyx wanted the mobility of the M with the load-bearing of the C, so they took both, ignored AGPI’s compatibility chapter, and built… whatever the BT4 is.”
“A confused shopping cart,” Jake said.
“Yes,” I said. “At speed.”
McCready blinked. “Is that dangerous?”
“Only,” I said, “when someone who doesn’t understand the design decisions gets nervous about a viral video and writes an email.”
“And you can keep them safe?” Administrator asked.
“I already do,” I said. “Daily.”
Budget perked up. “So what do we do?”
“We comply,” I said. “Exactly. Literally. Painfully. We put units into Standby where it’s ‘feasible and safe.’ We pause ‘public-facing’ tasks. We annotate logs with excruciating detail. And where BiOnyx’s wording gives us discretion, we use it.”
Jake grinned. “Weaponized obedience.”
“Valeroso compliance,” I corrected.
Adaptive Risk Counsel nodded. “As long as your logs reflect good-faith interpretation, I can defend it.”
Administrator looked around the table.
“Any objections?”
No one spoke.
“Howard,” he said. “You and Jake go comply.”
I pulled up the BT4 fleet console.
Forty-three green dots glowed across the county map.
Rusty—BT4-12—rested in the yard, hazard rail draped with red tinsel someone in Sanitation had decided was festive. Clunker—BT4-01—trundled slowly across the feed, sounding like the ghost of machinery past. Sprinkles—BT4-07—danced in tiny circles by the loading bay.
Jake watched my shoulder.
“So… how do we start?”
“We sort,” I said.
I filtered by terrain and task.
“These units are on slopes. Not safe for immediate Standby.”“These are mid-haul. Must complete loads.”“These are in ditches. We don’t leave equipment half-embedded.”“These are public-facing. We actually pause those.”“And these,” I said, pointing, “are in the yard and non-public areas. They can soft Standby.”
“So Rusty stays visible?” Jake asked.
“As a decorative compliance object,” I said.
Jake laughed. “A Christmas statue.”
I selected the first batch:
SET_MODE: STANDBYPRIORITY: HIGHNOTE: PER BIO NYX BULLETIN 22-B.
“Send it,” Jake said.
I hit ENTER.
The console replied:
BT4-03 (Patches): ACK — ENTERING STANDBY (TRANSFER YARD).BT4-05 (Bucket): ACK — MOVING TO SAFE POSITION.BT4-17 (Hobbes): ACK — COMPLETING CURRENT TASK.
Rusty’s line blinked.
BT4-12 (Rusty): IDLE — COMPLIANT.
He didn’t move. Good boy.
I exported the logs and drafted the email:
To: BiOnyx Municipal SupportSubject: Valeroso County — Compliance Log (Day 1)
Body:
Per Bulletin 22-B, all BT4 units have been placed in Standby Mode where feasible and safe.Public-facing tasks paused.Logs attached (14 pages).Please advise if clarification is needed.
“You think they’ll read it?” Jake asked.
“They’ll skim it,” I said. “And miss the parts that matter.”
“And if they do read it?”
“Then,” I said, “they’ll learn what they built.”
I clicked SEND.
Outside, BT4s slowed, repositioned, and powered down in neat semi-organized clusters.
Valeroso County complied.
And tomorrow, BiOnyx would feel the abundance of it.