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

I2652

The UI shows what the knowledge base holds: the candidates awaiting review and whether the deriver still writes, read and never acted on

Where it stands

devtask.issue

Readiness: ready no dependency and no gate holds it; nobody has started it
Status: READY
Can start: startable
Milestone: development-runtime
Milestone status: ACTIVE
Wave: 2
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 0 of 3

Moves

plan.transition

What it is

Objective: Give the queue the work leaves behind a screen: what awaits a reviewer, what it is about, and whether a derivation still follows every closed episode, so that the result of a review is seen where every other state of the delivery is.
Why: The owner, 2026-10-13: bring /evolve into Majordomus as a derived skill that improves the know-how in .ai/, with its result visible on /ui and on Pages; no new systems, only connect, derive, project. The skill is another session's; this is the half a reader sees. Every organ exists: knowledge_base.status and knowledge_base.candidates answer the questions, and no screen asks them.
Now: Measured on master 3442ce68c5 on 2026-10-13: the UI has thirteen screens and none names the knowledge base; src/ui mentions it only in passing in roadmap.rs and deployments.rs. The candidates are read from the command line, MCP and HTTP alone.
Wanted: A screen at /ui/knowledge reads knowledge_base.status and knowledge_base.candidates as readings and draws: how many records await review, on this branch and unattributed; the deriver's judgement in words with every finding; the subjects the records are about; and the newest candidates, bounded, each leading to its record, with what is left out counted. The review is named as the commands a person runs, as text. The screen stands in the navigation, in the published snapshot and under the UI's latency budget.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Acceptance

/ui/knowledge answers from knowledge_base.status and knowledge_base.candidates and names both as its sources with their age
A queue longer than the screen's bound is drawn newest first to the bound and says how many records it left out
An empty queue and a checkout where the deriver never ran are said in words, never as an empty table or an empty cell
The page carries no form and no button: the review is the commands a person runs, shown as text
No handler under src/ui executes a capability on the request, which case 1096 holds, and the route is within the UI's latency budget, which bench --check holds
Every screen's navigation leads to it

Validation: bin/majordomus plan validatecargo test --manifest-path apps/majordomus-cli/Cargo.toml --lib ui::knowledgeMJ_TEST_JOBS=2 bash test/run.sh 3003_the_knowledge_screen_answers 1096_no_screen_waits_for_a_sourcemajordomus bench system.http. --transport system --profile ci --no-write --check
Evidence required: knowledge_screen_unit_testsknowledge_screen_case_3003knowledge_screen_within_budget
Evidence present: unknown: the record carries no `evidence` entries

Scope

Touches: apps/majordomus-cli/src/ui/knowledge.rsapps/majordomus-cli/src/ui/mod.rsdocs/MAJORDOMUS_UI.mdtest/cases/3003_the_knowledge_screen_answers.sh.ai/repo/project/issues/I2652.yaml
Not: Promoting or rejecting a record from the screen: a screen reads and never executes (ADR 0142), and promotion is a person's actThe evolve skill itself and its projection as a command, which are another session'sA panel on the dashboard and a link from the Command screen, which follow once the application shell another session is building has landedA change to what knowledge_base.candidates answers
Depends on: I2486
Priority: p1
Profile: implementation
Parallel safe: true
Owner: unknown: the record declares no `owner`

The work so far

Branches: none
Merged: none
Commits: 0
Trunk: master
Sessions: none
Created: 2026-10-13
Updated: 2026-10-13
Started: unknown: the record declares no `started_at`
Verified: unknown: the record declares no `verified_at`
Completed: unknown: the record declares no `completed_at`

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.