Technical Debt & Organizational Memory
Credential Echo
The dangerous afterlife of copy-pasted specifications in high-stakes engineering.
“It says ‘pool-side locker integration’ in paragraph four, Claire.”
“Change ‘pool-side’ to ‘concourse’ and keep moving. The bid is due in four hours.”
“But the stadium doesn’t have lockers. It has turnstiles and VIP suites. And the chip frequency listed here is 125 kHz. Didn’t the hardware lead say the new readers are all 13.56 MHz?”
“The hardware lead isn’t the one signing off on the technical compliance matrix. That paragraph won us the Aquatic Center contract and the regional gym tender. If it was compliant then, it’s compliant now. Just hit save.”
It is on a Wednesday in an integrator’s office in Lyon. Claire Fontaine is not a lazy person; she is a tired person. She is a person who understands that in the world of high-stakes government and private tenders, a “proven” technical specification is a shield. If the system fails, but you used the same language that was accepted on a previous successful project, you have a paper trail of competence. If you change the chip type or the material specification to be more “accurate” and something goes wrong, you are the person who deviated from the standard.
Inherited DNA
So, Claire copies Section 4.3, ‘Credential Specification,’ from a folder titled ‘TENDER_TEMPLATES_FINAL_v7.’ She deletes a few mentions of swimming pools, leaves the rest of the jargon intact, and feels a
