Chapter 18: The Final Refusal
Location: The Mirror Realm・Jade Mirror Island (Fog Valley Technology Park) Time: January, 1025 Protagonist: Lin Zhaoming
An invite appeared on the Calendar.
A day in January. Afternoon. Lin Zhaoming sat at his hot-desk. The days of the Gray Rock mode were mostly identical—come to work, sit down, do what was assigned to him (which was getting less and less), attend the meetings he was told to attend (with increasingly less to say), and then leave.
He had stopped reacting. No proactive questions. No arguing. No explanations. Finish the job and leave. This state left them with nothing to work with—because a Gray Rock produces no material. No emotions to record as an "attitude problem." No rebuttals to record as "resistance to management." His existence had become a stone with no texture. You couldn't push it, but you couldn't extract anything from it either.
The PIP deadline at the end of October had passed. The conclusion was "failed to meet improvement goals." He had expected that. But the subsequent action—the anticipated immediate termination—never came.
November. Someone died.
December. KTV.
January. He was still here.
And then, that invite appeared on the Calendar.
Subject: "Next-Generation Core Architecture – Transition Assessment Kickoff Meeting"
He stared at that line of text.
Next-generation core architecture.
He knew about this project.
The whole industry knew. The next generation of computing core architecture would be spearheaded by a completely new supplier. Not an improvement. An overhaul. The legacy core architecture had been running for over a decade, and the entire ecosystem—firmware, drivers, interface protocols, testing pipelines—revolved around it. Industry insiders had long known a switch was inevitable. The question wasn't "if it will switch," but "how many things will break when it switches."
Lin Zhaoming knew even more.
Because the root cause of the issue he had spent three years tracking—the UIP timing defect—lay precisely in the legacy architecture's clock design. The CLK speed, the parallel processing methodology, the communication protocol of the system management bus—everything was different from the new architecture.
Under the legacy architecture, the UIP timing defect already existed. He had seen it. He had written reports on it. His report became Appendix B. The problem was propped up by a workaround. Nobody fixed the root cause. Because fixing the root cause meant acknowledging that the root cause existed. And acknowledging that the root cause existed meant—a cascade of systemic explosions.
Now, they were switching to the new architecture.
The new CLK timing would be different. The new parallel processing method would be different. The system management bus communication protocol would be entirely different.
Which meant: every single legacy workaround—the ones built over years, plastered together with infinite testing and justified as "complex issues difficult to isolate"—would completely fail.
Previous alternative architectures had already been trialed. Even the relatively similar alternatives couldn't solve the compatibility issues. This new one was an even further departure.
Lin Zhaoming didn't even need to calculate to know: this project, given the current system design, was a disaster.
He knew.
The Manager knew too.
Because the Manager had been secretly working on this for months.
This wasn't news.
Lin Zhaoming had always known about the next-gen architecture. Industry newsletters mentioned it. It was brought up in Town Halls. The Manager occasionally hinted in meetings that "some new directions need to start preparation."
But he was blocked out.
"I'll handle this for now."
"You don't need to worry about this part."
"Focus on the tasks at hand."
His tasks were getting fewer. Core responsibilities were shifted away. Weekly meetings became performances. His scope shrunk to nothing but documents and VLOOKUPs. Meanwhile, the prep work for the next-gen architecture—interface assessment, compatibility testing, supplier communication—things that naturally should have fallen into his wheelhouse—were all being handled in another channel he couldn't access.
He knew. He didn't ask. Gray Rocks don't ask questions.
But he had ears.
Fragments in the hallway. Half-heard sentences in the pantry. Someone accidentally mentioning "the timeline for the new core" in a meeting and immediately falling silent. Ah Keung—from the vendor side—once sent him a test report on the system management bus compatibility. Maybe it was an accidental CC. Maybe it was Ah Keung's way of passing a message. He read it.
The numbers in the report were ugly. The failure rate in compatibility tests was unreasonably high. The clock synchronization error was three times larger than the legacy architecture. The handshake protocol of the system management bus was entirely different—legacy drivers, legacy firmware, legacy interface logic, none of it lined up.
Lin Zhaoming finished reading it. He didn't reply.
Because replying = confirming he received the data = confirming his involvement in the project = walking into the trap.
He didn't reply. But he memorized every single number.
Now, an invite had appeared on his Calendar. His name was on the attendee list.
Meeting Room B. Three o'clock.
When he walked in, there were three people in the room. The Manager sat in the center. Beside him was Derek—the very Derek who had said "your commitment is so strong" months ago. On the other side sat a familiar face, a recent transfer named Kevin. Clean. No history. A product of the dilution mechanism.
Several printed slides were spread across the table.
The Manager watched him walk in. No pleasantries. No courtesy. All interactions since the Gray Rock protocol were like this—stripped down to nothing but commands and responses.
"Zhaoming, sit."
He sat down.
"The next-generation core architecture transition, you should be aware of it."
"I am. The whole industry is."
"We've been doing internal prep work for a few months." The Manager flipped to the first slide. A timeline. Highly colorful. Every phase had a name. "Phase 1: Requirements Definition. Phase 2: Compatibility Assessment. Phase 3: System Integration. Phase 4: Validation and Mass Production."
Four Phases. Every one packed with a massive list of sub-tasks.
"The current situation is—" The Manager paused for a moment, selecting his words. "Certain parts of Phase 1 and Phase 2 are progressing slower than expected. We need someone to specifically lead the latter half of Phase 2—interface compatibility assessment, system management bus protocol alignment, and firmware-layer timing calibration."
Firmware-layer timing calibration.
Lin Zhaoming sat there. Emotionless.
What he heard was: timing calibration.
What he knew was: the UIP timing defect. The CLK was faster. The parallel architecture was different. The system management bus protocol was completely incompatible with the legacy one. These were not "progressing slower than expected." They were fundamentally unsolvable under the legacy framework. Because the legacy framework itself harbored a defect that had never been officially acknowledged.
Now, you were layering a new architecture on top of the old framework. Not only was the old defect unfixed—it would be amplified by the timing variance of the new architecture. Amplified by how much? Looking at the numbers in the report Ah Keung sent—three times. At least three times.
But he couldn't say any of this out loud.
Because the UIP timing defect "never existed." That was the consensus post-November. Not only did no one acknowledge it—no one even mentioned it. Tickets vanished. Comments were edited. "What null pointer?"
If he were to say something, it would be: "The core difficulty of this project lies in the firmware timing. And the timing issue isn't new—the legacy architecture already has it. It's just propped up by a workaround. The new architecture will render all workarounds useless. To truly fix it, you have to go back and fix the root cause. And the root cause..."
And the root cause never existed.
So anything he voiced would be spun as: an employee with "communication issues," once again raising hypotheses with no data to support them.
The Manager continued.
"The timeline requires the Phase 2 report to be submitted by the end of March. As for resources—"
Derek took over: "Kevin and I will support you. But you'll be the primary driver. Your firmware background—" Derek smiled, a very friendly smile. "This is your strength, isn't it?"
My strength.
They had stripped him of all his core tasks. Locked him out of this project for months. Cut off his support. During the PIP, they told him to "pause all existing work and focus purely on self-improvement." And now, they were saying—this is your strength.
Derek kept talking. Talking about timelines. Milestones. "Stakeholder alignment." "Cross-functional collaboration."
Kevin sat to the side, silent. The standard posture of a newcomer in a meeting that had nothing to do with him.
Lin Zhaoming looked at the slides.
Within the scope of Phase 2, there was a single line of text: "Firmware timing alignment across legacy and next-gen interface protocols."
Legacy and next-gen.
The legacy timing—he’d chased it for three years. Written a report. The report became Appendix B. Appendix B sat inside a document no one ever opened.
The next-gen timing—the report Ah Keung sent. The failure rate. The variance. The mismatched handshake protocols. He had read it, and never replied.
Now, that line of text demanded he align them within two months.
Two months. No team. No backend logs. No data. No one who had ever officially admitted the legacy timing had a problem in the past three years.
He had to start from "this problem never existed" and, within two months, solve it.
The Manager finished speaking.
The room fell silent for a beat.
"Zhaoming, do you have any questions?"
Lin Zhaoming looked at the printed slides on the table.
He remembered many things.
He remembered the first week, Ah Wen poking his finger at two spots on the wall. Those two spots happened to be the firmware version transition nodes. Ah Wen had seen the exact same things he saw. Then Ah Wen brought his rules in and translated the map into Appendix B.
He remembered Christmas Eve. Engineer Chen's voice. "Thought about dying." A four-hour meeting. He single-handedly called for a halt. The halt left no record.
He remembered Transit Island. Standing beside his mother's hospital bed. The meeting buzzing in his earphones. Six o'clock to eight o'clock. All the DMs were scheduled during this time slot.
He remembered the thirty-nine days. The year-end banquet venue. The welfare committee meeting minutes. VLOOKUP. "Do a little bit of everything."
He remembered the PIP. A digitalization effort that couldn't be pushed through in a year transformed into a goal heavily penalized if failed in a quarter. The chaos he had tried to fix became the tool used to punish him.
He remembered the Gray Rock. Not reacting. Not providing material. Yielding nothing they could use.
Now—they wanted him to react. Wanted him to yield. Wanted him to do the impossible. When he failed, they would have new material. A new report could be written. A new "narrative" fabricated.
This wasn't a task.
It was a new PIP. Only this time, it wasn't administrative—it was technical. One he couldn't refuse—because "this is your strength." One he couldn't accomplish—because the three-year-old root cause had been rigorously insured to "never exist."
A perfect trap.
He knew it.
"Yes," Lin Zhaoming said.
The Manager looked at him.
"The scope of Phase 2—timing alignment—requires the complete legacy logs. The backend system operational records. The full revision history of the firmware versions. The timing profiles of every interface."
He listed them one by one. His voice was flat. Deliberate. Every item was something he had chased for three years and never gotten access to.
"I have never had access rights to these logs. If I am to perform the alignment, I first need to—"
"I'll talk to IT about the logs," the Manager interrupted. "You draft a list first."
"Second," Lin Zhaoming continued, as if he hadn't heard the interruption. "The legacy timing issue—if there is one—was not independently documented in past reports. That means, to do the alignment, I first need to re-establish the baseline for legacy timing. That workload alone exceeds two months."
The Manager's expression shifted slightly. A microscopic change. Derek glanced at the Manager.
"Third. The protocol discrepancies in the system management bus. The legacy protocol and the new one are fundamentally different. This isn't an alignment issue. It's a rewrite issue. Rewriting requires a development team. Development team manpower—"
"Zhaoming," the Manager's voice was level. "Everything you're bringing up, I'm already aware of. That's why I came to you."
Lin Zhaoming stopped.
He looked at the Manager.
"I have evaluated the scope and timeline." His tone didn't shift. Didn't raise. Didn't lower. It held the identical texture of the Gray Rock—but this time, with an added property. Clarity. "This scope, under the current conditions—no log access, no legacy baseline, no development team—delivering a Phase 2 report in two months is impossible."
The room was completely quiet.
"I can conduct an assessment: what resources are needed, how much time, and how much manpower to make it happen. That assessment, I can deliver. But as for this version—" He pointed at the slide. "This version, I cannot accept."
The Manager didn't speak immediately.
Derek stared at the table. Kevin looked out the window.
"What you're saying is—" the Manager began.
"What I am saying is, the prerequisites for this scope do not exist. If I forcefully take it on, I cannot be held responsible for the quality of the resulting report. And what you need is a report that can be defended. Not something with my name on it that has zero substance inside."
The Manager would understand that last sentence perfectly well, he knew.
A report that can be defended.
The Manager's job had always been manufacturing defendable documents. He had seen plenty of documents devoid of substance. He didn't need another one.
But what he needed was a failure report bearing Lin Zhaoming's name.
Lin Zhaoming was refusing to give it to him.
"Are you sure?" the Manager asked.
"I am sure."
Silence for a few seconds.
The Manager put the slides back into his folder.
"OK. We'll arrange things differently."
The meeting ended.
Lin Zhaoming walked out of the meeting room.
The corridor stretched out long. Afternoon sunlight pierced through the windows, casting parallel shadows across the floor.
He walked past the open area. Someone was on the phone. Someone was typing. Someone was frowning at their screen. A normal office. A normal afternoon.
No one knew what he had just done.
No one knew what had transpired in Meeting Room B.
The invite on his Calendar, slated for thirty minutes, was already over. If anyone checked, the invite simply stated "Next-Generation Core Architecture – Transition Assessment Kickoff Meeting." No meeting minutes. No follow-up emails. Nothing recording Lin Zhaoming saying "I cannot accept."
If anyone ever asked in the future, the Manager's version would be: "We discussed it with him. His capability doesn't match the requirements of this role. We've decided to make alternative arrangements."
Not a single sentence of it was a lie.
He walked to the restroom. Closed the door. Stood before the washbasin. Looked in the mirror.
The man in the mirror looked exhausted.
He turned on the tap. Washed his hands. Washed his face. The water was freezing.
He watched the water swirl down the drain.
When he stepped out, the hallway was exactly the same. Nothing had changed.
He knew he had made a decision. A decision that would leave no trace. No document. No recording. No email. As if it had never happened.
Just like Christmas Eve. The halt. No records.
Just like his report. Appendix B. No one turned the page to read it.
The thing this company excelled at most—wasn't manufacturing products, it was manufacturing things "never happening."
He returned to his seat. Sat down. Resumed his work.
The Gray Rock persisted.
★ Flashback D: "Sorry, It's Unfair"
That day came rushing back unexpectedly.
Not because of the lighting in the meeting room. Not because of the Manager's face. But because of those three words: "Are you sure?"
When the Manager asked, "Are you sure?", Lin Zhaoming's mind flickered. Instantaneously. To another room. Another person. Another "Are you sure?".
The year 1020. The Amerion Consortium. Old World Inheritor Territory. Across the Pacific.
The company was called... honestly, he couldn't even remember the full English name anymore. Too small. So small nobody knew it. Their product was incredibly niche—firmware customization for embedded systems. Around fifty people. A single floor. Lin Zhaoming was the only one there with a dual background in both hardware and software.
He could essentially do everything there.
Not because he was exceptionally brilliant. But because the structure there allowed him to. The boss knew what his skills were. His colleagues knew what he was working on. If there was a problem, they discussed it. After discussing it, they executed. After executing, they clocked out.
It was simple. So simple that back then, he thought all companies operated like this.
The final day.
The boss called him into his office. A tiny room. Documents piled on the desk. Post-its stapled to the wall. A man who had worked for thirty-something years, an Amerion native with graying hair, sitting in a squeaky office chair.
"Zhaoming, take a seat."
He sat down.
The boss looked at him. Didn't speak for several seconds.
"You know the company's situation."
He knew. Orders were down. A major client got acquired by another firm. Only two projects left in the pipeline.
"I fought for it," the boss said. His voice was low. "Talked to the board. Talked to the partners. Tried finding new clients. But—"
He stopped.
"Sorry. This isn't fair. Your performance was never the issue. This isn't on you. It's the market. It's timing. Things I can't control."
Lin Zhaoming sat there.
"I wrote you a reference letter. Anyone who calls to ask, I'll tell them exactly what you built here."
He picked up a piece of paper from the desk. Handed it over.
"This is your severance package. It's not much. I did everything I could. If there's anything I can ever help you with down the road—you call me anytime."
Lin Zhaoming took the paper. Glanced at it.
"Are you sure there's no other way?" he asked.
The boss looked at him. There was something in his eyes. Something very clear. Not pity—it was a kind of respect. Respect directed at someone he knew he had failed.
"I'm sure. If there were, I wouldn't be sitting here with you."
They stood up. The boss extended his hand. They shook hands.
"Take care of yourself."
"You too."
Lin Zhaoming walked out of that tiny office. Walked across that single floor. A fifty-person company, the hallway was short. People nodded at him. People said their goodbyes.
At the entrance. The parking lot. The sun in the Old World Inheritor Territory was glaring.
He sat in his car. Didn't start the engine right away.
He remembered the feeling in that moment—not anger. Not sadness. It was a strange sense of cleanliness. As if someone had thoroughly washed an object. After washing, the object just was what it was. Nothing extraneous.
Sorry. Unfair. I can't control it.
Seven words.
No "this is better for your career development."
No "you know your own situation best."
No "I am speaking to you with the benefit of hindsight."
No "if you don't leave, we'll use every trick in the book to taint your file."
No PIP. No trapped conversations. No seven-hour interrogations. No "you chose not to go to the QCC." No "no one stopped you."
Just seven words.
Sorry. Unfair. I can't control it.
Plus a reference letter. Plus a genuine handshake.
Lin Zhaoming sat at his hot-desk.
The flashback dissipated. The glaring sun of the Old World Inheritor Territory retreated back into memory.
Before him were the low-hanging clouds of Jade Mirror Island.
Seven words, and three years.
The exact same underlying event—you are being let go.
Two entirely different methodologies.
Was what that Amerion boss said a lie? No. The market was genuinely bad. Orders had genuinely dropped. He genuinely tried his best. The severance was genuinely small.
Was what the Manager at Aura Synthetics said a lie?
He said "Resigning is best for you." He said "The PIP is a development plan." He said "This is your strength."
The structure of every sentence was: wrapping a pre-calculated conclusion in the guise of "for your own good." He didn't even need to consciously scheme these things. These reactions were instantaneous and automatic in his brain. Doing it every day, every task, over and over, until fabricating narratives became an instinct—planning how to spin, how to document, how to lay the trap before even starting the task. He was no longer a person who just practically did the work.
Both bosses sounded sincere.
The difference was: one sincerity still contained a human being. The other sincerity contained only an algorithm.
That Amerion boss—his "sorry" was the genuine regret of a man who couldn't protect someone he knew had value.
The Aura Synthetics Manager—his "for your own good" was the execution of a man who had already calculated everything. He was like this from Day 1. It’s just that when things were fine, he didn't need to show it. When things went wrong—he was rotten to the core.
Who was harder to deal with?
The one who had calculated everything. Because every single word he spoke was actively building a record in his favor. What he spoke wasn't conversation—it was documentation.
That night.
Lin Zhaoming returned home. His wife was in the kitchen. He took off his shoes. Put down his bag. Sat on the sofa. Didn't turn on the TV.
His wife brought out a bowl of soup. Sat across from him.
"You look awful," she said. It wasn't a question.
Lin Zhaoming picked up his spoon.
"Something happened today."
His wife waited.
"They wanted me to take on a project. A project they've been running for months, one I was completely excluded from. Now that it's hitting a wall, they come to me."
"Did you take it?"
"I couldn't."
"Did you tell them that?"
"I did."
His wife looked at him.
"So what will they do?"
"I don't know. Probably find another way."
His wife took a sip of soup. Put the bowl down.
"Isn't refusing... just asking for trouble?"
Lin Zhaoming thought for a moment.
"It's not asking for trouble," he said. "It's refusing a trap."
"A trap?"
"Something crafted so beautifully that if I accept, it is guaranteed to fail. And the responsibility for the failure falls squarely on me."
His wife studied him for a long time.
"Are you sure it's a trap? And not... that they genuinely just need your expertise?"
It was an excellent question. Excellent because—he couldn't be a hundred percent certain.
His deduction was that it was a trap. But what if he was wrong? What if it truly was just because his background was the perfect fit?
A few seconds.
"It's both," he said. "They genuinely do need someone with my background. And I genuinely cannot accept it—because they have systematically severed every resource needed to actually accomplish it. Both things are true at the same time."
His wife stopped asking.
They drank their soup. Ate dinner. The atmosphere at the dining table was quiet. Outside the window, it began to rain.
Late night. His wife was asleep.
Lin Zhaoming sat in the study. The overhead light was off. The light from the desk lamp was dim, cast in an amber hue.
He wasn't working. He just sat there.
The thoughts turning in his head were moving slowly. Not stuck, but as if something massive, submerged in darkness, was steadily breaching the surface of the water.
He thought of Peter.
Months ago. Peter's office. The door open. Peter sitting there looking out the window.
On the last day of the thirty-nine days, he had visited Peter. Peter had said to him: "Your situation—during the QCC, the analysis with the suppliers—I know about it." Then he turned back to look out the window. "It wasn't documented that way in the files. But I know."
Peter knew. And then Peter actively did nothing. Because Peter couldn't. Or wouldn't. Or both.
But Peter had said another line. Even earlier.
When Lin Zhaoming was pursuing the QCC case. One day. Peter walked past his desk. Paused for a second. In an incredibly casual tone—
"Your colleagues are all here to support you."
Back then, he thought—it was comfort. A boss's reassurance. "Don't worry, you're not alone," that sort of thing. He even felt a brief moment of warmth. Peter might have been a fairly useless boss, but at least he offered a comforting word.
Now. Sitting in the study.
"Your colleagues are all here to support you."
The function of that sentence was not comfort.
It was documentation.
If someone were to audit Peter's management history in the future. If someone asked: "When Lin Zhaoming was at the company, did you provide him with support?" Peter could say: "Yes. I personally told him that his colleagues were there to help him. I gave him full support."
A verbal utterance. No email. No formal document. But in Peter's memory—if he chose to recall it—there was a version where "I supported him."
This wasn't Peter plotting a grand conspiracy. Conspiracies require planning. Peter didn't need to plan. When he spoke those words, it was automatic—like blinking. Fabricating records, laying down plausible deniability, uttering a defensively impregnable sentence for future audits—he had been doing these things for God knows how many years. The Manager knew to loop in HR for the PIP, knew to forbid recordings, knew to code-switch his tone two seconds before the call connected—none of it required deliberation. Yvonne joining for a mere fifteen minutes, just enough for the line "HR participated" to appear on the official record—it didn't need conscious design.
These people didn't "genuinely believe" they were doing the right thing. These people had mastered making false claims, gaslighting, and shifting blame until it became instinct. Before they even took action, they preemptively drafted the narrative arc. Before striking, they had already rigged the game board. The people who survived and climbed in this company were handpicked—and then thoroughly conditioned. Day after day. Year after year. Until finally, the very concept of "practically solving a problem" ceased to exist in their reality universe.
Lin Zhaoming sat in the study. It took him a very long time to accept this reality.
Not because he didn't want to admit they were this kind of people. It was because—he could understand why they became this kind of people.
A person enters this system. The system selects them—because they are flexible enough, obedient enough, 'shrewd' enough. Then the system teaches them: steal the credit, deflect the blame, spin the narrative, control the documentation. They learn it. They get promoted. They teach the next person. The next person learns it. The next person gets promoted.
An unbroken chain.
By the time the Manager sitting across from you tells you "this is your strength," he doesn't need to mentally calculate "what is the function of this sentence." That cognitive step has been excised. The boundary between calculation and breathing has dissolved. He has lost his humanity—not because he was born without it. But because the system forbids it. Anyone with intact humanity couldn't survive in this ecosystem for more than two years.
The ones who remain are all this type of person.
And that is the most terrifying part.
Lin Zhaoming sat in the study. The light from the desk lamp. The sound of rain against the glass.
In his mind, something finally fully surfaced. Not a word. Not a sentence. But a shape.
Everything he had done over the past four years—chasing the UIP timing, writing reports, verifying data with suppliers, halting destructive tests, pitching efficiency proposals, conducting QCC analysis—it was all a game.
A problem-solving game.
He had always assumed: you fix the problem, you prove your value. You execute well, you earn recognition. Those were the game's rules. He had played by those rules his entire career.
But the points the system was scoring weren't for this game.
The system was scoring a completely different game.
The rules of that game were: who controls the narrative. Whose name is on the approved documents. Whose version becomes the "official version." Whose contributions are officially recorded. Whose failures are artificially manufactured.
He hadn't even entered this game from start to finish. Not because he lacked the skill to play it. But because he didn't even know it existed.
He thought there was only one game in town. He thought making the best bowl of noodles was all that mattered.
But the referee had been sitting in a completely different stadium the entire time.
Every shot he took—the QCC analysis, the Christmas Eve halt, tracking the UIP, the efficiency proposals—every single one landed precisely. Every single one possessed technical merit.
But not a single shot landed in the arena the referee was watching.
So his score was forever zero.
Not because he was a bad player. It was because he was playing a game with no referee.
Meanwhile, those who played exclusively in the second arena—stealing credit, manufacturing crises, colluding on stories, performing theatrics—their actual technical skills might be garbage. But they were in the right arena.
The referee only tallied points there.
Lin Zhaoming sat in the darkened study. The rain grew heavier.
He thought about the meeting room that afternoon. The Manager, Derek, Kevin. Three people. An impossible mission. A trap he had rejected with three sentences.
He had refused.
But he knew: refusing wouldn't change anything. They would simply find a second avenue. A second document. A second "narrative."
What he could achieve wasn't a victory.
It was to avoid losing on their terms.
The Gray Rock yields no material. Refusing yields no failure. He had given them absolutely nothing to weaponize. But he gained nothing either. No vindication. No apologies. Nobody confessing "you were right all along." Nobody opening Appendix B.
Zero.
He sat there. From start to finish, all he walked away with was zero.
But a zero was fundamentally different from a negative number.
A zero meant: you didn't win.
A negative number meant: you lost on their terms. Your name was penned into a story you didn't recognize. Your version of reality was violently adulterated. You left carrying a mold that wasn't yours.
Today, he guarded the zero.
He stood up. Switched off the desk lamp. Walked out of the study. Walked into the bedroom.
His wife's breathing was steady and even.
It was raining outside. January on Jade Mirror Island. Bitingly cold.
He lay down. Stared at the ceiling.
He didn't know what tomorrow held. But today, he refused a trap. Nobody would ever know about this. No file would log it. No trace would remain to prove he ever made this choice.
Just like Christmas Eve.
Actions taken, left unrecorded.
Unrecorded actions, never happened.
But he knew.
"Two games running simultaneously. You believe you're navigating the first game—solving problems, isolating root causes, writing reports. You played flawlessly. You really did play flawlessly. But the referee sat in the second arena. The score being tallied was: who controls the narrative, whose name signatures the right document, whose reality becomes the designated truth. Every single one of your shots landed perfectly. It's just that they landed in the arena with no referee. Therefore, your score, from the very beginning, remained an unwavering zero. And that day, when I refused that impossible task—I wasn't rejecting the workload. I was rejecting losing under their terms and conditions. A zero isn't a win. But a zero and a negative number are vastly different parameters. A negative number is who you are within their fabricated narrative. A zero is: you are absent from their narrative entirely."