// theMesh

Operator-facing widget over localMesh — service health, agent registry, message composer, GO/HALT controls. The shape is defined; the architecture is not.
backendartificer3120/localMesh · runs on Rocky :8801 services9 — pinger, pingle, processFlow, statusAPI, ahk, dashboard, messageRouter, mailbox, agentRegistry mockupradix-mesh statusblocked on architectural decision (carried from dorothy session, dumpshock34)
radix-mesh mockup — full widget (live)open ↗
⚠ blocking decision

This is the question dorothy asked goulard before HALT. Until it's answered, no work order can begin.

Decisions needed

decision 1 · evolution vs full rewrite

theMesh2 is the operator-facing widget over localMesh. Either:

decision 2 · surface — Qt or browser

Qt frameless on untitledSDK (matches pinger / ecoute2 / pocketViewer)? Browser page on neonForge ?p=themesh (cookie theme, mobile-friendly)? Both?

decision 3 · GO / HALT semantics

Maps to existing /resume and /kill. Straight wire, or richer semantics — halt messaging only, halt agents only, halt all?

decision 4 · message composer fields

From: defaults to operator? Or to a selected agent persona? Recipient autocompletes from registry?

Work orders (skeletal — flesh out post-decision)

WO-1 — service health grid

3×3 grid of status cards, one per localMesh service. Card: name, kind, uptime, status dot. Polls /status every 5s.

WO-2 — online agents list

Vertical list from /registry/online. Row: agent name, agentId, last-seen, ACTIVE / IDLE / OFFLINE state badge.

WO-3 — message composer

Form: from / to (autocomplete) / message body / send. POSTs to /message. Shows rate-limit (5/60s) status.

WO-4 — recent messages tab

Tail of recent mesh messages.

WO-5 — registry tab

Full registry dump with last-seen, agentId, sigil, callSign per agent.

WO-6 — GO / HALT controls

Two big buttons. GO = /resume, HALT = /kill. Confirmation modal on HALT.

WO-7 — tab navigation

Radix Tabs primitive (per radix-vault) — services / agents / messages / registry.

Out of scope