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>
Someone in an empty repository saying "set this up" has nothing to read. The four
primitives say what things are and deliberately not what to do, which leaves a
set of primitives with no starting point — a puzzle rather than a foundation.
Two questions carry it: what can a reader not already know, which is what you
publish; and what do you need that nothing provides, which is a gap. Everything
else is conditional on having something to say, and the page says plainly that a
file carrying no delta should not exist.
It ends by pointing at jeffry/homelab-cluster and saying that if the two
disagree, the example is right. Precedent beats description, and a page about
writing documents should not be the longest document.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
jeffryandClaude Opus 5