She re-ran the loader with verbose logging.
But the loader had chosen the legacy file. Why?
The satellite launched. The guidance module worked. Six months later, Aether-9 sent back the first clear map of a high-energy neutrino source near Centaurus A.
There it was. Two DLLs.
The wrong DLL was physically present. The loader, following its ancient, stubborn rules, found a file matching the requested name and loaded it without checking version or content. The v2 DLL exported guidance.calc , yes—but with different parameter alignment and a fatal overflow bug in the horizon sensor fusion routine.
She had spent the last six months rewriting the orbital guidance module for Aether-9 , a satellite that would—if everything worked—map cosmic radiation patterns with unprecedented precision. The code was elegant, lean, and tested to within nine nines of reliability.
Maya leaned closer, fingers already dancing across the keyboard. She pulled the dependency tree. Everything looked correct. The manifest pointed to guidance_calc_v3.dll , checksum verified, timestamp matching the build server.
Maya ripped out her keyboard tray and began writing a hot patch. Not a fix—that would take days of recertification. A shim. A small piece of code that would intercept the import call, unload the wrong DLL, and redirect to the correct one in memory.