VCIM was currently wrapped in that silence.
We had sent the first wave of Standby directives. We had annotated the logs. We had complied with BiOnyx’s bulletin with such exacting specificity that I was beginning to feel a faint moral obligation to send their legal department a fruit basket.
A very small fruit basket.
Jake stood next to me at the console, staring at the map as the BT4 fleet transitioned into our “interpretive compliance protocol.”
The dots shifted slowly. Not off. Not inactive. Just… obedient in a highly bureaucratic sense.
From the yard camera, Clunker—BT4-01—rolled himself into a dramatically safe, flat piece of ground, let out a noise like a resigned tractor sigh, and powered into low-motion amber.
“See?” I said. “Compliant.”
Jake tilted his head. “He sounds depressed.”
“He sounds like a machine with a worn bearing,” I said.
“But he looks depressed.”
“He looks like he’s following manufacturer guidelines,” I said. “There is a difference.”
The beauty of malicious compliance is that it doesn’t require sabotage, rebellion, or antagonism. It only requires following instructions exactly the way they were written, rather than the way someone hoped you would interpret them.
This is a dangerous philosophy in the hands of the competent.
Jake and I grabbed clipboards—purely for theater; all the data lived in the system—and stepped outside to begin on-site verification.
The yard was a patchwork of BT4 obedience.
Sprinkles (07) sat perfectly still in a spot that was technically within the designated non-public zone but still visible from the main access road. Someone—probably Sanitation—had stuck a bow on him.
“It’s festive,” Jake said.
“It’s exhibit A,” I said. “If BiOnyx objects, they can take it up with the concept of public morale.”
Farther down the row, Rusty—BT4-12—had positioned himself beside two other units. He hadn’t moved since the previous evening, but his hazard rail still held the bit of tinsel from yesterday.
The yard camera caught him in the soft light of morning: proud, still, quietly glowing amber.
Jake put a hand over his heart. “He looks noble.”
“He looks stationary,” I corrected.
“But noble,” Jake insisted.
“I’m not arguing with you,” I said. “I’m correcting your interpretation.”
“Those are the same thing,” he said.
“Not in this department.”
We inspected the local fleet.
Daisy (02) had put herself in the exact center of a gravel square as if drawing an invisible X.Patches (03) had drifted three inches off a flat spot and refused to correct, because the bulletin said “minimize public-facing movement.”Scoot (10) had power-limited himself so drastically he moved like a nervous tortoise anytime wind hit him.
Jake scribbled on his clipboard.
“This is all technically correct,” he said.
“Yes,” I said.
“And also unhinged.”
“Yes,” I said again.
We reached BT4-17 (Hobbes), who sat in a ditch with the haunted look of someone contemplating existence.
His display read:AWAITING TASK RESOLUTION: INDETERMINATE.
Jake crouched. “Buddy… what does that mean?”
“It means,” I said, “AGPI’s control stack is waiting for confirmation of a C-series torque threshold that BiOnyx never implemented because they wanted M-series mobility.”
Jake frowned. “So… he’s confused?”
“He’s patient,” I said. “He will wait until the heat death of the universe for that torque reading.”
“Should we… help?”
A case of theft: this story is not rightfully on Amazon; if you spot it, report the violation.
“He is in a ditch,” I said. “Ditches are non-public. He is safe. He is not actively working. He is, per bulletin language, in ideal Standby.”
Jake made a small noise. “This feels wrong.”
“It’s not wrong,” I said. “It’s compliant.”
We had just finished verifying the yard when my phone buzzed.
Jake peered over my shoulder.
“It’s… the county Facebook group,” he said.
I opened it.
A resident had posted:
“Saw one of the trash robots sitting all quiet with a bow this morning. Is he okay?? #RustyStrong”
Within ten minutes:
-
A dozen comments
-
Two memes
-
Someone edited Rusty into a Christmas card template
-
Someone else suggested a parade
“Oh no,” I said.
“Oh YES,” Jake said.
We watched in real time as Valeroso County adopted the BT4 Standby state as a civic movement.
Someone had taken a picture of Clunker (01) sitting motionless and captioned it:
“When corporate tells you to pause non-essential tasks but your soul remains essential.”
Budget Officer commented a single exhausted emoji.
At noon, the phone rang.
Not the red line.
The “special ringtone” line—BiOnyx Support Escalation.
I answered.
“This is Howard.”
“Hello!” a too-cheerful voice said. “This is Brandi from BiOnyx Support Level II. We're following up on your Day 1 compliance logs.”
Jake mouthed: Oh no.
I said, “Wonderful. What can I clarify?”
“We just wanted to confirm,” she said, “that Standby Mode does not include… repositioning into decorative alignment.”
Jake choked on air.
I didn’t blink.
“Correct,” I said. “Standby does not include repositioning. The units repositioned before entering Standby, per the directive’s clause allowing for safe positioning.”
“Oh!” she said brightly. “We also noticed one unit—BT4-12—appears to have a… festive adornment?”
“Correct,” I said. “That is not unit-initiated. That is community-initiated.”
“I… see,” she said. “Our concern is maintaining public confidence.”
“Public confidence,” I said, “is extremely high.”
She hesitated. “We also noticed BT4-17 flagged as ‘Awaiting Task Resolution.’ Shouldn’t units be fully idle?”
“Only if their internal task list supports safe immediate suspension,” I said. “BT4-17 is waiting for a torque threshold that your C/M hybrid chassis design does not produce reliably.”
Silence.
“Torque… threshold?” she repeated weakly.
“Yes,” I said helpfully. “Specifically the C-series completion value that conflicts with the M-series motor profile BiOnyx implemented.”
Longer silence.
I could hear her typing like she was trying to Google her way out of a career.
“We… will escalate this to engineering,” she said finally.
“I look forward to hearing their insights,” I said.
She hung up so fast the phone clicked like a dropped wrench.
Jake stared.
“You just… told them.”
“I told them the truth,” I said.
“You told them the truth in a way that hurts.”
“I complied,” I said.
We rolled out for county-wide checks.This involved leaning into the truck’s heater and occasionally stepping out to “observe compliance markers” while Jake took photos of BT4s being technically obedient.
-
BT4-05 (Bucket) sat mid-haul beside a dumpster, having decided that completing the lift cycle was “unsafe for Standby.”
-
BT4-14 (JuneBug) had turned away from a set of flashing railroad signals so strongly that he was now facing a tree.
-
BT4-11 (Peanut) had taken the phrase “pause non-essential public-facing tasks” to mean “avoid being seen by humans at all costs,” and had tucked himself behind a Parks shed.
Jake took pictures of all of them.
“For documentation?” I asked.
“For posterity,” he said.
We stopped at a drainage site where BT4-19 (Patcher) had found a small hole in the shoulder gravel and decided it was the county’s most pressing existential threat.
He cycled through three repair motions, then powered into Standby with the resigned dignity of a craftsman prevented from finishing his art.
Jake sighed. “Poor guy.”
“He’s fine,” I said. “He obeyed the bulletin. He is paused. He is safe. He is… deeply frustrated, but software cannot experience that.”
“He looks frustrated,” Jake insisted.
“Everything looks frustrated when paused mid-task,” I said.
By four o’clock, we returned with a tablet full of annotated images, position logs, and behavior notes.
Jake flopped into his chair. “We are absolutely getting sued.”
“We’re not getting sued,” I said. “We are complying.”
“Howard,” he said seriously, “BiOnyx is going to read that torque comment and die.”
“They asked a question,” I said. “I answered the question.”
“You answered it like a physics professor who was tired of everyone’s nonsense.”
“Yes,” I said. “That is my default state.”
The county Facebook page continued erupting with support.
Someone made a digital Christmas sweater with Rusty on it.
Someone else wrote:
“They tried to silence our little metal workers but we STAND BY our robots!! #StandByStandby”
Jake laughed so hard he nearly dropped his tablet.
“BiOnyx is going to hate us,” he said.
“Good,” I said.
I finalized the Day 2 compliance log.
All BT4 units are in Standby Mode where feasible and safe.Public-facing operations paused.Non-public essential functions deferred or queued pending safe transition.Minor chassis-behavior inconsistencies observed consistent with BT4 C/M hybrid design.
Jake read over my shoulder.
“You’re just… telling them they broke their own robots.”
“They did,” I said.
He grinned. “I love malicious compliance.”
“It’s just compliance,” I said.
“Uh-huh.”
I clicked SEND.
Outside in the yard, Rusty sat immobile under the soft glow of an amber indicator, tinsel catching the last bit of afternoon sun.
Obedient.
Stationary.
Unintentionally heroic.
Valeroso County was in Standby.
BiOnyx was in denial.
And tomorrow, things were going to get interesting.