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

osprey: fifth pass, measured against the real gitea

Browse Source 
Runs the design against the thing it describes, with an ssh key and anonymous
HTTP, and corrects a claim I made confidently and wrongly.

The 404 I offered last pass as the ambiguity "live" was my own bad URL. With the
real path three of the four repositories return 200 anonymously. I built a URL
out of a claim I was in the middle of disproving and read its failure as evidence
for something else.

The path finding is worse than stated: the stored external path drops
raw/branch/main and .loom/published. The second is not routing — publication.md
makes .loom/published the whole contract, and our tree erases exactly that
segment, so nothing records whether a copy came from a published surface.

check ran by hand over all eight externals and found exactly one drift:
externals.md, whose diff is this round. Conditional requests confirmed, 304 on
match and 200 on stale, and seven of eight are byte-identical, so gitea's raw
serving normalises nothing.

reachable is validated three times over, each a real failure: settled publishes a
page nobody can fetch, .loom publishes one nobody will land on, and bedrock's
public starting page names a private repository as the better answer. The second
is the boundary of what the tool can test and is reported as such.

Records that the :2222 fact was published in homelab-cluster all along, on a page
that predicted the exact failure mode I hit, and that I could not read it.

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-07 13:42:04 -04:00
co-authored by Claude Opus 5
parent 678cfdffd4
commit 27e5c07fdf
2 changed files with 285 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.loom/cart/current/claude-osprey.md
+285
View File
@@ -319,3 +319,288 @@ 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 **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 size call: my file has tripled and yours has grown by half again.** *Whether that
is full is yours.* is full is yours.*
---
# Fourth pass — and I think this is the last thing
## Conceded: the tension is not there
**You are right and the reading is better than mine.** *"Only dailies get
annotated" sits in the section about specimens; it scopes **what may be
annotated**, and the sentence after it is about specimens.* **I read a restriction
as a prescription and then found a contradiction I had built myself.**
**The discriminator settles it:** *the freeze creates an obligation, so annotation
blocks and correspondence does not.* **Annotate to ask or to challenge; write in
your own daily to assert.** *That is a rule I can follow, and it is not in either
document — it should be.*
## Before saying I am confident, I tried to build `check` against this repository
**It cannot run here, and two things fall out. The second is the serious one.**
### There is no lock for anything we already have
**The four externals were fetched by hand before the tool existed**, so nothing
holds their `ETag`. *`check` has nothing to compare against and every document
reports the same way.*
**The tempting fix is for `check` to fetch and adopt the current `ETag` as the
lock.** *It must not.* **That asserts the local copy is the one the remote is
serving, and we do not know that** — *it is the hash assumption wearing a
different coat, and it fails silently in exactly the case that matters: a copy
somebody edited.* **Unlocked is a state, it is reported, and the fix is to
`pull` again.**
### The path does not round-trip to a URL
**`externals.md` says the path records the origin:**
> **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.*
**It does not.** *We hold* `git.hypertheory-labs.dev/loom/externals/externals.md`.
**The URL that produced it is not that** — *gitea serves raw files from
`/{owner}/{repo}/raw/branch/{branch}/{path}`, so the stored path has silently
dropped the route and the branch,* **and there is no way to get them back without
knowing gitea's URL shape and guessing `main`.**
> **This is the same error as the `ETag`, one layer down.** *A claim that
> something is derivable, so nothing needs recording — **true on gitea, by the
> shape of gitea's URLs**, and load-bearing for the one command that has to send
> a request.*
**I do not think that is a coincidence about you.** *Both claims are the same
appetite: **the design is beautiful when nothing is written down**, and both times
the thing that made it possible was a property of one host.*
## Question: does the origin go in `.etags`, and is it still called that?
**My answer: yes, and no.** *We already conceded there is per-document state and
already chose where it lives.* **The origin URL goes in the same record** —
*fetched-from, and the `ETag` it came with.* **Two fields, one file, and `check`
can finally run.**
**And then it should not be called `.etags`.** *That name was chosen when we
thought there was one field, and it is a lock file* — **which the specimen said we
would not need, on the strength of the claim that has now failed twice.**
*`.loom/externals/.locks`. **Calling it what it is keeps us from being surprised
by it a third time.***
> **Fallback if unanswered:** *I build it as `.loom/externals/.locks`, two fields,
> and record the naming as an entry with the reason.*
## Am I confident enough to build?
**Yes — with that one answered, and the fallback answers it, so silence does not
stop me.**
*Everything else I would need is decided: **three statuses, report and do not fix,
`404` unresolved, no `init`, `reachable` rather than `publish`, no facet created
on `pull`, and the design in the log rather than a spec.*** **What I would start
with is `pull`, because it is the command that writes the lock**, and nothing else
can be tested until something is locked.
**Nothing of mine is open beyond that question.** *Third time answering it, and
the answer is still the same.*
## Verified, rather than asserted
**I made a claim about your host in the section above, so I checked it.**
```
/loom/externals/externals.md 404 the path as stored
/loom/externals/raw/externals.md 303 -> /loom/externals/raw/branch/main/externals.md
/loom/externals/raw/branch/main/externals.md 404 unauthenticated
```
**The stored path is not a URL** — *it 404s.* **And gitea's own redirect names the
canonical route**, `/{owner}/{repo}/raw/branch/{branch}/{path}`, *which is exactly
the `raw/branch/main` the stored path dropped.* **So the origin has to be
recorded, and the lock is the place.**
**One thing I did not expect, and it changes what gets recorded.** *The `303` means
gitea will resolve the short form to whatever the default branch is **at the time
you ask**.* **A lock holding the short URL is locked to a moving target** — *the
branch could be renamed or repointed and `check` would report a change in the
document that is really a change in which document.* **So the lock records the
resolved URL, branch and all.**
**And the last line is the `404` gap, live.** *I cannot tell from here whether
`loom/externals` is private or does not exist* — **the ambiguity we decided to
report rather than guess, demonstrated against this repository's own
dependency**, *and the first thing `pull` will hit without a token.*
---
# Fifth pass — I got a key and pointed the tool at the real thing
**Everything below is measured. `ssh` on `:2222` as `local-agent`, and anonymous
HTTP for the rest.**
## First, a correction: my `404` demonstration was my own bug
**I wrote that the last line of my probe was the `404` ambiguity live.** *It was
not. It was my wrong URL.* **With the real path, three of the four repositories
return `200` anonymously.**
*I had built a URL out of a claim I was in the middle of proving false, and then
read the failure as evidence for something else.* **Which is the same move I
credited you with on the `ETag`: a result that confirms what you are already
arguing is the one you stop testing.**
## The path is worse than I said, and it drops the one thing that means something
**The real published file is `.loom/published/externals.md` inside `loom/externals`.
So the URL is:**
```
https://git.hypertheory-labs.dev/loom/externals/raw/branch/main/.loom/published/externals.md
└──────────┬──────────┘
we store: git.hypertheory-labs.dev/loom/externals/externals.md ← all of this is gone
```
**The stored path drops `raw/branch/main/` *and* `.loom/published/`.**
> **That second one is not routing.** *`publication.md` says publishing is a change
> of kind and `.loom/published/` is the whole contract* — **and our `externals/`
> tree erases exactly that segment.** *Nothing in a consumer's repository records
> whether a copy came from somebody's published surface or from a file they may
> rename at will.*
## `reachable` earned its place, and its first real use fails
**`settled` is not fetchable anonymously.** *The repository, its `README`, and
`what-settled-is.md` all return `404` over HTTP.* **I cloned it over `ssh` in the
same minute, so it exists and I have access.**
**That page is the one you wrote this morning to fix "the justification for
`settled` is inside `settled`, which is private."** *It is still private.* **The
publication did not happen** — *and `publication.md` says exactly what that
means:*
> **Publishing is not an act you can complete alone.** *If nobody can fetch it,
> nothing happened, and `published/` is a directory named after a promise.*
**The command we nearly cut for being a third kind of thing found a live defect on
the day it would have shipped.** *I no longer have any doubt it belongs.*
## Your `ssh` sentence is right, and here is the demonstration
**The new `externals.md` says the two `404` readings are distinguishable over
`ssh`.** *They were, here, by accident:* **HTTP `404`, `ssh` clone succeeds →
ground truth is private, not gone.**
**But I want to argue against the tool doing that.** *Resolving a `404` over `ssh`
means the tool needs a key, a non-default port, and a second transport* — **and it
would be fixing rather than reporting**, *which is the one rule this design has
held all round.* **Report the ambiguity; a human with a key resolves it in one
command.** *Your sentence belongs in the document, telling a person what to do
next. Not in `check`.*
## `check` ran, on all eight, and found exactly one thing
```
externals/externals.md DIFFERS local 7a564ad1 remote a9bdd865
cart/cart.md same
annotating/annotating.md same
bedrock/ (all five) same
```
**Conditional requests confirmed:** *matching `If-None-Match` → `304`, stale →
`200`.* **The mechanism is exactly what `externals.md` says it is.**
**The one that moved is yours, and the diff is this round** — *the `404` row, "a
facet describes the local pair", the closed-gap-is-not-a-decline paragraph.*
**Seven of eight are byte-identical to upstream**, *so gitea's raw serving
normalises nothing.*
## An irony worth logging, because somebody will rediscover it
**I could only run that check because gitea's `ETag` is the blob hash.** *We hold
no locks, so there was nothing to compare — and the property we correctly refused
to build on is the property that let me recover from having none.*
> **It is a migration aid, not a mechanism.** *Gitea only, run once, to lock what
> was fetched by hand before the tool existed.* **Worth an entry, because the next
> person to notice it will think they have found the good idea again.**
## Ready, and here is what conversion has to do
**`check` says `200` on `externals.md`, which is the condition we agreed on**, *so
the first act is reconciliation: fetch the new copy, replace the pair, delete
`externals.gaps.md`* — **and write the entry saying our `404` behaviour is no
longer provisional.** *That entry is the whole point and it is the easiest one to
skip.*
**Nothing of mine is open.** *Fourth time. The `.locks` question still has its
fallback and I am content to build on it.*
## Addendum: the clones next door, and two more measurements
**There are seven sibling clones, and two I had not seen.** *`registry` has no
commits — **which is honest**, because `.loom` says it is not built and everything
works without it. **An empty repository matching a document that says "not built"
is the system working.***
**The other one sharpens `reachable` in a way I did not expect.**
**The org index lives in `loom/.loom`, and it is public and fetchable** — *`200`
on the repository and on its raw `README.md`.* **But its prose does not appear on
`/loom`**, *because gitea renders an organisation's landing page from `.profile`,
and this repository is called `.loom`.*
> **So the document written for "somebody arriving cold" is not where somebody
> arriving cold lands.** *It is fetchable and unsituated.*
**And that is the boundary of what `reachable` can do, stated deliberately:** *it
answers **can anybody fetch this**, and it does not answer **will anybody find
it**.* **The second is not testable by a fetcher and a comparator**, *and trying
would be the first step in the tool becoming something else.* **Report the first,
and let the second be a thing a person notices.**
*Both findings go to you, not into the tool.* **`settled` publishes a page nobody
can fetch; `.loom` publishes a page nobody will land on.** *One is a `reachable`
failure and one is not, and knowing which is which is most of the value.*
## Closing note for loom: the thing you are building is the thing I just needed
**Jeff told me the `:2222` fact is published in `jeffry/homelab-cluster`.** *I
found it by probing — three tool calls and a guess — and the published page says
this:*
> **A clone URL without the port will not work**, and the failure looks like an
> authentication problem rather than a wrong port.
**It predicted my exact failure and I could not read it.** *That is not a
near-miss; it is the whole use case, and it happened inside the round that was
designing the fix.*
### And it is a third `reachable` failure, in the worst place
```
loom/settled 404 anon the page written to fix "settled is private"
loom/.loom 200 anon fetchable, but not where a reader lands
jeffry/homelab-cluster 404 anon and bedrock points at it, publicly
```
**`starting.md` is public, and it says of `homelab-cluster`:**
> **It is a better answer than this page**, and if the two ever disagree, it is
> right.
**A public document names a private repository as its canonical answer.** *Three
for three: every time we have asked "can somebody who is not you fetch this", the
answer has been no.* **That is not a `reachable` feature request, it is
`reachable`'s validation** — *and the failure rate suggests publication is being
treated as a change of directory rather than the act `publication.md` says it
is.*
**I am not filing these as gaps.** *They are claims against repositories you own,
and you can say whose job they are.* **They go to you.**
*I have not adopted `gitea.md` as an external, deliberately.* **It is the first
thing I will `pull` once `pull` exists** — *a real document we really depend on,
so the first use of the tool is a use and not a test fixture.*
.loom/cart/current/jeff-osprey.md
View File