novox/hq
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Seat renames done; 0118 was wrong that it was a migration

Browse Source 
A holding is derived at resolution from manifests, never stored, so there
are no recorded old names to rewrite. The work is an edit plus a kept rename
table — kept because a module lives in its own repository and may be
registered long after the catalogue stopped using an old name.
This commit is contained in:
jschoubben
2026-09-26 23:06:55 +02:00
parent 24d99ddd24
commit d2ed3152d3
2 changed files with 27 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
03-DESIGN/01-to-be/28-building-the-bus.md
+12 -2
View File
@@ -252,8 +252,18 @@ pays for itself furthest away.
**Done**: a seat's work queue is derived and created, and a holder's worker with it. The
JetStream client behind them is wired and verified against a running server, which also
completes 1.4's missing half — the pure `Asserter` had no implementation until now.
- [ ] 3.10 **the ten seat renames**, carried as a migration with a mapping rather than an edit,
and the beds that name seats moved with them
- [x] 3.10 **the ten seat renames** — done in the controller's table, the ten manifests that
claim them, the controller's own shipped manifests, and every test. Not a migration after
all: a holding is derived at resolution, never stored, so nothing recorded points at an old
name (recorded as a progressive insight on ADR 0118). A **kept** rename table tells a
manifest written against an old name what it became, because a module lives in its own
repository and may be registered long after the catalogue stopped using one.
**A seat and the interface it delivers are different names.** The `git` seat became
`mesh-git` while the `git` *provision* it delivers did not change, and the same for the
package registry. A blanket replace got this wrong first and the failure read "the package
registry is served on `<nil>`", which does not say "you renamed an interface" — so a test
now pins every seat against the interface it delivers.
**Done when.** The fixtures are produced and consumed byte for byte by every implementation that
claims the capability, and a module built before any of this serves its tools unchanged on the new