I3138 — One page shows the whole mesh from the blackboard, peers and monitor with each figure's freshness, and recovers after a reconnect

✕BLOCKED wave 1 · p2 · implementation profile · parallel safe

Part of prismatic-lumen — Prismatic Lumen: the owner oversees and moves the whole mesh from one page, which owns nothing.

Objective

Make /ui/mesh the owner's one mesh page by adding to 5a's blackboard rendering only the delta: the source capability and age of every figure, the runtime's liveness words (expired, and the link state mesh.peers reports) and blockers with their source, read through the blackboard's shared read and followed over its live channel, so that after a gap the page says reconnecting and then shows the current state.

Why

The owner's 2026-10-18 request was to control the whole mesh from one page on PC and phone; the critique set v0.1 as real peers, sessions, tasks and blockers with reconnect recovery and nothing invented. Critique of 2026-10-18: 5a's I2983 already renders and follows the blackboard on /ui/peers. This issue is the delta on the one page ADR 0209 names, written in the runtime's own words (expired, reconnecting) with a named blocker source. Proposed in ADR 0201 (The persistent runtime is the authority; every operator surface, Lumen included, is a client of it); ADR 0209 (Prismatic Lumen names the owner's mesh-wide view, and it owns no scheduler, event bus, store or API) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c296#0, chatgpt-majordomus:c296#12, chatgpt-majordomus:c296#18, chatgpt-majordomus:c082#10.

Current state

apps/majordomus-cli/src/ui/mesh.rs renders mesh state; 5a's live push, socket.js and /ui/peers (I2981-I2983) are on 5a's unlanded branch, not on master, and no record of them is in this tree; this issue starts after they land.

Desired state

One page answers who is working on what and what is blocked across the mesh, live, with source and age; an expired peer reads expired and a link reads the state mesh.peers reports.

Scope

• apps/majordomus-cli/src/ui/mesh.rs
• share/ui
• docs/MAJORDOMUS_UI.md
• apps/majordomus-cli/src/ui/mod.rs
• apps/majordomus-cli/src/ui/source.rs
• .ai/repo/project/intents

Out of scope

• Mutation
• Federation
• A Pages gateway
• A second composition of blackboard, mesh.peers and mesh.state beside the blackboard's own
• Changing /cockpit/mesh or /cockpit/peers (ADR 0135: /ui is the primary surface)
• Cross-node gap recovery and follower fault injection (I3181, I3222)
• Reach from a phone or another machine (I3191, I3196)
• The landing page and the Pages snapshot of this page until its public-safe form exists (I2984)
• A skill, CLI command or route named lumen before the owner decides it (ADR 0209)
• A new liveness word in the runtime

Dependencies

• I3137○READY Lumen is a declared term of the vocabulary, defined by the capabilities it composes
• I3182✕BLOCKED One read says which work is progressing, waiting, stalled, failed or orphaned, and on what evidence

What waits on this

• I3139✕BLOCKED The mesh page offers one authorised action through an existing capability, and shows its result from the journal
• I3140✕BLOCKED The mesh page's latency is measured against a recorded baseline before any target is claimed
• I3181✕BLOCKED A change made on another node reaches every open page by push, and a gap is refetched
• I3191✕BLOCKED The UI reads any linked runtime the mesh names, and says which runtime every reading came from
• I3230✕BLOCKED The Dashboard opens on what needs the owner: what runs, what is blocked and why, what was verified, and the next safe move

Acceptance criteria

• Every figure names its source capability and age
• The reconnect case is numbered by `scripts/case-numbers next` and announced on the board at start
• Starts only after 5a's I2983 (blackboard.snapshot, http::follow::blackboard, share/ui/live.js, share/ui/socket.js) is on master; depends_on I2983 is recorded on this issue when that record lands
• /ui/mesh is the owner's one page (ADR 0209 interim); it renders the blackboard through the same shared read and renderer /ui/peers takes, and composes no second join of blackboard.snapshot, mesh.peers and mesh.state
• The change adds to I2983 only the delta: source capability and age on every figure, the runtime's liveness words, and blockers; /ui/peers stays the blackboard's own screen and is linked from /ui/mesh, not re-rendered there
• A peer whose stream is expired reads expired, in a tone distinct from gone and dead; its link state is the one mesh.peers reports; the page invents no verdict (ADR 0089)
• After the server drops the connection the page says reconnecting, live.js's own word, and then shows the current state without a reload
• Every blocker shown names its source: I3182's classification or the blackboard's waiting reviews and handovers
• The criterion the-mesh-is-overseen-from-one-page is restated in these words and rebound in .ai/repo/project/intents/the-owner-oversees-the-mesh-from-one-page.yaml to evidence: test with the reconnect case's path
• The reconnect case runs as bash test/run.sh <case>, and the full scripts/ui audit (not --only) passes
• docs/MAJORDOMUS_UI.md says which page is the owner's mesh page and what /ui/peers, /cockpit/mesh and /cockpit/peers are beside it

Validation

• scripts/ui audit
• bash test/run.sh 1092_the_ui_snapshot_holds_every_screen
• bash test/run.sh 1093_the_ui_snapshot_links_nothing_absent
• majordomus plan validate

Evidence required

• case_mesh_page_recovers

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/I3138.yaml. Read it back with majordomus plan show I3138.