I3023 — The Knowledge screen reads in review order, in plain labels, and leads to the knowledge manual
/ui/knowledge orders its panels as a reviewer works (Awaiting review, By subject, How to review, Is learning up to date?), labels its tiles and facts in plain words (From an unknown branch, Sessions not yet learned from, Newest session, Up to date, Last learned from, Last session closed) and links the review to the knowledge manual under /docs/knowledge/.
DONE wave 0 · p1 · implementation profile · parallel safe
Objective
/ui/knowledge orders its panels as a reviewer works (Awaiting review, By subject, How to review, Is learning up to date?), labels its tiles and facts in plain words (From an unknown branch, Sessions not yet learned from, Newest session, Up to date, Last learned from, Last session closed) and links the review to the knowledge manual under /docs/knowledge/.
Why
The published /ui/knowledge (majordomus.dev, v0.29.0) opened on the deriver's internals before the queue a reviewer came for, used internal terms as labels (Unattributed, Closed, underived, Newest episode, The deriver), and linked nowhere a reviewer could learn what a record class or a promotion means.
Current state
The grid draws The deriver, Review, By subject, Awaiting review in that order, with internal labels and no link to the manual.
Desired state
The grid draws the queue first and the deriver's judgement last, under plain labels, and the review panel ends with a link to the knowledge manual; crate tests pin the order, the labels and the link.
Scope
- apps/majordomus-cli/src/ui/knowledge.rs
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- Awaiting review precedes How to review, which precedes Is learning up to date?
- No tile or panel is labelled Unattributed, Closed, underived, Newest episode or The deriver
- The review panel links to the knowledge manual under the documentation mount
Validation
- cargo test --lib ui::knowledge
- scripts/ui audit --only /ui/knowledge
Evidence required
- knowledge_screen_reads_in_review_order
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| knowledge_screen_reads_in_review_order | ci | validate run 39438896504 at master 9a5a9b77520: rust (1-3) jobs 118683336143 118683336062 118683336401 run cargo test, incl. ui::knowledge::the_screen_reads_in_review_order_with_plain_labels_and_the_manual (076312f8aef) | success (the run's only red job is pages, which runs no test) | a81b1e3 |
Timeline
- started
- 2026-10-20T16:15:13Z
- verified
- —
- completed
- 2026-10-20T16:27:11Z
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/I3023.yaml. Read it back with majordomus plan show I3023.