Chapter 3 - THE BUDGET EXPLANATION
James Morrow arrived in Richard’s office the next morning carrying three binders and the confidence of someone who expected numbers to make the problem boring. He did not deny that the wrong translation saved money. He argued that the savings were incidental because the residency requirement had been interpreted conservatively for years.
According to James, Meridian’s education fund had been repeatedly abused by employees applying for dependents who were not truly relocating with them. Compliance tightened documentation after an internal audit found inconsistent residency claims. Version 6.2, he said, reflected that stricter interpretation even if the Spanish source had not been updated cleanly.
Richard asked why the source document later moved to Version 8.1 and restored conditional language.
James said legal changed its view.
“Then why didn’t the translation change?”
“Process failure.”
“Why was Emily’s account used at two in the morning?”
“Probably credential sharing. People did that constantly before the new authentication system.”
Emily stiffened. “I never shared my password.”
James looked at her sympathetically. “People forget.”
The explanation was plausible enough to slow the investigation. Large corporations accumulated bad processes, inherited passwords, and undocumented workarounds. Saving money did not prove intent. A sloppy translation, conservative interpretation, and weak controls could produce the same result without a conspiracy.
Richard almost accepted that framing until Sofia asked for the earlier versions.
She sat beside Emily with three source documents and three English translations arranged in chronological order. Version 5.4 contained correct conditional language. Version 6.2 changed one term to mandatory. Version 7.0 kept the error. Version 8.1 corrected the source wording even more clearly, but the English system continued using 6.2.
Sofia pointed to the pattern. “If this was an old mistake, why was the earlier translation right?”
Nobody answered.
The error had not always existed.
Someone introduced it.
Emily then found the change request that created Version 6.2. The translator’s original delivery still used conditional wording. A Meridian reviewer manually replaced it with mandatory during internal editing.
Reviewer account:
J. MORROW.
James looked at the screen and said he reviewed hundreds of documents. He might have made the change based on legal guidance.
“Show us the guidance,” Richard said.
James could not.
The first explanation began collapsing.
Still, he had another defense. He produced an email from Meridian’s former deputy general counsel, Karen Lee, asking compliance to “tighten residency-document expectations due to fraud concerns.” The phrase could support his interpretation.
Then Emily opened the full email thread.
The next sentence read:
Do not create new eligibility conditions without counsel review.
James had quoted the part that helped him and omitted the limitation.
Richard’s patience began disappearing.
The chapter-ending contradiction arrived from Sofia again, not because she understood corporate politics better than adults, but because she kept reading the actual text. In Version 6.2, the mistranslated clause used a phrasing style different from the rest of Brightline’s translation.
“Whoever changed this,” she said, “wasn’t the translator.”
Brightline confirmed the same thing through linguistic review. The problematic sentence had been rewritten inside Meridian after vendor delivery.
May you like
The mistake was internal.
And deliberate enough that someone overrode a correct translation to create it.
