mesh-controller

Files

T

jschoubben ad797d8742 A routed name resolves to the node whose proxy serves it, never to a provider merely told it (hq 178)

The names region attributed a composed name to whichever labelled contribution a map yielded last.
A dashboard contributes its label to its route and to the identity provider, which must know the
public name for a redirect; so on one plan grafana.<domain> pointed at the proxy's machine and on
the next at the identity provider's, and the whole region flipped with it (forge issue 227). And a
module routed several times contributed no name at all, because the single-value reading of its
contributions is empty for the many shape.

Now every node's resolution is read first and the names are attributed across them at once: the
terminus serves the name — the provider that is not itself published under a labelled name through
another — walked in order, so one mesh yields one region. Name-agnostic, structural, deterministic.

2026-10-01 02:03:50 +02:00

broker

A build says what it does on the bus, as it happens (novox/hq ADR 0157)

2026-10-01 00:43:07 +02:00

builder

A build says what it does on the bus, as it happens (novox/hq ADR 0157)

2026-10-01 00:43:07 +02:00

catalogue

A routed name resolves to the node whose proxy serves it, never to a provider merely told it (hq 178)

2026-10-01 02:03:50 +02:00

envfile

An address is read from the node's settings where it is used, never recorded with a port