T

jschoubben be74c94151 mesh-wireguard: the module that holds the-private-network, with its manifest and peer generator its own package (ADR 0636 §6; issue 1966)

The names and the manifest come from mesh-sdk's overlay, the peer graph, the generator and the declaration from the node-engine's internal/overlay; the value's layout is the seat's contract in mesh-connectivity-contracts.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

2026-11-05 14:07:21 +01:00

modules

mesh-wireguard: the module that holds the-private-network, with its manifest and peer generator its own package (ADR 0636 §6; issue 1966)

2026-11-05 14:07:21 +01:00

.gitignore

Move route-proxy out of the controller's repository, which is archived with the controller

2026-11-02 11:45:17 +01:00

README.md

Move route-proxy out of the controller's repository, which is archived with the controller

2026-11-02 11:45:17 +01:00

README.md

mesh-networking

Novox Mesh — networking: the modules that carry traffic into and across the mesh, each under modules/<name> with its own manifest (module.json) and Go module.

route-proxy provides route: the public HTTP and HTTPS entry, serving each name a consumer asks for from the seat mesh-provisioner's plans (its README says how). It moved here from the controller's repository, history kept, when the controller was removed (issue 1126).

Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/check passed and the operator approved.