jeffryandClaude Opus 5
ffa56daa41
publication.md gains the procedure, with "fetch it, from somewhere that is not your machine and not your account" as its own step. Steps 1-3 are things you do; step 4 is a fact about the world you find out, which is why it is the one that gets skipped. Declined a separate procedural document: publishing.md beside publication.md is two files one letter apart, and the gap filed was that this document was underspecified. starting.md still described the worked example as private and refused to link it. It went public four days ago. The first page a newcomer reads was demonstrating its own lesson instead of teaching it. Entries 82-83. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
bedrock
The primitives. Four documents, in .loom/published/:
- The
.loomdirectory — everything lives there, and a directory means a kind - Sibling facets —
x.<facet>.mdbesidex.md, owned by whoever wrote the facet - Recording decisions — what an entry says, and why it is never revised
- Publication — what
.loom/published/means - Starting one of these in a repository — the one page here that tells you what to do, because a set of primitives with no starting point is a puzzle
Nothing else here says what to do. loom/annotating, loom/cart and
loom/externals are built on these and are where the practices live.
Most repositories will never read this. Its audience is people building conventions, not people using them — and it is a good sign that a primitive is one nobody needs.
Publishers are the exception, because publication is defined here, and the people whose choices land on somebody else should have read the primitives.