jeffryandClaude Opus 5
969524b8ea
Astro Starlight over .loom/externals/. Every reference page is a copy of a document published by another loom repository, adopted with loomctl, locked to the etag it was fetched at. Nothing is written twice. Two kinds of page. Generated ones are overwritten every build because nobody typed them. Guides are hand-written, never overwritten, and stamped in frontmatter with the etags they were written against; when a source moves, the build renders a banner onto the page asking whether it is still true. It cannot answer that — only a person can — so it asks where a reader will see it too, and the site degrades honestly instead of reading as authoritative and being wrong. npm run ack is the person saying they re-read it. Declined: having the build stage a polad into the cart. loomctl external check does that and is right to, but a docs build runs in CI and in worktrees where there is no cart, and staging a polad is an act of judgment. The build reports; a person raises. The guides are worked examples rather than explanations, deliberately. An explanation is a second saying of a rule owned on the page beside it and goes stale silently; an example goes stale visibly, because the artifacts in it are the wrong shape. Generation is byte-deterministic — locks are walked in path order, no timestamps — because the diff is most of the value. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
915 B
The .loom directory
A repository that uses loom keeps everything in .loom/ at its root.
Type is determined by location. The directory a file is in says what it is. So frontmatter carries almost nothing, and often nothing at all.
A stream is a file. A collection of things with identity is a directory. A log is appended to and no entry is ever addressed; a thing that is referred to individually gets its own file.
Everything not recognised is shown rather than rejected. These files are edited by hand and by agents, constantly, and that is supported. A reader that fails on an unfamiliar directory is wrong.
What is fixed
Only .loom/ itself, and that a directory means a kind. Which kinds exist
is not fixed here — conventions built on this one declare their own, and a
repository has only the ones it uses.
Nothing outside .loom/ is loom's business.