Cited, not measured by AMDai

Secure home lab

Shannon’s lab write-up describes an isolated command enclave behind its own router, Proxmox VMs that split the agent host from the knowledge-base host, a guardrail / prompt-injection layer in front of agents, models on a separate NVMe, and offsite backup. Cited layout only. We have not built this on the local desktop.

Source: How I run my Lab (2026-10-12). Write-up: Shannon’s lab. llama.cpp first. This is not a local desktop recipe.

1. 1 · Cited, not measured by AMDai

   Isolated command enclave

   Put the command host behind its own router so agent tools and the rest of the house do not share a LAN by default.

2. 2 · Cited, not measured by AMDai

   Proxmox split

   One VM for the agent host, another for the knowledge-base host. A compromised tool loop should not sit on the same guest as the notes store.

3. 3 · Cited, not measured by AMDai

   Guardrail in front of agents

   A prompt-injection / guardrail layer in front of the agents — Shannon’s layout, not a product we pin. Tokens on the GPU still come first.

4. 4 · Cited, not measured by AMDai

   Models on their own NVMe

   Keep GGUFs on a disk that is not the OS or the knowledge-base volume. House rule on AMDai is still NVMe, not a spinning disk.

5. 5 · Cited, not measured by AMDai

   Offsite backup

   Back up the knowledge base and configs offsite. We do not invent a vendor or a retention number.

After the box is isolated, attach a harness the usual way: Connect. the house Hermes notes stay on /harnesses/hermes.