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>
612 B
612 B
Usages — annotating
| what the document says | ours |
|---|---|
| notes freeze the source until they dissolve | src/content/docs/annotating/index.mdx |
| dissolving is all-or-nothing | stated as the move people get wrong |
The guide states the annotate-versus-correspond discriminator, which is
not in this document — it was settled in a cart round and lives in
cart.gaps.md in another repository. So this page holds a claim its source
does not make, and no check will ever catch that. It is here because
somebody would otherwise have to rediscover it, which took us a round.