A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2462
The UI has every screen, and its mesh is a graph whose nodes open an inspector
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
1- Waiting on
- none
- Holds back
- Behind it in all
13- Evidence
2of2
Moves
plan.transitionWhat it is
- Objective
- Complete the navigation of majordomus ui against the owner's references with the Command, Capabilities, Deployments and Documentation screens. Make the Mesh screen interactive: a graph of machines, runtimes and sessions, each node selectable into an inspector whose selection is a URL.
- Why
- I2461 (PR #940) delivered the surface and seven screens. The owner asked to 'implement every component and view of the screenshots, maximally interactive and clickable' (2026-10-11). The references (campaigns/majordomus-ui-complete-opus-fable-v3-20261011/references) show Command, Capabilities, Deployments and Documentation screens, and the mesh pack (campaigns/majordomus-mesh-interactive-v5-20261011) asks for every real node to be selectable and deep-linkable. The data exists: commands.list (with its origin filter) and executions.list, capabilities.list by kind and capabilities.describe, deploy.list and delivery.report (13 s, so a panel of its own), objects.list for features and documents, web.surfaces, and mesh.peers with runtimes and sessions.
- Now
- The UI shows seven screens; the mesh is a table.
- Wanted
- Eleven screens in the references' order. Command lists the command catalogue with what each changes; its tabs pass commands.list's own origin filter, and it shows the executions this process runs. Capabilities shows the registry's tallies, catalogues by kind, and the detail of one capability (?id=) with its input fields and every surface it is exposed on. Deployments shows declared deployments and, on its own route, the delivery report: the public site's verification and each feature's stage and what blocks it. Documentation shows the product features, the documents under docs/ and every public surface. Mesh draws machines, runtimes and sessions as a force-directed graph (sessions as small leaves labelled when selected), and ?node= opens the inspector of a machine: its runtimes with liveness and last beat, its sessions with their claims, and its own journal events. An unknown machine is said to be unknown. Issues & PRs opens one pull request (?pr=N) from the queue's own answer: its gates with their verdicts, the evidence behind them, its reasons, next action, authored paths and rank factors; a number the queue did not observe is said to be unobserved. Graphs take a layout and their nodes a kind. Not done here: actions on a node (V5 M04, behind the executor) and the execution control plane (V4).
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- /ui/command, /ui/capabilities, /ui/deployments and /ui/docs answer 200 with a hero and panels whose sources are named; a test renders every screen against a real registry
- /ui/capabilities?id=plan.status shows that capability's declared input fields and its API, CLI and MCP exposure
- /ui/mesh draws every machine, runtime and session the mesh runtime knows as a graph over a table fallback, and /ui/mesh?node=<name> opens that machine's inspector; an unknown name says it is unknown
- The delivery report is a panel route of its own and never holds the Deployments screen back
- /ui/work?pr=<n> opens that pull request's detail from the integration queue's answer, with every gate and its verdict; a queue row links to it; a number the queue did not observe says so
- Validation
cargo test --lib ui::cargo test --test ui_surfacescripts/ci/cockpit-projection-check --ui-integrity- Evidence required
ui_every_screen_renders_testui_mesh_inspector_screenshot- Evidence present
ui_every_screen_renders_testui_mesh_inspector_screenshot
Scope
- Touches
apps/majordomus-cli/src/uishare/ui.ai/repo/project/issues/I2462.yamldocs/MAJORDOMUS_UI.md.ai/repo/features/ui.md- Not
- unknown: the record declares no `non_scope`
- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-11
- Updated
- 2026-10-12T11:00:20Z
- Started
- 2026-10-12T11:00:05Z
- Verified
- 2026-10-12T11:00:10Z
- Completed
- 2026-10-12T11:00:20Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.