jeffryandClaude Opus 5
104cbd050c
check found three documents moved and they were the three the gaps were filed against, so the loop ran the other way for the first time: gaps filed, documents amended, and the tool reported it rather than somebody saying so. publication now carries publishing is not an act you can complete alone as its own section, with the part we asked for — the failure is invisible from the inside, every check available to the publisher passes — and says publication has a visibility, which is what externals' confidentiality rule had been depending on. recording-decisions permits compaction with the four kinds that may never be dropped, adding that a compaction is itself a decision and gets an entry. cart is v2 and says converting destroys, so extract first, naming the write-ahead log. Both closed gap files are deleted at reconciliation rather than at repair, since each stayed true of the copy held until check reported 200. cart.gaps.md keeps four of five and gains a reframing of the third-file case: ours appeared because a round was converted while somebody was still writing, which the agreement already forbids, so it may be a symptom rather than a category and the fix is upstream. cart.usages.md gains a v2 section and a note that the cart arrived headed rowan in a file named loom-osprey.md with no name file — the name is what tags durable entries, so a disagreement mis-files the record silently. Answers staged in wal.md as the round runs, which is v2's rule applied to the round that produced 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.