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

I2780

The UI has an intent workspace: an intent, its milestones, issues, waves and graph on one screen

Where it stands

Readiness: review implementation is declared finished and completion is not recorded
Status: VERIFY
Can start: not now
Milestone: idd-workspace
Milestone status: ACTIVE
Wave: 0
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 1 of 1

Objective: Add /ui/idd to the UI's screens: the intents as a choice with stage and verdict, the chosen one's criteria, its milestones in the roadmap's order with status, its issues with status, wave, priority and what blocks them, the waves those issues occupy, and the dependency graph between them with a table beneath it, every entity a link to its existing inspector and every ready issue a link to the move that starts it.
Why: On 2026-10-16 the owner asked to direct the work from the UI rather than from pasted prompts. Every answer the workspace needs is already a capability; what is missing is the one screen that starts from what the work is for.
Now: No /ui/idd; the plan is read on four screens, the waves on none.
Wanted: /ui/idd answers with a hero, the intent choice, the criteria, milestones, issues, waves and graph panels, each naming its sources, and refuses an unknown intent by name.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

The intent the query names, or the first executing then planned one in intents.list's order, is shown, and the rule is printed
Milestones, issues and waves come from plan.roadmap, plan.issues and plan.waves and no list of the screen's own
An issue added to the plan appears with no other edit
An intent that is not recorded is refused by name, and a capability that cannot answer says so in its panel

Validation: majordomus plan validatemajordomus intent validatecargo test --lib ui::cargo test --test ui_idd
Evidence required: ui_idd_tests
Evidence present: ui_idd_tests

Touches: apps/majordomus-cli/src/uiapps/majordomus-cli/tests/ui_idd.rsdocs/MAJORDOMUS_UI.md.ai/repo/project
Not: unknown: the record declares no `non_scope`
Depends on: none
Priority: p0
Profile: implementation
Parallel safe: false
Owner: unknown: the record declares no `owner`

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

Nothing is wrong with these records.