jeffryandClaude Opus 5
021bf63a11
Restores something the specimen said and the round that discarded the specimen lost with it: a changed external becomes a polad in the cart, and somebody decides. check now stages what moved into .loom/cart/current/polad/ with the ETag that was served alongside the bytes, and prints the .usages.md beside it, because reconciliation runs the other way — the facets usually survive and what moves is the code a usage named. It says so when there is no usages file, which is its own finding. With no cart open, check reports and stages nothing. The tool does not open a round: a cart is a bounded exchange between two presences and starting one is somebody's act, not a side effect of asking about freshness. add now adopts what is not here and refuses what is already adopted, superseding the entry that had it announce an overwrite — it no longer overwrites at all. The one exception is the only way out of a dead end: a document present but unlocked was fetched by hand, nothing records its origin, and the path does not round-trip, so check cannot ask about it and a refusal would strand it forever. add accepts it and the bytes decide — identical locks it without rewriting anything, which makes the lock's assertion verified rather than assumed, and different stages a polad and leaves the local copy alone because it is the only evidence anything moved. apply exists because the lock is the half a person forgets: moving a polad by hand leaves a lock describing the copy you just replaced. Recorded with its limit — for an external, discard does not mean the change goes away, so discarding is really knowingly stale and nothing yet records that choice. Measured end to end on this repository: eight hand-fetched documents, all eight locked, nothing rewritten. 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.