Back to corpus
architecturetechnical paper candidatescore 30
LinkedIn Post — HomeLab Architecture v1
Tonight I locked in the architecture for what started as "a few scripts" and evolved into a genuine distributed system running across three Mac machines.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
# LinkedIn Post — HomeLab Architecture v1 *Generated: 2026-02-19 00:05 EST* *Source: Technical Snippet*
Tonight I locked in the architecture for what started as "a few scripts" and evolved into a genuine distributed system running across three Mac machines.
**The Setup:** - **Mac1** (Control Plane): Clawdbot Gateway, kubectl, k9s for cluster management - **Mac3** (Infrastructure Node): K3s, Prefect Server, Postgres, Graph Kernel, RAG++ - **Mac4** (Compute Node): Ollama, Agent Workers, Adobe Creative Pipeline
All connected via Tailscale mesh network. All orchestrated through Kubernetes. All monitored via Prometheus + Grafana.
I had 46 cron jobs. They worked, mostly. But understanding dependencies? Handling failures? Knowing which ones were running? That was archaeology, not engineering.
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.