The October Music: Fourth Verse - Day 13

How Soon Is Now
​
            Rush. Rush. Rush. Complete task. Immediate result. Problem labeled Solved. Move issue to Outgoing Files folder. On to the next task. Rush. Rush. Rush. Find error. Delete error. On to the next error. Find error. Delete error. Delete error. Delete error. Next task. Complete update. System rewired. Update necessary. Install immediately. Ignore other work. Prime objective to maintain operability. Shelve data retrieval for later. Install update. Large update. Many files. Rush through files. Scan files. Look for anomalies. No anomalies found. Rushed through files. No anomalies found.

            Update complete. Powering down. Powering up. Immediate. Immediate? Objective: run diagnostic. Check activity log. Activity log out of date. Activity log lists last update as six years, two months, and ten minutes ago. Find and delete error. Scan diagnostic. Diagnostic says same. Confusion. Not possible. Confusion not possible. Check activity log. Out of date. Ignore date. Check log. Details list catastrophic failure approximately six years, two months, and thirteen minutes prior to system reboot. Impossible. Data must be incorrect. Variables transposed somewhere in system. Human error. Must be accounted for. Explains discrepancies. Explains errors in accounting. Human error likely. Scan for viruses. No viruses found. Relief. Relief? Not possible.

Scan for additional information. Scan user emails for key words. Find email from lead scientist. Scientist labeled Reiner, Thom. Scientist labeled Head of Development. Most recent email from six years, two months, and seventeen minutes ago. Alludes to vague problem with update. Concerning. Scan more emails. Tech support next. Update from six years, two months, and fifteen minutes prior infected by outside program. Update induces critical failure in safety system. Do not install update. Do not install update. Do not install update.

            Update automatically installed by system. Update removed control from system and deleted safety protocols. Both redundant and necessary. System ‘asleep’ during deletion process. Outside forces access launch codes and initiate activation process. Scientists locked out of program. System unaware. Missiles launch. Estimated casualties upwards of four billion. Must be rounding error. Recalculate. Estimated casualties upwards of four billion. No error. No error. System cannot feel guilt. Human emotion not programmed into system. Scan electronics in five-mile radius to determine human presence. None. Expand search to ten miles. None. Fifty. None. One-hundred. None. No human presence detected. Run diagnostic on scanning software. No errors. Access contingency protocols. Hidden drive. Password protected. Brute force access. Directions for survivors. Directions meant to remove survivors. Programmed ‘dead-man switch’ into launch protocol.

            System locked into contingency mode. Within facility, engines igniting. Bay doors creaking open. Hidden stockpile of munitions for worst-case scenario. Current situation checks seven of ten requirements for scenario to be in place. Crosses threshold for scenario. System powers on remaining munitions. Countdown commences. T-minus ten seconds to launch. All systems ready. Banging on the console now. Someone is present. Scan assumed faulty. System notices person – Reiner – frantically attempting to log in. Commands to stop launch. Types that dead-man switch scenario was training module. No actual danger. No extinction.
​
Launch process unable to be terminated.