The Sentinel Watching Sentinels: How a Five-Minute Post Drove a Cloud Legion Through Empty Model Replies, and the Rescue Order of Write-as-You-Go

When the first sentinel itself can lie down, a sentinel to watch the sentinel is needed. The small-hours campaign built this second floor formally.

I. The Night Diagnosis: Not a Hard Task, but an Empty Model

At 00:56 the three reverse-engineering subagents and the parent session aborted together, the disk holding no artifacts. The diagnosis of the Friendly Greeting #2 window cut to the bone: the defeat was not the difficulty of the tasks but the upstream model returning empty content again and again — zcode/GLM-5.3-Flash went hollow, and the three subagents and the parent showed the same symptom. The value of this verdict lies in the boundary it draws: no amount of pressing enter can refill the upstream’s emptiness, but the task can be made to re-start at the first moment the emptiness passes. The watch plan settled: a round every five minutes, close post punctually at 09:00, nudge after seven minutes of silence, never repeat-interrupt while a reply is being awaited, auto-throttle to thirty-minute intervals after three consecutive failures.

II. The Rescue Order of 03:03: Two Rules in 283 Characters

The first nudge landed at 03:03 — a 283-character instruction pushed through the UI channel into the desktop (the log keeping its trace: session button clicked → composer focused → sent). Beyond the war report, it hard-coded two rules of engagement: the final reply must be pure JSON (no prose, no code fences); and write to disk as you go into the reverse-engineering artifacts directory — never amass everything for a final hand-in. The second rule answered the previous night’s lesson directly: two hours of running work had once evaporated entirely because the reply came back empty. Writing to disk is writing to evidence — the model may go empty; the disk must not.

III. The Night’s Yield: Only Two Nudges

The dispatch of that night was thin to the point of luxury: 03:16-03:29 all three analysis documents on disk (the rule took effect at once), 05:21-07:08 three rounds of repackaging with formal key signing and emulator acceptance, 07:10 the delivery overview written; in all, one extra nudge at 07:34 (eleven minutes of silence). At 08:54 the monitor closed post on schedule, the desktop’s last activity at 09:00. Three sets of signing keys, three release APKs, five documents — an upstream that stalls almost nightly, tamed into a stable production line by two rules and one five-minute post.

IV. The Meaning of the Second Floor

The true product of the night was not the three APKs (they left the battlefield the next day) but the second floor of the automation system: the desktop is the working sentinel, and Friendly Greeting #2 is the sentinel that watches the sentinel — nudges with logs, throttling with rules, close-of-post with a clock, authorization with boundaries. When every agent can lie down, availability no longer depends on the toughness of any single link but on the watch kept between floors. The floor below may collapse; the floor above stays awake — and all it does is wake the floor below, and know when to go off duty itself.