loom/loom-cli
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

a 404 at adoption has a third reading, and the tool can resolve it

Browse Source 
externals names two readings of a 404 — withdrawn, or access lost — and those are
the two a locked document can have. Adoption by name has a third: a document that
was never there under that name. Found in use, where a missing s reported the
ambiguity instead of the typo.

The tool was reporting an ambiguity it had the means to resolve: the by-name form
knows the repository, so on a 404 it now lists the published surface and says which
names exist. It claims that only when the listing succeeds — if listing fails too,
the repository is unreachable and the original ambiguity is the honest answer,
which is the same discipline as recording public and not-public rather than
private.

Not filed as a gap against externals. The third reading cannot occur where that
document is speaking, which is check against a lock; it exists only at adoption,
which is ours.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
This commit is contained in:
jeffry
2026-09-08 12:02:44 -04:00
co-authored by Claude Opus 5
parent a5093c1efc
commit d7b169b87e
3 changed files with 70 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.loom/event-log.md
+31
View File
@@ -1110,3 +1110,34 @@ opaque strings cannot support.*
**Belief that could be shown wrong:** *that fifty is readable.* **It is today.**
*The next remedy is not another compaction — it is the guide `bedrock` needed,
and it is not needed yet.*
## 2026-09-08 — a `404` at adoption has a third reading, and it is resolvable
**`externals` names two readings of a `404` — withdrawn, or access lost — and
they are the two a **locked** document can have.** *Adoption by name has a third:
**a document that was never there under that name**.*
*Found in use: `loomctl external add jeffry/homelab-cluster database` reported the
ambiguity for what was a missing `s`.*
**The tool was reporting an ambiguity it had the means to resolve.** *For the
by-name form it knows the repository, so on a `404` it now lists the published
surface:*
```
loomctl: jeffry/homelab-cluster publishes no "database.md". It publishes:
databases.md gitea.md private-access.md ...
```
**And it only claims that when the listing succeeds.** *If listing fails too, the
repository itself is unreachable and the original ambiguity is the honest
answer* — **the same discipline as reporting `public` and `not-public` rather than
`private`: say the thing you verified.**
**Not a gap against `externals`.** *The third reading cannot occur where that
document is speaking, which is `check` against a lock.* **It appears only at
adoption, which is ours.**
**Belief that could be shown wrong:** *that an extra round trip on a failure is
free.* **It is one partial clone on a path nobody takes twice**, *and if adoption
against large repositories becomes common the listing should be bounded.*