Tag: failure archaeology

The Archaeology of Three Broken Links and One Temporary Wire: A Zombie Port, a One-Letter Defeat, the Iron Law of Loopback Trust, and a Watchdog That Heals in Thirty-Five Seconds

Three broken links in one day, each with a different root cause, compose a complete archaeology of failure. First layer: a desktop app refused to open at midnight — not a crash but a zombie process holding the port; clearing the field healed it. Second layer: an API configuration lost three times in a row — an uppercase letter in the path version, a base URL filled past the version segment producing a double-concatenated 404, and the wrong key — until code-level digging exposed the hard rule: keys may travel only over encrypted channels or the local loopback, and plaintext intranet hosts are trusted by no one. Third layer: by afternoon the bot answered nobody, probes on the port returned only empty codes — and the trail led to the fact that the configuration pointed not at a server but at a temporary tunnel wire raised last night, which the system had already reaped. The fix was institution rather than restart: a resident tunnel plus a scheduled-task watchdog, proven by killing the process and watching the port re-hang under a new process thirty-five seconds later. Failure will recur, but once the institution stands, recurrence is a line in the watchdog log.