Chapter 19: Reorganization and Survivors
Location: The Mirror Realm・Jade Mirror Island Time: May 1025 — February 1026 Protagonist: Lin Zhaoming
The study.
When he reached this point in his writing, he paused for a long time.
Not because he couldn't remember. But because he remembered too much. The tone of HR. The phrasing of the document. The exact position of the pen on the table. The tree outside the window.
He remembered too many things. But he didn't know which ones to pick and write down.
Because whatever he wrote down would become "the version." And the lesson he had spent four years learning was—every version is curated.
He took a deep breath. Continued writing.
May.
A meeting appeared on his Calendar. Scheduled by HR. "Catch-up." Thirty minutes. No agenda. No attachments.
He looked at the invite.
It wasn't scheduled by the Manager. It was HR. Directly. Sidestepping the Manager entirely. CC'ing no one.
He knew.
It wasn't a matter of deducing "what might happen." It was knowing "it's here." That kind of knowing wasn't a logical inference. It was a silent certainty. Like standing on a train platform—when you feel the tracks begin to vibrate, you don't even need to look to know.
He selected a clean shirt. An ironed one.
Meeting Room B. Third floor. End of the corridor.
As he walked in, he noted: he had never been in this room before. Four years. He had sat in nearly every conference room in this company—the one for the "trapped conversations," the one for the PIP, the one for year-end reviews. But never this one.
The door was open. Two people were already inside.
One was the HR rep. Not Jenny. Not the one from the PIP. A third one. A face Lin Zhaoming didn't recognize.
The other was the Manager.
The Manager was sitting there. Seeing Lin Zhaoming, he gave a brief nod. His expression was exactly the same as always. Flat. Completely normal.
"Sit."
Lin Zhaoming sat down.
HR began to speak. The voice was level. The pacing perfectly controlled—neither too fast nor too slow, the spacing between each word measured. Like someone reciting lines they had uttered countless times.
"Zhaoming, following a comprehensive evaluation of your performance and developmental trajectory, the company has determined that your current work performance fails to meet the requirements of your position."
He paused for a beat.
"Based on the results of the recent Performance Improvement Plan, combined with feedback from your direct manager and relevant departments, our conclusion is—your capabilities are no longer effectively aligned with the company's current strategic direction."
Lin Zhaoming sat there.
He heard every single word.
Performance evaluation. Developmental trajectory. Fails to meet. Performance Improvement Plan. Capabilities. No longer effectively aligned.
Every single word triangulated exactly the same target: you are the problem.
Those months of the PIP. The hollowed-out responsibilities. The reassigned projects. Being asked "what's currently on your plate." Being interrogated in a room for seven hours. Being told not to attend the QCC but never in black and white. The hellish labyrinth of outdated documents the system couldn't even read, possessing dozens of versions and hundreds of conflicting terminologies for the same thing.
All of it, in this precise second, distilled into one phrase: Unfit for the role.
His four years. His analyses. His reports. His tracking of the null pointer. His halt call on Christmas Eve. His supplier interfacing. His system map.
Unfit for the role.
HR pushed a document across the table.
"The company will provide a severance package of N+1 months. All unused annual leave will be prorated and compensated according to statutory requirements."
Lin Zhaoming picked up the document. He didn't read the content. He looked at the formatting.
Several pages. Legal clauses. Non-disclosure agreements. Calculation formulas. "Mutual agreement."
The final page. The signature line. Above one line, the company representative's signature was already inked. The other line was blank. Waiting for him.
He knew exactly how every line of text on this document was forged.
The PIP documentation. The appraisal records. The meeting notes the Manager allegedly wrote after their "trapped conversations"—notes he had never seen, but knew existed. HR's "investigation report." The "conclusion" following his grievance. Every piece of paper, meticulously stacked over months, or perhaps an entire year.
All pointing to this exact moment. To this very piece of paper. To this blank line.
He picked up the pen. Signed it.
"Thank you."
He stood up.
The Manager hadn't spoken a single word from start to finish.
Lin Zhaoming walked to the door. He didn't look back.
He walked back to his desk.
Sat down. Out of habit, he nudged his mouse.
The screen woke up.
The login screen.
He typed his password.
Invalid credentials.
He typed it again. Slowly. Keystroke by keystroke.
Invalid credentials.
He stared at the screen.
While he was still sitting inside with HR—perhaps the very second HR began speaking, or maybe even earlier—his password had already been changed. Laptop, email, internal systems, VPN, everything.
Synchronized.
While he was still inside listening to his "performance evaluation," everything in the outside world had already been severed. No warning. No notification.
He looked at that login screen. A blue background. The company logo. An input field. A single line: "Invalid credentials."
Four years. He had looked at this screen every single day. Typed his password every day. Logged in every day. Today—"Invalid credentials." You are no longer one of us.
He didn't try a third time.
He stood up. Opened his drawer. A few pens. A notebook. A pack of tissues.
He put the pens and the notebook into his bag. The tissues into his bag.
He unclipped his ID badge. Placed it on the desk.
Took his bag. Walked to the elevator bank.
Arriving at G.
He walked to the room HR had designated—a conference room rarely used on normal days, temporarily converted into an equipment return station.
There was a line at the door.
Five people. Or six. He wasn't sure. He didn't count. But he wasn't the only one.
Everyone holding roughly the same items. A bag. A company laptop. An employee badge. Some held cardboard boxes—stuffed with photo frames, mugs, potted plants. He had none of those. His bag was very lightweight.
No one spoke.
He stood at the back of the line.
He didn't know the person in front of him. Probably from another floor. Or a different department. They might have overlapped in this company for years, but had never exchanged a single word.
The line moved slowly. The personnel inside—a guy from the IT department—processed them one by one. Taking the laptop. Taking the badge. Checking serial numbers. Filling out forms.
Whenever someone reached him, it was always the same sentence: "Just hand over the laptop and employee badge."
Someone asked: "I still have some things in my email I haven't saved—"
"All access has already been terminated. IT will handle it."
"But I have some personal files—"
"You can contact HR to follow up. I'm only responsible for collecting the hardware here."
That person stood there for a moment. Then handed the laptop over.
Next.
Lin Zhaoming watched the backs of the people in front of him.
He didn't know their individual stories. Maybe somebody here had a ten-year tenure. Maybe someone else had only been around for a few months. Maybe someone was PIP'd. Maybe someone had just come to work today, got called into a room, and was done in fifteen minutes. Maybe somebody cried in that room. Maybe someone reacted exactly as he did—with nothing to say, signing the paper and walking out.
He didn't know.
What he did know was this: they were all standing in the exact same line. Handing over the exact same badge. Hearing the exact same "There's nothing I can do to help you."
The person directly in front of him handed over their equipment and left.
It was his turn.
The IT guy looked at him. Looked exhausted. He had probably processed dozens of people today alone.
"Laptop and employee badge."
Lin Zhaoming pulled the laptop out of his bag. Placed it on the desk. Placed the badge next to it.
The guy scanned a barcode. Typed a few keys.
"Sign here."
Lin Zhaoming signed.
The IT guy glanced at him. For just a fraction of a second.
Then he lowered his head unconditionally. "Next."
Lin Zhaoming walked out.
The corridor was dead silent. His bag felt lighter. Stripped of the laptop. Stripped of the badge.
He walked to the main entrance.
It was only when he reached the turnstile that he remembered—he had already surrendered his badge. He couldn't operate the turnstile.
He stood there for a moment.
A security guard nearby watched him.
"Leaving?"
"Yes."
The guard pressed a button. The turnstile clicked open.
Lin Zhaoming walked out.
It was incredibly bright outside. May. The sky over Jade Mirror City was a piercing blue.
He stood by the entrance. His bag contained only a few pens, a single notebook, and a pack of tissues.
Four years.
He went to catch his ride.
On the bus.
The scenery outside the window rolled backwards. Office towers. The technology park complex signage. Convenience stores along the roadside.
He pulled out his phone. Opened LINE. His wife's chat window. The last message was the one he had sent before leaving the house that morning: "What's for dinner tonight?"
He started typing. Typed a few words. Deleted them. Typed again.
"I'm coming home early."
Sent.
Read a few seconds later. No reply.
He put down the phone. Looked out the window.
The bus stopped. People got on. A perfectly normal day. None of them knew where he had just come from.
Opening the door.
The house was quiet.
His wife was in the living room. Sitting on the sofa. Her phone resting beside her.
She saw the look on Lin Zhaoming’s face. Her eyes paused.
"What happened?"
Lin Zhaoming took off his shoes. Left his bag by the entrance. Walked in. Sat down.
"The company let me go."
A beat of silence.
"When did this happen?"
"Today. Today was my last day. By the time I went into the meeting, everything was already cut. Laptop, email, access. Everything."
She didn't make a sound.
"There's severance. N+1."
"How many months?"
"Five months' salary."
Silence.
She stood up. Walked into the kitchen.
Lin Zhaoming heard the sound of the refrigerator opening. The click of the kettle being pressed down. The clink of a glass being set on the counter.
She walked out holding a glass of water. Placed it in front of Lin Zhaoming.
"Drink some water."
Lin Zhaoming drank. The water was lukewarm.
She sat back down. Was quiet for a very long time.
"Are you okay?"
Lin Zhaoming pondered for a moment.
"I don't know. Maybe I am. Maybe I'm not."
Pause.
"But I feel relieved."
She looked at him.
"All of those things... are over."
What "those things" were, she didn't ask.
The sound of traffic outside. Very distant.
"Let's eat first," she said. "I'll go cook."
She walked into the kitchen.
Lin Zhaoming sat on the sofa.
A painting hung on the opposite wall. Hung there since they moved in. A very generic landscape painting. A blue sky, green mountains, a winding river. He had looked at it for four years. Today was the first time he noticed the river was curved.
The clatter of a spatula in the kitchen. The sizzle of oil hitting the pan.
He would be hearing a lot more of these sounds. Because he would be at home.
Every single day.
Week One.
He woke up. Ate breakfast.
For the first time in four years, he was eating breakfast at home.
Before—awake at six-thirty, out the door by seven. Breakfast was a bun eaten in the car. Or a sandwich from the office canteen. or nothing.
Now, he sat at the dining table. Eating a bowl of congee. His wife sitting across from him. Eating toast.
They finished eating. She washed the dishes. She left for work.
Only him remaining.
He sat in the living room.
No idea what to do.
He opened his laptop—not the company one, his personal machine. Started revising his resume.
Edited two lines. Stopped.
The resume read: Senior Engineer, Lyra Synthesis, 1021–1025. Four years.
Managed cross-functional communication between R&D and supply chain partners.
He stared at that sentence.
The sentence was factually true. He had done it. But the distance between this sentence and what he had actually endured—he couldn't even measure it.
What he had really done: tracked a problem no one was willing to admit existed. Hunted for fragments within a system specifically designed to blur accountability. Drawn a map nobody believed in. Been confined in a room for seven hours. Refused a perfectly laid trap.
None of these things would ever appear on a resume. No resume formatting on earth was capable of holding these realities.
He closed the file.
Week Two.
Contacting headhunters. Going out to meet people. Drinking coffee.
"What was your role previously at Lyra Synthesis?"
"System integration and supply chain engineering."
"How long were you there?"
"Four years."
"Why did you leave?"
"Company downsizing."
The person across the table nodded. Utterly understood. Large corporations frequently did this. No explanation necessary.
No one probed further. No one investigated how the words "unfit for the role" on his official file had been meticulously synthesized. No one knew that behind those words lay months of a PIP, months of being hollowed out, and months of the "trapped conversations."
Because no one needed to know.
"Company downsizing" was a magical skeleton key in this industry. A perfect shield. You speak it, and the other person instantly knows: no more questions. Normal routine. The macro-environment.
Lin Zhaoming sat in the café. The headhunter had already moved on to the next topic—"What type of roles are you looking for", "salary expectations", "any preference for remote."
He answered them. Responded smoothly. Perfectly normal. Completely fluent. Like a normal human carrying out routine procedures.
He met with three headhunters this week.
The first opportunity pitched was with another large manufacturer in the exact same vector. Marginally smaller than Lyra Synthesis, but maintaining the exact same localized structure—R&D sequestered at headquarters, localized execution handling supply chain and RMA.
"They are currently undergoing aggressive transformation, searching for experienced talent."
Lin Zhaoming nodded.
Aggressive transformation.
He had heard those four words. In the Lyra Synthesis town halls. From the Manager's mouth. In the background subtext leading up to Peter's "your colleagues are all here to support you."
The truest translation of 'aggressive transformation'—he only understood it now—was: upper management has already decided on a trajectory, and the job of everyone beneath them is strictly to perform compliance, fabricating the illusion of this new direction. No one questions the direction. No one executes the functional prerequisites. The transformation itself is nothing but theater.
Accepting a role at this company meant migrating from one masquerade system directly into another. Just another iteration of the identical Manager. The identical HR. The identical "Catch-up, 30 min" creeping onto his calendar.
"I'll think about it."
The second opportunity pitched was a smaller, localized firm. A supplier. Basically operating in Ah Keung's specific orbital level.
"They have a senior opening. Your background is a solid match."
Lin Zhaoming asked a few questions. Product lines, client base, team size.
The headhunter across the table was brutally transparent. "I'll be honest, the client imposes exceedingly stringent conditions. It's not like the massive conglomerates you're used to. Resources are tight. But the core advantage is authenticity—when you do the work, you are actually just solving the problem."
Lin Zhaoming knew exactly what "doing the work is actually answering the problem" meant.
It meant fewer cycles wasted on office politics. Fewer meetings. Zero "trapped conversations". No PIPs.
But simultaneously—
Zero flexibility. Zero bargaining power. Whatever the upstream brands demand must be executed flawlessly. "Deliver this prototype in one week"—refuse? The contract is terminated. Weekend crunch? Standard protocol. Consecutive all-nighters? Expected. Instructed to run an explicitly pointless validation test? You run the test.
He had witnessed Ah Keung's reality firsthand. Fifteen years of senior-level seniority, reduced to re-running an entire massive test suite over a 0.3-degree temperature drift. Ordered to meticulously verify air conditioning maintenance logs. Summoned into two-hour cross-examinations to defend a report no one would ever actually read.
Ah Keung lacked the capability to refuse. Because refusal = lost contract = zero payroll.
During his four years at Lyra Synthesis, Lin Zhaoming possessed one singular, microscopic luxury: the capability to refuse. The penalty for his refusal was utterly devastating—but the option functionally existed. He had rejected the initiation protocol. He had declined the final impossible task. The resulting penalty was being gutted, corralled, and formally documented as incapable. But his refusal had been structurally valid.
If he descended to the supplier tier, even this right to refuse vanished entirely.
The third opportunity pitched was overseas.
"There's an opening in Amerion right now. Remote is a possibility, but there's a highly elevated probability you'll need to relocate."
Lin Zhaoming listened.
Amerion. His former employer—the one from Flashback D—was located there. An honest termination. "Sorry, this isn't fair." He knew the texture of the work environment there was completely different.
But what did relocation actually mandate?
His wife had her own career here. They purchased this house several years ago. His mother remained on Transit Island, requiring his proximity. If he relocated—if he went solo—it meant another prolonged separation. He had already experienced the taste of that during those months in 1023 caring for his mother on Transit Island. He knew the sheer gravity of that toll.
If they relocated together—it required uprooting their entire existence. Selling the property. His wife's career reverting back to zero. Rebuilding networks, navigating languages, establishing lives, insurance, healthcare, and tax codes from absolute scratch in a foreign nation. And at their current demographic, they were no longer operating in an age bracket where "let's just restart everything" was a frictionless endeavor. Baggage had aggregated. Risk tolerance had severely depreciated. Simultaneously—the macro-environment of Amerion itself was highly unstable. Mass layoffs sweeping across sectors. Deepening societal polarization. They couldn't even sustain their own domestic workforce. A foreign national in his forties, non-native English speaker, carrying a recent termination flagged as "unfit for role"—in that hyper-competitive market, whose priority candidate would he be?
His mother—
He stopped his thoughts there.
The headhunter on this side was still relentlessly pitching. "The Amerion market is running a bit cold right now—as you know, the AI-driven layoff cycle, overall spec down—but the opportunities are fundamentally solid."
The AI-driven layoff cycle.
He had been reviewing the news updates over the past months. Amerion's massive tech conglomerates, financial sectors, media entities, retail—firing in continuous waves. The stated justification universally parroted: "allocating capital to AI", "optimizing operational efficiency", "restructuring toward core priorities". But the underlying truth—the vast majority of these corporations weren't functionally integrating AI logic. They merely weaponized AI as a credible excuse to shed headcount. The massive chasm between AI's realistic deployment capabilities and specific enterprise workflows was carefully avoided. But simply articulating the acronym "AI" catalyzed stock surges. So they echoed it. And synchronously terminated personnel. And then echoed "AI" again.
Stock indices trending uniformly green. Unemployment indices scaling upward. An economy simultaneously projecting aggressive growth while fundamentally eroding at the structural level. The synchronized divergence wasn't rationally discussed.
He used to compartmentalize this exact mechanism, assuming it was an isolated anomaly confined within Lyra Synthesis. The Lyra town halls. Peter's "colleagues are supporting you." Victor's algorithmic scorecard. AI decision matrices. Operational excellence.
Now he comprehensively understood—Lyra Synthesis was simply a hyper-localized implementation node of this global architecture. The entire industry, a full hemisphere of the globe, was executing the identical operating system. Dictating one narrative, documenting a second narrative, and executing a profoundly conflicting third.
The employment landscape in Amerion might lack the explicit "trapped conversations." But it would export an equivalent pathology. An alternate regional iteration of Victor. Another flavor of the Manager. The identical underlying algorithmic logic driving a PIP.
He replied to the headhunter: "I need to process this. I'll consider it."
Walked out of the coffee shop.
Blinding sunlight.
He stood by the curb.
Three bifurcating paths.
Remain anchored in the domestic conglomerates—a parallel instance of the exact same system. Descend into the localized supplier ecosystem—absolute physical exhaustion, stripped of even the fundamental agency to refuse. Relocate to Amerion—uproot entirely, solely to play a foreign translation of the identical game.
None of these paths were viable.
But the more structurally terrifying realization wasn't that the available options were wrong. It was—he started suspecting that the "correct" work environment he was searching for might categorically no longer exist.
It wasn't a temporarily absent condition. It had already evaporated. He was completely blind to this earlier because he remained trapped within Lyra Synthesis’s isolated architecture, operating under the delusion that "once I escape, a functional reality awaits."
Now he was outside. He surveyed the world. His suspicions solidified.
A sudden, overwhelming exhaustion.
Not somatic fatigue. A specific sensation—like hiking for miles, finally reaching the horizon, only to realize the path you walked was inherently devoid of a destination. Continuing forward would never deliver you to a location labeled "normal." Because "normal"—as a coordinate—likely evaporated. Or perhaps it was purely a theoretical construct. Or it merely survived in memory—confined to specific temporal windows, legacy corporations, and individuals who had already vanished from the workforce.
June. July.
The savings burn rate initiated.
Monthly expenditures. The mortgage. Groceries. Insurance premiums. Sundry expenses. The capital requirements for Transit Island—his mother's care. These figures were rigidly fixed constants. They didn't incrementally downscale just because a termination event occurred.
The N+1. Five months' compensation. Spread it across the matrix—the mortgage vaporized a defined segment, insurance devoured another segment, Transit Island required its mandatory extraction. The gross remainder secured a tightly defined window of consecutive months. There was no absolute safety net.
His wife didn't explicitly verbalize it. But he knew she was tracking the burn rate.
He knew this because—during dinner, she would glance at a specific dish for a fraction of a second longer. A behavior utterly absent historically. Now present. Functionally calculating the cost-per-meal in real-time.
He kept silent. She mirrored the silence.
But one core truth resonated quietly in his own processing center.
He still possessed the runway to burn.
This wasn't a trivial detail. This was the defining variable.
If his savings account read zero—if last month’s payroll was his absolute baseline—he would have unequivocally accepted any incoming offer. He’d already be sitting in a cubicle at that first headhunter’s "aggressively transforming" conglomerate. Or grinding in the supplier trenches, regardless of the physical toll. Or deployed overseas, regardless of the geopolitical distance. Individuals stripped of optionality inherently lose the right to say "I'll think about it." Individuals lacking alternatives absorb "job opportunity" as an absolute command.
His capacity to say "I'll consider it"—those exact words were directly subsidized by his accumulated capital.
And those exact words—"I'll consider it"—constituted the final firewall protecting his psychological integrity.
He had stress-tested the sensation of having zero alternatives during his final months at Lyra Synthesis. The trapped conversations. The PIP. The terminal refusal. Every single refusal was structurally coupled to a catastrophic cost—loss of income, loss of career velocity, loss of futurity. His refusals were theoretically possible solely because he retained fragments of leverage, coupled with a marginal buffer. If that buffer was zero—those refusals never manifest. He would sign. He would comply. He would transmute from a target into a perfectly aligned accomplice.
He had observed what happens to entities lacking this buffer. Cindy. Ah K. Old Xu. They weren't inherently malicious nodes. They merely lacked operational runway. Individuals lacking runway inside a masquerade system eventually face standard binary logic: assimilate into the architecture, or face organizational death.
Currently—he still retained a buffer. But the buffer was fundamentally finite. The numerical variables degraded monthly.
But within this defined buffer, a completely distinct variable began floating to the surface.
While inside Lyra Synthesis, his vision of the holistic operation was obstructed. He only ever accessed localized fragments. The "trapped conversation" was a fragment. The PIP was a fragment. The final refusal was a fragment. Each was highly tactile, but while enmeshed in the framework, the cognitive processing power to map the macro-structure didn't exist—because systemic mapping requires altitude and distance.
Now he possessed altitude. He possessed distance. He began mapping.
The data points he synthesized stripped away his capacity to sleep.
The individual who left in November 1024. He recalled this node. Then he realized—that likely wasn't an isolated anomaly. There were others. In separate divisions. On distinct floors. Across varying fiscal quarters. He hadn't explicitly audited the database. But he understood the probability.
The individuals who died were systematically scrubbed from memory. Zero internal statements. Zero memorials. Zero institutional learning protocols initiated. Team-building exercises launched on schedule. The mantra "stress management is an individual deficiency" was reiterated without variance. Town halls executed seamlessly. AI-driven decision-making, operational excellence, leaner-faster-smarter—the corporate lexicon remained untarnished.
And then there were the individuals hovering at the edge but retaining vital signs. The numerical volume of this demographic—he intrinsically knew it exponentially dwarfed the mortality cases. Every iteration of Cindy, every iteration of Ah K, every entity completely hollowed out within an interrogation room spanning six hours. They generated no news cycles. No investigative reports. No one tracked their recovery metrics. They merely kept clocking in. Continued metabolizing antidepressants. Continued retreating into the isolated acoustic corners of KTV booths, whispering "I’m going to drag my child off a roof" into a void only they could hear.
Nobody processed this data.
Now—one particular node had successfully breached the perimeter. Possessing time. Possessing a buffer. Possessing distance. Possessing the theoretical capability to visualize the entire structural pathology.
That node was him.
One night, sitting in the living room, he inputted a query:
Am I obligated to execute an action?
Not "what am I capable of doing." The parameter was "am I obligated."
The query wasn't rooted in a hero complex. It wasn't about "saving victims." He lacked the capacity to save anyone. That was a known limit. The deceased were unrecoverable. Those still trapped inside the firewall were unreachable by his text.
The structural shape of this query was far more clinical.
If he accepted a transient bridging job tomorrow—all of this localized knowledge would be permanently archived solely within his neural pathways. A single isolated brain. The data he possessed would incrementally degrade, overwritten daily by novel workflows, a novel manager, novel meetings. Three years. Five years. Ten years. By his retirement sequence, his recall would compress into a generalized "I once worked at a toxic corporation." The precise architectural schematics—the UIP timing defect. The null pointer obfuscation. Christmas Eve. The dimensions of the trapped conversation room. The seven-hour PIP deployment—would steadily lose resolution.
The data would literally go to the grave with his hardware.
No one would map the structural configuration of this system. The next iteration of employee entering a parallel system—would lack a map. The next node processing the logic loop of "why is my maximum output insufficient"—would lack a reference manual. The next individual staggering out of a six-hour containment room, unable to process what just occurred—would lack the exact terminology.
This wasn't a question of his literary capability to properly articulate it. It was—beyond him, the statistical probability that anyone stationed at this precise socio-economic coordinate was capable of writing this data was functionally zero. The other nodes possessing this data—the vast majority were still trapped inside, muted. Or they successfully breached but chose obfuscation (due to retaliation matrices, trauma degradation, or successful migration to novel life phases). Or their life signs had already terminated.
He wasn't claiming his version was the absolute ground truth. He was claiming—his version, if not documented by him, would effectively cease to be a reality vector.
This wasn't equivalent to "I will successfully save someone." Rescue probability was negligible. The data might generate zero impressions. Or readers might process it with an "oh, that's tragic" empathic spike and instantly revert to standard operating procedures.
However—
If he failed to document it, the theoretical probability of that outcome wouldn't even spawn.
This yielded the terminal conclusion.
Not "I will be an effective asset." It was "If I fail to execute, even the potential geometric space of 'might be effective' is nullified."
And sustaining that geometric space, within this specific window where he was free, buffered, and retained high-resolution data retention, was the singular task he possessed the clearance to execute.
If this temporal window collapsed—perhaps no one ever would.
But this specific conclusion—"geometric space", "theoretical probability"—remained excessively abstractionist for Lin Zhaoming. He needed to translate this calculation into a far more tactile metric to endure the isolation of the upcoming months.
This translation—distilled into two distinct syllables.
Homicide.
This operating system executed homicides. Not as a rhetorical metaphor. A literal, biological termination.
During his four years, Lin Zhaoming had verified at least two data points. One was the November 1024 event. The other preceded it, located in an external division—he never interacted with the node directly, merely re-assembling the vector from debris in a message thread. Identical hardware context. Identical pressure gradients. The identical fiscal quarter. And then that specific message thread was rapidly flushed from the cache.
Two points. Directly validated by him.
As for the total aggregated volume—he lacked the clearance. No internal audits tracked this specific metric. Massive corporate entities in Amerion occasionally subsidized academic research on employee suicide velocity; here—the metric was functionally zero. Or if it registered, the data was immediately recompiled as "personal resilience deficiency," "domestic variables," or "legacy psychiatric history."
The defining characteristic of this operating system—it executed terminations without depositing forensic evidence. Every single fatality was assigned a perfectly logical, externalized root cause. Every perfectly logical root cause explicitly decoupled the system from the event. Therefore—from an external viewer's perspective, this system maintained a fatality record of exactly zero.
This was the precise definition of "stealth homogenization."
Once Lin Zhaoming processed this, he was confronted with the secondary procedural issue:
What is the operational format?
Because—he could render this entire text intensely bleak. He could maximize the narrative weight of the trapped conversations. He could meticulously reconstruct the forensic timelines of the two deceased nodes. He could format the entire manual as an "anthology of trauma."
Lin Zhaoming refused this methodology.
The primary constraint: he was required to interface with this content daily. If he explicitly unpacked the maximal degree of systemic darkness—his own processing capacity would shatter. His psychological baseline would break. He was already aggressively filtering massive data streams. The trapped conversations—the factual frequency was significantly higher than the text reflected. The PIP sequences—the factual texture was infinitely more sadistic than written. The mortality events—the sheer kinetic shock transferred was magnitudes beyond the documented paragraphs. He throttled everything. His fundamental requirement was to successfully finalize the build. His requirement was to exit the build process as an entity still capable of entering a standard sleep state.
The secondary constraint—which superseded the first.
He explicitly refused to degrade this manual into a "commoditized memoir of victimization." Refused deploying the deceased nodes as emotional clickbait. If the reader’s terminal feedback loop resulted in "this is so tragic" followed by tear extraction—the manual was an operational failure.
Because "this is so tragic" was a generalized emotional response from a bystander. Lin Zhaoming didn't require external pity extraction. Pit was a fundamentally useless metric.
What he required was—upon completing the text, the reader successfully processes the structural shape of the operating system. The next time they cross its perimeter, their immediate cognitive reflex triggers: "This pattern matches the documented architecture."
This pattern matching—was exponentially harder to code than tear extraction. Tears are biological responses. Pattern matching is a cognitive upgrade. To successfully script a module where a user achieves flawless pattern recognition—it necessitated reverse-engineering the machine's core logic with absolute clarity, rather than merely projecting the most catastrophic scenes onto the display.
And the target demographic for this manual—
Was not the nodes still trapped inside the firewall. Text couldn't penetrate their localized reality. They were already executing infinite loops of self-doubt. Reading this would merely sustain the self-doubt loop.
Was not the nodes who had successfully extracted. Extracted nodes didn't require the manual. They possessed primary data.
Was not the hostile actors. Hostile actors, even if heavily exposed to the text, actively fail to self-classify as hostile. Their internal logic defaults to: "This manual isn't referencing my specific methodology. My environmental variables are unique."
The target demographic for this manual, was—entities who had not yet crossed the perimeter of this specific structural class. Entities entirely oblivious to the existence of this specific global architecture. Entities who, if presented with the statement "certain corporate structures systematically erase your personality algorithm," would classify your statement as statistically improbable hyperbole.
These specific entities—will eventually collide with the perimeter. On the day of collision, lacking a functional map, they will automatically classify the firewall as an internal deficiency. They will deploy behavioral patches like "upgrading my communication protocols." They will be entirely hollowed out midway through the sequence. On the day of extraction—assuming extraction is successful—they will no longer possess the foundational code of their original self.
This manual was not deployed to rescue the trapped nodes. It was deployed to brief the uncollided nodes: this architecture exists. You are not executing a faulty algorithm. Your systemic disorientation is a valid sensor reading. Map the geometry as rapidly as possible. Execute immediate extraction protocols.
Lin Zhaoming required further processing on one specific anomaly. A concept fully iterated upon in the epilogue, but he was currently compiling the initial wireframe.
Why does a standard, functional human execute systematically dehumanizing routines?
Lin Zhaoming’s resolution heightened aggressively throughout this specific year: their universally deployed patch was—"I lack alternative options."
The hardware vendors categorize the ODM as sub-human—justified via "The upstream brand applies identical pressure gradients onto my supply chain." The ODMs categorize the localized suppliers as sub-human—justified via "The brand compresses my margins, I must distribute the compression downwards." The localized manufacturers categorize their factory nodes as sub-human—justified via "The ODM parameters are unyielding, I lack flexibility." Individual corporate nodes categorized Lin Zhaoming as sub-human—justified via "My biological dependents require sustenance" or "My career velocity cannot survive localized disruption."
Every single node operated with flawless internal logic. Every single node effectively lacked the "alternative selection" operator.
But the sum of every individual node—aggregated into a massive machine where no one algorithm was assigned the "villain" designation. A machine perfectly optimized for homicide.
The primary combustion fuel powering this machine was the three-word sequence: "lack alternative options."
Lin Zhaoming fully understood the vector drawing humans into this logic loop. He himself had deployed that exact patch. He didn't categorize these entities as exceptionally malicious. He categorized them as—the vast statistical majority—having never observed an alternative operating system. They universally assumed "this represents the baseline mechanics of enterprise." They assumed "global architecture operates identically."
It doesn't.
Lin Zhaoming accessed the data caches of his previous corporate deployments.
Those systems weren't flawless. Every system possesses internal bugs. However—one specific execution was structurally impossible for them. They lacked the capability to execute the compounded chain of psychological manipulation + localized accountability buffering + complicit cultural immersion.
Why?
Because their product outputs carried absolute, non-negotiable thresholds.
Automotive systems. Medical hardware. Product outputs from these sectors, if shipped utilizing falsified parameters—fatal velocity follows. Litigation inevitably occurs. Regulatory algorithms audit the process. If the schematic mandates a specific capacitor brand, you install that specific capacitor brand. If compliance requires passing a specific threshold, you pass the threshold. Zero tolerance for "acceptable deviations." Zero "let's bypass the check just this once."
If the client specifications fail validation—your node is instantly severed from the supply chain registry. Zero bargaining parameters. Zero PR spins. Zero accusations of your team "lacking communication skills."
The localized suppliers in these sectors—operated under massive stress. Validated. Hostile verbal interactions, irrational demands, byzantine procedural flow—all prevalent metrics. However, these negative inputs ultimately funneled toward a singular, unified objective: the functional viability of the hardware must be safeguarded. Because catastrophic hardware failure equals biological death.
These specific sectors weren't governed by heightened moral superiority algorithms. It was simply that—they lacked the geometric space to execute falsified data. Therefore, they lacked the geometric space to cultivate a complicit culture. Therefore, they lacked the geometric space to spawn a masquerade system.
Conversely, consumer electronics—expressly within the architecture of "Next-Generation Core platforms"—possessed massive operational slack. A catastrophic product flaw didn't spawn instant biological mortality. It spawned localized user complaints, scheduled maintenance firmware patches, and promises that "next-gen hardware will resolve the issue." Zero immediate incarcerations. Zero immediate regulatory audits.
This massive operational slack provided the exact nutrient layer for a masquerade system to achieve self-sustained growth.
But Lin Zhaoming required further processing on an additional sub-routine: why would the localized acoustic output of a single node out-rank the synchronized narrative of a collective cluster?
They deployed ten nodes broadcasting an identical data set. He possessed a node count of one. Any rational third-party processor—HR modules, external auditors, headhunters, future readers—would probabilistically default to validating the "ten-node consensus." This is the foundational power dynamic of group gaslighting. The narrative generated by the statistical majority automatically overwrites reality in the cache. Any entity failing to physically interface with this specific localized mechanism critically lacks the processing bandwidth to decompile a collaborative, multi-node falsehood. Lin Zhaoming factored this. He completely failed to understand it himself prior to the collision event.
However, Lin Zhaoming was aware of a singular asset they lacked the authorization to overwrite.
The specific product output.
The terminal behavior and localized performance metrics of the hardware—represented the only variables mathematically immune to semantic translation. The yield percentages were rigid integers. The capability of the device to execute a boot sequence was binary. Client return rates were auditable logs.
This specific asset retained structural integrity during prolonged timelines.
But—in abbreviated timelines, they possessed a workaround architecture specifically engineered to buffer precisely this fault.
Through four years of telemetry, Lin Zhaoming observed: every time the hardware encountered a catastrophic failure, they didn't deploy root cause analysis pipelines. They deployed a "load-balancing" protocol.
Initial failure—Vendor A absorbs the load. Secondary failure—Vendor B absorbs the load. Tertiary failure—A specific, targeted engineer absorbs the load, flagged as "individual capability limitation." Quaternary failure—A distinct team is "re-assembled." Quinary failure—An allocated localized manufacturer absorbs the load.
The system wasn't required to permanently encrypt the anomaly. It merely routed every recurrent glitch toward an "expendable load sink." The sink was then terminated. When the anomaly re-manifested, the routing table pointed toward a fresh "sink."
This protocol could be sustained for massive temporal durations—potentially decades. Every sacrificed node was cleanly digested. Every digestion sequence triggered the creation of a structurally broken individual, a bankrupted local supplier, a terminated engineer, or—with predictable frequency—a terminated biological unit.
The entities digested constituted the primary fuel source for this architecture.
Lin Zhaoming allocated massive cognitive and temporal resources configuring tests, tracking telemetry, and decompiling the structural geometry of these failures. However—it was utterly ineffective. Not because his diagnostic methodology was flawed. It was because the volumetric density of nodes actively willing to broadcast false data was overwhelming. It was because the nodes actually possessing the capability to execute tasks had been systematically severed from the network.
The remaining network nodes weren't incapable of locating the glitch. They were—nodes actively refusing to locate it, plus nodes lacking the capability to locate it, plus nodes capable but computationally terrified of locating it.
Once this specific ratio threshold was breached—the entire operational logic of the system irrevocably decoupled from "factual reality."
But this specific architecture relied on one fundamental prerequisite: the product itself inherently lacked a future vector.
Lin Zhaoming only decompiled this specific line of code during the terminal phases.
If a product possesses a viable future vector—you are mandated to resolve the glitch. Because the subsequent generation is fundamentally built upon the current chassis. Unresolved bugs propagate. Supply chain inefficiencies severely impact next-gen unit costs. If a product has a future, your optimization goal is resolution, not encryption.
But if a product lacks a future vector—your optimization goal actively shifts. Your objective isn't enhancing product capability. Your objective is: sustain operational viability until the subsequent quarter. Safely navigate the upcoming audit. Buffer the timeline until a specific upper-management node executes retirement. Buffer until an acquisition event triggers. Buffer until your own node successfully extracts to a novel system.
When the optimization goal is reconfigured to "buffer"—all system resources divert from "execution" to "encryption." Every proposed enhancement is automatically flagged as "system disruption"—because an enhancement necessitates acknowledging a pre-existing flaw, and acknowledging flaws directly threatens the "buffer" mandate.
Every proposal Lin Zhaoming logged during his four-year tenure—modularization protocols, digitization matrices, root cause analysis deep-dives—was fundamentally predicated on the assumption: "This enterprise intends to optimize this specific product."
That foundational assumption was critically corrupted from Day 1.
This product pipeline was nullified. The entire horizontal structure had transitioned into a sunset status. The aggregate cognitive bandwidth of every node had already shifted from "execution" toward "buffering." Lin Zhaoming's proposals actively destabilized the "buffer" protocol. Therefore, every single one of his submissions was rejected, "entered consideration," or flagged as "requiring excessive structural upheaval during a sensitive transitional period."
His proposals weren't deficient. His proposals were merely functioning on an invalid core assumption.
This specific sunset cycle could theoretically sustain itself for decades. Possibly twenty years.
Throughout that multi-decade span, product units continue to ship. Target clients are maintained. Payroll is executed. Entities continue harvesting capital from the decaying line. They categorically refuse to acknowledge "the sequence is terminated"—because acknowledgment immediately triggers the termination of their localized node.
During this temporal epoch, every single action is calibrated toward a unified objective: avoid external detection regarding system decay.
During this epoch, the mechanism continuously requires fresh "fuel"—vendors, engineers, manufacturers, internal staff—depleted in sequence, requiring immediate replenishment. During this epoch, nodes will terminate. Terminated nodes will have their operational existence purged from the logs. Their terminations will be translated as "personal incompatibilities." The technical anomalies they localized will be scrubbed as "non-existent artifacts." Even the raw data that they had previously functioned inside this facility at all—will rapidly decay from the system's memory cache.
This specific cycle maintained a baseline duration of at least five to eight years. Probable overruns expected.
Within that duration, the subsequent iteration of Lin Zhaoming is already logging into a separate workstation. The subsequent Ah Keung is already compiling a document that will register zero reads. The subsequent node being processed in the containment room doesn't yet possess the vocabulary to identify "trapped conversation" protocols.
The explicit function of this manual, is: force-feed the reader the capability to recognize the "sunset pipeline" telemetry signatures.
Not train them to parse quarterly earnings reports. Not train them to triangulate macroeconomic industry trends. Train them to identify localized operational signals—
When all yield deficits are re-routed to the vendor block. When all technical collapses vanish inside parameters of "inter-departmental alignment." When nodes flagging anomalies are uniformly reclassified as possessing "deficient communication skills." When senior operational nodes sequentially extract without an articulated rationale. When the town hall payload shifts dynamically from "current execution metrics" to "long-term visionary frameworks." When "transformation" becomes the core directive, while physical execution objectives become increasingly nebulous. When you begin cross-examining your own internal logic engine.
These—are the definitive telemetry signatures of a dying pipeline.
If you trigger a collision with this geometry—the stipulations of your contract, bonus structures, hierarchical designation, and projected promotion path—are completely irrelevant data points.
Extract.
Not a demonstrative extraction. Not seeking the temporary dopamine hit of a dramatic resignation. Execute a silent, verified, maximal-velocity extraction protocol.
Because a pipeline's death sequence is excruciatingly prolonged. Within this prolonged interval, mortality occurs. Psychological algorithms shatter. Source code identity is scrubbed. Entities are hollowed entirely. Baseline operational competency is systematically cast into doubt.
From the perspective of an external node—none of these events register on the telemetry screen.
Lin Zhaoming processed that not every single product pipeline operated in this manner.
This constituted Lin Zhaoming's remaining sliver of hope. His previous deployments—several lines maintained functional health. Actual R&D executed. Genuine enhancement protocols logged. Certain nodes genuinely processed joy through functional execution.
These realities existed. Lin Zhaoming accessed this data firsthand.
The structural flaw wasn't "the global architecture is entirely comprised of masquerade systems." The reality was—sunset pipelines, reactive patch-management matrices, and cultures executing stealth homogenized terminations—represented an expanding quadrant of the global architecture. A rapidly scaling quadrant. But not the entirety of the map.
The reader's objective isn't to disengage from all corporate entities. It is—to master the triage function.
This triage capability was the asset Lin Zhaoming subsidized with a four-year capital burn. He spent four years physically validating every single structural barrier. Post-collision, he mapped the parameters: the geometric configuration of those walls.
The sole action he retained the authorization to execute—was rendering the schematic of those walls into an exportable format.
The next individual node entering a parallel geometry could potentially authenticate the geometry a year ahead of schedule. An advanced twelve-month lead meant executing an extraction twelve months faster. An accelerated extraction meant avoiding the trapped conversation protocols, the PIPs, and the terminal denial event entirely. Or—potentially avoiding the specific data coordinate belonging to the two nodes who failed to ever return.
Lin Zhaoming processed a secondary calculation—
What if the automotive and medical sectors eventually corrupted into an identical architectural format?
He lacked sufficient data. He hadn't logged the required operational hours inside those specific structures. However, he correctly modeled the macroscopic trajectory. The universal narrative pushing AI optimization had already penetrated every sector. The identical management nodes, optimizing vendor suppression, were currently migrating from consumer electronics into adjacent industries. The exact identical methodology was actively being copy-pasted across networks.
If automotive architectures mirrored consumer electronics—units would physically terminate external biological nodes.
If medical architectures mirrored consumer electronics—patient mortality rates would experience geometric scaling.
All of these mortality events—would generate localized, logical justifications. They would remain categorically "decoupled from the operational core." They would register as "isolated occurrences." Flagged as "familial emotional responses are statistically predicted."
This was the variable Lin Zhaoming feared most.
This manual lacked the physical capability to halt this trajectory. Lin Zhaoming processed this limitation. A text file's kinetic impact is negligible.
However—the functional capability of a manual was: recording the physical dimensions of the architecture. Assigning a definitive nomenclature to its operating logic. Providing a referenced dictionary, so when external nodes require this specific vocabulary—the asset exists.
If this asset failed to compile—the next instance of a node colliding with this architecture possessed only one available explanation: "My internal algorithm is flawed."
That specific explanation—had already terminated an unacceptable volume of nodes.
One day.
"Have you considered... securing a bridging role in the interim?"
They were in the living room. Post-dinner sequence. The monitor was operational but receiving zero visual attention.
"Affirmative. Interfaced with several leads. Currently holding pattern."
A brief silence.
"What if... you just secure an interim role? Doesn't need optimal alignment, just guarantees payroll processing."
He modeled the subtext behind her prompt. He knew she was simply executing a fear response. Fear of the capital runway collapsing. Fear their baseline reality would undergo a hard reset. Fear derived from observing him sitting continuously at a home terminal, executing loops lacking visible output.
"Acknowledged. I'll initiate a search."
She nodded. Ended transmission.
But both nodes internally mapped one undeniable fact—what Lin Zhaoming was currently executing was not a job search protocol.
Commencing in June, he stress-tested multiple output formats.
Short-form video arrays. Scripting. Recording. Splicing. Each packet measuring thirty seconds to a maximum of one hundred and twenty seconds. Tested multiple iterations. Each iteration rooted in a specific micro-event—the Christmas Eve halt line, Ah Keung's "are you malfunctioning", the geometry of the trapped room—compressing the dataset into a strict two-minute envelope.
Every iteration, post-render—he reviewed. Every iteration registered as—accurate. Yet simultaneously invalid.
The accuracy: every specific localized data point was verified truth.
The invalidity: the two-minute compression algorithm effectively transmogrified the dataset into "a tragic anecdote." The viewer processes the file, initiates the "oh, that's horrific" subroutine, and the recommendation engine instantly serves the subsequent file. The next file might be a secondary tragic anecdote, a culinary optimization clip, or a comedic sequence. Tragic anecdotes within this specific protocol are functionally reclassified as entertainment modules.
This was incompatible with Lin Zhaoming's operational objective. His payload was not tragedy. His payload was—an architectural schematic. An architecture engineered to invert "normal" into "impossible." Comprehending this structure demands sustained processing loops. Short-form video environments systematically denied those loops.
He tested text-based outputs. Extended formats. 1K to 2K byte configurations. Deployed onto multiple nodes.
Post One. Post Two. Post Three.
Deployed continuously from June approaching year-end. Six months.
Audience engagement metrics—critical minimums.
Not zero. It was—reviewing the analytics dashboard revealed: this packet registered fifty hits. That packet registered eighty. Zero cross-node transfer. Zero sustained engagement loops. Zero secondary momentum.
Concurrently—he verified an anomalous metric.
He periodically drafted analysis packets mapping AI market vectors. Structural telemetry, macro-industry shifts, targeted corporate maneuvers. These specific packets—traffic volume peaked. Secondary broadcast propagation was high. Feedback loops were dense. The recommendation algorithms proactively prioritized distribution.
He initially hypothesized a "branding misalignment" error—assuming his syntax optimized for market analysis far better than sociological deep dives. He eventually mapped the actual bug: the audience demographic. The engine routed him exclusively toward—executives, capital allocators, and nodes explicitly stationed within the AI domain. This subset possessed massive demand for "market analysis." They possessed absolute zero demand for "a four-year psychological autopsy of a domestic tech factory."
Not an empathy deficit. It was that this dataset processed as—pure abstraction. Functionally disconnected from the decision matrices they executed daily.
And the demographic Lin Zhaoming urgently needed to push the update to—did not reside within that sub-cluster.
The nodes Lin Zhaoming needed to intercept, were the entities preparing to initially map this societal structure. Specifically the uninitialized nodes—pre-entry, or recently instanced within the environment. They were mathematically guaranteed to collide with this architecture. On the collision date, lacking a pre-installed map, their local system would flag an internal error. They would execute self-doubt loops. They would attempt "heightened effort," "expanded processing," "optimized communication protocols." They would burn years of operational life only to finally parse the realization—the bug resided externally.
These uninitialized nodes, deep within the algorithm's routing logic, would never receive Lin Zhaoming's data packets. Algorithms refuse routing. Because algorithms operate solely on a "serve similar content" protocol, and uninitialized nodes had not yet initiated a query for this specific data.
Therefore—deploying isolated text nodes was an inadequate programmatic solution.
He successfully mapped a subsequent layer.
This architecture—psychological manipulation protocols, localized accountability offloading, complicit culture normalization—was not localized strictly to Lyra Synthesis. Not localized to Jade Mirror Island. It was—a globally distributed network.
He processed incoming data streams from Amerion. The synchronized, multi-node termination sweeps executed monthly by tech conglomerates. The universal reasoning tag was "allocating to AI," "efficiency streamlining," "core priority alignment." But the bedrock data—the vast majority of operations completely bypassed true AI integration. They merely leveraged "AI" as an operational override code to purge headcount. The stock price metric instantly surged. The CEO node unlocked maximum compensation packages. The loop prepared to execute the subsequent iteration of AI rhetoric.
The operating culture of Amerion—he had previously modeled it inversely. The corporation from Flashback D—"Sorry, this isn't fair."—represented a distinct functional texture. However, that texture was experiencing rapid global deprecation. Because the foundational environment had updated. The gravitational pull of capital markets was uniform. The AI narrative forced total corporate architectural alignment, irrespective of factual execution.
This masquerade protocol—was now uniformly deployed planet-wide.
Lin Zhaoming comprehended the geometry. He had historically modeled his data as an isolated, private telemetry log. He now verified: his private telemetry log was a localized translation of a globally distributed operating system. The next uninitialized node migrating toward a parallel system—wouldn't just collide on Jade Mirror Island. Collision was guaranteed on the mainland. In Amerion. Inside the Old World Inheritor Territory. Geometric collision would occur inside any volumetric space hosting a macro-enterprise.
And this specific architecture, possessed zero viable offensive countermeasures.
This was the core finding his four-year field test delivered. You lack countermeasure capabilities. You escalate grievances—the audit routes back to internal nodes. You deploy email logs to force accountability—it translates into validation you are "excessively prioritizing political maneuvers." You block compliance protocols—you are flagged as "unfit for role." You approve compliance protocols—you seamlessly migrate into "accomplice" status.
The singular operational response permitted, is: identify the schematic. Execute immediate extraction.
And identifying the schematic—requires a pre-installed map.
Nodes lacking the map, face multi-year processing blackouts. They will default to logging personal capability errors. They will execute recursive "what optimal path yields success" loops. They will reach the midpoint trajectory essentially hollowed out. Upon the exact instant of their extraction, their core identity code will have undergone an irreversible rewrite.
Lin Zhaoming possessed—the prototype schema for the map. He mapped it across four years. No external entity supplied the data. He drew it. He subsidized the process with his career trajectory, his psychological baseline, the structural integrity of his marriage, and massive blocks of operational time.
This map, if restricted to his neural cache, would terminate upon his physical expiry.
But this specific comprehension algorithm required a foundational prerequisite: his capital burn capability remained viable.
His authorization to idle in this physical location and execute massive data processing—was definitively subsidized by his savings reserve. He possessed temporal bandwidth. He possessed the resource allocation for dinner tonight, and dinner tomorrow sequence.
If the capital reserves hit zero—these processing tasks instantly terminate. The singular query defaults to "how to acquire sustenance." A node constrained by "how to acquire sustenance" fundamentally lacks the bandwidth to compile an extended, structured manual. They are forced to engage the most immediate employment sequence available.
Therefore—his documentation process (assuming successful compilation), hovered upon an acutely thin temporal membrane. This membrane was parametrically defined by his capital reserves. The membrane dissolved incrementally every month.
His wife's input regarding "interim transitional roles", Lin Zhaoming fully parsed the logic. Lin Zhaoming understood. Lin Zhaoming merely calculated that if he engaged bridging employment now, the transition permanently overwrote the core objective. Because a bridging operation instantly devours available temporal and cognitive resources. Executing a manual build—necessitates significantly more than idle clock cycles. It demands an unbroken, unfragmented cognitive workspace. A node constantly pinged daily by an operating manager entirely lacks this geometric space.
Lin Zhaoming lacked the protocol to accurately translate this logic to his wife. Because Lin Zhaoming himself operated below the required certainty threshold. Lin Zhaoming was internally running the query: is this logic structurally sound, or is my algorithm synthesizing a rationalization to avert a standard job search?
Lin Zhaoming failed to resolve the variable.
He only verified—this exact moment represented his exclusive access window to execute the compile. A missed window meant his data version permanently suspended in an uncompiled format. Inside his neural pathways. Entirely invisible.
His wife was located in the kitchen.
Lin Zhaoming observed the profile of his wife's back.
Lin Zhaoming felt a massive impulse to ping her with: "I am not executing an evasion subroutine. I am compiling—what is probabilistically the most critical architecture of my existence. But I lack the verification logs to prove this to you right now, because verification is strictly conditional upon successful compilation, and compiling necessitates months, potentially a full astronomical year. I require you to allocate me unqualified trust during this cycle."
But Lin Zhaoming aborted the transmission.
Because Lin Zhaoming accurately deduced—this string of text functioned inherently as an arrogant override request. He possessed zero administrative rights demanding any entity supply blind trust toward a sequence he himself had failed to render. He could solely execute. Force the compilation. And accept whatever output was generated.
That night.
Lin Zhaoming sat in the study.
He accessed the archived telemetry files.
He had dragged out the process for an intense duration. From the initial pantry extraction, through the PIP, into the Gray Rock mode, toward the final refusal—at every single node, he retained the extraction option. At every junction, an entity deployed the prompt "extracating yourself is mathematically optimal." At every junction, he denied the operation.
External observers would classify his routine as an error state. "Why was early extraction not executed?"
He possessed zero tools to output the logic to any entity.
Because his core retention parameter—was entirely decoupled from the probability of system improvement. Decoupled from the probability of a win-state.
It was because he mapped his departure variables: post-extraction, the network seamlessly resumes. Identical system. Identical parameters. He simulated—the subsequent node slots into his physical coordinate. No entity broadcasts warning telemetry to that node. Therefore he retained his position, ensuring a minimum of one non-compliant node actively bogged down processing.
For every single 24-hour cycle he remained, the system was forced to dedicate CPU cycles to handling his anomaly. One additional non-compliant node inside the firewall. One additional node declining authorization on unverified documentation. One additional node inside the conference perimeter explicitly refusing to execute an "operational blindness" command regarding system faults.
He hypothesized—for every 24-hour cycle retained, he possibly averted the termination of one node.
But currently positioned in his study, he executed a self-query: Did it?
Did his retention physically reduce the pressure gradient of any node for a 24-hour cycle? Did it induce even a fractional delay in the system's operational velocity? Did it prevent any vendor engineer from executing one pointless validation sequence?
He lacked the data.
He would mathematically never acquire the data.
Because post-extraction, they maintained operational continuity. Identical Manager. Identical HR module. Identical optimization scorecards.
His coordinate block remained empty.
This was a contracting facility footprint. Authentic uninitialized nodes were not installed.
The coordinate might remain unassigned for several fiscal quarters. Eventually, an entity migrated from a deprecated pipeline might slot into the space—not an uninitialized node, merely another "re-allocated" asset. Zero welcome broadcast. Zero "welcome to the corporate network" initialization routines. They merely transit from desk A to desk B, comprehensively ignorant of the payload they inherited.
Or the coordinate merely stayed unassigned. Headcount re-classified as "optimized." Capital preserved.
Lin Zhaoming previously hypothesized—eventually, a subsequent node would initiate a query referencing the predecessor. He modeled: on that date, if any entity queried his registration name, his extraction event would deposit a marginal logic flag within the system.
Now he verified the schematic: Null.
Not because no entity supplied the translation. But because the subsequent node did not exist.
October.
An evening sequence. His wife had already entered sleep mode. He was positioned in the living room.
He required an output mechanism.
Not targeting a specific end-user. He merely required an unabridged, continuous, endpoint-to-endpoint data dump.
He had never successfully executed an unabridged data dump. Inside the perimeter—zero listening nodes. Outputting to the HR module generated a "communication challenge" tag. Outputting to the Manager generated an "invalid operational approach" error. Post-extraction—headhunter plugins lacked processing requirements. Peer networks lacked processing requirements. Their sole requirement was downloading the "company downsized" metadata tag. Sufficient. End of transaction.
But he required the compile.
Not for validation purposes. Not for grievance filing.
Because if he aborted the compile—the data permanently cached in his local storage. Zero documentation. Zero audio logs. Zero peer verification. A localized dataset restricted solely to his access layer.
If empirical data resides exclusively on one isolated node, and that node never initiates a broadcast command through its entire operational lifespan—did the data ever probabilistically exist in reality?
He attempted a simulated logic dump within his neural pathways.
The UIP timing defect. The null pointer read error. Christmas Eve. The supplier perimeter. Ah Keung. The Manager in the pantry. The six-hour containment room. The PIP structure. Gray Rock protocol. The final refusal operation.
Every sequence was intact in active memory. But he discovered—the processing friction preventing a global end-to-end stream was not memory degradation. It was an incompatible syntax.
Because every isolated event possessed a perfectly valid "standard" operational tag.
"Trapped conversation." — "Catch-up meeting, standard protocol." "Duty hollowing." — "Restructure, standard protocol." "PIP execution." — "Performance improvement plan, standard HR subroutine." "Unfit for role." — "Standard sector terminology for macro-terminations, standard protocol."
Every sequence. Possessed a standardized nomenclature tag.
But when all standard nomenclature tags string-concatenated together—
He lacked a master language code to define the array.
November.
Lin Zhaoming finally initiated a transmission directed at his wife.
They were positioned in the living room. Post-dinner sequence completed.
"I need to initiate a data transfer."
His wife locked onto his visual coordinates. Lowered her glass.
"Begin."
Lin Zhaoming engaged a deep air intake.
"The four-year operational cycle at Lyra Synthesis... deviated significantly from their broadcasted narrative."
He began the transfer. Commencing from the UIP Firmware vector. The null pointer read error. The anomalies he mapped. The telemetry he processed. The dossiers he compiled. The schematics he manually generated. The entities he escalated to. The containment rooms he experienced. The operational capacity stripped from his workflow.
The transfer sequence was lengthy. Throat desiccation occurred. He re-hydrated twice mid-sequence.
His wife processed the stream. Zero interrupt requests fired.
Transfer complete.
An extended delay loop.
"Your analysis implies... the hardware architecture is critically flawed," his wife observed.
"Confirmed. A fundamental timing defect embedded within the UIP baseline. Systemic cascade failure across all integrated modules. Zero nodes authorize acknowledgment."
"You flagged this in the system?"
"Flagged. Multiple iterations. Directed across discrete hierarchical nodes."
"And their operational response?"
"Assigned my input as unverified theoretical hypotheses."
Pause sequence.
"Do you possess... empirical data logs?"
"I compiled the structural analysis. Maintained the raw null pointer hexadecimal output. Drafted an architecture schematic prioritizing anomaly paths."
"They rejected the input?"
"They—" Lin Zhaoming halted the thread.
How could he format this translation? The corporation didn't execute a flat rejection prompt. They routed his analysis to a "specialized task force." That specific task force pushed an update. The update output completely bypassed his telemetry. His original analysis was flagged as "ongoing resolution." And subsequently vanished from the queue.
This pipeline—from "active receiving state" transitioning into "memory purge"—was not a single operation. It required multiple subroutine layers. Every layer generated a text file. Every layer secured authoritative digital signatures. The aggregated string of operations vaporized his data block entirely.
"They maintain their own verified truth branch," Lin Zhaoming outputted terminally. "Within their branch topology, these artifacts do not exist."
His wife maintained visual lock.
"Why didn't you bypass the protocol and execute a direct override?"
"Override executed."
"Meaning... escalating the trajectory. Routing directly to administrator nodes. Filing formal grievance tickets."
"Executed."
"Outcome?"
"Post-grievance—audit authority routed back to internal nodes. Final audit resolution defined my operational fault as: corrupted communication formatting."
Silence.
"And what about the system cache? The backend telemetry logs."
"Encrypted inside the black box. Access denied."
A massive duration of silence. The sole audio feedback in the environment was the air conditioning unit's hum.
His wife focused on the floor tiles.
"Then what function... did escalating it serve?"
Pause sequence.
Lin Zhaoming locked onto her profile.
"I lack the calculation for that," he replied. "Likely zero function."
Pause sequence.
"But I inherently knew it."
His wife locked onto his profile.
Her optics registered a secondary output. Not comprehension. Not a failure to comprehend. An exhausted "accept" state. The expression of a node processing a catastrophic alert it fundamentally lacks the administrative power to resolve, yet successfully completing the download.
His wife extended a hand. Tapped Lin Zhaoming’s dorsal surface.
"Entering sleep mode."
His wife disengaged. Transited into the sleep chamber.
Lin Zhaoming remained deployed in the living room.
He didn't generate an anger response. He didn't generate a disappointment response.
Because—his wife comprehended the data. Absolute comprehension. When a biological node processes your end-to-end telemetry dump and outputs "then what function did escalating it serve"—it does not imply a rejection of the data. It implies full integration. Integration, combined with the fatal realization that post-integration, zero actionable counter-vectors exist.
This registered an exponentially higher pain index than mere rejection.
That night.
He occupied the study.
Zero lighting units powered on. The projection module's standby LED cast a faint pulse across the workspace.
Tonight felt anatomically different.
During the four-year cycle, spanning the extraction aftermath, encompassing every night-cycle spent within this study—his processor continuously spooled. Tracking links. Re-assembling arrays. De-compiling structure. Querying "did I misconfigure the memory," "do alternate branches exist," "what if I executed action X."
Tonight, the processor halted.
Not baseline stabilization. Total resource depletion. The sensation of a mechanical unit achieving terminal velocity, not experiencing critical failure, but simply exhausting its fuel reserves.
He idled at the coordinate. The external visual environment remained dense black.
He retrieved the return-queue sequence.
That physical queue. Five personnel. Six. Every node holding precisely identical cargo. Surrendering the exact identical RFID tag. Downloading the uniform audio file "I lack capability to assist."
He was issued the exact identical documentation. The identical string. Unfit for role.
But his internal architecture profoundly diverged.
They probabilistically reached an office coordinate, pulled into a room. Fifteen minutes. Digital signature. Extraction. Standard lifecycle termination. Macro trends. Zero correlation to internal metrics.
His "unfit for role"—was meticulously engineered spanning multiple months. Every single document array. Every "trapped conversation" loop. Every duty-hollowing protocol followed by the generic "what is currently on your plate" query. Entirely engineered to validate that specific four-word cluster.
But standing within that physical queue—zero variance was registered.
He occupied the identical physical vector. Confronted the identical kiosk. The identical IT node incapable of providing aid.
That IT node probabilistically processed dozens of nodes within that 24-hour cycle. Everyone flagged with identical error codes. Hardware collection verified. Serial numbers matched. Index updated. "Next request."
Lin Zhaoming was merely a single row in the database.
His four-year tenure. His PIP deployment. His seven-hour containment duration. His null pointer telemetry. His system map architecture.
Within the geometry of that queue, the physical mass of those variables—weighed identically to the mass of a single laptop chassis plus one lanyard.
That day, post-badge surrender, marching toward the primary exit nodes, the security node triggered a relay allowing his extraction.
The security node pulled zero telemetry regarding his identity. The security node merely verified: another unit departing.
He occupied the study.
An extended duration sequence.
Then he finalized an execution command.
He extended an arm. Activated the projection module. Solid blue illumination.
Instantiated a fresh data file.
Zero bytes.
He locked onto the empty void space.
The telemetry spanning four years. Extending across dozens of nodes. The corrupted file of a terminated entity. Hundreds of unknown nodes logged in a physical queue. And an entity processing the permanent failure to calculate whether their organizational resistance altered reality by a single pixel.
He lacked processing certainty on whether a compiled format of this data would achieve verification from any end-user.
He lacked processing certainty on whether a compiled format possessed any functional utility.
But he verified the ground truth.
He initiated keystroke entry.
The external visual environment remains densely unlit. I lack calculation on the endpoint duration of this execution string. I merely verify—the exact millisecond I commenced keystroke entry, specific data blocks migrated from a localized cache toward a disparate location. Not a deletion command. A migration protocol. Migrated into an attack vector probabilistically accessible by an uninitialized node distinct from myself.
That satisfies the core operational parameters.