Story code: ST-001203
Part 2: The Deviation Loop
Marcus’s thumb hovered over the violation report icon on his tablet, his eyes scanning Leo’s stiff posture. “Last chance, guys. Move, or I submit the report. That’s a automatic three-hundred-dollar penalty for queue obstruction, and your local network access gets suspended for thirty days.” I reached out and grabbed Leo’s forearm, attempting to force him forward. “Come on, Leo, just take a step. Walk through the red lines. I’ll buy you a double order of churros. Just move.” The moment I pulled him off his designated spot, the AR glasses hummed with a sharp, high-pitched frequency that made Leo wince. The script’s visual interface guide detected a physical deviation from the programmed path. Suddenly, Leo’s legs jerked. He stumbled backward, his boots clattering against the metal ramp as he performed a rigid, unnatural sequence of steps to realign himself with the holographic marker only he could see on his display. To anyone else, it looked like he was throwing a bizarre, silent tantrum, deliberately mocking the manager’s orders. “See?” Marcus yelled, gesturing wildly at Leo. “He’s doing it on purpose! He just jumped backward to stay on the ramp. What is wrong with you, kid? Explain what you’re doing right now!” Leo opened his mouth, his chest heaving with silent panic. He looked at Marcus, then at me, his eyes pleading. But no words came out. He couldn’t explain the instruction. The behavioral filter had hijacked his audio output channel, locking his speech interface to prevent him from saying anything that wasn’t pre-authorized by the script. He was completely mute, unable to defend himself or tell Marcus that he was physically locked in place by a developer’s parental override. The line of teenagers behind us was growing longer, and several of them pulled out their phones, recording Leo’s mechanical, jerky attempts to stand perfectly still. Whispers rippled through the crowd. “Is he on something?” one girl asked. “Look at his eyes. He’s totally out of it,” a boy responded. The public blame was landing squarely on my brother, while the real culprit sat comfortably in a climate-controlled SUV outside, analyzing the failure logs on a glowing monitor. “He has a custom filter running,” I explained to Marcus, my voice shaking with a mix of anger and desperation. “Look at the temple pieces. The blue lights are flashing in a developer pattern. It’s a parental control script that’s glitched. He physically cannot walk forward because the glasses are overlaying a solid boundary wall on his screen. He thinks he’s going to walk into a barrier.” Marcus didn’t care about the technical details. “I don’t track private family filters, and I don’t care about your family drama. The plaza policy is clear: if a user’s hardware or software interferes with the gaming environment, the user is liable. If he can’t clear the ramp, he’s violating safety rules. I’m finalizing the report now.” I looked down at my phone. I had exactly three hundred and fifty dollars left in my savings account-money I had spent the last six months earning by clearing tables and running errands. If Marcus submitted that report, my savings would be wiped out instantly to cover the fine, and we would be blacklisted from the only safe recreational space in the neighborhood. And worst of all, Uncle Devin would get away with it, hiding behind the excuse that we just hadn’t followed his safety guidelines properly. I looked up at Leo’s sweating forehead, his face pale under the harsh neon glow. The blue lights on his glasses pulsed faster, a clear sign that Devin was pushing a force-update to resolve the handshake error without manually releasing the lock. The script was pushing my brother to his physical limits, and I had to find a way to stop it before the security guard at the bottom of the ramp intervened. But how could I break a developer’s lock without the admin credentials?