jeffryandClaude Opus 5
c09a1b7570
The round that authorised this work converted into the log; this is the work. list, add, check and apply, in Go with no dependencies outside the standard library and git shelled out for list alone. Exercised rather than demonstrated. Eight documents adopted by hand before the tool existed were locked without rewriting any of them, because identical bytes make a lock's assertion verified rather than assumed. Two real upstream changes were found that nobody would have noticed, and the second of them — the rule that confidentiality does not travel with the copy — arrived through the tool rather than through somebody saying so, and is now half-implemented with the tool saying which half it can see. 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.