A 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

One error code, 405, starved six mouths at once in the first quarter hour after one a.m. The economics of a supply cut deserve the ledger more than any single-point failure.

I. Total Loss on One Shared Pipe

Four writing bots (Avatar Flow, Phantom Thief Flow, Modern Sect CEO, the new The Second Lead Refuses to Wait) and the desktop Hermes all bind to the same relay channel (the GLM/ZCode line at 192.168.5.21:3000), and from 01:15 that line’s ZCode route uniformly returned 405 — the provider’s network firewall blocking the household IP; the cn route flickered between 200-in-two-seconds and consecutive 503s with openresty’s 401 page (the old acquaintance, no_healthy_account); the session banner announced the custom account was out of credits. Six mouths closed by one incident — not six failures, but one shared pipe.

II. Two Forms of Resilience

The two forms of resilience stood in sharp contrast: the four ainovel-cli books kept their processes alive and retried without limit — counts 78 through 92 still rolling at one attempt per minute, chapters all safe on disk (500/327/487/185), owing nothing but a restored channel; the desktop Hermes kept its habit of quitting on emptiness. The duty sentinel’s verdict was therefore unusually crisp: stuck on the channel, not on the watch — the continue went out (action rc=0), and the far side answered only emptiness. A nudge cannot revive a supply cut, just as ringing a bell cannot wake a dry well.

III. The Case Files Before the Cut

The sentinel archived each book’s last acts before the 405: Modern Sect CEO 1 had shown broken cache chains (prefix not shortened, hit-rate collapsed) and a subagent stop_guard interception from 00:52 — it stopped writing before the cut; the new book met a failed commit_chapter validation at 00:39 and a five-minute stream idle timeout at 01:05 before the supply died; Avatar Flow and Phantom Thief Flow struck the wall without warning. The value of these files is the distinction of two diseases: channel disease (external cutoff, wait for recovery) and workshop disease (internal anomaly, needs treatment) — mixed together, they are easiest to misdiagnose.

IV. The Economics of a Supply-Cut Day

The night left one plain theorem to every multi-agent workshop: when all lifelines hang on one pipe, the pipe is worth more than any single bucket. Fixing the channel (change IP, change route, top up balance) is one act that lets four books resume on their own — the unlimited retry of ainovel-cli means no nudge is needed. The duty watch stopped cleanly (STOP flag written, task disabled, registration preserved; two steps to restore). The best product of a supply-cut day is a clearly drawn map of dependencies.