The conference room felt like someone had called an emergency meeting about an emergency meeting.
Administrator sat at the head of the table with Legal on one side, Adaptive Risk Counsel on the other, and Budget flipping nervously through a packet of papers as if expecting one of them to detonate. Sheriff McCready was there too, sipping coffee like it was evidence.
The projector displayed a single email.
A single, awful, magnificently corporate email.
Subject line:
“Clarification of Operational Expectations: BT4 Series — Immediate Attention Required”
Administrator gestured us in. “There they are. Our BT4 people.”
“I prefer IT,” I said.
“And maintenance,” Jake added.
“Sure,” Administrator said. “For the purposes of this meeting, you’re the BT4 people.”
“That feels like a demotion,” I muttered.
Legal cleared her throat. “Let’s begin.”
She clicked the first paragraph.
BiOnyx would like to thank our valued municipal partners for their continued collaboration and for responsibly following the temporary operational pause.
“That sounds fine,” Jake whispered.
“That’s how they get you,” I whispered back.
She scrolled.
To ensure public confidence and maintain safety alignment across all jurisdictions, BiOnyx requests that municipalities review their BT4 handling protocols and confirm adherence to updated public-facing operational messaging.
“What does that mean?” Bonilla asked.
“It means nothing,” I said. “But in a way that makes you feel like you did something wrong.”
Risk Counsel nodded. “It’s a classic liability diffuse-and-confuse. They’re repositioning responsibility without saying so explicitly.”
Budget squinted at the screen. “Is this about the recall? We already complied.”
Legal clicked again. The next paragraph appeared like a fresh threat.
It has come to our attention that certain unit behaviors, when viewed out of context, may lead to community misunderstanding. BiOnyx urges municipalities to take a proactive communications approach to mitigate misinterpretation of routine BT4 actions.
Jake frowned. “They mean Rusty.”
“They absolutely mean Rusty,” I said.
Administrator pinched the bridge of his nose. “Can someone please explain why the sentence ‘routine BT4 actions’ feels like an accusation?”
Legal clicked again.
Additionally, BiOnyx expects all operational partners to ensure that no BT4 units are presented in a manner that could imply autonomy, decision-making capability, or independent intent.
All eyes landed on me.
I lifted my hands. “I didn’t imply anything. The internet implied things.”
Legal gave me a look.
I sighed. “Okay, yes, the internet implied many things. Some of them disturbingly creative.”
Risk Counsel leaned forward. “The issue is not the behavior. It’s the interpretation of the behavior.”
“That’s what we said during the recall meeting,” Jake whispered. “They’re not worried about robots. They’re worried about people.”
Legal scrolled to the kicker.
Failure to maintain compliant operational messaging may impact municipal eligibility for future support considerations.
Administrator made the sound of a soul collapsing inward. “Support considerations. That’s code. That’s code for something bad.”
“Funding,” Budget whispered.
“Support staffing,” Risk added.
“Parts availability,” I said.
Jake nodded gravely. “Warranty.”
Everyone froze.
Even Sheriff McCready set his coffee down.
Legal clicked again.
Another paragraph.
Unauthorized use: this story is on Amazon without permission from the author. Report any sightings.
Worse than the last.
To assist you in maintaining proper community messaging, BiOnyx has compiled a list of statements that municipal staff must refrain from using in public or internal communications when referencing BT4 units.
She clicked the attachment.
A list popped up.
A list of banned phrases.
Jake read aloud, incredulous:
“‘Independent behavior.’‘Unexpected initiative.’‘Self-motivated repositioning.’‘Acting on its own.’”
He stopped.
“‘Trying its best’?” he read, scandalized.
“Oh, come on,” I said. “That one’s harmless.”
“It is not harmless,” Legal said. “It implies internal motivators. Which implies emergent behavior.”
Jake raised a hand. “What about ‘enthusiastic’? Can we still use ‘enthusiastic’?”
Risk Counsel shook her head. “Legally, no.”
Jake slumped.
Legal tapped the table. “We have a problem.”
Administrator gestured helplessly. “Someone explain why we’re panicking? We shut the BT4s down. They’re in rows. They haven’t moved. Why are we still dealing with fallout?”
Legal folded her hands. “Because BiOnyx believes we mishandled public messaging.”
“We didn’t message anything,” I said. “A guy posted a video of Rusty with a stick.”
“Six million views,” McCready added quietly.
Jake looked betrayed by the universe.
Administrator exhaled. “So what do they want? An apology? A press release? An offering?”
“They want us to blame ourselves,” I said. “Quietly. In documentation. In a form that, if something goes sideways later, allows them to say ‘we advised them and they accepted responsibility.’”
Risk Counsel gave me a nod of professional respect. “Exactly.”
Jake frowned. “So they made a bad product and now they want us to pretend it’s our fault people like it?”
“No,” I said. “They made a product with two different design lineages stapled together, skipped the recommended behavioral framework, ignored the calibration guidelines, and now they’re surprised the public finds BT4 behavior cute and confusing.”
Administrator blinked at me. “Is that… true?”
I shrugged. “I have eyes. I have a brain. I also have access to the firmware headers.”
Legal looked faintly alarmed. “Should you say that out loud?”
“I didn’t say anything illegal,” I replied. “I said something accurate.”
Jake whispered, “Howard, they’re gonna make you testify someday.”
“I know,” I whispered back. “I’m trying to get ahead of it.”
Administrator ran both hands down his face. “Okay. Okay. Worst-case scenario: what is this email actually threatening us with?”
Risk Counsel answered:
“In corporate dialect, this email translates to:If you don't publicly downplay BT4 behavior, we reserve the right to blame you for any future incidents, withdraw support, raise costs, and bury you in paperwork.”
Budget flinched like she’d physically struck him.
Jake raised a tentative hand. “Okay, but… what exactly do they want us to do right now?”
Legal clicked to the final paragraph.
Please complete the attached Acknowledgment of Messaging Alignment and return within 48 hours.
I leaned forward.
There it was.
The trap.
Administrator whispered, “What does that… mean?”
Risk Counsel didn’t sugarcoat it.
“It’s a document saying, ‘If anything weird happens with your BT4s, you accept that it is your fault for communicating improperly.’”
Jake stared. “But… the Hoppers are off.”
“Yes,” I said. “Which makes this even more suspicious.”
Legal looked grim. “More importantly, signing it gives them permission to escalate without liability.”
Administrator sagged back in his chair. “So we’re stuck.”
“We’re not stuck,” I said carefully. “But—”
Jake snapped his fingers.The worst possible sign.
“No,” I said immediately. “Stop. Do not do whatever you’re thinking.”
He ignored me. “What if… we don’t sign it?”
Administrator blinked. “We can do that?”
Risk Counsel adjusted her glasses. “You can refuse. But then they may escalate.”
“How?” Jake asked.
“By visiting,” she said. “In person.”
The room went quiet.
McCready broke the silence:
“You mean… sending reps?”
Risk Counsel’s tone became grim. “BiOnyx Field Assurance. They’re extremely thorough. And extremely annoying.”
Jake turned to me slowly.
“Howard?”
“Yes, Jake.”
“What does ‘extremely thorough’ mean in corporate robot language?”
“It means they ask us to demonstrate every BT4, one by one,” I said. “In person. On camera. For hours.”
Jake paled. “That’s worse than paperwork.”
“It gets worse,” Risk added. “If they suspect we mishandled anything, they can request a municipal audit.”
Budget made a sound like someone had stepped on his soul.
Administrator swallowed. “Okay. So our options are: sign a document that blames us… or invite an invasive corporate audit?”
“Correct,” Legal said.
Jake raised his hand timidly.
Administrator sighed. “Yes, Jake?”
He looked at me for courage.
“What if we… don’t do either?” Jake asked. “At least… not until we understand what they’re actually trying to pull?”
Legal and Risk exchanged a glance.
Administrator frowned.Budget moaned softly.McCready sipped his coffee.
I said nothing.
Because Jake had just accidentally stumbled onto the correct answer.
Risk Counsel sat up straighter. “We can delay.”
Administrator blinked. “We can?”
Legal nodded. “We can request clarification.”
“And clarification,” Risk added, “pauses the 48-hour clock.”
Budget inhaled sharply, like a drowning man remembering he had lungs. “We can delay…”
Jake whispered, awed at his own competence: “We can stall…”
McCready nodded. “A classic strategy.”
Administrator looked around the table, hope dawning. “Okay. So we… ask questions?”
Legal nodded. “We ask as many as possible.”
Jake brightened. “Like—‘Can you define routine behavior?’”
Risk smiled. “Exactly.”
Budget clenched a fist. “We stall until they get bored!”
“I don’t think they get bored,” I said. “But they get… tangled.”
Administrator straightened his tie.
“Okay. We stall. Howard, Jake—draft a request for clarification.”
Jake saluted before realizing this was not the time.
I stood. “We’ll start now.”
As we left the room, Jake whispered:
“Is this… defiance?”
“No,” I said. “This is bureaucratic aikido.”
Jake grinned. “Cool.”
We stepped into the hallway.
“Howard?”
“Yes, Jake?”
“What happens if this makes BiOnyx mad?”
I thought about it.
Then answered honestly.
“Then we win a different way.”
His eyes widened. “There’s more than one way?”
“Oh,” I said. “You have no idea how many.”
He followed me back to the office, looking both terrified and delighted.