Skip to content

I2912 — A screen's sources are one disclosure, not a footer per panel

Fold every panel's source line into one \"Sources\" disclosure per screen, keeping each capability, its time and its technical-view link.

READY wave 0 · p2 · implementation profile · runs alone

Part of idd-reads-at-a-glance — The intent workspace reads at a glance and leads everywhere it names.

Ready. Every dependency is done, so majordomus plan start I2912 will be accepted.

Objective

Fold every panel's source line into one \"Sources\" disclosure per screen, keeping each capability, its time and its technical-view link.

Why

On 2026-10-18 the owner read the published /ui/idd three times and found it unergonomic: thirteen source footers repeat capability ids and timings under every panel.

Current state

A source footer per panel.

Desired state

One disclosure per screen.

Scope

  • apps/majordomus-cli/src/ui/shell.rs
  • apps/majordomus-cli/src/ui/view.rs
  • .ai/repo/project
  • docs
  • site

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

  • /ui/idd carries one Sources disclosure and no per-panel source footer

Validation

  • majordomus plan validate
  • scripts/ui audit --only /ui/idd

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started
—
verified
—
completed
—

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/I2912.yaml. Read it back with majordomus plan show I2912.

Searches the titles and descriptions of every page this site publishes.