I3020 — The Knowledge screen states nothing about the repository that its checkout could not observe
Where knowledge_base.status read no line of the session ledger (no close, no derivation, no close without a derivation), /ui/knowledge shows the ledger-derived tiles (Closed, underived; Newest episode) as 'not recorded here' and its deriver panel says that no ledger is recorded in this checkout and where the judgement is made, instead of '0', 'unknown' and 'never, in this checkout'.
DONE wave 0 · p0 · implementation profile · parallel safe
Objective
Where knowledge_base.status read no line of the session ledger (no close, no derivation, no close without a derivation), /ui/knowledge shows the ledger-derived tiles (Closed, underived; Newest episode) as 'not recorded here' and its deriver panel says that no ledger is recorded in this checkout and where the judgement is made, instead of '0', 'unknown' and 'never, in this checkout'.
Why
The published snapshot of /ui/knowledge (majordomus.dev, v0.29.0 at 707a04c7ce8) read 'Closed, underived 0', 'Last derived: never, in this checkout', 'Last closed: never, in this checkout' and 'Judgement: not judged'. The Pages runner is a fresh clone with no session ledger; a visitor reads those as facts about the repository's knowledge base. Candidate counts are tracked records and stay as read.
Current state
The screen draws every status field as read, so a checkout with no ledger shows zero and never.
Desired state
A tile or a panel whose value comes from the session ledger says it is not recorded here when the status read no ledger line; a crate test pins it.
Scope
- apps/majordomus-cli/src/ui/knowledge.rs
Dependencies
None. This issue is a root of the graph.
Acceptance criteria
- In a checkout without a session ledger, the Closed, underived and Newest episode tiles read 'not recorded here' and still cite knowledge_base.status
- The deriver panel names no 'never' there and names majordomus knowledge status as where the judgement is made
- A checkout whose ledger holds a close keeps its counts and judgement as read
Validation
- cargo test --lib ui::knowledge
- scripts/ui audit --only /ui/knowledge
Evidence required
- knowledge_screen_reads_true
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| knowledge_screen_reads_true | ci | validate run 39438896504 at master 9a5a9b77520: rust (1-3) jobs 118683336143 118683336062 118683336401 run cargo test, incl. ui::knowledge::a_checkout_without_a_ledger_states_nothing_it_could_not_observe (4767d1be4fe, 6afb1240313) | success (the run's only red job is pages, which runs no test) | a81b1e3 |
Timeline
- started
- 2026-10-20T16:14:31Z
- verified
- —
- completed
- 2026-10-20T16:24:44Z
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/I3020.yaml. Read it back with majordomus plan show I3020.