Chapter 13 - THE ENGINEER WHO APPROVED TRANSPARENCY
Amara testified to the independent committee before speaking publicly.
She had believed TideSure’s earliest simulations were isolated system tests. Then she noticed the same events appearing in investor reports.
When she objected, Saye told her every response network used synthetic traffic.
“The difference,” she said, “was that other networks labeled it.”
TideSure removed the labels after the tests succeeded.
Amara preserved raw logs outside company servers. That violated policy.
It also prevented their destruction.
Her conduct would be examined separately from what the records proved.
The investigation then returned to Nereid.
TideSure could reconstruct identities because our open incident database published exact event times, device-generation codes, failure categories, and hashed identifiers.
We believed transparency required enough detail for outsiders to audit us.
Priya had designed the export.
I had approved it.
Encryption protected names only while no one possessed another dataset capable of matching time, device, and location.
Pelagos possessed one.
Harborline possessed another.
We had published the final piece.
“No one hacked Nereid,” Priya told the board. “We released data that could be re-identified.”
A director asked whether she would resign.
“If the board determines that serves safety.”
“Do you believe it does?”
Priya looked toward Lucy, Claire, and the affected families seated behind the committee.
“I believe my desire to prove we had nothing to hide made me careless about what belonged to other people.”
Transparency had become another form of authority.
We decided what the public needed.
The people inside the records carried the risk.
Priya’s resignation was not accepted immediately. The independent board suspended her from data-governance decisions while retaining her engineering responsibilities during the emergency migration.
She did not demand that years of honest work erase one serious failure.
Nereid notified every person whose event might have been re-identified.
Some notices reached families who had spent years trying not to revisit the worst day of their lives.
One woman called me personally.
“My husband survived,” she said. “We did not agree to become safety research forever.”
She was right.
Nereid funded independent counseling, legal advice, and data review. Accepting any service did not require releasing claims.
We also faced the engineering problem.
More than eighty thousand legacy beacons remained active worldwide.
Changing every key immediately could cause older devices to become unverified.
Leaving them unchanged allowed further cloning.
Some board members proposed blacklisting duplicated identifiers.
Rafael attended the meeting with two stiff fingers resting on the table.
“My signal was called a duplicate.”
The proposal ended there.
The new protocol would never suppress raw location because identity appeared suspicious.
Coordinates first.
Rescue first.
Authentication afterward.
Medical information would transmit only if the user had chosen it and the device could verify possession locally.
The redesign required governments, fleets, and competitors to cooperate.
TideSure still controlled infrastructure in remote regions.
Saye threatened to disable it unless Nereid released him from civil claims.
Mara refused.
“No company gets immunity in exchange for not switching off rescue.”
A court placed TideSure’s response network under temporary public supervision.
Hours later, an unknown administrator attempted to erase the offshore platform.
Amara’s preserved logs identified the command.
It came from Saye’s private yacht.
May you like
Coast Guard officers found him twenty miles offshore with three encrypted drives and a satellite terminal.
The man who sold faster rescue had chosen the ocean as his route away.
