Automation & AI agentsThe Walker — eyes and hands on the server
The Walker — eyes and hands on the server
A service that walks the whole fleet every fifteen minutes and brings back up whatever has fallen. It writes only when something is down; on quiet days it says nothing.
How it's wired
Drawn from the live workflow — every node and every arrow is really there. The labels are translated from the originals.
What it is
Monitoring usually only reports. That is half the job: between a failure and a human there is sleep, a commute, a meeting — and a service is down for two hours because nobody was there to press the button, not because the button was hard to press. The walker does the other half: it does not just see what fell, it brings it back up.
Every fifteen minutes it walks the whole fleet: pages, consoles, containers, services, disk space, automations. It writes only when something is down, and that rule matters more than the walk itself: a watchman who reports every fifteen minutes that all is well is a watchman nobody reads by Thursday, and his real message will sink with the rest.
Specifications: Python, systemd as the watchdog over the service itself, Docker and n8n on the watched side. Running since 27 Aug 2026. Verified by deliberate breakages: every target was knocked over to see whether it would come back up on its own — because a watchman who has never been broken is a watchman nobody knows anything about.
Nearby work
Zero — an offline voice assistantA voice assistant that wakes on its name and thinks on the laptop’s graphics card: no internet, no login, an answer in 0.3–0.6 seconds.My own automation serverMy own server carrying over a hundred automations around the clock: bots, digests, finance, reminders, nightly backups, app synchronisation.Quality Watchdog — a guard that reads the automations themselvesA watchdog that reads how the automations are built rather than the run log, and catches what breaks silently.