Automation & AI agentsSystem Map — what is installed where and how it starts
System Map — what is installed where and how it starts
One picture of the whole machine: every project on disk, every scheduled task, every service and every workflow on the server — and, more usefully, everything that no longer matches its own records.
What it is
When projects exceed a dozen, memory stops working: where things are, what runs by itself, and what you forgot to turn off half a year ago. The usual response is to keep a manual list, and it becomes outdated on the same day.
This map is not maintained manually: it scans the machine and server to build a single picture — every project on disk, every scheduled task, every service, every workflow. Its value is not in the list, but in discrepancies: it shows what no longer matches its own records — a task calls for a file that doesn't exist; a service is listed as running, but isn't.
Specs: Python, reading the Windows Task Scheduler and n8n API, custom repository, desktop shortcut. Limitations are stated plainly: the map won't see a project without standard signs in the root, and if the server access key disappears, the server layer will empty out — and it will report this rather than staying silent.
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.