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

I1012

One detail view, assembled from what a node actually has

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
I1026
Behind it in all
2
Evidence
0 of 3

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 I1012

majordomus plan verify I1012

majordomus plan done I1012

What it is

Objective
Render a capability's detail page from its populated sections and its resolved relations, with a stable deep link and a repository-relative reference to where the information came from.
Why
The question a detail page has to answer is where this thing actually comes from. A separate hand-written template per kind guarantees that answer is inconsistent, and a link built from a display title breaks the first time somebody improves the wording.
Now
The Cockpit renders views over the registry. Deep links and source traceability are not part of the model.
Wanted
One assembly renders any node, showing only populated sections, with a stable link and a repository-relative source reference.
Done when
unknown: the record declares no `completion`
Risk
Traceability that publishes a path from the machine that built the site is a leak. Repository-relative is the only form that ships.

Acceptance

  • Empty sections are absent rather than rendered blank
  • The deep link is built from the stable identity and survives a title change
  • Source references are repository-relative and never machine-absolute
  • The static projection produces compatible links
Validation
cargo test --workspace --all-featuresbash test/run.sh
Evidence required
detail_assembleddeep_links_stabletraceability
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/cockpit/view.rs
Not
A separate hardcoded template per kind unless the presentation genuinely differsA machine-absolute path in any published outputIdentity derived from a display title
Depends on
I1005
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-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.