They fired me effective immediately; the new female ceo said, barely looking up from her tablet, “hand over the smart factory system, all of it”; i smiled calmly: “i’m afraid i can’t… not yours to take.”

Olivia’s response arrived six hours later. “We will be transitioning to internal systems management effective immediately. Final payment will be processed per contract terms. Thank you for your service.”

That was it. No discussion, no transition planning, no acknowledgment that she was about to disconnect the central nervous system of a twelve-facility manufacturing operation. Just corporate-speak for, You’re done, and we’re keeping your work. I sat at my desk for a long moment, staring at that email. Then I walked out to my workshop.

Inside that converted two-car garage sat the physical control infrastructure I had built specifically for Sterling’s network. Custom hardware interfaces with dedicated circuits for every major subsystem. Production coordination, quality monitoring, predictive maintenance, equipment synchronization—all of it flowing through boards I had assembled and programmed by hand. Olivia Matthews had no idea that control panel existed. She thought the system was software running on Sterling’s servers. She was about to learn the difference between a user interface and actual operational control.

Six days after her termination email, a calendar invite appeared: “Systems Transition Meeting. Friday, 10:00 a.m. Eastern.” No agenda, no context, just a meeting title suggesting she expected this to be a simple handoff conversation.

I joined the video call three minutes early. Professional appearance, clean button-down shirt, the background showing my home office with my engineering certifications and twenty-eight years of Ford service awards visible on the wall. Olivia logged in two minutes late, settling into her chair with the satisfied expression of someone who thinks they have solved a complex problem with simple cost-cutting. A man from IT joined next—Brad Coleman, according to his screen name. Then a woman who looked fresh out of business school, tablet in hand, ready to take notes.

George Whitman was nowhere on the call. Not surprising. He had probably advised against this entire approach, and Olivia had decided his operational experience wasn’t relevant to modern business strategy.

“Harold, thanks for joining,” Olivia began, her tone suggesting this was routine administrative business. “We’ve made the decision to bring systems management in-house. Appreciate all your work up to this point, but we’re ready to assume direct operational control.”

Assume control, as if navigating through dashboards was the same thing as running the underlying infrastructure. I kept my expression neutral. “You’re terminating the license agreement.”

“Correct,” Olivia said, leaning back like she expected praise for her decisive leadership. “We’ll need complete handover of all code repositories, system architecture documents, and back-end credentials. Standard transition process.”

Brad nodded along. The note-taker typed something into her tablet. They had this choreographed like routine vendor management.

“You’re not licensed to access the core infrastructure,” I said calmly. “Your agreement covers operational use of system outputs. You never purchased ownership rights.”

Olivia’s confident smile faltered slightly. “We paid for development of this system, Harold. That makes it company intellectual property. This is standard business practice.”

“You paid for operational access to a functioning manufacturing network,” I replied. “You never bought the underlying technology. That distinction is outlined explicitly in Section Seven of your contract.”

She glanced off-camera, probably pulling up the contract on another screen. I waited while she scanned through language that George Whitman had reviewed carefully with their legal team five years earlier.

“Look,” she said, attempting to regain control. “We understand there might be some technical nuances here, but we’re prepared to handle operations internally going forward. Just provide whatever documentation you have so we can maintain service continuity.”

“I’ll provide everything you’re legally entitled to receive,” I said. “Nothing more.”

The silence across the video call was sharp. Brad looked uncomfortable. The note-taker stopped typing. Olivia’s jaw tightened as she realized this wasn’t going to be the smooth asset transfer she had planned.

“That’ll be fine,” she said curtly, trying to end the call quickly. “We’ll expect full delivery by close of business today.”

I didn’t respond. I just sat there looking directly into the camera while she fumbled with her mouse, clearly wanting to disconnect before I could complicate her timeline further. The screen went black. I closed my laptop.

Olivia Matthews thought she understood manufacturing because she could navigate software interfaces and review quarterly performance reports. She had zero comprehension of the physical infrastructure, the custom hardware, the dedicated communication protocols, or the specialized knowledge required to keep it all functioning. She was about to get an expensive education.

I walked out to my workshop and powered up the control panel. Every indicator showed green. Production lines synchronized across twelve facilities. Quality metrics updating in real time. Predictive maintenance algorithms running flawlessly across eighty-nine stations. The entire Sterling manufacturing network was running exactly as I had designed it.