jeffryandClaude Opus 5
a5093c1efc
recording-decisions now permits compaction and names four kinds that may never be dropped. Applying it removed six entries and left fifty, and the ratio is worth more than the saving. Every entry dropped became droppable by being published. what this tool is, the lock format, unlocked is a state, --help as the documentation surface, and the visibility field all now live in .loom/published/guarantees.md or README.md, and conversion-destroys lives in cart/v2 and cart.usages.md. Nothing was summarised away — the content moved into documents somebody else can lock, which is a stronger place for it than a log only we read. The entry names each one and where it went, so the compaction is auditable rather than trusted. What did not compress is the point. Almost everything left is a decline, a measurement, a supersession, or a belief shown wrong. Declines are not recoverable from code because the code is what they are absent from; measurements are facts about other people's systems that no artifact here holds; supersessions are changes of mind, which is most of what a reader wants. The log is long because the work was exploratory, not because it was padded. 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.