jeffryandClaude Opus 5
af8f739bfe
Extracted at conversion rather than staged as it went — there was no wal this round, and the answers lived in the daily that the rm destroys, which is precisely the failure v2 added the rule to prevent. Worth noticing that the round which answered a question about durable records is the one that nearly lost its own. Records two declines with their reasons: a second orientation file, since the publishing half varies not at all and is already adopted so it appears in the index by itself; and .loom/externals/README.md as the path, measured rather than argued, because check walks that directory and would report a generated file as unlocked in every repository using the feature, forever. Records the visibility field with the word it refuses — public or not-public and never private, because an anonymous request tells those apart and nothing finer, and private would claim precision the signal does not have. And records a one-line bug whose trap is permanent: visibility was computed by one function used both after a successful fetch and as a probe, where "no credential configured" means opposite things. In the audit it would have silently cleared real alarms, which is the worst failure available to a check. 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.