Chapter 3 - THE MISTAKE INSIDE THE ZIP
ATLAS_FINAL_PACKAGE.zip contained:
source code,
model documentation,
performance benchmarks,
system architecture,
a customer demo dataset,
and compliance notes.
The demo dataset was supposed to be synthetic.
Fake names.
Fake borrower IDs.
Fake addresses.
Fake balances.
But three days earlier, Ethan’s team had run a production-simulation test.
One engineer copied a real client sample into a staging folder.
The names were tokenized.
Addresses masked.
Account numbers truncated.
But several fields were not properly de-identified.
Business names remained.
Property parcel IDs remained.
Loan amounts remained exact.
One text-notes field still contained:
borrower names,
guarantor names,
and dispute comments.
The test file should have been deleted.
It was not.
Then a packaging script pulled the entire staging directory into ATLAS_FINAL_PACKAGE.zip.
Ethan had noticed the file that afternoon.
He told himself:
I’ll clean it after dinner.
He never did.
Claire sent the package before he returned to the office.
That fact changed the moral map.
Claire intentionally transmitted company materials to a competitor.
Ethan had negligently allowed sensitive client data into the package.
Two different wrongs.
One incident.
The staging file itself existed because ATLAS had produced inconsistent debt-service calculations on one unusual loan structure.
A borrower owned:
three warehouse properties,
one operating company,
and several cross-guarantees.
Synthetic data did not reproduce the problem.
An engineer asked Ethan for permission to use a small real sample.
Ethan approved it verbally.
The engineer copied forty records first.
Then expanded the sample after the bug persisted.
No one updated the temporary-data exception because there was no formal exception record.
The sample quietly became more than two thousand records.
That was not Claire’s fault.
May you like
It was a process failure Morgan Systems already had before she touched the laptop.
The incident simply exposed it.
