jeffryandClaude Opus 5
d3701c7722
The round is over and its artifact is .loom/event-log.md — fifteen entries, each carrying the belief that could show it wrong, all tagged osprey so it stays findable what else was in the room. No spec is written. A spec flattens everything to equal confidence, which is how the specimen managed to be wrong with a straight face within a day of being proposed. The specimen is discarded rather than promoted; the story of its being wrong is in the log, where it can be found, and the artifact would only mislead somebody who read it without the round beside it. Reconciles externals.md, which check flagged as the one drifted document of eight. The new copy carries the 404 row, so the gap filed against it is closed and externals.gaps.md is deleted — at reconciliation rather than at repair, because a facet describes the local pair and the gap stayed true of the copy we held until we fetched. The entry recording that our 404 behaviour is no longer provisional is the one that would have been easiest to skip and is the reason the log exists. No shelf: nothing was unresolved. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
887 B
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.