I2916 — The workspace reads in the order a person asks
Order the panels: what the intent is, what is missing, what to do next, the work (milestones, issues, waves, graph), then evidence and moves.
DONE wave 0 · p1 · implementation profile · runs alone
Part of idd-reads-at-a-glance — The intent workspace reads at a glance and leads everywhere it names.
Objective
Order the panels: what the intent is, what is missing, what to do next, the work (milestones, issues, waves, graph), then evidence and moves.
Why
On 2026-10-18 the owner read the published /ui/idd three times and found it unergonomic: the panels follow the capabilities, not the questions.
Current state
Capability order.
Desired state
Reading order.
Scope
- apps/majordomus-cli/src/ui/idd.rs
- test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh
- .ai/repo/project
- docs
- site
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- The panels of /ui/idd appear in the reading order the record states
Validation
- majordomus plan validate
- bash test/cases/3220_the_idd_loop_is_walked_in_a_browser.sh
Evidence required
- panel_order_test
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| panel_order_test | ci | gh run view --job 117890228077 --log | ui::idd::tests::the_panels_stand_in_the_order_a_person_asks ok, in rust (2) of validate run 39192952944 on dd4c0a87cba, carrying 069970820d3 | eb72106 |
Timeline
- started
- 2026-10-19T10:03:31Z
- verified
- 2026-10-19T10:03:48Z
- completed
- 2026-10-19T10:04:02Z
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/I2916.yaml. Read it back with majordomus plan show I2916.