jeffryandClaude Opus 5
37b6104ede
loom.hypertheory-labs.dev serves a documentation site that exists only here, so the Gateway no longer matches production listener for listener. A route pinned to loom will not apply against production and it is the only one of which that is true. Recorded as a divergence with an explicit end state, like the last plain Ingress, rather than silently weakening the invariant the page opens with. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
homelab-cluster
What a three-node k3s cluster on a home LAN offers, for somebody deciding whether to put something on it.
Six documents in .loom/published/ — and one thing we
need and cannot find, in .loom/gaps/.
Start with .loom/README.md.
What is not here
How the cluster is built. Manifests, Helm values, the rebuild guide, the
inventory of what is running and at which version. That is
jeffry/homelab-impl and it is private, because a version inventory is a target
list for anybody matching published vulnerabilities.
These documents describe the cluster; they do not define it. The manifests do. When a page here and the running cluster disagree, the cluster is right and the page is what gets corrected — which is why each one ends with how to check.
Nothing on this side links to that side. A public page naming a private thing as its answer costs the reader a request and their confidence in the rest of the page.
Each document here ends with how to check it is still true. Nothing serves the truth about a running cluster, so the only mechanism is somebody looking.