Issue 076: the route-forwarding bed proves ADR 0098; what the run taught about the overlay

2026-09-21 22:44:24 +02:00
parent 75af72ca27
commit 6d3cb60949
1 changed files with 14 additions and 0 deletions
@@ -9,3 +9,17 @@
 **Located in:** the two manifests. Decided in
 [ADR 0098](../../02-DECISIONS/0098-a-fact-a-provider-makes-at-first-start-is-fetched-from-it.md).
 **Proven** the same day: the route-forwarding bed raises the authority, the proxy and a consumer
 from the catalogue on one node and serves a public name through the proxy. Two things the run
 taught, both about the bed rather than the decision:
 - The authority certifies itself for the machine's private-network address, which is what a
  consumer on any node dials. A machine raised from the foundation bundle has no such address
  until it is placed on the overlay, so a bed must place it first — as a hub of one, the way a
  real first node is.
 - With the overlay's networking and the three modules in **one** push, the proxy's fetch of the
  roots timed out at the private-network address; with the overlay converged first and the
  modules pushed after, it passes. Whether that was the order of application within a push or
  the filter closing the interface until it was derived was not isolated. A consumer whose first
  start dials a provider assumes the provider's network is already there; the bed makes it so.