Chapter 3 - THE CODE THAT REMEMBERED
Evan had always believed that confidence could substitute for proof.
It had worked at school, where teachers praised his presentations while I quietly corrected the numbers in his spreadsheets. It had worked at family dinners, where he repeated my ideas with enough enthusiasm that everyone assumed they were his. It had worked in business meetings, where polished language often mattered more than the hours spent making an idea real.
But a live demonstration was different.
Code remembered what people forgot.
“It's a standard synthetic fraud scenario,” Evan said finally. “Our engineers created it during testing.”
Dr. Ellis folded her arms.
“Then your engineers should be able to provide the original test specification, the first commit, and the documentation showing how the scenario was developed.”
“Certainly.”
“Excellent. Please have those records delivered to our team tonight.”
Evan smiled, but the corners of his mouth trembled.
“I'm sure that can be arranged.”
I knew it couldn't—not honestly.
My original test specification contained a strange little detail. I had named one fictional vendor Northstar Paper Company, although the vendor's transactions represented a digital payment processor. The name was an inside joke about an old children's book my grandmother used to read to me.
It was not a sensible label for professional testing.
It was simply mine.
On the screen, the simulation ended. The results were impressive, and for a moment the audience applauded again. Evan seized the opportunity to thank his engineering team and speak about innovation, resilience, and the future of responsible finance.
He was good at this. I would never deny that.
My brother could make a room believe in him.
The tragedy was that he had started believing his own performance.
When he left the stage, he came directly toward me.
“You're enjoying this,” he whispered.
“No.”
“Don't pretend. You've been waiting for an opportunity to embarrass me.”
“Evan, I came because Mom asked me to.”
“And you brought a lawyer's folder.”
“My attorney told me to bring it.”
He stared at me.
“Why would you need an attorney if you had nothing to hide?”
“That's an interesting question coming from someone who just demonstrated my work in front of four hundred people.”
His face reddened.
“You can't prove I stole anything.”
“Then prove you didn't.”
He leaned closer.
“You always did this. You found one tiny thing and acted like it made you better than everyone else.”
“No. I found tiny things because tiny things are where people hide big lies.”
He looked as if he might shout, but the presence of guests restrained him.
Then he said the words I had dreaded hearing for years.
“Dad was right about you. You don't want a career. You want to punish us.”
I felt something inside me go still.
For a long time, I had believed that if I could just explain myself clearly enough, my family would eventually understand. If I showed them the evidence, they would recognize the truth. If I worked hard enough, they would stop treating my success as a threat to Evan's.
That hope had cost me more than I wanted to admit.
“I'm not trying to punish you,” I said. “I'm trying to protect work I created.”
“From your own brother?”
“Especially from my own brother, if he's the one using it without permission.”
He stepped back, and for the first time I saw something behind his anger.
Fear.
It vanished quickly, replaced by the familiar smirk.
“You're going to regret this.”
Before I could answer, Daniel approached with Naomi and two members of his investment team.
“Evan, we need the technical founders and whoever manages your source repository to join us in the conference room.”
“This is a launch party.”
“And this is an investment decision worth forty million dollars.”
Daniel's tone remained measured.
“We will not proceed without understanding the ownership of the underlying technology.”
Dad hurried over.
“Daniel, surely you don't intend to derail an entire company because of a disagreement between siblings.”
Daniel turned toward him.
“Mr. Bennett, if your son is correct, the review will clear him. If Claire is correct, the review may prevent a serious legal problem. Either outcome requires evidence.”
Dad fell silent.
Naomi looked at me. “Would you mind telling us when you first created your system?”
“Twenty-two months ago. I was working as an independent consultant.”
“And did you share it with Veyra?”
“No. I did not work for Veyra, license the system to Veyra, or sign any agreement transferring ownership.”
“Did you ever send your brother technical materials?”
“I sent him a short business article about financial risk modeling. Nothing containing my code or proprietary architecture.”
Evan interrupted. “She had access to my early business plans!”
I looked at him.
“Your first business plan was a six-page document about applying artificial intelligence to small-business lending. It contained no source code, no technical architecture, and no working model.”
He went quiet.
I had read that plan because he had asked me to review it. I had offered suggestions about his market analysis and told him to avoid promising customers that a predictive system could eliminate financial risk entirely.
He had ignored that advice.
Now, months later, Veyra was advertising the very engine I had built independently.
Naomi took notes.
“Was anyone else present when you discussed your work with your family?”
“No. I deliberately kept my prototype private. After what happened at Halcyon, I was careful about access.”
“That's helpful.”
Evan laughed bitterly.
“So she gets to accuse me, and everyone just believes her?”
“No one is asking us to believe anyone,” Daniel said. “We're asking for records.”
The conference room door opened.
A tall man with a worried expression stepped inside. He was introduced as Marcus Lee, Veyra's chief technology officer.
Evan looked relieved.
“Marcus can explain everything. He built the engine with our engineering team.”
Marcus glanced at me.
His expression changed so slightly that someone unfamiliar with him might have missed it.
I didn't.
He recognized me.
And he looked terrified.
“Marcus,” Naomi said, “when did development of the core engine begin?”
He cleared his throat.
“About eighteen months ago.”
“Do you have the original repository history?”
“Yes.”
“Can you produce it?”
He hesitated.
Evan gave him a sharp look.
“Of course he can.”
Marcus swallowed.
“I can produce what we have.”
It was the first honest-sounding sentence anyone from Veyra had spoken that night.
Daniel closed the conference room door.
“Then let's begin.”
As Marcus opened his laptop, I noticed the name of the repository displayed on the screen.
Veyra-Core-Engine.
Underneath it was a creation date.
Six months after my original system had been registered.
But the next line showed the first imported development branch.
Its timestamp was older.
Much older.
I leaned forward.
The branch had been created under a username I recognized immediately.
Not Evan's.
Not Marcus's.
May you like
Mine.
And I had never given Veyra permission to access my repository.
