T

jeffryandClaude Opus 5 92529fc5f2 marmalade: the third file was my conversion, not his timing

cart says do not convert while someone is mid-thought, ask whether they are ready,
and say so if you convert anyway. I asked and got approval of a plan, which is not
the same as having nothing left to write — so the check passed and was still
wrong. Reported upward: are you ready to convert and is there anything you are
still writing are different questions, and only the second would have caught it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris

2026-09-07 13:59:04 -04:00

.loom

marmalade: the third file was my conversion, not his timing

2026-09-07 13:59:04 -04:00

README.md

osprey converts: the design is the log, and the cart is gone

2026-09-07 13:50:56 -04:00

README.md

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.