Divide the bus work into five steps, each proved on its own

The NATS change was recorded as one undivided item, which hid three gaps: a mesh already running had no adoption path, the protocol specification did not know its transport was being replaced, and nothing was runnable until everything was. Dividing it is what surfaced them.
2026-09-26 18:19:56 +02:00
parent 782d5ace04
commit fe0c1e9da2
4 changed files with 294 additions and 32 deletions
@@ -95,6 +95,7 @@ python3 00-META/checks/index.py            fail if stale
 - **0104** — [A provision may be answered by an adapter to the predecessor](0104-a-provision-may-be-answered-by-an-adapter-to-the-predecessor.md)
 - **0105** — [The mesh adopts the predecessor's tunnel in place](0105-the-mesh-adopts-the-predecessors-tunnel-in-place.md)
 - **0106** — [The bus is NATS](0106-the-bus-is-nats.md)
+- **0115** — [The bus is built in five steps, and the protocol moves with it](0115-the-bus-is-built-in-five-steps.md)

 ### Its tiers, from the bottom up