I3827 — The hosted hub is this repository's default rendezvous, and every node shows it as the path from anywhere

✕BLOCKED wave 3 · p1 · implementation profile · runs alone

Part of an-authorised-node-connects-from-anywhere — An authorised node reaches another across LAN, tailnet or NAT, and says how.

Objective

Once TLS (I3823) and the hub's closures (I3826) hold, the owner's trust.allow entry for the hub's key is committed and https://prismatic-majordomus.gigalixirapp.com is added to rendezvous.endpoints of .ai/repo/mesh/majordomus.yaml; case 491 accepts an https public hub and still refuses a public http one; /ui/mesh on the hub shows every trusted runtime heard through it to a trusted reader, and the live hub is observed to fold and relay the journal. ADR 0220 decision 6.

Why

The owner asked on 2026-10-21 for the Gigalixir server to be an optional but default rendezvous that shows the whole mesh.

Current state

The declaration lists six private and tailnet hubs on port 8791; the hosted application's mesh is closed (its key is not in trust.allow).

Desired state

The declaration names the hosted hub, the hub's key is in trust.allow by the owner's recorded decision, two nodes on different networks see each other's claims through the hub, and a working tree can narrow the endpoint out.

Scope

• .ai/repo/mesh/majordomus.yaml
• test/cases/491_the_mesh_is_on_here.sh
• docs/MESH.md
• .ai/repo/project/issues/I3827.yaml

Dependencies

• I3823✓DONE The mesh client reaches an https endpoint over TLS and refuses cleartext to a public address
• I3826✕BLOCKED A hosted hub keeps one key from a secret, advertises its URL, and shows the mesh only to those it trusts
• I3822✕BLOCKED A deployment that names a provider is observed at its own URL, and is active only while it serves master

Acceptance criteria

• The declaration names the hub over https and the hub's key by the owner's decision
• Case 491 accepts an https public hub and refuses a public http one
• Two nodes on different networks exchange a claim through the hub

Validation

• env -u MAJORDOMUS_SHARE -u MAJORDOMUS_HTTP_HOST -u MJ_ROOT bash test/run.sh 491_the_mesh_is_on_here

Evidence required

• hub_relays_a_claim

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3827.yaml. Read it back with majordomus plan show I3827.