mesh-controller

Files

T

jschoubben e09a14ba4c A served value may name the consumer it is served to (hq ADR 0188)

${consumer:as} and ${consumer:as:dns} in a serves block are filled per
consumer at resolution, and the one filled value reaches both ends: the
consumer's binding and its ${bound:...} substitutions, and the provider's
contributions entry as `derived`. A fact or alphabet the mesh does not have
is refused at parse; a consumer whose own file already holds the derived
value is refused at resolution, naming the placeholder to write instead.

2026-10-02 21:24:43 +02:00

broker

The proxy is told its routes and the mesh on the bus, and serves internal names to the mesh only

2026-10-02 01:46:30 +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 served value may name the consumer it is served to (hq ADR 0188)

2026-10-02 21:24:43 +02:00

envfile

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