One Proxmox box, a rack of self-hosted services, and a small fleet of agents that watch, triage, rehearse, update, and repair — surfacing a human only where judgment actually matters. This page is generated from the system's own records, and refreshes on its own.
The top of this list is generated live from the system's own issue log — caught, healed, or self-resolved in the last fortnight. Below it, a few signature moments worth keeping.
Latest · this fortnight, automatically
Signature moments
Fake “releases” — Windows executables padded to gigabytes and named like episodes — had settled in from public trackers. A library scan identified all eleven by signature and quarantined them. None had ever been recognised as media, so nothing was playing them; they were simply sitting there, unnoticed, until the sweep looked.
A media-server version jump was first replayed against a throwaway copy of the real box. The rehearsal caught five breaking surprises — a plugin that crashes the server on boot, a migration that wipes the library if a mount isn’t ready — every one fixed before a single byte reached production. Then it shipped clean, full library and watch-history intact and verified.
An automated log-capture accidentally carried an API key into the repo. The secret scanner flagged it, the key was rotated and revoked, and redaction was added at two independent layers so a credential can never reach the logs or the repository again. Root cause fixed, not just the symptom.
The update scout saw the advisory, weighed it against the running version and the project’s maturity policy, and proposed the patch. Then it stopped and waited: a reboot of the whole house is not a decision an agent gets to make.
Small, single-purpose, and boring by design — the interesting behaviour is in how they compose.
The system is deliberately not a black box that changes things on a whim. Four rules keep it trustworthy.
Every change is a branch, a review, a merge. Nothing is configured by hand and forgotten. The repository can rebuild the box from scratch.
Anything destructive is replayed on a throwaway clone of production first. The dangerous surprises get caught on a copy, not on the live system the household depends on.
Agents find root causes and propose. A human approves anything that changes state. Confident-but-wrong auto-fixes were tried once — and deliberately removed.
Secrets are scrubbed at the log shipper and again before the repository. A leaked credential is a bug to fix at the source, at multiple layers — never a fire drill.