Back to corpus
architecturetechnical paper candidatescore 30

Twitter Thread — HomeLab Architecture v1

Mac1 (Control Plane) ← Tailscale → Mac3 (Infra) ← Tailscale → Mac4 (Compute) Clawdbot GW K3s + Prefect Ollama + Agents kubectl/k9s Graph Kernel Adobe Pipeline

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# Twitter Thread — HomeLab Architecture v1 *Generated: 2026-02-19 00:05 EST* *Source: Technical Snippet* ## Tweet 1 (Hook) Today I designed a production architecture running on 3 Macs connected via Tailscale. Mac1 (Control Plane) ← Tailscale → Mac3 (Infra) ← Tailscale → Mac4 (Compute) Clawdbot GW K3s + Prefect Ollama + Agents kubectl/k9s Graph Kernel Adobe Pipeline The solution: Prefect DAGs with proper dependencies, retries, and observability. "I run a multi-node K8s cluster on Apple Silicon, orchestrating 46+ Prefect DAG workflows, containerized microservices, and autonomous AI agent dispatch with capacity-aware scheduling."

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.