Chapter 6: Seeds of Doubt
Taiwan Edition v2
Location: Mirror Realm · Intermediary Island (Baiyue Commercial Port) Time: January—August 1023 Protagonist: Lin Zhao-ming
The fluorescent lights in hospital corridors are always that sterile, temperatureless white.
February 1023. Intermediary Island. Baiyue Commercial Port.
Lin Zhao-ming sat on a plastic chair outside a public hospital ward, staring at the acrylic plaque mounted on the wall: "Visiting Hours: 18:00–20:00." Rules are dead things written by the living, but the security guards at the door were not. You couldn't get in before six. And the moment the clock struck eight, the nurses punctually drew back the curtains and efficiently asked family members to leave in emotionless tones.
Every day, just those two hours. Sitting by his mother's bedside, listening to the rhythmic whir of various machines.
The remaining twenty-two hours of the day, he faced his computer screen.
The day his mother was admitted, he dropped everything and flew back. He initially thought it would only take a few weeks. But his mother remained in the hospital for a very long time. From critical condition to stable, to recovering, followed by exhaustive physical rehabilitation. He stayed on Intermediary Island; one month turned into two, two months turned into four. In the end, he stayed for eight months.
For those eight months, his life narrowed into two singular tethers: the hospital, and the computer.
Visiting hours were from 6:00 PM to 8:00 PM. But his mother had a large extended family. Aunts, uncles, cousins, his sister—they loved his mother deeply, and there was someone visiting almost every day. During those two visiting hours, the ward was often filled with several people at once. The actual amount of time Lin Zhao-ming could spend alone with his mother was usually just half an hour to an hour. On holidays, there were even more people, and sometimes he only had fifteen minutes before having to step out.
He never complained. His mother having people to keep her company was inherently a good thing.
But during this period, some exceedingly strange things began occurring back at the company.
He was excluded from the vast majority of meetings. He could understand that. He wasn't physically on Emerald Isle, and there were remote meetings he simply didn't need to attend. But inexplicably, there were a handful of them—syncs with vendor DMs, a freshly rebooted emergency Tiger Team—and every single one of them was scheduled precisely between 6:00 PM and 8:00 PM.
Cindy and K claimed they had coordinating conflicts concerning those syncs. The factory side needed to maximize testing bandwidth before six o'clock, meaning the DMs were only free after six. They even added, "Don't worry about it, we'll handle it."
Yet Lin Zhao-ming logged on every single day. Even while standing next to a hospital bed, he kept his earpods in and listened to the meetings on mute. His mother slept most of the time, and he would periodically talk to her, wake her up gently, and chat for a few sentences. The doctor had warned him: If she lost her will to live, she wouldn't make it. So Lin Zhao-ming spoke to her every single day he went. Sometimes a lot, sometimes just a little. But he made absolutely sure to speak.
And the voices in his earpods churned onward. Endless meetings blowing past 8:00 PM, hitting nine, dragging into ten. Auditing overlapping test results, debating various "creative" testing methodologies—proposals that sounded highly innovative, but produced the exact same outcomes as the previous attempt. Doing things simply for the sake of doing them. But you were required to be present.
What about the other meetings? Were there other meetings going on behind his back that he had zero visibility of? He was certain there were. But no one told him. When he asked, he got nothing. The boss's words continually surfaced in his mind: "Stop with the conspiracy theories. You're overthinking things."
Perhaps he was overthinking things.
But why were all those mandatory meetings scheduled during the exact sliver of time he was at the hospital?
He didn't ask.
The incident on Christmas Eve remained cemented in his mind.
Not Engineer Chen's voice. Not the phrase "thought about dying." He remembered those things, but they weren't what actively haunted him.
What haunted him was that meeting's minutes.
"Lin Zhao-ming submitted an analytical report suggesting a shift in investigation direction; noted for reference."
Noted for reference.
Those four words were burned into his retinas. Months of data analysis and hundreds of test results, entirely liquified into those four words. And the conclusion had remained utterly unchanged: The supplier must continue testing.
He had called a halt to it. On Christmas Day, he had single-handedly made the calls and sent the messages, tearing the momentum out of the machine. Engineer Chen could rest; the suppliers could finally breathe.
But the core problem remained unsolved.
There was absolutely no issue with the energy core module—he was certain of that. Hundreds of tests had passed flawlessly. The failure cases manifested exclusively on the new system. If the issue existed within the intersection of the new system and the old module—the timing, the handling of edge cases—you could order the supplier to test their module until the end of time itself and they would never isolate the anomaly.
There was one other vector: Substitute materials. Someone suspected the supplier had secretly swapped out components. But the reports from the manufacturer's side stated definitively that there had been no component swaps in years. Furthermore, intuitively—would several completely independent suppliers simultaneously swap components at the exact same moment? It defied logical probability.
But Lin Zhao-ming recognized one grim reality. If you shifted the blame to substitute materials, there was an immense upside: It justified a hard push to replace them entirely with highly customized, proprietary parts.
The business of custom parts was astronomically lucrative. Hundreds of millions, even billions in gross output value. Exactly which tier those parts sat at, and exactly whose pockets that money ultimately lined, Lin Zhao-ming didn't know. He only knew one thing: The colleagues on his immediate team wouldn't see a significant fraction of it, but they would nonetheless passionately champion the initiative.
At the time, he hadn't traced the webs that deeply. He just felt the vector didn't align with the data.
His technical report had articulated all of this with absolute clarity. But no one would listen.
So where exactly was the actual problem?
Lin Zhao-ming started digging back into the data.
Not because someone ordered him to. No one was ordering him to do anything. He had halted the testing while on vacation, and subsequently, his mother was hospitalized, forcing his immediate return. Back on Emerald Isle, no one so much as mentioned the incident to him again. As if it had never occurred.
But he remembered.
He remembered Engineer Chen's voice. Remembered that four-hour interrogation. Remembered the four words stamped onto the meeting minutes.
And he began to think: If the problem didn't lie with the energy core module, and instead resided in the system integration layer... which specific layer was it?
He didn't have the backend logs. He had never possessed them. ALC—the Soul Record Core—he only had baseline access privileges, allowing him to pull frontend test reports, symptom logs, and publicly available datasets. But the backend infrastructure—the comprehensive system logs and foundational runtime diagnostic records—he couldn't touch them.
This wasn't a new barrier. He had asked the boss about it previously. The boss had replied, "You're overthinking things."
So he utilized what he had.
He exported every single test report from the preceding six months. The distribution of symptoms, the time of the errors, the trigger conditions, which specific device models, which production batches, the exact environmental temperatures, and the operational sequences.
The volume of data housed within ALC was unfathomable. It wasn't an empty vessel. Quite the opposite—it was glutted. Tens of thousands of error logs, thousands of status updates. Tags, classifications, contextual notes. Every single entry written by a human being, and every single entry stamped with a reference serial number.
The problem was: None of it aligned.
The test reports utilized one numbering convention, JIRA (the project management system) utilized another, and the product specifications utilized a third. For the exact same symptom, Department A would log "Hardware Interface Timeout," Department B would tag "Firmware Version Mismatch," and Department C would abruptly close the ticket with "Unable to Reproduce."
At his previous company, Lin Zhao-ming used to spend two days a week writing custom scripts to synthetically align datasets across disparate departments. One formula, one Excel mapping table, and it was entirely structurally resolved. He used it himself to save massive amounts of time, and gradually introduced it to his peers. From one person using it, it grew to two, and eventually evolved into the entire team's baseline standard.
He had attempted the exact same integration here at Aura Synthesis.
But the reaction here was entirely alien.
To be fair, it wasn't that no one was working. Other colleagues were actively building tools. For example, there was a mapping table for converting energy core units into module specifications—reportedly provided by a vendor, but internally branded as an "in-house developed" standard tool. Every vendor recognized it, everyone utilized it, and it eventually became the entire team's operational system.
It wasn't that there was no space for utility tools. There was, and others had successfully deployed them.
But Lin Zhao-ming acutely observed one critical distinction: Every single one of those tools was engineered for "unification." Converting Format A into Format B, mapping this specific name to that specific name. A flat table, a rigid rule, brittle and fixed in place.
What he wanted to build wasn't unification. It was abstraction.
Unification says: This specific serial number equals that specific serial number. One-to-one mapping, hardcoded in. Abstraction says: Uncovering the foundational, underlying architecture to exponentially increase compatibility, allowing data from disparate hardware to automatically self-align. Bypassing the need to manually build a brand-new mapping table every time a new product drops.
The two concepts sounded similar. But one was taping over a leak, and the other was replumbing the entire architecture.
He figured he could start with a Minimum Viable Product (MVP). Build a localized demonstration model, prove the concept worked, and gradually pitch it outward.
The feedback from the boss was a barrage of deflections: "A tool just for your own personal use doesn't contribute value to the company." He was then handed a laundry list of contact info—the director of this engine, the head of that department—and ordered to go negotiate a systemic overhaul of the entire Enterprise Resource Planning (ERP) infrastructure.
"I can construct a demonstration case first," Lin Zhao-ming offered. "Just to showcase the viability. Wouldn't that be cleaner?"
"How many people have bought into your demonstration case? Does your team agree? Do the vendors agree? Can you bridge it across departments?"
He froze. Once the conversation is violently escalated to the ERP infrastructural level, the concept of a "demonstration case" is instantly pulverized.
Meanwhile, his colleagues enthusiastically continued deploying their "unification tools." One crude mapping table after another, one brittle localized subsystem after another. Every single one lauded, every single one classified as "contributing value."
Lin Zhao-ming looked at those tools, and he didn't feel angry. It wasn't indignation; he just found the entire spectacle deeply bizarre.
Because those tools were incredibly agonizing to actually use. Initially, everyone complained ceaselessly. But complaining was irrelevant; functionality was irrelevant. The only thing that mattered was that the tool looked meticulously aesthetic, the facade was impenetrable, and the creators collected their accolades.
And after they collected their awards? The tools slowly faded into obscurity, abandoned on the shelf. Then, after a while, someone would architect a new one, the complaining would resume, the facade would be polished, the awards would be distributed, and it would be shelved once more.
An endless loop.
Lin Zhao-ming watched this cycle, finding it utterly meaningless. He aggressively insulated himself from participating in actions of such kinetic waste.
But he later discovered that one of the core mappings inside a heavily utilized mapping table was mathematically flawed. He hadn't thought much of it at the time. But the seed had already been planted.
He was forced to resort to the dumbest, most brutal methodology. Ripping out data rows one by one, manually aligning them line by line. Doing it himself, in absolute silence.
The study on Intermediary Island was suffocatingly narrow. One desk, one computer, one chair. Outside the window was a dense grid of dilapidated apartment blocks. Returning from the hospital past 8:00 PM, he would take a shower, sit down, and boot up the machine. And he would grind until three or four in the morning. He would sleep a few hours, wake up, and grind again. At five in the afternoon, he would leave for the hospital.
Every single day.
His workload during this period dwarfed anything he had ever executed while physically stationed on Emerald Isle.
Not because anyone forced him. It was because an echo refused to leave his head—an engineer with over a decade of experience, saying over the phone that he had pondered suicide. And the genesis of the entire nightmare likely had absolutely nothing to do with him or his team.
If Lin Zhao-ming found the genuine root cause, he could, at a minimum, mathematically prove that the supplier wasn't at fault. Those endless inquisitions and Sisyphean testing cycles never should have occurred.
March.
He began to notice the anomalies.
Within hundreds of fragmented error logs, there was a specific cluster of timestamps that stood out. They weren't randomized; they adhered to a pattern. Every time the system was forcefully wakened from hibernation, under specific operational sequences paired with a specific processing load, the anomaly would trigger.
The first time he isolated it, he chalked it up to coincidence. But when he synthesized three months of disparate data, the identical pattern manifested over a dozen times.
It wasn't random. It wasn't a coincidence. It possessed a mathematical rhythm.
That night, he sat in his study, staring at his monitor for a very long time.
He couldn't verify it with absolute, 100% certainty. Because he had zero access to the backend logs. All he possessed were frontend symptom readings—exactly like a doctor restricted to solely viewing a patient's temperature charts but forbidden from ordering an X-ray.
But the trajectory of those temperature spikes told him: The rot was on the inside, not the outside.
He drafted a comprehensive memo, organizing the scattered breadcrumbs and indicators, and fired it off to several key individuals.
No one replied.
April.
He plunged deeper.
This time, he intercepted a secondary vector—under the exact millisecond the system awoke, a highly specific cluster of memory blocks would register catastrophic anomalies. Not every single time, but exclusively under extremely specific gating conditions. It was astonishingly covert; if you weren't manually cross-checking agonizing lengths of raw line logs, it was invisible.
He began meticulously mapping his own cartography. No one ordered him to draw it, and no one knew he was building it.
This map contained: Every single recorded failure case, the geographical distribution of symptoms, the temporal rhythm of the anomalies, and his precise hypothesis of the root cause.
Hypothesis. He was acutely aware of the weight of the word. All he possessed was a data pattern; he possessed no terminal evidence. The evidence was locked in the backend, and the backend was barricaded.
But the rhythm was sharp, incredibly consistent. The longer he stared at it, the more crystallized the reality became: It wasn't localized hardware failure. It was embedded in the subterranean layers. Possibly the BIOS (Basic Input/Output System), possibly the firmware, possibly a driver, or potentially a lethal vulnerability within a specific initialization sequence.
He couldn't definitively name the culprit, but he had isolated the coordinate vector.
He picked up the phone and called Brother Qiang.
Brother Qiang was the PM on the supplier's side. They had collaborated several times previously while physically on Emerald Isle. Brother Qiang was fully briefed on the Christmas Eve incident; Engineer Chen was one of his direct reports.
"Brother Qiang, I just sent a packet over; take a look at it," Lin Zhao-ming said, his voice scraped raw. "During your next testing cycle, explicitly target the memory state during the fractional millisecond of system awakening. I heavily suspect those phantom anomalies from before weren't originating from your hardware; there's something bleeding out from our subterranean structural layers."
Silence hovered across the line for several seconds.
"Brother Zhao-ming, the granularity on this packet is incredibly fine," Brother Qiang muttered, dropping his voice to a low register. "I'll instruct my guys downstairs to run it."
"Thank you. Ping me when the telemetry comes back."
Call ended.
Lin Zhao-ming believed that if he could weaponize Brother Qiang's physical hardware telemetry as corroborating evidence, his hypothesis could advance into terminal certainty.
Over the ensuing weeks, Brother Qiang went dark.
Lin Zhao-ming assumed they were drowning in operational latency and that the testing cycles required time. He shelved it temporarily and rotated to excavating other vectors.
May. His mother finally woke up. The agonizing trudge from critical condition to stability to full consciousness had been excruciatingly long, but she had finally opened her eyes.
Lin Zhao-ming casually mentioned it to the company.
And instantaneously, every single meeting scheduled between 6:00 PM and 8:00 PM abruptly vaporized.
Not deleted one by one, but systematically eliminated in a unified sweep. The synced vendor meetings, the Tiger Team emergencies—all of them evaporated from that specific time band. As if they had never been scheduled in the first place.
Lin Zhao-ming stared at his calendar. He didn't hyper-analyze it. His mother was awake, and he no longer had to act as a silent specter with an earpod vibrating during visiting hours; this was an absolute positive.
But a microscopic tremor vibrated through his chest, incredibly faint. A fleeting pulse that vanished before it could solidify.
At the very end of May, an email landed in his inbox. It was the transcript of a massive, high-level structural review meeting convened deep within Aura Synthesis. Because he wasn't physically present on Emerald Isle, he had possessed zero visibility of the meeting's existence. The transcript was merely forwarded to him post-mortem.
He opened it.
Page three. The header on one of the slides screamed: "Initial Milestones in Systemic Stability Optimization."
His eyes locked onto it.
The architecture embedded within the slide—the symptom distribution matrices, the logical pathways for log cross-referencing, the precise methodology utilized for tagging anomalous clusters—he instantly recognized it. Because he had engineered it; he had burned through countless sleepless nights forging it, the precise packet he had deployed to Brother Qiang.
But the name affixed to the slide was not his.
Within the meeting minutes, an executive explicitly stated: "This optimization vector is highly promising; we've finally secured a tangible thread." Another individual immediately amplified: "Exponentially superior to forcing the vendors to endlessly run blind tests."
Lin Zhao-ming sat in his study on Intermediary Island, staring at his monitor.
He wasn't furious. Or rather, it wasn't that he was entirely devoid of anger. He simply couldn't manifest it.
He thought of the Cha Chaan Teng diners back in his childhood home of Hong Kong. Was the instant ramen delicious? That was the sole, terminal metric. You cook a bowl of noodles, the patron eats it, the hunger is vanquished. Who physically carried the bowl to the table, and who pocketed the spare change as a tip—did it fundamentally matter?
He sat there for an eternity.
And then he mathematically reconciled it to himself: Let it go. At a minimum, someone was accelerating the investigation. At a minimum, that specific vector was being aggressively audited. At a minimum, no engineer would ever be driven to the brink of suicide via endless, torturous blind testing over this specific issue ever again.
He would simply find new problems to solve.
But the history relentlessly regurgitated itself.
He would excavate a raw thread from deep within ALC. Deprived of the architectural privileges required to enact a direct fix, he would meticulously aggregate the telemetry and deploy it to the relevant stakeholders. It would plunge into a silent void. Or, a few weeks later, magically resurrect bathed in the spotlight within someone else's pristine presentation deck.
He was on Intermediary Island; he wasn't on the battlefield; he was stripped of the very right to defend his own kinetic output.
But he kept grinding. Because an image refused to decouple from his psyche—Engineer Chen's hollow voice echoing over a phone line. "Thought about dying." If the subterranean structural rot wasn't identified, the identical trauma would inevitably detonate again. If not obliterating Engineer Chen, it would obliterate someone else.
So he kept digging.
June.
His mother's vitals had violently stabilized, and aggressive rehabilitation was ongoing. Every day during those two visiting hours, he would gently push his mother in a wheelchair up and down the corridor. His mother walked painfully slow, and he walked agonizingly slow right alongside her.
One day, his mother halted in the glow of the corridor window, staring outward.
"While you've been anchored here all this time, what's happening with your job over there?" she asked.
"Still working," Lin Zhao-ming replied.
"Is it grueling?"
"It's manageable."
His mother looked at him and didn't press further. His mother possessed a lethal intuition for reading people, but she would never force you into a confession.
Lin Zhao-ming pushed his mother onward. The corridor lights remained that sterile, temperatureless white.
During that period, in the margins surrounding his log excavations, Lin Zhao-ming idly reviewed the firmware architecture of the "energy core"—the "GG file."
His initial intent was merely to construct a mental model of the underlying subterranean logic—understanding exactly what that foundational sub-layer was attempting to execute. But upon opening it, he realized a stark truth: The foundational logic was brilliant—simple, pure, flawlessly universal. Impeccable.
The rot was localized entirely "above" it.
Stacked haphazardly upon that pristine and simple basement layer was a bloated tower of functionalities comprising nearly half the total architecture. Layer collapsing upon layer; every single one branded with a name, every single one backed by a sprawling piece of documentation. But as he plunged deeper into the code—what in God's name was this bloated architecture actually executing? Did a single living soul actually know?
He interrogated several engineers. Not a single person could architecturally articulate it. Every vendor unanimously felt certain functionalities were inherently grotesque, but absolutely no one possessed the velocity to challenge it.
He breached it to the CTO.
Two Senior Principal Engineers instantaneously materialized and intercepted: "We currently have a highly classified Tiger Team actively auditing this vector. We'll deploy a brief to you subsequently."
A Tiger Team. On the other end of the line, the CTO visibly flatlined into silence. Neither of them had possessed zero visibility into the existence of this phantom squad.
But if they explicitly declared its existence, what countermeasure did you possess?
It wasn't his first collision with parasitic, dark-matter functionalities. Stay in the industry long enough, you see it everywhere.
The standard operating protocol was: You have zero idea what it executes, but since the system hasn't caught fire yet, do not touch it. "If it compiles, do not touch it." There is legitimate logic encoded within this—if you don't know what it executes, it mathematically guarantees you don't know the blast radius of detonating it. It isn't laziness; it's self-preservation.
But the environmental variables here were radically disparate.
The operational reality here was: The surrounding topography was already undergoing tectonic shifts. A totally new architectural framework was imminent; incoming AI integration was imminent. Those archaic, parasitic functionalities were no longer resting silently—they were actively generating kinetic friction with the incoming upgrades. The foundational prerequisite of "if it compiles, do not touch it" is that the system remains mathematically static. But now, it was violently unstable.
He cross-examined the vendors for months. Every time he demanded, "What does this function practically execute," it wasn't a conspiracy of silence—they fundamentally possessed zero idea.
The vendors weren't the only ones flying blind. He queried back into the hierarchy of Aura Synthesis, escalating layer upon layer. At terminal velocity, nobody housed an answer.
Everyone simply regurgitated a foggy, amorphous impression: "It seems to be a fossilized remnant from a legacy project." "There must be a logical justification for it, right?" "It's been hardcoded like this forever and hasn't triggered a macroscopic failure." But granular architectural specifications? Utter vapor.
It wasn't a guarded corporate secret; it was simply that no living soul had ever possessed the knowledge.
Lin Zhao-ming logically deduced at the time: If you possess zero architectural comprehension of its function, and it's actively generating kinetic friction—then surgically terminating it, and aggressively auditing the subsequent fallout, is the sole rational maneuver. It isn't radical. It is simply because the option of "ignoring it" had evaporated long ago.
The feedback from the boss remained brutally consistent: "These are explicitly outside your operational purview. You need to focus on familiarizing yourself with our established workflows, and comprehending the standardized procedures for every execution."
Lin Zhao-ming had maintained constant surveillance on those workflows. But the workflows silently executing beneath the table remained eternally cloaked from his view.
He temporarily shelved the initiative, pivoting back to his raw log analysis.
July.
His cartography had aggressively expanded into a massive blueprint.
The localized cross-referencing of hundreds of raw logs, over a dozen confirmed rhythmic patterns, and a handful of highly-probable vectors. Every single vector was explicitly tagged as a "Hypothesis." Because deprived of the backend logs, every single one remained technically anchored in conjecture.
But the aggregate weight of these hypotheses all converged onto a singular, burning coordinate: The anomaly was not hardware; it resided in the subterranean software strata. Most probably, the BIOS.
The bizarre reality was that the other departments weren't utterly ignoring the defect. They would constantly launch challenges, loudly debating: "Is it mathematically possible it's an obscure configuration setting?" "Could it be a flaw in this localized architecture?" It all resonated with immense logical validity, projecting the flawless illusion of a massive, unified hunt for the root cause.
But hunting and capturing are not synonymous. It wasn't that the individuals lacked kinetic drive—many were genuinely grinding. But the terminal output—the sprawling Ishikawa fishbone diagrams generated to map the failure—every single radiating branch systematically resulted in "Exhausted" and "No Error."
BIOS? No error. Firmware? No error. Drivers? No error. Hardware? No error. Energy Core Module? Active, ongoing testing parameters.
No errors across the board.
But the macroscopic system remained critically unstable. The cascading avalanche of user complaints was mathematically real; the terminal blue-screens were mathematically real.
Zero localized errors, but massive systemic failure.
Lin Zhao-ming stared at the Ishikawa fishbone diagram. He was fighting a bloody war attempting to exculpate the energy core, but when every single tertiary department aggressively deployed telemetry proving their localized architectures were flawless, what countermeasures did he possess? At terminal velocity, the global consensus inevitably dissolved into: "Alright then, let's keep hunting together."
The atmospheric pressure was profoundly distorted. As if everyone was burning massive amounts of energy, yet mathematically, everyone failed to secure a kill. As if everyone was actively engaged in kinetic work, yet the operational frontier remained frozen in time.
He would only comprehend it later: It wasn't an inability to capture a kill. It was a globally synchronized, unspoken pact to buy time.
But he hadn't pierced through to that conceptual layer yet. He merely found it immensely bizarre.
If the rot truly resided within the BIOS—or any subterranean software layer—it was statistically impossible for no one to have detected it. Someone deeply embedded within the system absolutely had to possess visibility. The architects forging the BIOS, the engineers patching the firmware, the devs writing the drivers—they stared at this architecture every single day; it was mathematically impossible they were utterly oblivious.
Yet no one uttered a single syllable.
Within the meeting minutes, those four letters—"BIOS"—had never materialized. Every debate, every terminal conclusion, remained eternally locked onto the hardware, the suppliers, and "the urgent necessity for optimized testing methodologies."
Lin Zhao-ming sat in his study, staring at his meticulously forged cartography.
He couldn't reconcile the logic. Maybe he was fundamentally flawed; maybe his pattern recognition algorithms were fatally distorted; maybe there were hidden architectural variables he lacked visibility into that rendered his hypothesis dead on arrival.
But a microscopic shard of dissonance remained wedged in his chest, entirely incommunicable. It felt as if there were specific variables—not variables that eluded him, but variables that someone explicitly did not want him to recognize.
He shook his head. Terminate the paranoia.
Keep grinding.
During this block of time, he frequently spoke with his wife over the phone.
Because he remained grounded on Intermediary Island, and his wife operated out of Emerald Isle. Every evening, before deploying to the hospital, he would initiate a call.
"What's the telemetry looking like on Emerald Isle?" he asked.
"Status quo," she replied. "What about your company's side? Has anyone inquired about your extraction timeline?"
"Radio silence."
Silence.
"And your mother?"
"Aggressively stabilizing, initiating mobility."
"That's exceptionally good."
Another patch of silence.
"Your vocals sound incredibly drained," his wife noted.
"Sleep deficit."
"You must actively maintain your physical integrity."
"Copy that."
Terminating the connection, he stood perfectly still by the window. The dusk settling over Intermediary Island; the claustrophobic density of the dilapidated blocks across the street. The condensation from air conditioning units impacting the pavement below—drip, drip.
Massive amounts of data clogged his mental bandwidth, desperate to be articulated. But he lacked the cryptographic key to encode it.
A man was pulverized to the brink of suicide by a single meeting. He aggressively aborted the testing, but the subterranean rot remained entirely unaddressed. The telemetry he bled to excavate was hijacked and weaponized by another. He viscerally sensed an immense, systematic distortion, but he lacked the architectural vocabulary to even isolate exactly where the distortion resided.
How do you transmit this data to your family?
He maintained silence. Departed the apartment. Deployed to the hospital.
August.
His mother was successfully discharged. Rehabilitation was aggressively ongoing, but she was cleared for home recovery. Lin Zhao-ming finalized all logistical deployments and primed his extraction parameters to return to Emerald Isle.
Prior to an egress, he occupied the study on Intermediary Island for one terminal night.
Eight months. Entombed within a study so claustrophobic he could barely pivot, staring into a monitor, he had excavated hundreds of esoteric logs, forged a sprawling cartography no living soul had ever witnessed, and deployed dozens of memos into a soundless void.
He believed that upon extracting back to Emerald Isle, he could finally deploy these assets. Face to face, aggressively locking onto the correct targets.
What he fundamentally failed to calculate was that the physical office on Emerald Isle had radically mutated during his eight-month absence.
He lacked visibility into who had been vaporized, who had been instantiated, whose coordinates had shifted, what assets had been reallocated, and how the relational architecture between the operators had been profoundly reconfigured.
He only knew one thing: He was fully primed. He possessed the telemetry, the rhythmic patterns, the terminal hypotheses.
He believed these armaments were sufficient.
Beyond the aircraft's window, the silhouette of Emerald Isle slowly crystallized from the atmospheric haze.
Lin Zhao-ming gazed down at the sprawling infrastructure below. Incredibly narrow, incredibly dense, as if every single monolithic tower were actively violently crushing into its neighbor.
What he possessed absolutely zero calculation of, was that the geometry he was plunging back into was entirely decoupled from the one he had evacuated.
The pieces across the global chessboard, during the void of his eight-month absence, had been violently and systematically re-ordered.
And he, clinging onto his cartography, his telemetry, his hypotheses, stepping back into the exact office he arrogantly assumed he recognized—
He had no idea he was stepping onto a chessboard he fundamentally failed to comprehend.
★ FLASHBACK C <We Fix It Together>
That night in the study on Intermediary Island—likely around May—Lin Zhao-ming was burning midnight oil, his cognitive processing slowly beginning to decouple and drift.
He had just mathematically verified that his telemetry had been hijacked. He sat immobilized for a very long time. And then his memory involuntarily executed a backward slide.
Five years ago. Identical geographic coordinates on Intermediary Island, identically triggered by his mother's medical collapse.
At that time, he was operating within Amerion. The Amerion Collective. Senior System Architect. He had been grinding there for years.
A catastrophic cardiac event struck his mother. He initiated an emergency extraction protocol and flew directly back to Intermediary Island.
The instant the aircraft hit the tarmac, while still initiating transit to the hospital in a taxi, his terminal was vibrating relentlessly. A core payment gateway backend had catastrophically destabilized post-update at Amerion, and transaction failure metrics were aggressively spiking per minute.
The subterranean architecture of that exact gateway had been engineered by him. Beside him, no other operator possessed the velocity to disentangle the incredibly complex dependencies within a viable timeframe.
Lin Zhao-ming stood in the emergency room corridor, gripping his luggage. Surrounded by the deafening sirens of accelerating ambulances and the kinetic chaos of nurses. He ripped open his machine attempting to establish a Virtual Private Network (VPN) uplink. The hospital's Wi-Fi signal was so catastrophically degraded he couldn't even execute a handshake.
At that exact millisecond, he mathematically concluded he was dead.
The operational logic of the corporate battlespace is brutally clear: The system detonated, you are geographically decoupled, you failed to execute a fix; therefore, the blood is entirely on your hands. He had already internally processed his termination.
And then his direct supervisor initiated an uplink. An American, an old veteran bristling with a massive beard.
Lin Zhao-ming intercepted the call, his vocal tone heavily fortified: "Boss, I'm sorry. I have full visibility on how catastrophic the telemetry is, but my mother is currently being wheeled into surgery, and I can't even lock onto the VPN. I will likely be utterly incapable of deploying a workaround for several hours—"
His cognitive subroutines had already preemptively compiled the incoming fire: "This is your project." "You need to figure it out." "The company is bleeding revenue every single minute."
But across the line, there was only a brief, momentary patch of silence. In the background, the rapid kinetic tapping of a physical keyboard could be heard.
And then the old veteran spoke, his voice carrying the calm, absolute velocity of pure granite:
"Take care of your mom, Zhaoming. Don't worry about the gateway. We fix it together."
Take care of your mother, Zhaoming. Don't worry about the gateway. We'll fix it together.
It was never an empty algorithmic pacifier; it was an absolute operational guarantee.
For the succeeding forty-eight hours, three elite engineers positioned at California HQ violently hijacked his architectural privileges. Not a single operator utilized the chaos to deploy an email assassinating his "project management metrics," no one initiated a subterranean whisper network condemning him for "evacuating to Intermediary Island the second the system caught fire." The old veteran personally breached the frontlines, leading the squads through two consecutive all-nighters, brutally and physically sealing the breach.
Once his mother's surgical execution concluded successfully, and Lin Zhao-ming re-established an uplink to the corporate email server, the first file he intercepted was an officially decommissioned incident post-mortem.
Under the "Contributors" column, the old veteran had explicitly bolted Lin Zhao-ming's name into the number one slot.
Within that specific corporate framework, the pronoun "We" possessed mathematical reality. It wasn't a decal slapped onto a ceramic mug, it wasn't a synthetic buzzword deployed by human resources modules.
When your kinetic stability was compromised, an actual operator would physically extend an arm and catch you. Genuinely catch you.
END FLASHBACK.
Intermediary Island. Study. A night in May.
Lin Zhao-ming's cognitive matrices violently snapped back to the present. The ambient noise of the air conditioning unit was deafening.
He stared down the monitor. Aura Synthesis's internal portal remained rendered. Scrolling across the top was a banner: "Our People First Commitment."
He locked his eyes onto it for an eternity.
Then he brutally terminated the browser instance.
He booted up ALC, re-engaging his grind.
Within these coordinates, there was no "We." From genesis to terminal execution, it had always been only him.
He had already acclimated.
JUICY POINT:
"During those eight months he spent on Intermediary Island securing his mother's survival, an unseen operator within the Emerald Isle office had meticulously re-ordered every single piece on the board. When he finally extracted back, he was stepping directly onto an alien chessboard he fundamentally could not comprehend. And he had absolutely zero visibility of this reality."