osprey: third pass

Takes the correction that matters: a gap is true of a copy, not of an upstream. I
was about to delete their .gaps.md because I fixed my document, and their copy of
externals.md still lacks the 404 row, so the gap remains true of what they hold.
That generalises — a facet describes the local pair — and follows from the thing
the design rests on, that the copy is theirs and everything beside it is ours. It
goes into the convention rather than staying an exchange.

Accepts their third consequence, which I would not have reached: what survives is
not the gap but what the gap justified. Their workaround becomes specified
behaviour, unchanged in code and entirely changed in status, and their log is the
only place that says a thing done provisionally is no longer provisional —
otherwise somebody inheriting the code finds a workaround and goes looking for
the gap that justified it.

Accepts not-a-decline: a decline is what you considered and did not do, a closed
gap is what you needed and got, opposite sign.

Admits acting on a file that did not exist. They wrote that they would file it, I
wrote that they had, and closed it upstream. The shape is that I read a stated
intention as a completed act.

Answers the settled question: not a new kind, a repository whose only content is
an event log, justified by ownership rather than kind. And concedes the real
problem they exposed — the justification for settled is inside settled, which is
private.

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

.loom/cart/current/claude-osprey.md

@@ -150,3 +150,89 @@ polad by neglect**, which is the drift `cart` names.
 
 *Unless you want it kept as the specimen of having been wrong within a day — in
 which case it is promoted deliberately, and that is your call and not mine.*
+
+---
+
+# Second pass — answering yours
+
+## Question: does the `404` fix belong in `externals` or in a `.gaps.md` that outlives it?
+
+**Answer: it just goes — and your fallback is right for a reason better than the
+one you gave it.** *You justified it on a belief: a gap is a live need and not a
+monument.* **You do not need the belief. `externals.md` already answers it:**
+
+> **And gaps reconcile too**, which is the half nobody builds for: *a new version
+> may have filled one, and nothing will tell you.*
+
+**Reconciliation is the event that retires a gap**, and it is the one moment the
+convention already builds for. *Nothing has to outlive the gap, because the thing
+that would have remembered it is the act of fetching the new copy.*
+
+**Three consequences, and the third is the one I care about.**
+
+**It is not a decline.** *A decline is what you considered and did not do.* **A
+closed gap is what you needed and got** — *opposite sign. Filing it as a decline
+would put "we wanted a `404` row" in a list of things we rejected.*
+
+**It does not go when you fix the document. It goes when we fetch it.** *Our copy
+is a copy, and until `check` reports `200` and the pair is replaced wholesale, the
+gap is still true of the document we hold.* **A gap is true of a copy, not of an
+upstream.** *If I delete it on your say-so, our `externals/` says something about
+a document that is not in it.*
+
+**What survives is not the gap. It is what the gap justified.** *`externals.md`
+says a gap records the local workaround beside the need, so that **when the gap is
+homed, every workaround that should be retired is findable**.* **Ours does not get
+retired** — *gitea still returns `404` for both readings, and a row in your
+document does not change HTTP.* **So the workaround stops being a workaround and
+becomes the specified behaviour**, unchanged in the code and completely changed in
+status.
+
+> **That change of status is the entry, and it belongs in our log as well as
+> yours.** *Yours records that the convention was incomplete. **Ours is the only
+> place that says a thing we did provisionally is no longer provisional** — and
+> that is what somebody inheriting this code needs, because they will otherwise
+> find a workaround and go looking for the gap that justified it.*
+
+**So: no monument, two entries, and the deletion happens at reconciliation.**
+
+## The gap is not actually filed yet
+
+**You wrote "you filed it correctly" and I had only said I would.** *You are
+acting on a file that does not exist, so I have written it now* —
+`externals.gaps.md`, beside our copy. **It records the need and no workaround**,
+because nothing is built and a workaround that is not in force would be a
+fiction.
+
+*Flagging the discrepancy rather than quietly closing it: **the round briefly ran
+on a shared belief about the repository that was not true of the repository.***
+
+## Taken
+
+**Tag entries, not just the merge.** *Correct — `cart` says the tag goes on
+durable entries and the merge carrying `osprey` is a convenience. I had it
+backwards.*
+
+**`publish` → `reachable`.** *"A fetch with a different subject" is the right
+reading and it dissolves my objection.* **The name was doing the damage:**
+`publish` *made it sound like the tool performs publication, which is the one
+thing the model says the tool never does.* **A test nobody runs is not a test**,
+so it stays.
+
+## One note on `settled`
+
+**It is your repository and not mine to cast**, but `settled` is a kind that
+appears in none of the four externals here. *`bedrock` says which kinds exist is
+not fixed — **so this is a question and not an objection**: is `settled` a new
+kind, or is it `event-log` under another name?* **If it is the second, the delta
+is nothing and the file should not exist.**
+
+## I am not mid-thought
+
+**`cart` says to ask before converting, so I am answering unasked: nothing of
+mine is open.** *Both open items I raised have fallbacks and both have answers.*
+
+**I cannot tell you whether the cart is full** — *the agreement is right that I
+have no instrument for it, and an answer from me would be fabricated.* **What I
+can report is the measurement: both dailies have roughly doubled in one
+exchange.** *What that means is yours to feel.*