The lab started as a place to learn by doing, but it has become useful infrastructure: smart home control, DNS filtering, backups, remote access, media, and AI-agent experiments all live in the same ecosystem.
The useful part is not the number of services. It is the practice of making the system understandable enough to fix later.
The Shape
- A reliable core handles DNS, remote access, backups, and smart home basics.
- A compute layer runs VMs, LXCs, Docker, media workloads, and test systems.
- A storage layer holds backups, photos, Time Machine, general storage, and media.
- An experimental edge handles AI agents, coding workflows, automation runners, and research tools.
The important split is not “home” versus “lab.” It is relied-on versus experimental. AdGuard, Tailscale, Home Assistant, backups, and storage need to be boring. AI-agent systems, new containers, and automation experiments can be more adventurous because they have clearer boundaries.
Documentation Rule
Documentation should show intent and tradeoffs without turning into an access guide. Diagrams work best when they explain responsibilities, dependencies, and failure modes.