Chapter 38 - THE RECORD JUNE COULD NOT CORRECT HERSELFJune received an independent guardian ad litem because her parents’ claims included injury to her own privacy and legal record.
The appointed attorney was Mara Chen, no relation to Mara DeLeon.
Her first meeting occurred at Evelyn’s home.
June was four months old.
She slept through most of it.
Mara Chen did not call the sleeping child symbolic.
She examined the live chart, hidden flag, newborn screening records, access logs, and data-retention policies.
“Evelyn and Sophie can seek damages for what happened to them,” she explained. “My role is to ask what remedy protects June when she becomes old enough to decide.”
Evelyn looked toward the bassinet.
“Delete everything.”
“Would that remove accurate birth records too?”
“No.”
“Who decides which history she may want later?”
Evelyn stopped.
The family had learned that destruction could protect privacy and also remove choice.
Lucas had ordered some letters destroyed.
Noah had kept others.
June could not decide yet.
Mara proposed a sealed personal-data trust.
The false score, access history, and legal corrections would remain available to June at adulthood. Hospitals would see only the corrected chart. Researchers would receive nothing without later consent.
Sophie disliked the word trust.
“Trusts created half this family’s harm.”
“A trust is a legal structure,” Mara answered. “The question is who controls it and for what purpose.”
“No family elder?”
“No company.”
“No automatic disclosure at eighteen?”
“June receives notice and chooses whether to open it.”
“What if she never does?”
“Then the sealed material remains private or is destroyed according to instructions established now and reviewed later.”
The plan treated June as a future decision-maker rather than only a current victim.
Continuity Metrics opposed it.
The company argued that individual data removal from model infrastructure could undermine safety validation.
Mara Chen replied:
“June is not obligated to improve a product that injured her family.”
Judge Romero approved the personal-data trust temporarily.
Then Caleb Shaw found something worse.
Family Futures Foundation’s maintenance key did not merely update software.
It transmitted new hospital outcomes back into the model.
Every newborn review became additional training data.
June’s case had already entered the system:
Flag issued.
Security notified.
Social worker refused.
Legal intervention initiated.
Discharge delayed.
Complaint filed.
The model interpreted the outcome as confirmed custody conflict.
Evelyn’s successful challenge strengthened the algorithm’s belief that her family was unstable.
Resistance became proof.
“Can the record be removed?” Mara DeLeon asked.
“Yes.”
“Have you done it?”
“I do not have authority.”
Caleb agreed to preserve instructions and wait for court approval rather than altering production evidence himself.
Aaron Bell accused him of threatening public safety.
Caleb was suspended.
The court protected him from immediate termination but could not force Continuity Metrics to continue trusting him with sensitive systems.
Whistleblower protection did not automatically preserve every job function.
He remained paid outside technical access.
The feedback system operated in eighty-three hospitals.
Families were never told their outcomes trained the model.
Hospital contracts described service improvement.
Patient consent forms used broad language allowing quality analysis.
No form mentioned a commercial family-risk product.
First Record’s original categories remained the foundation layer.
The model had learned for twenty-three years.
Removing only the old data would not remove patterns reinforced through new cases.
Judge Romero appointed a technical special master.
The master proposed three options.
Retire the product entirely.
Rebuild from lawfully consented data.
Continue under strict review while removing punitive functions.
Hospitals argued immediate retirement would create operational gaps.
Family advocates argued the gap was safer than hidden separation.
Lena offered a fourth option.
“Use human identity verification when documents conflict. Do not calculate whether a family history makes current parents suspicious.”
The hospital had performed those tasks before buying the software.
It would require more staff.
Automation had not created the duty.
It had reduced the cost by transferring risk to families.
The court suspended every function capable of recommending separation, security restraint, or protective-service referral without current evidence.
The identity-matching component could continue under review.
Family Futures Foundation appealed.
While the appeal remained pending, a hospital in Indiana separated a newborn from adoptive parents based on an offline copy of the old model.
The software had not received the suspension update.
The child returned after six hours.
The parents contacted Mara DeLeon.
The offline installation had no known connection to Aaron Bell’s nonprofit.
Its license belonged to a company called Second Record Systems.
Amelia Cross searched First Record’s files.
No contract used that name.
No board had approved it.
Yet Second Record possessed the same categories, model weights, and maintenance certificate.
May you like
Someone had created a duplicate before the lawsuit began.
👉 Even if the court dismantled Family Futures, an unknown company already possessed another living copy of the system.
