HEDDLE

Concept

Heddle.sh: spools, namespaces, and the hosted record

A spool is Heddle's repository. Marketing and Git still say repo; the app and this manual say spool. Hosted heddle.sh keeps a shared record of those spools. The local CLI does not need an account to do that work on disk.

What a spool is

A spool is the thing you clone, capture into, and publish. On GitHub it is a repository. Here it is a spool. Same object, one product word — so explore, the create form, and this manual do not have to guess which synonym is in season.

The hosted tree also uses the word for a grouping node: a namespace can be created through the same spool form. That node is not a repository. It holds spools, grants, and policy. The definition of that container lives on namespaces, not here.

What hosted adds over local

The CLI writes a local record: captures, states, threads, the oplog on disk. No login. That loop is the product even if you never touch heddle.sh.

Hosted adds a shared record of the same objects. Push and pull move them. Explore ranks public spools. Review and inbox run against the hosted copy. Namespaces and grants live on the control plane — the architecture page covers that split; this page only names what you get by logging in.

Who can use which

heddle capture and the rest of the local loop do not wait on an account. heddle auth login --server heddle.sh does: there is no open signup. Reserve a handle if you want in, or redeem an invite if you already have one. The login command itself is on auth and identity.

States and captures

On the States tab the nouns are state and capture. A capture is the act of taking a snapshot; a state is what it produces. The URL for that tab is ~/changes and stays that way — the path is not a third product word. The definitions are on captures and states.