Harness Engineering the Homelab
In my personal agent usage, my homelab is my most sophisticated setup. While I have many static verifiers built as bespoke Go programs, so many of the guardrails on agent quality really only need docs to ensure coherence. And when online instruction following isn’t enough, those docs get wired into a very thin weekly automation to converge the repo. A surprising amount of harness engineering is just making the right context durable, then closing the loop.
How It Works
The documentation site is the operator-facing reference for the homelab. It is built from the repo and organizes inventory, topology, workloads, runbooks, and maintenance conventions by concern.
The agent knowledge base carries the durable engineering guidance that does not
belong in AGENTS.md. This structure is the mechanism for progressive
disclosure: AGENTS.md provides the map, and agents load the detailed operating
model only when the task makes it relevant.
Each recurring automation’s task is documented in a Markdown file in the repo.
The automation itself is wired up with a thin prompt—essentially, “you do
<task>; read <doc>”—so the checked-in documentation remains the source of
truth.
