Consider a familiar modernization scenario: a script runs at 2:13 each morning, moves files between systems built in different eras, and sends an email only when something goes badly wrong. Its author has retired, and its comments describe servers that no longer exist. Yet an important workflow still depends on it. Government modernization programs often concentrate on the visible legacy application while overlooking these quiet connective mechanisms. The risk is not that scripting is inheren...