the-mesh-is-operated-from-any-device — The owner understands and operates the whole mesh from one page, on any device
From a phone, a desktop or a Claude Code session the owner sees which nodes, sessions and tasks are live, what is blocked and why, and performs an authorised action whose result and evidence come back live; the page is a client of the persistent runtime, so closing it or ending a session loses nothing and changes nothing.
BLOCKED 0 of 1 issues done
- ready
- 0
- blocked
- 1
- active
- 0
- verify
- 0
- done
- 0
- cancelled
- 0
Problem
From a phone, a desktop or a Claude Code session the owner sees which nodes, sessions and tasks are live, what is blocked and why, and performs an authorised action whose result and evidence come back live; the page is a client of the persistent runtime, so closing it or ending a session loses nothing and changes nothing. Sources: chatgpt-majordomus:c118#6, chatgpt-majordomus:c138#2, chatgpt-majordomus:c296#0.
Outcome
From a phone, a desktop or a Claude Code session the owner sees which nodes, sessions and tasks are live, what is blocked and why, and performs an authorised action whose result and evidence come back live; the page is a client of the persistent runtime, so closing it or ending a session loses nothing and changes nothing.
Current state
Its issues extend existing milestones; see each issue's why.
Desired state
Every criterion of the intent is carried by an issue here and proven by its test.
Acceptance criteria
- The UI served on one machine reads a linked runtime the mesh names and says which runtime every reading came from
- One mutating operation started from /ui/mesh is authorised, executed, audited and its result shown live; refused without authentication
- The hub's UI, API and MCP answer over the tailnet from a second authorised device and nowhere publicly
- Ending the session or closing the page loses no persistent work and the next client resumes from a snapshot and cursor
Validation
- majordomus plan validate
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.
| issue | status | wave | depends on | title |
|---|---|---|---|---|
| I3181 | BLOCKED | 2 | I3138, I3222 | A change made on another node reaches every open page by push, and a gap is refetched |
The graph
flowchart LR
I3181["I3181<br/>A change made on another node reaches every open page by push, and a gap is refetched"]:::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:2pxLinked from this diagram (1)
Canonical record: .ai/repo/project/milestones/the-mesh-is-operated-from-any-device.yaml. Read it back with majordomus plan show the-mesh-is-operated-from-any-device.