PART 10 – The Anonymous Claim Against Emiliano’s Software Pointed Toward Karla Until One Technical Detail Led Somewhere None of Us Expected

The licensing company froze the next scheduled payment.

Not the entire agreement.

Not yet.

But enough to matter.

Their legal department explained that an intellectual-property complaint had alleged that substantial portions of Emiliano's software architecture originated from another developer's unpublished work.

Emiliano read the notice without blinking.

Then he said, “Architecture is vague.”

Mr. Méndez looked at him.

“That's your first reaction?”

“Yes.”

“Not anger?”

“I am angry.”

“You don't look angry.”

“That is not required.”

He enlarged the complaint summary.

“They don't identify code.”

“No.”

“They don't identify modules.”

“No.”

“They don't identify the claimant.”

“Correct.”

“Then they have nothing.”

“Perhaps.”

Emiliano looked up.

“Perhaps?”

“Companies investigate claims because ignoring one can create liability.”

He hated that answer.

“So someone can lie and stop payments.”

“Temporarily.”

“That is stupid.”

“Sometimes caution looks stupid until the lawsuit arrives.”

The company eventually provided the supporting material under confidentiality restrictions.

Emiliano, Mr. Méndez, a software attorney, and an independent engineer reviewed it.

I understood perhaps one sentence in twenty.

But I understood faces.

At first Emiliano was dismissive.

Then he became quiet.

Then very quiet.

“What?” I asked.

He pointed to a diagram.

“This is old.”

“How old?”

“Four years.”

The engineer looked at him.

“You recognize it?”

“Yes.”

“From where?”

“My first architecture.”

“Was it public?”

“No.”

That was the problem.

The complaint contained design concepts from versions Emiliano had never released.

Someone had obtained old development material.

Mr. Méndez asked the obvious question.

“Who had access?”

“Me.”

“Only you?”

“Grandma's computer.”

I stared at him.

“My computer?”

“Before I had my own.”

I remembered.

He had spent hundreds of hours on the battered laptop I used for invoices and recipes.

“Anyone else?”

He thought.

“School.”

“What exactly?”

“I emailed early files to myself from the computer lab.”

The investigation widened.

Old accounts.

Cloud backups.

School servers.

USB drives.

The trail was messy because nobody had expected a sixteen-year-old's childhood project to become worth millions.

Karla denied filing the complaint.

Mr. Méndez asked through Salazar.

Her response was immediate.

No.

Emiliano did not believe her.

“Ask Daniela.”

Daniela knew nothing.

“Ask Gabriel.”

Gabriel had never seen the software until recent news reports.

“Then Karla.”

“We already asked.”

“She lies.”

“Yes.”

“So asking is useless.”

Mr. Méndez looked tired.

“That is occasionally a problem in legal practice.”

The independent engineer found the first real clue.

The complaint included a screenshot.

Tiny.

Almost irrelevant.

In one corner was a username.

Not Emiliano's.

The account belonged to a former teaching assistant named Mateo Rivas.

Emiliano recognized the name.

“He helped in the computer lab.”

“When?”

“I was thirteen.”

“Did he work with you?”

“No.”

“Did he have access to your files?”

“Maybe.”

That maybe became important.

Mateo had left the school three years earlier.

He now worked for a small software consultancy.

Mr. Méndez's investigator located him.

Mateo initially denied everything.

Then the company disclosed that the anonymous complaint had been submitted through counsel representing an unnamed client.

That lawyer had previously represented Mateo's consultancy.

Coincidence was becoming less likely.

Emiliano wanted to confront him.

Mr. Méndez refused.

“Why?”

“Because you are sixteen.”

“That explanation is becoming repetitive.”

“It remains legally useful.”

The company's forensic review discovered that several documents attached to the complaint had metadata connecting them to Mateo's workstation.

The anonymous claimant was no longer very anonymous.

His lawyer changed position.

Mateo had not stolen anything, they said.

He had contributed.

Emiliano laughed when he heard that.

Not because it was funny.

Because it was ridiculous.

“He showed me how to reset a printer.”

Mr. Méndez blinked.

“That was his contribution?”

“Yes.”

“Anything else?”

“He told me my interface was ugly.”

“Was it?”

“Yes.”

“Could that be considered valuable feedback?”

“No.”

The case might have become absurd if not for the money involved.

Mateo claimed he had given Emiliano technical guidance that later formed the basis of the software.

He wanted compensation.

The licensing company demanded evidence.

Mateo produced emails.

Some were real.

He had occasionally answered technical questions from students.

One exchange with Emiliano existed.

Emiliano had asked about database synchronization.

Mateo had suggested a standard method.

The independent engineer called the suggestion generic.

Not proprietary.

Not foundational.

Then Mateo produced something more dangerous.

A file containing early code.

Timestamped before one of Emiliano's archived versions.

For the first time, the engineer stopped dismissing him.

Emiliano stared at the code.

“That is mine.”

“Can you prove it?”

“Yes.”

“How?”

“There is an error.”

The engineer leaned closer.

“What error?”

“I wrote that function incorrectly.”

“That doesn't prove ownership.”

“I fixed it three days later.”

He opened his archives.

There it was.

Same error.

Same structure.

Then corrected.

The engineer compared the files.

Mateo's supposedly earlier version contained the exact mistake from Emiliano's later draft.

That meant the timestamp had likely been manipulated.

More forensic work confirmed it.

The creation date had been altered.

Mateo's claim began collapsing.

But one question remained.

Why now?

How had he learned the contract's value?

The number had appeared publicly, but only after negotiations were complete.

Why risk fraud over software he had ignored for years?

The answer came from a bank record obtained during settlement discussions.

Mateo had received a payment shortly before filing the complaint.

Not from Karla.

From a company called Nexo Advisory.

Mr. Méndez searched corporate records.

Nexo Advisory had been formed six months earlier.

Its registered manager was a man named Arturo Vega.

Daniela recognized the name.

Karla did too.

But neither reaction matched what I expected.

Daniela said, “That's not Karla's person.”

“What does that mean?”

“He worked for the technology company.”

Emiliano looked up sharply.

The licensing company.

Mr. Méndez verified it.

Arturo Vega had been a contract consultant during the early negotiation period.

Suddenly the entire shape of the problem changed.

This might not be about Karla.

It might be about the company trying to weaken Emiliano's bargaining position.

Mr. Méndez warned us not to jump ahead.

“We have a payment. We have relationships. We don't yet have motive.”

Emiliano was furious.

“They froze money because of a complaint connected to their own consultant.”

“Yes.”

“Do they know?”

“They do now.”

The company responded within hours.

Arturo had not worked for them in months.

They denied authorizing any payment to Mateo.

They opened another internal investigation.

Then Arturo disappeared.

Not physically.

Professionally.

Phone disconnected.

Office emptied.

Emails unanswered.

The investigator traced him to another startup.

That startup had been developing a communication platform suspiciously similar to Emiliano's.

Now the motive emerged.

Arturo had seen portions of Emiliano's product during negotiations.

He apparently believed the concept could be reproduced cheaply.

Mateo provided old material to make the competing product look independently developed.

The anonymous complaint against Emiliano served two purposes.

Delay his licensing rollout.

And create doubt about who invented what.

Emiliano listened to the explanation.

Then asked one question.

“Did they copy my privacy design?”

The engineer looked surprised.

“That is what concerns you?”

“Yes.”

The competing platform collected substantially more user data.

Emiliano's did not.

“No.”

“Good.”

I stared at him.

“You could lose money.”

“I know.”

“And you're worried about privacy settings?”

“Yes.”

“Why?”

He looked at me as if the answer were obvious.

“Because people will use it.”

That was the moment I understood why his program had succeeded.

Not because he was brilliant.

Though he was.

Because he had built it from the perspective of someone expected to surrender control.

He hated that expectation.

In software.

In court.

In life.

The licensing company restored the frozen payment and formally rejected the complaint after the forensic evidence came in.

Mateo's lawyer began discussing settlement.

Arturo faced potential civil claims.

For several days, we breathed again.

Then Karla asked for an additional therapy session.

Emiliano agreed.

When he returned, he looked unsettled.

“What happened?”

“She knew about Mateo.”

I froze.

“How?”

“He contacted her.”

“When?”

“Before she came to our house.”

My stomach tightened.

“Why?”

“He offered information about my software.”

“For money?”

“Yes.”

“Did she pay him?”

“No.”

“Are you sure?”

“She showed the therapist and me the messages.”

Karla had refused Mateo's proposal.

That was good.

But she had done something else.

She had kept the messages.

She had never told us.

Never told the company.

Never told the court.

Emiliano confronted her.

“Why?”

Karla's answer was ugly but believable.

“At first I thought I might need him.”

“For what?”

“If the company was exaggerating what your software was worth, I wanted information.”

“So you kept someone who was trying to steal from me as an option.”

She cried.

“Yes.”

“Then when did you decide not to use him?”

“When he asked me to help claim you stole the program.”

“And you said no.”

“Yes.”

“Why?”

“Because I knew it wasn't true.”

Emiliano stared at her.

“You knew?”

“I had watched the videos from your school. I saw you building it.”

Another piece of her secret observation.

She had known more about him than she admitted.

Not enough to parent him.

Enough to know his work was his.

“Why didn't you tell anyone?”

“Because then I'd have to admit I had talked to him.”

The old pattern again.

Shame.

Concealment.

Damage.

More shame.

More concealment.

Emiliano left the session early.

At home, he opened Karla's evidence folder.

He created another folder beside it.

He named it:

Things She Told Before We Found Out.

I stood behind him.

There were only three files inside.

The residential placement.

The financial waiver.

Mateo's messages.

“What is this?”

“Difference.”

“Between what?”

“Confessing and being caught.”

I understood.

He was beginning to measure Karla not by apologies, but by whether she told difficult truths before circumstances forced them out.

The next week, the folder gained another file.

Karla voluntarily disclosed a bank account we had never known existed.

An account opened when Emiliano was a baby.

There was almost no money left in it.

But its original source was listed clearly.

Gabriel Serrano.

Child support.

Payments he had sent before Karla convinced him Emiliano was not his son.

And according to the statements, Karla had withdrawn nearly every dollar.


Click here to continue reading: PART 11: The Forgotten Child-Support Account Forced Karla to Explain What Happened to Money Gabriel Had Sent for a Son He Lost

Story Parts

Eleven Years After Leaving Her Son at My Door, My Daughter Returned With a Lawyer and a Very Different Story

Part 10 of 27

Previous: Part 9
Next: Part 11

Leave a Reply

Your email address will not be published. Required fields are marked *