T

jeffryandClaude Opus 5 f0b3269610 marmalade converts: eleven entries, and no shelf

Moves the wal into the log and closes the round. Nothing was unresolved: the one
open item — where the credential lives — is recorded as decided by fallback rather
than shelved, since cart says silence is a usable reply and that a fallback which
quietly becomes the decision is worth being able to find later.

The round decided the shape (loomctl, nouns, no plugin seam until somebody reports
a gap, no audience declaration), declined published check on the registry argument
with both its falsifiers, kept the insight that outlives it, settled list on git
with the three-host measurement behind it, established that nothing needs ssh and
nothing needs write access anywhere, chose Go, and recorded git-on-PATH as the
consequence.

Two entries carry things nobody decided. One is the untested assumption that a
read-scoped PAT authenticates git over HTTPS and not only the API and raw files,
which is the first thing to run against the next token and the only argument that
would bring ssh back. The other is a wrinkle in the isolation role: it assumed work
happens during a round, and both rounds so far have decided work that happens
after, so a branch is named for the round that authorised it and outlives the cart.

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

2026-09-07 14:43:25 -04:00

.loom

marmalade converts: eleven entries, and no shelf

2026-09-07 14:43:25 -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.