loom-cli publishes one page: what the tool guarantees, not what it does

Browse Source

The earlier decision stands rather than reverses. .loom/published/ was recorded as
deferred, not declined — it earns publication when somebody depends on the tool's
behaviour rather than reading its help — and a docs site whose build calls add,
check and apply is that consumer. The condition fired.

The delta is real and is not the command list: --help says what the tool does, and
a reader cannot learn from it which behaviours survive the next version. The
sharpest case is loom's — the tool is now a second holder of externals' rule that
the lock is the publisher's ETag and never one you compute, and nothing anywhere
said the tool holds it, in a repository where a specimen was written that computed
a hash instead.

Includes what a contract must include and the ask did not mention: what is not
promised. The command surface, the orientation file's format across versions, the
precision of the visibility signal, and that anything is checked when nobody is
looking. That is the half a reimplementation needs most, and it keeps the page from
quietly committing us to the CLI.

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

...

This commit is contained in:

jeffry

2026-09-08 10:33:14 -04:00

co-authored by Claude Opus 5

parent af8f739bfe

commit 4e7aa1ff1f

2 changed files with 93 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

.DS_Store

Vendored

BIN

Binary file not shown.