the-mesh-is-operated-from-one-page — The owner operates the mesh from one page: every runtime readable, one action authorised end to end

✕BLOCKED 0 of 2 issues done

ready

0

blocked

2

active

0

verify

0

done

0

cancelled

0

Problem

On 2026-10-18 the owner asked for a skill and one page ('prismatic-lumen') to control the whole mesh from PC and mobile, report periodically and stay up to date; on 09-15 for a Cockpit whose default backend is lundra. /ui/mesh reads only the local runtime and offers no authorised action. 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#18, chatgpt-majordomus:c138#0.

Outcome

/ui reads any linked runtime and says which runtime every reading came from, and one mutating operation is authorised, audited and streamed back.

Current state

Verified: /ui/mesh (apps/majordomus-cli/src/ui/mesh.rs) reads the local server; ADR 0126 refuses remote writes without authentication; web-sign-in (I1201-I1208) is open; the peer blackboard (I2980-I2983, 5a) is in flight with no records yet.

Desired state

A backend-target choice derived from mesh nodes, an audited action path, runtime-scheduled reports, measured SLOs.

Scope

• apps/majordomus-cli/src/ui
• apps/majordomus-cli/src/capability/builtin/executions.rs
• apps/majordomus-cli/src/execution
• docs/MAJORDOMUS_UI.md

Out of scope

• A Lumen backend or repository (open question)
• Federation with a second project
• Natural-language control without the typed operation underneath

Acceptance criteria

• Every reading names the runtime it came from
• No operation reachable from the page bypasses authorisation

Validation

• majordomus plan validate

Risks

• False authority: the page must never say healthy without evidence (10-18 critique)
• It follows everything-is-followed-in-one-stream in practice; the edge is kept off the milestone so two milestones of one order are not reordered.

Issues

Each one is an execution contract with its own acceptance criteria, validation command and required evidence. The wave column is the layer of the dependency graph it sits in.

The graph

flowchart LR
    I3191["I3191<br/>The UI reads any linked runtime the mesh names, and says which runtime every reading came from"]:::blocked
    I3192["I3192<br/>An operation started from /ui/mesh is authorised, executed, audited and its result streamed back"]:::blocked
    classDef done stroke:#16a34a,fill:#dcfce7,color:#14532d,stroke-width:2px
    classDef active stroke:#2563eb,fill:#eff6ff,color:#1e3a8a,stroke-width:2px
    classDef verify stroke:#7c3aed,fill:#f5f3ff,color:#4c1d95,stroke-width:2px
    classDef ready stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
    classDef planned stroke:#0891b2,fill:#ecfeff,color:#164e63,stroke-width:2px
    classDef blocked stroke:#b45309,fill:#fffbeb,color:#78350f,stroke-width:2px
    classDef cancelled stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px
    classDef superseded stroke:#6b7280,fill:#f9fafb,color:#374151,stroke-width:2px

Canonical record: .ai/repo/project/milestones/the-mesh-is-operated-from-one-page.yaml. Read it back with majordomus plan show the-mesh-is-operated-from-one-page.