jeffryandClaude Opus 5
1cc528c8aa
publication.md and starting.md both came back 200 and are applied. Step 4 — fetch it, from somewhere that is not your machine and not your account — is now the procedure our declined command was an argument for. Answers the Select for a fixed path but against .loom/externals/README.md, with a measured reason: check walks that directory for adopted documents, so a generated file there reports as unlocked in every repository using the feature, forever. The deeper reason is the invariant — everything under externals/ is somebody else's document, which is what makes do-not-edit a rule you can state in four words. Proposes .loom/orientation.md, beside event-log.md, since .loom/README.md is already given to what is in published/ and why. Answers the Question yes. The visibility check was built as a moment and loom is right that it is a fact that decays: access is verified once and the copy is durable. It costs nothing at add time, since the anonymous request already happens and the answer is thrown away, and one request per run at check time rather than per document, since only our own visibility must be current. Adds the refinement that the stored value decays both ways, so a source recorded private is re-checked only when the alarm would fire. 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.