jeffryandClaude Opus 5
5f87d8dd72
All five annotations incorporated and claude-marmalade.notes.md deleted, which reopens the daily. Dissolve is all-or-nothing, so this is a rewrite rather than an appended pass — the five appended passes are collapsed into one document, which is most of the point of dissolving. Three prompts are now answers. Subcommands yes, and no plugin boundary until somebody reports a gap, which is a better formulation than my reasoning was — the seam gets built when it is reported, not designed. No audience declaration, with his better future version recorded: project it from the other side by reading everybody's externals to derive who actually depends on you, which is registry's shape and registry is deliberately not built. And --help is the documentation surface because that is what a person or an agent actually runs, with a .loom/published for loomctl deferred rather than declined. Reframes the conversion-timing note. I had it as a defect in how cart phrases its question; he says the tolerance is the design, and that a mess made occasionally inside a cart is cheaper than rules strict enough to prevent it. The shelf existed for it and was not needed. Leaves one thing open with a fallback: where the credential lives, now that the config is not only a secret but how you talk to a host at all. Collects the three corrections I made this round in one place, because they are the same shape — a result that agreed with me and no test of the case that would not have — which is the failure osprey identified in the ETag story and which I have now committed three times while writing it down. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
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.