Chapter 18: The Territorial Firewall

【Elizabeth PoV】

The admin dashboard lit up my bedroom like a control tower at midnight.

Three monitors formed a semicircle around my desk, each displaying different data streams from Alfred’s phone. His location blinked on the left screen, tracking his pathetic journey through the school hallway. The center monitor showed his vitals—heart rate spiking at one hundred thirty beats per minute, cortisol levels through the roof, sweat gland activity off the charts. The right screen displayed the app’s interaction logs, recording every failed attempt at his so-called grinding strategy.

I leaned back in my chair, watching the disaster unfold in real time.

My calculus homework sat abandoned beside the keyboard, equations half-finished and completely irrelevant compared to this entertainment. Numbers and formulas couldn’t compete with watching Alfred terrorize random students while convinced he was executing flawless technique.

The center screen flashed red.

《Pencil Exchange Quest: Catastrophic Failure. -10 CP penalty applied.》

A laugh escaped before I could stop it, sharp and genuine. He’d actually managed to lose points while trying to gain them. The app had awarded him a negative balance, something I’d coded as a theoretical punishment but never expected anyone to actually trigger.

My phone buzzed against the desk, Seda’s contact lighting up the screen.

“Are you watching this?”

Her voice carried barely suppressed amusement, the kind that made her words sound dangerous even when she was entertained.

“He just recited OSHA safety guidelines to a first-year library assistant.”

“I saw. The carbon monoxide detector speech was my personal favorite.”

I pulled up the replay footage, watching Alfred’s eye twitch in slow motion as his mouth betrayed every ounce of confidence his brain tried to project. His body language screamed malfunctioning robot, all stiff movements and mechanical positioning. He looked like someone had uploaded combat algorithms into a civilian model and forgotten to include basic social programming.​

“He thinks he’s grinding CP from random girls now.”

Seda’s tone shifted, losing the amusement and gaining something colder.

“That’s a problem.”

Problem was putting it mildly. The app was designed for us, for our specific dynamic with Alfred. The parameters were coded around three users—him, me, and Seda. Watching him attempt to expand his target pool triggered something territorial in my chest, sharp and possessive.

“I’ll handle it.”

I ended the call before she could respond, my fingers already moving across the keyboard. Code appeared on the center screen, lines of text flowing faster than most people could read. The Monopoly Protocol had been a theoretical project, something I’d outlined but never fully implemented. Time to make it operational.

My other phone buzzed, the encrypted one I kept in my desk’s locked drawer.

The screen displayed a message from Tanaka, my lieutenant handling operations in the Shibuya district. Three rival gang members had been spotted moving product through our territory without authorization. The message included photos, license plates, detailed movement logs.

I typed a response with my left hand while coding with my right, multitasking between my legitimate schoolwork identity and my actual career.

“Logistical reorganization authorized. Standard protocol. No permanent damage. Send them a message about proper territorial respect.”

The response came back immediately, a simple affirmative emoji followed by confirmation of received orders.​

Being the current Oyabun of the Yakuza required constant attention, endless management of personnel and territory and revenue streams. Most people would crack under the pressure, struggle to balance high school student obligations with organized crime leadership responsibilities. I thrived on it, found the complexity engaging, treated both roles with equal calculated precision.

The code compilation finished, green text confirming successful integration.

《Monopoly Protocol: Active. Target parameters locked to registered users only.》

I tested the parameters, running simulations through the admin dashboard. If Alfred tried to use any app function on someone outside the approved target list, his phone would trigger multiple defensive responses. Overheating, error messages, GPS scrambling, the works. Complete digital lockdown disguised as random technical failures.

My calculus homework called from the desk corner, equations still demanding completion.

I pulled it over, solving derivatives with mechanical efficiency while monitoring Alfred’s vitals on the side screen. His heart rate had dropped below one hundred, breathing stabilizing, probably hiding in a bathroom somewhere trying to rationalize his spectacular failure. The pattern was predictable at this point, almost boring in its consistency.​

Thirty minutes of homework completion later, my encrypted phone buzzed again.

Tanaka sent confirmation photos. Three rival gang members sitting in a warehouse, zip-tied to chairs, looking appropriately terrified. No visible injuries, no permanent damage, just enough intimidation to ensure they understood whose territory they’d violated. Professional work, exactly what I expected from competent subordinates.

I sent back approval and instructions for their release, including the standard warning speech about respecting organizational boundaries.

The parallel between that situation and Alfred’s grinding attempt wasn’t lost on me. Different contexts, same fundamental violation—unauthorized activity in claimed territory. The rivals had learned their lesson through traditional methods. Alfred would learn his through code and carefully engineered technical failures.

My laptop screen split into multiple windows, each displaying different aspects of the Monopoly Protocol’s implementation.

The beauty of the design was its subtlety. Alfred would never know he’d been restricted, would just think his app had compatibility issues with other targets. He’d rationalize it as bugs, glitches, technical problems requiring troubleshooting. His brain would construct elaborate explanations rather than accept the simple truth—we controlled everything he experienced through that app.​

Control through code was cleaner than control through force, more elegant and sustainable.

The Yakuza taught me that power came in many forms. Physical intimidation worked for street-level operations, but real influence required information dominance, technological superiority, the ability to manipulate systems from the shadows. My position as Oyabun wasn’t maintained through violence alone. It was built on intelligence networks, digital surveillance, strategic positioning across multiple sectors.

Alfred’s phone was just another asset under my control, another system I’d compromised and repurposed for my objectives.

Seda called again, her timing impeccable as always.

“Did you finish the protocol?”

“Deployed and active. He’s completely locked to us now.”

“Good.”

She paused, background noise suggesting she was outside somewhere, probably walking between classes.

“When do we test it?”

“Tomorrow. Let him try his grinding strategy again, let him select some random target, then watch the app brick itself.”

The satisfaction in planning that moment felt similar to closing a major territorial deal, pieces falling into position according to carefully designed strategy. Alfred would experience confusion, frustration, maybe even actual fear when his supposed power tool suddenly malfunctioned. Those emotions would drive him back toward us, back toward the only targets that actually worked.

Behavioral conditioning through technical manipulation, elegant and effective.

“His vitals are still elevated. He’s definitely still freaking out.”

I glanced at the monitor showing Alfred’s biometric data. Heart rate hovering around ninety, breathing pattern irregular, stress hormones maintaining elevated levels. He was probably staring at his phone right now, studying that negative five CP balance like it held answers to the universe’s mysteries.​

“Let him stress. It builds investment in the system.”

Seda made a sound of agreement, that particular tone she used when watching plans unfold exactly as designed.

“See you tomorrow then. This should be entertaining.”

The call ended, leaving me alone with glowing monitors and half-finished homework.

I returned to calculus equations, solving problems while simultaneously monitoring data streams from Alfred’s phone. The dual focus came naturally, my brain comfortable operating multiple complex systems simultaneously. Some people needed dedicated attention for difficult tasks. I thrived in orchestrated chaos, found clarity in managing competing priorities.

My encrypted phone stayed silent for the rest of the evening, operations running smoothly without requiring additional intervention.

That was the mark of proper organizational structure—systems that functioned independently while maintaining alignment with central command objectives. The Yakuza ran like well-maintained code, each component performing its designated function, escalating to leadership only when parameters exceeded normal operational boundaries.

Alfred represented a very different kind of project, more personal than professional but requiring similar systematic approach.

The admin dashboard logged his movement as he finally left the bathroom, returning to normal school areas. His vitals gradually normalized over the next hour, stress responses declining toward baseline. He was recovering, probably constructing elaborate rationalizations for why his grinding strategy had failed so spectacularly.

Tomorrow he’d try again with renewed determination and modified tactics.

Tomorrow the Monopoly Protocol would activate, and his entire understanding of the app’s functionality would shatter into confusion and technical error messages.

I smiled at the monitors, watching data flow across multiple screens, each number and metric representing another aspect of a situation under my complete control.

In my world, unauthorized grinding wasn’t just ineffective—it was a violation punishable by total digital isolation and carefully engineered psychological pressure. Alfred would learn that lesson the hard way, through overheating phones and compatibility errors and mounting frustration that drove him exactly where we wanted him.

The calculus homework finished itself almost automatically, my hands solving equations while my mind planned tomorrow’s entertainment.

Control through code was beautiful in its precision, elegant in its execution, and absolutely impossible for targets to recognize until far too late.

Alfred’s phone data continued streaming across my monitors, each data point another confirmation of complete system compromise.

Tomorrow would be very educational for him.