Phase 0 Β· The Constitution

πŸ—οΈ The TK Home
Infrastructure Handbook

A living, continuously maintained knowledge base for TK's home lab β€” built one volume at a time, the same way we built the lab itself: incrementally, with understanding.

Build it once Understand it forever Open-ended No enterprise complexity unless justified

What this is

Not a TrueNAS manual. Not a one-off PDF. This is a living body of knowledge that grows alongside the lab. It started as a single question in a conversation with ChatGPT β€” "what's a pool?" β€” and grew into a multi-volume handbook covering storage, networking, virtualization, services, and the philosophy behind building infrastructure you can actually understand.

The website is the canonical version. PDFs are snapshots. The PRD (Product Requirements Document) is the constitution every chapter is measured against.

The 8 design principles

Every chapter, recommendation, and architectural decision in this handbook is measured against these principles. They were drafted in the original conversation with ChatGPT and are the spine of the project.

Principle 1Understand Before You Configure. Never tell the reader to click a button without first explaining why that button exists.
Principle 2Simplicity Wins. Choose the simplest solution that solves today's problem while leaving room for tomorrow.
Principle 3Reliability Over Cleverness. The most elegant system is the one that quietly works for years.
Principle 4Build Incrementally. Never install five new services at once. Build. Test. Learn. Repeat.
Principle 5Document Everything. Today's notes become tomorrow's troubleshooting guide.
Principle 6Automation Should Remove Repetition. Don't automate because it's possible. Automate because it saves time and reduces mistakes.
Principle 7Security Is a Feature. Not bolted on at the end. Built in from day one.
Principle 8Your Infrastructure Should Serve You. Don't build a homelab to impress Reddit. Build one that improves your daily life.

Structure

The handbook has three layers:

How to use this site

Why "handbook" and not "guide"?

A guide is finite. A handbook is something you keep on the shelf and reach for again and again. Five years from now, when TK is running AI servers, a second NAS, and a Kubernetes lab, the handbook will still be relevant β€” because it documents the thinking, not just the buttons.

Built by Aida (with the original conversation with ChatGPT as the spec) Β· v0.1 Β· July 2026