Back to corpus
architecturetechnical paper candidatescore 30

Substack Article — HomeLab Architecture v1

At 11:30 PM on a Tuesday, I drew an ASCII diagram in a Discord channel and realized I wasn't running a collection of scripts anymore. I was running infrastructure.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# Substack Article — HomeLab Architecture v1 *Generated: 2026-02-19 00:05 EST* *Source: Technical Snippet* At 11:30 PM on a Tuesday, I drew an ASCII diagram in a Discord channel and realized I wasn't running a collection of scripts anymore. I was running infrastructure. Three Mac machines. A Tailscale mesh network connecting them. Kubernetes orchestrating containers. Prefect managing workflows. Prometheus watching everything. And a fleet of AI agents humming along 24/7, doing work while I sleep. A cron job to check emails. Another to poll a database. One more to trigger an agent. Before I knew it, I had 46 cron jobs scattered across three machines, connected by nothing but hope and SSH. The system worked. Mostly. But understanding it was archaeology. Which job depends on which? What happens when one fails? Is that process supposed to be running or did it crash three days ago?

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.