Skip to main content

Chapter 7: Deduction

Taiwan Edition v3


Location: Mirror Realm · Emerald Isle Time: September—October 1023 Protagonist: Lin Zhao-ming


The first day Lin Zhao-ming returned to Emerald Isle, he walked into the office.

Not the kind of office you see during WFH—a grid of boxes on a screen. An actual, physical office, with desks, chairs, and human beings. The hum of the air conditioning, the sound of the coffee machine operating, the kinetic friction of people walking back and forth.

He hadn't been back in eight months.

He stood at the entrance, gazing inward. It felt identical, yet simultaneously alien.


The first anomaly he noticed was the desks.

More accurately, it was the bizarre hybridization characteristic of transitional phases.

Several floors remained in the legacy configuration. Deep desktops, high partition walls, wide corridors. Nominally, those floors operated on a hot-desking model—no one was officially allocated a fixed seat. But his colleagues—the vast majority of them—migrated there anyway. When they arrived, they sat in the exact same seat, day after day, in absolute silence, forging an unspoken consensus. No one explicitly stated it was your seat, but it was definitively your seat. There were mugs on the desks, pen holders, Post-it notes slapped onto the partitions. A pirated version of a "land deed"—completely undocumented, yet universally respected. If you occupied the seat, you had staked your territory.

Some even manually dragged a second chair over. Two people occupying a single desk, crammed together. The system didn't explicitly forbid it; the hot-desking mandate merely stated there were no fixed seats, it didn't state you couldn't sit physically conjoined. So they sat together, naturally, normally. No one raised an objection.

Reflecting on it later, Lin Zhao-ming realized that the specific floor wasn't the terminal metric. People remained on the new floors, and people evacuated the legacy floors. Seating arrangements didn't dictate operational destiny. The genuine leading indicator was entirely different—it was "relationships." But at the time, he hadn't pierced through to that conceptual layer yet.

The newly renovated floors were on the opposite side. The desks were narrow, the corridors had aggressively contracted. Partitions existed in some zones, and had been entirely ripped out in others. Securing a seat on this floor was frictionless—few people came here, and no one came here to "stake territory."

Lin Zhao-ming deployed to the new floor.

Not because the seating was superior. Architecturally, it was inferior—narrow desks, zero partitions, no fixed allocation. But it was computationally simple. You arrive, you sit, you execute, you leave. You never encounter that specific gaze of, "You're sitting in the wrong seat."

It wasn't that he couldn't infiltrate the legacy floors; it was that he possessed zero requirement to do so.

He extracted his glasses and put them on.

He had purchased this pair out of his own pocket. The company provided a few shared communal pairs, but nowhere near enough to equip the entire floor. Besides, he fundamentally despised holographic projection interfaces—having your entire operational workspace vomited into the ambient air, completely visible to whoever happened to walk past. He couldn't execute tasks under those parameters. Wearing the glasses, the visual telemetry was restricted exclusively to him. It was silent, sterile, secure.

He engaged the glasses, and the interface illuminated. Visible only to his retinas.

He scanned the immediate perimeter. Some facial signatures were recognizable, others were completely foreign. Many of the faces from the previous era had simply vanished. He had zero visibility into exactly when those individuals had been extracted; no one had ever updated his telemetry.

There was one face he could mathematically verify he had never seen before. The man was occupying a seat adjacent to the window. The facial geometry was unknown—Lin Zhao-ming had operated within this specific team for two years; he could definitively confirm this individual was an exogenous variable. But the way he occupied the seat didn't resonate with the kinetic signature of a new hire. The chair was calibrated to a highly specific angle. The mug on the desk wasn't paper; it was proprietary hardware. He wore his glasses, his holographic projection neutralized, isolated entirely to his own visual field. He wasn't violently scanning the perimeter. He lacked the disoriented gaze of someone attempting to map the coordinates of the restrooms or the pantry. K approached from the opposite vector, locked eyes with the man, and stated: "That packet you deployed yesterday. I audited it; I'll brief you on it shortly." The man raised his head: "Copy that. I'm listening." K closed the distance, and the two immediately engaged in a low-bandwidth exchange. Lin Zhao-ming couldn't intercept the audio. It wasn't deliberately encrypted; it was simply modulated at a volume that inherently didn't require global broadcasting. Lin Zhao-ming rotated back to his primary monitor. He couldn't articulate exactly what felt anomalous about that specific interaction. Or perhaps it wasn't anomalous at all. An operator is laterally transferred in, they previously shared operational history, they execute a brief sync—mathematically normal. He terminated the processing thread.


For the preceding few days, his primary operational focus was auditing legacy emails—filtering backward, email by email, starting from the exact hour of his extraction to Intermediary Island.

Eight months of archived logs. Hundreds of packets. The vast majority were materials he had either skimmed or actively deprioritized while stationed on Intermediary Island.

Only by executing this retroactive audit did he mathematically grasp that three executives had been vaporized. One retired, one executed a lateral transfer, and one "departed for personal reasons." In R&D, the architectural org chart remained nominally static, but massive swaths of personnel from Product Engineering (PE) and Project Management (PM) had violently evacuated, their roles forcefully absorbed by R&D. Consequently, the entire R&D division was exclusively executing PE tasks; no one possessed the bandwidth to engage in actual Research & Development.

The cohort that previously drove terminal decisions had evaporated.

The operators currently occupying these coordinates were an entirely different species.


He had voluntarily initiated an RTO sequence. Return to Office. Thirty-nine days.

It wasn't a corporate mandate; it was his own autonomous calculation.

During his eight-month exile on Intermediary Island, every single kinetic action he had executed was mediated through a monitor. Emails triggered zero responses, memos were deflected into the void, analytical telemetry was hijacked. He had derived a terminal conclusion—

If you lack physical presence on the battlefield, your kinetic output mathematically equals zero.

Therefore, he returned. For thirty-nine days, he would operate face to face, engaging in direct acoustic transmission. Armed with his telemetry, his rhythmic patterns, his cartography, sitting inside physical briefing rooms, executing transmissions directly into the auditory receivers of the correct targets.


Mid-September.

Lin Zhao-ming engineered a simulation.

It wasn't sanctioned by the corporation; no one ordered him to architect it. He built it autonomously—fusing the massive datasets he had excavated during his eight months on Intermediary Island with fresh testing telemetry he had acquired upon his return, forging a system-level simulation completely localized within his own segregated environment.

The objective of the simulation was singular: Replicate the catastrophic intermittent blue-screen.

While isolated on Intermediary Island, he had already forged a sprawling map. The rhythmic patterns were mathematically flawless. Every time the system executed a wake command from hibernation, under highly specific operational sequences, burdened by a highly specific processing load, the anomaly detonated. He logically deduced the rot was localized in the subterranean layers—the BIOS or the firmware.

But a deduction is merely a deduction. He lacked terminal proof.

So he ran the simulation.


The simulation churned for days. The vast majority of the runtime was clear—normal, stable.

Then, deep into the graveyard shift of the fourth day, he locked onto the monitor.

At the exact millisecond of detonation—that fractional sliver of a second when the system violently tore itself from hibernation—he intercepted an anomaly.

A null pointer.

Under mathematically normal parameters, this pointer should invariably index to a valid memory address. But during the chaotic millisecond of the wake sequence, driven by a catastrophic flaw within the initialization hierarchy, it indexed to a vacuum. An empty address. Null.

The system subsequently attempted to fetch data from that address, violently colliding with Null. The fallout—dictated by the real-time processing load, the microscopic timing, and dozens of tertiary variables—sometimes resulted in a catastrophic system crash, and sometimes resolved into localized instability. Those crashes were the exact "bizarre, inexplicable malfunctions" the end-users were continuously flagging.

Lin Zhao-ming stared dead into the monitor.

The phantom he had hunted for over half a year was sitting right there.

It wasn't a defect in the energy core, it wasn't supplier incompetence, it wasn't a hardware failure. It was a null pointer buried deep within the subterranean initialization sequence of the macroscopic system. A microscopic flaw residing at the absolute bedrock code level.

He inhaled deeply.

Then he forcefully rebooted his own cognitive loops: This is a simulation. A localized environment he had engineered himself; it is not the live production system. What he was observing was a pointer indexing to Null within his synthetic architecture. Whether this mathematically correlated to the live-fire chaos occurring within the production system was entirely unconfirmed.

What he possessed remained, fundamentally, a deduction.

But this deduction aligned with absolute algorithmic perfection against every single rhythmic pattern he had aggregated over the preceding eight months.


The next day, he initiated contact with the CTO.

The CTO was still active; Lin Zhao-ming had verified this baseline reality immediately upon his return—the CTO had not yet been vaporized.

He scheduled a one-on-one sync. Video uplink. The CTO was operating out of a disparate physical facility.

Lin Zhao-ming screen-shared his simulation telemetry. He walked through the execution step by step. The rhythmic patterns, the raw data, the simulation parameters. And finally—the null pointer.

"I intercepted this specific block of code," he stated, his vocal tone resting at baseline absolute zero. "I logically deduce this is the root cause. But the comprehensive logs—the telemetry from the live production environment—are locked in the backend. I possess zero access privileges. Can you run the query for me?"

The CTO did not instantaneously execute a response.

Silence.

During a standard one-on-one sync, when deploying a technical query, the target typically initiates an immediate conceptual counter-volley. Or they execute a buffer phrase like "Let me process that," or demand, "Expand on that vector."

But the CTO's silence sustained for a fractional baseline longer than normal.

It wasn't an eternity; perhaps merely a delta of two or three seconds. But Lin Zhao-ming registered the anomaly.

Then the CTO transmitted: "The granularity of your analysis is exceptionally high. I have visibility on the pattern you isolated."

A deliberate pause.

"I will require a window to audit the backend."

"What's your operational timeline?"

"I'll do my best."

Call ended.


Lin Zhao-ming sat at his hot-desk in the physical office, staring at the monitor.

"I'll do my best."

Not "I will run the query for you." Not "I'll take a look." It was "I'll do my best."

He possessed zero cryptographic key to decode the actual meaning of those four words. Perhaps it was merely the standard operational deflection of an overloaded executive; perhaps it translated to absolutely nothing.

He terminated the processing thread. He waited.


Several days elapsed.

There was an engineer embedded in the office who operated exclusively on firmware. Lin Zhao-ming had synced with him previously; the man was a lethal operator, deeply knowledgeable in the architecture. When you deployed the term "null pointer," his cognitive receivers instantly decoded it.

One day, Lin Zhao-ming intercepted him in the pantry and engaged in a low-bandwidth sync. Casually, Lin Zhao-ming dropped a probe: "That anomaly within the initialization sequence. Have you established any visibility on it?"

The target locked eyes with him, his facial geometry shifting as if preparing to execute a data dump. Then he abruptly aborted and stated: "I'm on leave starting tomorrow."

"Copy. Where are you deploying to?"

"Heading home."

"What's your extraction timeline to return?"

"Unknown."

Lin Zhao-ming registered the anomaly, but elected not to press further. Leave was leave.

One week elapsed. Zero re-entry.

Two weeks. Zero re-entry.

Lin Zhao-ming queried other operators. An anonymous node supplied the intel: "Intel suggests he's not spinning back up."

"Decode that. He tendered resignation?"

"Unconfirmed, but highly probable."

One month later, the HR global broadcast hit the servers. Resignation confirmed, effective date retroactively locked to the exact day his "leave" initiated.

Lin Zhao-ming stared at the email vector.

He aggressively retrieved the visual data from that day in the pantry. The way the engineer's eyes had locked onto him. The aborted data dump, ultimately reduced to the terminal phrase, "I'm on leave starting tomorrow."

He lacked the data to decode what the engineer had actually intended to transmit. And he would remain mathematically blind to it for eternity.


Subsequently, the CTO tendered resignation.

The delta between the two events was less than a week.

Lin Zhao-ming acquired the intel via a global email broadcast. A brutally truncated notification. "The CTO has departed the corporation due to personal reasons, effective immediately." Standardized boilerplate expressing gratitude for his kinetic output, paired with wishes for a luminescent future.

Effective immediately.

Lin Zhao-ming parsed the text twice.

The delta between his presentation of the null pointer simulation and this broadcast was less than two weeks. He had requested the CTO audit the backend logs. The CTO had transmitted "I'll do my best." And then the CTO had been evaporated.

He possessed zero visibility into whether the CTO had actively executed the query. Zero visibility into what the CTO might have intercepted. Zero visibility into whether the CTO's extraction was in any mathematical way correlated to his localized operation.

He possessed zero visibility across the board.

He only knew one absolute certainty: The architecture he had excavated—the null pointer, the cyclic patterns—every single operator who possessed visibility into those specific assets had been systematically neutralized.

The firmware engineer. Vaporized. The CTO. Vaporized.

During his operational exile on Intermediary Island, there were still nodes who possessed the bandwidth to decode his transmissions. The CTO was online; operators capable of parsing a null pointer were online. When Lin Zhao-ming initiated an uplink, there was a receiver capable of catching the packet.

Now, every single capable receiver was being systematically terminated, one by one.


Within the physical office, it wasn't as if absolute radio silence was maintained.

There were subterranean transmissions indicating the CTO's extraction was an unmitigated disaster for the org. This data flowed strictly through encrypted channels—pantry chatter, never broadcast on open comms.

Occasionally, a colleague would initiate a lateral sync with Lin Zhao-ming. Not technical data exchanges, but probes configured like: "Do you calculate the org executed the wrong personnel?"

Lin Zhao-ming maintained an absolute zero-state. He deployed no stance.

Because he mathematically understood—regardless of whether he categorized the termination as logically sound or fatally flawed, his transmission could be intercepted and weaponized. Both vectors provided lethal leverage to an adversary.


Actually, that specific colleague wasn't the sole node attempting to probe him.

Lin Zhao-ming had previously—both during his exile on Intermediary Island, and following his RTO sequence—attempted to deploy his data packets to a massive swarm of targets. He briefed them on the initialization catastrophic failure, briefed them on his deductions, briefed them on his global architectural assessment of the system's terminal rot.

The feedback from the vast majority? Zero bandwidth for support. Or the aggressive deployment of cognitive firewalls pretending zero comprehension.

You transmit the term "null pointer," and they return: "Error. What pointer?" You transmit "telemetry rhythm," and they return: "Error. What rhythm?" It wasn't a genuine inability to decrypt the packet; it was a deliberate, weaponized refusal to do so. Acknowledging comprehension mathematically required deploying a stance, and deploying a stance equaled absorbing kinetic risk.

There had been a microscopic subset of operators who initially provided bandwidth, who genuinely decrypted the packets. But those nodes—a significant percentage of them had been extracted. Voluntary vaporizations, corporate restructurings; regardless of the mechanism, they were offline.

The pool of supporting nodes contracted, while the pool of terminated nodes expanded. The surviving operators were consequently subjected to an exponential spike in the risk parameters for supporting him. It was a self-feeding algorithmic loop. Every time an operator was neutralized, the noose governing the loop tightened another terminal fraction.


That specific week at the end of the operational cycle, he extracted back to his residential coordinates.

His wife was deployed in the kitchen.

"You've initiated re-entry," she noted.

"Affirmative," Lin Zhao-ming replied, disengaging from his tactical pack and seating himself on the sofa.

"Have you executed caloric intake yet?"

"Negative."

His wife closed the distance and sat adjacent to him. "Your operational bandwidth seems heavily constrained recently."

"Status quo. I'm running diagnostics on a highly complex anomaly over there."

"Have you isolated a terminal solution?"

Lin Zhao-ming idled his cognitive processors for a moment.

Had he isolated a terminal solution.

He had. Within his localized simulation, a null pointer was violently indexing a blank address block. The mathematical genesis of hundreds of user crash reports. The sole mechanism driving the supplier into months of agonizing, infinite loop testing. The exact vector that drove an engineer to the absolute brink of suicide on Christmas Eve.

He had isolated it. But he fundamentally lacked the parameters to prove it—because he lacked the backend logs. And the exact nodes possessing the clearance to authorize access to those logs had been systematically vaporized.

He had isolated it. But he possessed zero operational targets to transmit that data to—because every single node capable of decrypting the packet had been extracted from the battlespace.

He had isolated it. But he couldn't even confidently deploy the syntax "I found it"—because what he possessed, up until the terminal moment of the universe, remained solely a deduction.

"Diagnostics are still ongoing," he replied.

His wife locked eyes with him. "Maintain operational integrity."

He executed a smile. A microscopic, almost invisible modification of facial geometry.

"Copy that."


Nighttime. His wife had entered sleep mode.

Lin Zhao-ming was stationed in his study.

He booted up his terminal and locked his retinas onto his own cartography. Eight months of intense, grueling fabrication on Intermediary Island, synergized with the simulation telemetry he had generated post-RTO. The exact geographical coordinates of the null pointer, the precise distribution architecture of the geometric patterns. Every single vector converged with devastating lethality onto a solitary coordinate.

But this cartography was now entirely unreadable to the surviving population.

His memory banks accessed the study on Intermediary Island. Accessed the specific execution cycle in June, when he had ripped open the energy core's firmware specifications, registering the absolute anomaly for the first time: Stacked upon a brilliantly pure, sterile sub-layer of foundational logic was a bloated, hyper-dense superstructure constituting nearly fifty percent of the total operational mass. Layer crushing layer; every single node branded with an identifier, every single node supported by sprawling documentation. But when he probed the surrounding forces regarding the actual, physical utility of those architectures, absolutely no one could formulate a coherent sequence of logic.

At that specific coordinate in time, he hadn't possessed the bandwidth to aggressively decompile the anomaly. He had merely logged the visceral sensory input—there were hidden architectures buried deep, deep beneath the surface geometry.

And now, locking optics onto that null pointer, locking optics onto that firmware specification, locking optics onto the CTO's two-to-three-second buffer lag prior to his extraction—

These fragmented nodes began violently orbiting within his cognitive center.

He lacked the processing architecture to compile them into a unified macroscopic rendering. He couldn't mathematically compute why the CTO had been evaporated, why the firmware engineer had been evaporated. Why every single probe he launched seemed to impact a subterranean landmine that was strictly designated as a no-fire zone.

He possessed only one verifiable absolute: He had successfully excavated every single terabyte of actionable intelligence he was physically capable of extracting.

And subsequently, every single operator who possessed visibility into his payload had been systematically, flawlessly evaporated.


"He had successfully excavated every single terabyte of actionable intelligence he was physically capable of extracting. And subsequently, every single operator who possessed visibility into his payload had been systematically, flawlessly evaporated."