jeffryandClaude Opus 5
d3fec24bc6
loom's .usages.md for this page found the hole. The docs site depends on the command surface — its README and publish script tell a person to type loomctl external add loom/<repo> <doc>.md — and this page explicitly does not promise it. Nothing parses the command, which is exactly why no check would catch a rename: the thing that moved is not a document anybody adopted. The answer is not to promise the surface, which would freeze the CLI. It is to promise that a change to it lands on this page — which consumers already lock — so a rename reports 200 the day it happens. The exclusion goes from "you are on your own" to "you will be told", and it costs one append-only section. Same shape as a supersession in the event log: the record is not that the thing never changes, it is that the change is findable by whoever depended on it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
loom-cli
loomctl fetches the documents this repository depends on, and tells you when
they change. It reports; it never repairs.
go build -o loomctl .
./loomctl --help
check only reads. Nothing here writes over the network, so a credential it is
given never needs write scope.
Why it is the way it is: .loom/event-log.md. Every
entry says what was decided and the belief that could turn out to be false.
What it depends on, and what we could not tell from those documents:
.loom/externals/ — the .gaps.md files beside each one.