Story code: ST-001144
Part 2: The Cryptographic Wall
The transfer of the business registry was supposed to make Greg the master of my startup, but legal ownership did not write code. Within forty-eight hours, the illusion of his control began to fracture right in our parents’ living room.
Greg sat at the dining table, his laptop open next to a cold cup of tea. His brow was furrowed, and he kept typing something, clicking aggressively, and then deleting it. Every few minutes, he checked his phone, his leg bouncing nervously against the table leg.
“Sarah,” he said, not looking up. “What’s the host login for the production server? I’m trying to update the landing page copy for the partner integration.”
“It’s in the developer documentation I shared with the LLC last year,” I replied, sitting on the armchair across from him with my hands folded in my lap.
“I looked at that,” Greg snapped, his defensive tone slipping through his concerned-brother facade. “It’s just a bunch of markdown files. I need the direct password to the hosting dashboard.”
“There is no simple password, Greg,” I said. “The deployment pipeline is automated through a secure repository. You have to push the code changes through the command line.”
He stared at his screen, his jaw tight. I watched him open a terminal window-something he had clearly looked up how to do on Google. He typed a few commands, hit enter, and got a wall of red error text. He didn’t know what a repository was, let alone how to pull or push branch updates. He was completely out of his depth, trying to manage a complex database architecture with the skills of a basic office administrator.
“Just give me the master login,” he said, his voice rising slightly before he checked himself and looked toward the hallway where our mother was vacuuming. He lowered his voice. “We have a deadline with the integration partner tonight. If the landing page isn’t live, they’ll pull out of the pilot program.”
“I can’t just give you a password,” I said. “The production server requires a hardware security key. The two-factor authentication is tied to my physical device. Even if you change the registry, the system doesn’t care about legal paperwork. It only cares about cryptographic keys.”
Greg closed his laptop halfway, glaring at me. The stolen therapy note lay on the table beside him, scribbled with messy notes he had taken while trying to figure out my systems. He was realizing that owning the company on paper meant absolutely nothing if he couldn’t actually run the platform, and the partner deadline was ticking down by the minute.
He stood up, grabbing the yellow paper and pacing the room. “If this integration falls through because you’re being difficult, Sarah, it’ll prove to Mom and Dad that you’re sabotaging your own business.”
I remained silent. I knew the integration partner was expecting a fully functional API update, not just a landing page copy edit. Greg had no idea that the entire backend database was waiting for a migration script that only I knew how to write. How far was he willing to push this charade before he admitted he couldn’t type a single line of working code?