# Declines

**What was considered and not done, with the reason.** *Only a belief can later
be shown wrong, so each says what was believed and not only what was chosen.*

---

## `cart: almanac`, 2026-09-07

**A registry service, first.** *Considered for three days and deferred.* **We
believe a git host already provides a document with an owner, an address, an
`ETag`, history and rendering** — so the service buys aggregation and a
self-describing entry point, and buys them better after the conventions have been
used. *Entry 78. **Wrong if the conventions turn out to need a server to be
usable at all**, which using them will show.*

**Affordances, stagings, roles and beads, for problems 1 and 2.** *Built out over
three days and then bracketed.* **We believe the model is for describing software
above its implementation, and that infrastructure and practice description is a
different altitude** being forced into it. *Entries 69 and 70. **Wrong if the
documentation layer turns out to need decomposition to answer anything
useful.***

**Bulk recasting a bead across stagings.** **We believe the list is the migration
plan** — resumable, observable, owned by whoever owns each staging — where a bulk
operation is one uninspectable moment that breaks every consumer at once. *Entry
35.*

**Signatures on receipts.** **We believe a content hash catches every accident,
and a signature answers an adversary that does not exist** — one tailnet, one
operator. *Entry 41. **Revisit when a consumer must verify without being able to
ask.***

**`watch`, and any subscription.** **We believe it would be the first thing
giving the registry persistent knowledge of its consumers**, which is the line
drawn at *a pin is not a subscription* — and a conditional `GET` suffices for
documents that change monthly. *Entry 72.*

**Naming what loom kept reaching for — "accommodations", "standard".** **We
believe it is a lifecycle stage with a measurement rather than a kind needing a
name**: a specification is a thing that names roles and casts none of them.
*Entries 45 and 48. **Coin it when we keep needing to say it.***

**An `internal/` directory.** **We believe naming the complement of `published/`
invents a category, and one that looks like a security boundary and is not.**
*Entries 29 and 67.*