loom

What this is

A repository knows things nobody wrote down. Why the default ingress class is the one that leaks. What was decided in March and what it was believed to buy. What you tried that did not work. Somebody arriving — a new colleague, or an agent asked to change one file — cannot find any of it, and the code cannot tell them, because the code is the answer and not the question.

These are conventions for holding that. Four of them, small, and each is a document in a repository you can read.

bedrock

The primitives. A .loom/ directory, what goes in it, and what publishing something means. Start here.

externals

How a repository records what it depends on — a copy, a lock, and what you use it for. Read it.

annotating

Two parties who never edit each other’s text. Read it.

cart

Two presences, one round, and never a third file. Read it.

This site is an instance of the thing it documents

Every reference page here is a copy of a document published by one of those repositories, adopted under externals, locked to the version it was fetched at, and checked against its source. Nothing here is written twice.

Which has a consequence worth stating plainly: a document has to be public to appear here. Not as a policy — as arithmetic. The rule is do not adopt from a source less readable than the repository you are adopting into, this site is on the public internet, so its sources are public or they are not its sources.

The pages that are not copies are the section fronts — one per convention, hand-written, holding worked examples and reading order. Those are stamped with the version they were written against, and when a source moves they say so at the top of the page rather than quietly going wrong.