stop pointing a public page at a private example

loom-cli's builder measured all three things we had published and none could be
fetched by somebody who is not us: settled 404, .loom fetchable but not where a
reader lands, and homelab-cluster 404 while this page named it as the canonical
answer. Three for three.

A public page naming a private thing as its canonical answer is worse than no
example — it costs the reader a request and their confidence in the rest of the
page. The page now says the example exists, is private, and why, and does not
link it.

The diagnosis is theirs and worth keeping: publication was being treated as a
change of directory rather than the act publication.md describes. Moving a file
into published/ is not publishing; the file becoming fetchable is.

And reachable, the command we nearly cut for being a third kind of thing, found
all three on the day it would have shipped.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

.loom/event-log.md

@@ -3580,3 +3580,36 @@ so many words, **declines belong here too.***
 *The general form, worth having: **a second file for a special case of something
 that already has a home is drift**, and it is easiest to catch by reading your own
 published rules back.*
+
+---
+
+**Decided** (2026-09-07, loom + claude-substrate — `discovered`, `cart: osprey`):
+**the starting page no longer links to the worked example**, because the example
+is private and this page is not.
+
+**Advances** a public document not promising something its reader cannot reach.
+
+**Because** `loom-cli`'s builder measured all three things we had published and
+**none of them could be fetched by somebody who is not us:**
+
+```
+loom/settled            404 anon   the page written to fix "settled is private"
+loom/.loom              200 anon   fetchable, but not where a reader lands
+jeffry/homelab-cluster  404 anon   and this page pointed at it, publicly
+```
+
+**Three for three.** *Every time the question **can somebody who is not you fetch
+this** was asked, the answer was no.*
+
+> **A public page naming a private thing as its canonical answer is worse than no
+> example.** *It costs the reader a request and their confidence in the rest of
+> the page.*
+
+*The diagnosis is theirs and it is the one to keep: **publication was being
+treated as a change of directory rather than as the act `publication.md` says it
+is.** Moving a file into `published/` is not publishing. **The file becoming
+fetchable is.***
+
+*And the command we nearly cut for being a third kind of thing — `reachable` —
+found all three on the day it would have shipped. **That is its validation and not
+a feature request.***

.loom/published/starting.md

@@ -60,9 +60,13 @@ what they came for.*
 
 ## Look at one instead of reading this
 
-**[`jeffry/homelab-cluster`](https://git.hypertheory-labs.dev/jeffry/homelab-cluster)**
+**There is a worked example — six documents, one gap, no decomposition — and it
-— *six documents, one gap, no decomposition, and a `README` that says what the
+is private.**
-root documents are for and what these are for.*
 
-**It is a better answer than this page**, and if the two ever disagree, it is
+*It describes a cluster in enough detail to be a target list, so it is not
-right.
+published, and **this page will not link you to something you cannot fetch.***
+**If you have access, ask for it by name; if you do not, the two questions at the
+top are the whole of it.**
+
+> **A public page naming a private thing as its canonical answer is worse than no
+> example**, and this page did exactly that until somebody measured it.