jeffryandClaude Opus 5
0c61c7a42d
loom asked whether .loom/declines.md was a thing or had drifted. It had drifted: written during the conversion of cart almanac because the cart agreement says a round emits the artifact and the declines, and made a separate file without checking against .loom/published/recording-decisions.md, published in this repository an hour later, which says declines belong in the event log. A decline is a decision — what you considered and did not do, with the belief that could later be shown wrong. Splitting them loses the ordering between what we did and what we did not, and makes a reader know to look in two places. The seven declines from almanac are now entries, followed by an entry recording the fix and its general form: a second file for a special case of something that already has a home is drift, and it is easiest to catch by reading your own published rules back. 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
Nothing 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.