Skip to content
Cockpit0.29.0
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

I1009

Every menu in this repository comes from one derivation

Where it stands

devtask.issue
Readiness
ready no dependency and no gate holds it; nobody has started it
Status
READY
Can start
startable
Milestone
capability-graph
Milestone status
ACTIVE
Wave
3
Waiting on
none
Holds back
I1016I1028
Behind it in all
5
Evidence
0 of 2

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1009

majordomus plan verify I1009

majordomus plan done I1009

What it is

Objective
Derive the desktop navigation, the mobile navigation, the Cockpit sections, the documentation navigation and the landing links from one projection of the graph, with deterministic grouping and ordering.
Why
Five menus mean five edits for one new page, and the fifth is the one everybody forgets. Grouping by facts the model already holds gives an order that is stable without anyone maintaining it.
Now
Navigation and landing content are assembled per surface. The landing page and the Cockpit each know their own entries.
Wanted
One navigation projection feeds every surface, grouping derives from kind, category, scope and availability, and ordering is deterministic.
Done when
unknown: the record declares no `completion`
Risk
Derived menus can order badly for a reader while being perfectly deterministic. Semantic grouping with alphabetic ordering inside it is the default; an authoritative order is metadata, never a template edit.

Acceptance

  • Every navigation surface reads the same projection, and none holds its own list
  • Grouping derives from metadata the model already carries, and ordering is deterministic and stable across builds
  • Adding a capability or a document changes every menu that should show it with no template edit
  • An entry unavailable in the current environment is not rendered as an active destination
Validation
cargo test --workspace --all-featuresbash test/run.sh
Evidence required
one_navigation_sourcedeterministic_order
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/cockpit/nav.rs
Not
Any hand-written menu entry in a template, a script or a data fileLayout coordinates, columns or component trees expressed as data
Depends on
I1004I1005
Priority
p0
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-09-06
Updated
2026-09-06
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.