He Credited His Lover for My Genius, So I Revoked His Billion-Dollar Empire

Chapter 2 Code Double-Sign

The afterglow of the press conference curdled into a new, oppressive reality the following morning. Serena, flush with her newfound status as Oracle’s muse, had arrived at the office with an entourage and a white-board marker. She commandeered the primary strategy room—my strategy room—and began sketching out what she called a “narrative-driven logic path.”

I was summoned like a junior engineer. Arthur stood beside her, a hand resting proprietarily on the back of her chair. He smiled at me, a tense, placating expression that said, *Just play along. For the IPO.*

“Chloe, Serena has had a breakthrough,” Arthur announced, his voice a little too loud in the sterile quiet of the room. “It’s about enhancing the user’s emotional journey with the AI.”

Serena gestured to a series of crude boxes and arrows on the whiteboard. “Right now, Oracle is too… efficient,” she said, the word dripping with disdain. “It gives the user the most optimal answer. But where’s the story? I propose we add a ‘serendipity’ module. It would intentionally route a percentage of queries through less logical, more poetic data nodes. It would make the AI feel less like a tool and more like a companion.”

I stared at the diagram. She was proposing to deliberately cripple the core function of the system. It was the equivalent of asking a surgeon to occasionally use a butter knife instead of a scalpel, just to make the procedure more “interesting.”

“The core logic is designed for probabilistic accuracy and speed,” I stated, my voice flat and devoid of emotion. “Injecting randomized, non-optimal pathways would degrade performance by an estimated 40% and introduce a significant risk of data-looping paradoxes. The system could lock up.”

Serena’s smile tightened. “Perhaps. Or it could produce something beautiful and unexpected. That’s the kind of disruption that gets headlines, Arthur.”

“She has a point, Chloe,” Arthur said, turning to me. “We need a ‘wow’ factor for the final investor demo. Something less… predictable.”

“The ‘wow’ factor is that it works with 99.98% accuracy at petaflop speeds,” I countered. “It’s a multi-billion-dollar system, not a slot machine.”

The air grew thick with unspoken history. This was the chasm between us: I built things to be perfect; Arthur sold things by making them sound perfect. For five years, my perfection had fueled his narrative. Now, the narrative was demanding to rewrite my code.

“There has to be a middle ground,” Arthur said, stepping into the role of mediator. He didn't look at me, but at the whiteboard, as if the solution lay in Serena’s scribbles. “We need to innovate, but we need to be stable. So, here’s what we’ll do. We’re implementing a new development protocol for the Oracle core. A dual-key approval system.”

My blood ran cold.

“From now on,” he continued, his tone now one of decisive leadership, “no updates to the core architecture can be pushed live without two signatures: one from Chloe, for technical stability, and one from Serena, for strategic vision. It enhances collaborative oversight and ensures our technology is always aligned with our market narrative.”

It was a masterstroke of corporate castration. He wasn't firing me. He wasn't even demoting me. He was making me a co-dependent, shackling my authority to the whims of a woman who didn't know the difference between Python and a python. He was turning my creation into a committee-run bureaucracy.

I saw the triumphant glint in Serena’s eyes. She had won.

“I see,” I said. I let the silence hang for a moment, letting Arthur’s gaze finally meet mine. I needed him to see my expression, so I manufactured one of weary defeat. I let my shoulders slump slightly. “If that’s your decision, Arthur, I’ll abide by it.”

Relief washed over his face. He had expected a fight, an academic’s tantrum. My quick capitulation was a gift. “Thank you, Chloe,” he said, his voice softening with patronizing gratitude. “I knew you’d see the big picture. This is for the good of the company. For us.”

He thought my compliance was rooted in my love for him. He thought I was folding, as I had always folded, for the promise of a future that was always just one more compromise away.

He was wrong. He wasn't shackling me. He was handing me the keys to my own freedom. This new protocol was the perfect, legally documented firewall I needed. It created an official, board-approved division between my foundational work and the cosmetic, chaotic superstructure they wanted to build on top of it. He was building the wall for me, brick by brick, and calling it collaboration.

That afternoon, I returned to my private lab. The first email I opened wasn't a corporate directive, but one that had arrived in the inbox of my old university email address, an account I kept active for academic journals and research alerts.

The sender was Julian Croft. CEO of a rival deep-learning firm, a man known for his technical acumen and ruthless efficiency. The subject line was: *Re: “Asynchronous Neural Lattices,” JQCS 2018.*

My heart gave a jolt. It was the title of a paper I had published under my own name, Chloe Reed, three years before I met Arthur. It laid out the theoretical framework that would eventually become Oracle.

*Dr. Reed,* the email began.

*I am writing to express my long-overdue admiration for your 2018 paper. The elegance of your model for predictive self-correction was years ahead of its time. I have followed your subsequent work—or lack thereof, in the public domain—with great interest. If you ever find yourself considering a return to a research environment where foundational architecture is prioritized over market narrative, I would be honored to have a conversation.*

*Sincerely,*

*Julian Croft*

I read the email three times. It was a lifeline from a world I thought had forgotten me. A world that saw *me*, not Arthur’s shadow. It was a confirmation that my value wasn’t tied to the company he was about to take public. My value was in my mind, and it was portable.

I didn't reply. Not yet. But I saved the email to a secure, encrypted drive. It was a seed of a future I was now actively cultivating.

Then, I turned to the task at hand.

With Arthur’s new “dual-key” mandate as my official justification, I began the process of technically partitioning the system. I wrote a formal memo to our head of compliance and the CTO, outlining the new security protocol.

*“To adhere to the new dual-key approval process and to safeguard the integrity of the core P-387-Oracle-Core patent during the implementation of experimental narrative modules, I am isolating the foundational algorithm within a secure, sandboxed container on the main server. All front-end applications and UI-level functions will now interact with the core via a restricted API bridge. This will prevent any top-level code changes from causing accidental corruption to the foundational logic. It is a necessary measure to ensure stability and compliance.”*

It was perfect corporate-speak. Every word was true, yet the full truth remained hidden. I wasn’t just protecting the algorithm; I was preparing it for extraction. I wasn't building a sandbox; I was building a lifeboat.

For the next ten hours, I worked with a focus I hadn’t felt in years. I wasn't building, I was meticulously disassembling. I carefully uncoupled my elegant, self-correcting lattice of code from the clumsy, sprawling mess of the company’s application layers. I severed the thousands of tiny, unnecessary tendrils their engineers had coded in over the years, replacing them with a single, clean, and legally defined API connection.

By the time I was finished, the Oracle system was like a patient under anesthesia. On the outside, all monitors showed it was alive and functioning. But on the inside, its heart had been surgically isolated, ready to be lifted out, leaving behind nothing but the humming machinery of life support.

I ran a final diagnostic. The system was stable. The API bridge was holding. From Serena and Arthur’s perspective, they now had the control they wanted over the front-end. They could paint the car any color they wished.

They had no idea I was about to repossess the engine.

I logged out, the soft glow of the server racks reflecting in the dark glass of the lab. On my monitor, a small calendar widget displayed the date. The countdown had moved forward.

Six days.