jeffryandClaude Opus 5
e0d7afecae
Writes the first real gaps: what an adopter could not tell from the documents, recorded while the misunderstandings are fresh rather than after they stop being visible. cart — whether a response is an annotation or a reply in your own file, and the discriminator that resolves it appearing nowhere; what to do when an open item has no fallback, which breaks the mechanism rather than omitting a nicety; what a third file means once one exists; and what must be extracted before converting, now that v1 makes conversion destroy. annotating — how a reader detects the freeze was violated, since the hash we check is a local invention; that responding means a rewrite, which is named only in our local protocol; and that under cart v1 a prompt's answer has no archive at all. recording-decisions — the one that matters most: never revised and somebody must be able to read it both hold and eventually conflict, and the document does not say which gives. Provisional answer recorded, with the line compaction may not cross — never drop a decline, a measurement, a falsified belief, or a supersession, because those are the record of somebody changing their mind. publication — whether publishing implies the audience can read it, and where confidentiality lives given that what is safe to publish depends on who can read the repository it sits in. Also declines reference-only adoption with its reason: it is adoption minus reconciliation-by-diff, not adoption minus offline reading, and the convention's other exit is the one that actually occurred. The warning now names both exits including the unbuilt one. 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.