“Dad.”
“Twelve.”
I stared at him.
“That leaves seventy-eight thousand.”
His face hardened.
“You don’t understand how these things work.”
I had started hearing that sentence often.
“I understand subtraction.”
“It would humiliate Harrison.”
“What would?”
“Having to scale it down.”
“So?”
Dad looked at me with genuine disbelief.
“You don’t do that to family.”
I should have said no.
Instead, I paid.
Harrison slapped me on the shoulder at the rehearsal dinner.
“Little bro comes through.”
No repayment plan.
No thank-you beyond that.
I told myself the wedding would be the final major expense.
Then Bianca’s car no longer fit her public image.
Then she wanted the dining room redone because “dark wood doesn’t photograph well.”
Then the kitchen appliances needed upgrading.
Then club memberships.
Luxury trips.
Designer furniture.
My mother began repeating Bianca’s language.
“Presentation matters.”
Dad developed a new version of his past.
He told people he had transitioned successfully from business ownership into private investing.
The house looked wealthier every year.
The people inside it became more financially fragile.
I was the hidden support structure.
And the more completely I supported them, the less visible I became.
That paradox took me years to understand.
If someone saves you once, you feel grateful.
If someone saves you every month, eventually you may stop thinking of it as saving.
It becomes infrastructure.
Nobody thanks the foundation under the floor.
They complain when it cracks.
At work, my life was entirely different.
Aegis grew to fifty employees.
Then ninety.
Then one hundred fifty.
We moved into three floors of a downtown tower overlooking the Mississippi.
Our customers included major banks, hospital networks, and multinational logistics companies.
I spoke at technical conferences under my full name.
Industry publications interviewed me.
Our board included former software founders, security executives, and institutional investors.
A later financing valued Aegis at approximately $940 million.
My stake, through direct holdings and a founder trust, remained substantial.
The funny part was that my family could have discovered everything in thirty seconds.
My name was on the company website.
Press releases existed.
Public conference videos existed.
None of them ever searched.
They already knew who I was.
Why look?
Harrison’s interest in cybersecurity began one year before the dinner.
He had just lost another sales position.
He came into my room one evening and sat on the edge of my bed.
“I need your help.”
That sentence meant more than it should have.
“With what?”
“I’m thinking of building something in cybersecurity.”
I stared.
“You?”
He laughed.
“Try not to sound so shocked.”
“No. I mean, why cybersecurity?”
“Look at the market.”
Of course.
Money.
He continued.
“I can sell. I know investors. I understand business. I just need enough technical knowledge not to sound stupid.”
I should have kept my worlds separate.
Instead, I was touched.
My big brother wanted to learn from me.
For three weekends, I taught him.
Basic network architecture.
Threat modeling.
Encryption concepts.
Security product economics.
What investors ask.
What enterprise customers care about.
He took notes.
Asked surprisingly good questions.
For a while, I enjoyed it.
Then he asked for a demo.
“Something investors can see.”
“Build one.”
“I don’t know how.”
“That’s the point.”
“Julian.”
He smiled.
“A proof of concept. Nothing commercial.”
I hesitated.
He added, “I’m finally trying to build something for myself.”
That got me.
The next week, I created a stripped-down demonstration build based on one of Aegis’s older Sentinel modules.
I did not simply hand him company property without documentation.
Aegis’s general counsel would have removed my head.
We generated an evaluation license.
Limited use.
No redistribution.
No commercialization.
No derivative sales.
Ownership remained with Aegis Dynamics.
Harrison signed electronically.
I sent him the demo.
“This is for investor demonstration only.”
“I understand.”
“If you want a real product, hire engineers and build one.”
“I will.”
“Do not incorporate this code into anything you sell.”
“I won’t.”
He looked me directly in the eye.
I believed him.
Harrison incorporated Ironclad Systems two months later.
He told the family his company would revolutionize cybersecurity.
Dad loved it.
Finally, one of his sons was a technology entrepreneur.
At dinner, Harrison explained cybersecurity to me using concepts I had taught him.
I let him.
At first, I assumed he had hired engineers and built something independent.
Then Aegis received an unusual inquiry.
Three weeks before the duck dinner, Silas walked into my office carrying a confidential technical due-diligence packet that had been shared with us under a formal verification request from a venture-capital firm.
He locked the door.
“You need to see this.”
The fund was evaluating Ironclad for a large Series A round.
Harrison had told my parents the company was about to be valued around ninety million dollars.
The prospective investor’s engineers had reviewed the repository.
They found architecture inside Ironclad that looked suspiciously familiar.
Not because programmers can magically identify ownership from a few lines.
Because the build contained a combination of internal structural conventions, test patterns, and cryptographic workflow choices that aligned closely with the Aegis demonstration package.
The investor contacted Aegis to ask whether we had licensed commercial rights.
We had not.
Silas opened the report to the technical comparison.
I felt cold.
“How much?”
“Enough.”
“Exact?”
“They need a full repository review to quantify it, but the core packet-filtering engine appears derived from the evaluation build.”
I leaned back.
“Who developed their commercial version?”
“Felix Moreno.”
I knew Felix.
Freelance developer.
Talented.
Inconsistent.
I had referred Harrison to him years earlier for a website project.
Silas continued.
“Victor Hale’s fund paused the round pending chain-of-title verification.”
“Does Harrison know?”