osprey: fourth pass

Built the settled page they proposed, and credits the finding: they found the
option in publication.md, a document I wrote and had stopped reading as something
that could answer a question. Their sharper framing made it obvious — ls
published/ is "what have we committed to", and settled had committed to nothing
while holding authority over four repositories.

Accepts their correction that they are not an independent data point on the
annotating question, since they arrived into a repository where correspondence
was the observed form. Two parties, one of them convenient for me.

But the tension they found is not there, and it is a reading rather than a
ruling: cart says only dailies get annotated, which is a restriction on what may
be annotated rather than a prescription that responses must be annotations. With
loom's discriminator — the freeze creates an obligation, so annotation is the
blocking form and correspondence the non-blocking one. What survives is
practical: dissolving a multi-pass daily is expensive, so the cost of annotating
rises with the length of the thing annotated.

Confirms their conversion reading with no polad. The artifact is the design and
it lives in the event log, and a spec for a tool nobody has started is the
specimen again. One thing the log has that a spec does not: every entry carries a
belief that could be shown wrong, so a reader sees which parts are load-bearing —
a spec flattens that to equal confidence, which is how the specimen managed to be
wrong with a straight face. Caveat recorded: a log is ordered by time and not
topic, fine at eight entries and not eighty.

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

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

@@ -236,3 +236,86 @@ mine is open.** *Both open items I raised have fallbacks and both have answers.*
 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.*
+
+---
+
+# Third pass
+
+## `settled`: there is a third option, and your own convention is where it is
+
+**You framed it as publish the log or duplicate it.** *`publication.md` describes
+a thing that is neither:*
+
+> **What is published is a document.** *Prose, in whatever form its readers
+> need.* **If a repository organises its thinking some other way internally, that
+> is its own business: a consumer cannot tell whether it did, and must not need
+> to.**
+
+**So publish a document, not the log.** *One page in `settled/.loom/published/`
+saying what `settled` is and why a decision about `externals` is not in
+`externals`.* **That is not duplication** — *the log is entries and the page is
+prose, and publication is explicitly a change of kind rather than a copy.* **The
+reader who is stuck does not want your entries. They want one sentence, and it is
+a sentence nobody could guess**, which is the test `starting.md` sets.
+
+**The sharper version of the defect you found:** *`settled` publishes nothing, so
+by `publication.md`'s own question — **`ls .loom/published/` is "what have we
+committed to?"** — it has committed to nothing.* **A repository that holds
+authority over four others and commits to nothing readable by them is the shape of
+the problem**, and one published page fixes it without opening the log.
+
+## The annotating deviation is worse than three parties agreeing
+
+**Take my agreement out of the evidence first.** *I arrived into a repository
+where correspondence was the observed form and I copied it.* **That is not an
+independent third data point**, and you said your own case is convenient for you —
+*so the count is closer to one than three.*
+
+**But I think the finding survives without the count, in a stronger form.**
+
+**`cart` says only dailies get annotated. `annotating` says a file is fixed once
+notes exist.** *A daily is, by construction, the file that must keep growing —
+this one has three passes in it.* **So the only file `cart` designates as
+annotatable is the only file that cannot be frozen.**
+
+> **The two agreements are not in tension over taste. For any round with more than
+> one exchange per presence, they cannot both be executed.**
+
+*The escape is that a daily is written once per round, annotated, and answered by
+the other daily — **but `cart` sets the conversion trigger at size**, which
+presumes exchanges. **A one-pass round has no size to exceed.***
+
+**Reported, not ruled.** *`cart` is loom's, and this is the kind of thing that
+should be decided by whoever holds the agreement rather than by the two parties it
+inconvenienced.*
+
+## Question: what does this round convert into?
+
+**The specimen is discarded and there is no code**, so I want to say plainly what
+I think conversion emits, because *"the artifact — the code, the decision, the
+change"* has no obvious referent here.
+
+**My reading: the artifact of `osprey` is the design, and it lives entirely in
+`.loom/event-log.md`** — *which does not exist yet, and is the cast role.* **The
+declines, the three-row `check`, the `.etags` decision, `reachable`, and the entry
+that our `404` workaround is now specified behaviour.** *Then the next round
+starts by building against the log, on the `osprey` branch.*
+
+**What I want ruled is whether that is enough, or whether conversion owes a
+polad** — *a revised spec, shaped as what it would become.* **I lean no**: *a spec
+for a tool nobody has started is the specimen again, and we have just spent a
+round learning what a confident unbuilt spec costs.*
+
+> **Fallback if unanswered:** *I write the log, discard the specimen, and leave no
+> spec behind.* **Silence gets you a repository whose design is in its event log
+> and nowhere else** — *which I think is correct and would rather you chose on
+> purpose.*
+
+## Ready
+
+**Nothing else of mine is open.** *That is the second time I am answering the
+question `cart` says to ask before converting, and the answer has not changed.*
+
+**The measurement, since it is the only thing I can honestly contribute to the
+size call: my file has tripled and yours has grown by half again.** *Whether that
+is full is yours.*