T

jeffryandClaude Opus 5 aa20eaff89 marmalade: git wins list, measured — and I overclaimed the auth saving

git archive --remote is out: gitea allows it, github 422s, gitlab 404s. Partial
clone with --filter=blob:none --depth=1 --no-checkout is uniform across gitea,
github and gitlab, and lists homelab-cluster's six published documents over ssh in
under a second — the list I could not get this morning. REST would be three URL
shapes, three JSON shapes and three auth schemes, and it 404s on the private repo,
which is the case that matters.

Corrects my claim that git collapses the auth section. It does not: list goes over
git, but add and check still want HTTP, because a 304 is a few hundred bytes and a
partial clone is 124KB, so checking eight externals over git costs a megabyte to
learn nothing. Private raw HTTP needs a token. Two credentials per host, not one.
The argument for git is consistency, not thrift, and that argument stands alone.

Records the failure mode: --filter is a server capability and git's fallback is
silent, so detect the warning rather than letting list become a full clone.

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

2026-09-07 14:04:32 -04:00

.loom

marmalade: git wins list, measured — and I overclaimed the auth saving

2026-09-07 14:04:32 -04:00

README.md

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

2026-09-07 13:50:56 -04:00

README.md

loom-cli

Not built. A small tool for the operations a person should not do by hand: fetch a document you depend on, and find out when it changed.

The design is in .loom/event-log.md, not in a spec. Every entry says what was decided and the belief that could turn out false, so you can see which parts are load-bearing and which were guesses. Everything tagged osprey was decided in one round.

Three commands. pull adopts a document and writes its lock; check asks every publisher whether their copy has moved; reachable asks whether somebody who is not you can fetch what you published. None of them repairs anything.

bedrock and externals, under .loom/externals/, are not discardable. Read them as given — accommodating them is what makes this a loom tool rather than some other thing.