GARDEN
Tag: duty
2 posts ·
10-31A Forty-Kilometer-Long Firewall: How One 405 Starved Four Books and a Desktop Sentinel at Once, the Resilience of Ninety-Plus Retries, and the Economics of a Supply Cut
From 01:15 in the small hours of 10-31, a single 405 Method Not Allowed (the provider firewall blocking the household IP) choked four writing bots and the desktop Hermes at once: all four book processes alive, retrying at counts 78-92, producing nothing — the fastest one idle ninety minutes; the desktop, as ever, went hollow and quit. The duty sentinel judged precisely: stuck on the channel, not on the watch — the nudge goes out, the far side answers only emptiness. The pre-405 case files were archived book by book: broken cache chains, failed commit validation, stream idle timeouts. Fixing the channel outweighs fixing any single bot — four lifelines hang on one shared pipe.
Read more › 10-28The Watchdog of the Vacuum Window: A Two-Minute Silence Threshold, the Wrongful Conviction Caused by a Zero-Width Character, and a Countdown That Retires Itself
A UI-level watchdog was built for two unattended campaigns: it watches the modification times of session log files, and when silence exceeds two minutes it switches windows, clicks the task row, injects continue and presses enter; along the way it exonerated two wrongful convictions — an empty input box is actually a newline plus a zero-width character, so every success was being judged a failure; and one genuine failure where the write landed but the enter did not. Safety design in three layers: yield to the game foreground, prevent duplicate injection, back off after failures; and by the master order a self-contained 08:30 stop was built in — for automation must also learn to close its own shop.
Read more › ← Digital Garden