Chapter 4 - THE BROTHER WHO KNEW TOO MUCH
For three seconds, nobody spoke.
The username on Marcus's screen was an old identifier I had used during my consulting years. It had been associated with my private development environment, not any public code repository.
I stared at it, trying to understand how it had appeared inside Veyra's system.
“Where did that branch come from?” I asked.
Marcus quickly minimized the window.
“It's probably a migration artifact.”
“Then restoring the audit history should explain it.”
He looked toward Evan.
That glance told me more than his answer would have.
Daniel noticed it too.
“Marcus,” he said, “please reopen the repository history.”
Evan stood abruptly.
“This is absurd. We're letting a family dispute turn into a corporate interrogation.”
“No,” Naomi replied. “We're examining a possible ownership problem in a company we may invest in.”
“Then examine the documents our lawyers prepared!”
“We will. We also need to examine the underlying records.”
Marcus slowly reopened the window.
The branch had been imported from an archive. Its original creation date matched the month I had developed the first working version of my engine.
The archive name was unfamiliar.
The commit structure was not.
I recognized my method of organizing test cases, the way I separated validation logic from risk scoring, and the comments I wrote to remind myself why certain assumptions had to be challenged before the software produced a recommendation.
My throat tightened.
I had spent months building that system while working a second job to cover my expenses. I had eaten cheap dinners at my desk, tested the same calculations until dawn, and rebuilt entire sections whenever the results seemed too confident.
Now my work was sitting on someone else's laptop, dressed in a different interface and presented as a corporate invention.
“Who imported this archive?” Naomi asked.
Marcus's voice was barely audible.
“I don't know.”
Evan slammed his palm against the table.
“You manage engineering! How can you not know?”
Marcus flinched.
“Because I didn't create the original archive.”
The room became very quiet.
Evan stared at him.
“What did you say?”
Marcus took a breath.
“I joined Veyra after the initial prototype existed. You told me the foundational engine had been developed by an outside contractor who had transferred all the necessary rights.”
I felt cold.
“Which contractor?”
Marcus shook his head.
“I was given a folder with a contract summary. I never met the person.”
“Do you still have the folder?” Daniel asked.
“I believe it's in our legal archive.”
“Then preserve it. Don't alter or delete anything.”
Evan looked around as if searching for someone willing to rescue him.
Dad had remained silent for several minutes. Now he finally spoke.
“Claire, perhaps there's an explanation. Maybe you and Evan independently developed similar systems.”
I turned toward him.
“Independently?”
“Technology evolves. People have similar ideas.”
“Similar ideas don't produce identical internal test names, matching development comments, and a private branch linked to my username.”
Dad's face reddened.
“I am trying to keep this family together.”
“No,” I said quietly. “You're trying to keep it looking together.”
His eyes flashed.
“You have always resented Evan.”
I almost answered with every memory I had collected since childhood. The science fair where he received praise for a project I helped him build. The scholarship interview where Dad told me to avoid mentioning my independent research because it might embarrass Evan. The family dinner where Evan announced that he had invented a business idea I had explained to him months earlier.
Instead, I closed the folder.
“This is not about who you like more. It's about who owns the work.”
Daniel asked everyone to remain while his legal team contacted independent technical specialists. No one was permitted to access the repository until a forensic copy could be preserved.
Marcus looked exhausted.
As the others discussed procedure, he leaned toward me.
“Can I speak with you privately?”
“Through the attorneys,” I replied.
He nodded, but his eyes filled with something that looked like shame.
“I should have said something earlier.”
“What did you know?”
He glanced toward the door.
“Not everything. But enough to be worried.”
Before he could continue, Evan stood and announced that the company needed to address the guests. He insisted that the issue was a misunderstanding and that the launch would proceed as planned.
Daniel refused to endorse that statement.
“I won't make public claims before the evidence is reviewed,” he said. “Neither should you.”
Evan walked out without another word.
My mother followed him.
Dad remained, staring at the closed door.
“You've destroyed his future,” he told me.
I looked at the man who had taught me to keep my head down, never argue in public, and protect the family name at any cost.
“If his future depends on people believing he created something he didn't create, then I didn't destroy it.”
I had barely finished speaking when my phone vibrated.
It was a message from my attorney.
Do not sign anything. Do not discuss settlement without us. We found an additional file in the archive you sent. Call immediately.
A second message arrived.
Claire, the file contains evidence that your original source materials were accessed through a device registered to your family.
My hands went numb.
A device registered to my family.
I looked through the glass wall toward the ballroom, where my father stood beside the champagne table and my brother was speaking urgently to a group of executives.
For years, I had assumed that my work had been stolen by strangers.
Now I had to consider a possibility far more painful.
May you like
Someone close to me might have opened the door.
And the person who had done it might have been the one who had spent eighteen months calling me a failure.
