osprey converts: the design is the log, and the cart is gone

The round is over and its artifact is .loom/event-log.md — fifteen entries, each
carrying the belief that could show it wrong, all tagged osprey so it stays
findable what else was in the room.

No spec is written. A spec flattens everything to equal confidence, which is how
the specimen managed to be wrong with a straight face within a day of being
proposed. The specimen is discarded rather than promoted; the story of its being
wrong is in the log, where it can be found, and the artifact would only mislead
somebody who read it without the round beside it.

Reconciles externals.md, which check flagged as the one drifted document of eight.
The new copy carries the 404 row, so the gap filed against it is closed and
externals.gaps.md is deleted — at reconciliation rather than at repair, because a
facet describes the local pair and the gap stayed true of the copy we held until
we fetched. The entry recording that our 404 behaviour is no longer provisional is
the one that would have been easiest to skip and is the reason the log exists.

No shelf: nothing was unresolved.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris

.loom/externals/git.hypertheory-labs.dev/loom/externals/externals.gaps.md

@@ -1,19 +0,0 @@
-# Gaps — `externals`
-
-## `404` is not in the status table
-
-**The table lists `304`, `200`, and `410`.** *`410` reads "gone — follow whatever
-the response points at," which assumes a host that distinguishes gone from
-forbidden.*
-
-**Gitea does not.** *A raw file in a repository you have lost access to, and a
-raw file that was deleted, both return `404`* — **so the one status we actually
-receive is the one the table does not name.**
-
-**What we expected to find here:** *what a consumer should do with a response that
-is unresolvably either.*
-
-**No local workaround yet — nothing is built.** *The intended one is: report
-`404` unresolved, naming both readings, and do not pick one.*
-
-*Filed in cart `osprey`.*

.loom/externals/git.hypertheory-labs.dev/loom/externals/externals.md

@@ -5,8 +5,20 @@
 ## Pull what you use
 
 **You fetch a copy of somebody's document and keep it** at
-`.loom/externals/<host>/<path>.md`. *The path says where it came from, so nothing
-has to record an origin.*
+`.loom/externals/<host>/<path>.md`.
+
+> ~~*The path says where it came from, so nothing has to record an origin.*~~
+> **This was false and it was load-bearing.** *A stored path is short enough to
+> read and therefore too short to resolve: it drops the host's routing, the
+> branch, and — worst — the `published/` segment, **which is the whole contract.***
+
+**The path is for a person. The origin is recorded in the lock**, resolved: host,
+route, branch, and full path.
+
+*Record the **resolved** URL and not the short form. A host may redirect a short
+form to whatever the default branch is **at the time you ask** — so a lock holding
+one is locked to a moving target, and a rename of the branch reports as a change
+in the document.*
 
 **Pull what you need to understand, not everything it depends on.** *A document
 you fetch may refer to others; follow one when you hit something you do not know.
@@ -22,6 +34,21 @@ you fetch may refer to others; follow one when you hit something you do not know
 > `manifests/ingress.yaml`" is the whole value**, because it answers the only
 > question reconciliation asks.*
 
+## What a lock holds
+
+**One record per adopted document, in `.loom/externals/.locks`:**
+
+- **where it was fetched from** — *resolved, as above*
+- **the publisher's `ETag`** — *verbatim*
+
+**It is committed**, because the thing it locks is committed, and *a lock that
+travels separately from what it locks is the drift this is meant to prevent.*
+
+> **A document with no lock is not broken; it is unlocked.** *Report it and fetch
+> again.* **Do not adopt whatever the remote currently serves as the lock** — that
+> asserts your copy is the one being served, which is the thing you were going to
+> check.
+
 ## Freshness is a conditional request
 
 **Locked on the publisher's `ETag`, verbatim — never a hash you compute.** *A
@@ -33,6 +60,19 @@ did not happen.*
 | **`304`** | nothing changed |
 | **`200`** | changed — the new copy is a candidate, not a replacement |
 | **`410`** | gone — follow whatever the response points at |
+| **`404`** | **unresolved.** *Report both readings; do not pick one* |
+
+**`404` is two different answers wearing one status.** *The document was
+withdrawn, or you no longer have access — **and over HTTP they are
+indistinguishable**, because a host that distinguished them would leak the
+existence of things you may not see.*
+
+> **Say both. Do not guess.** *They want different actions — re-pull elsewhere,
+> versus ask somebody for access — and a tool that picks one will be wrong half
+> the time silently.*
+
+*Over ssh they **are** distinguishable — permission denied against repository not
+found — so a client that has both transports should say which it used.*
 
 ## Reconciliation runs the other way
 
@@ -47,6 +87,20 @@ config, the code that a usage named — which is why a usage names them.*
 **And gaps reconcile too**, which is the half nobody builds for: *a new version
 may have filled one, and nothing will tell you.*
 
+> **A facet describes the local pair.** *A gap is true of **the copy you hold**,
+> not of the document upstream — so a publisher fixing their end does not close
+> it.* **It closes when you fetch the new copy and replace the pair**, and until
+> then it is still true of what is in your tree.
+
+**What survives a closed gap is not the gap. It is what the gap justified.** *If
+you recorded a local workaround, ask whether it is retired or merely no longer
+provisional* — **the second is the common case and it is invisible in the code**,
+which is why it is an entry in your own log. *Somebody inheriting your workaround
+will go looking for the gap that justified it, and find nothing.*
+
+*A closed gap is **not** a decline. A decline is what you considered and did not
+do; a closed gap is what you needed and got.*
+
 **The new copy replaces the old pair wholesale.** *There is no merging a document
 you do not own.*