Skip to content

I1012 — One detail view, assembled from what a node actually has

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.

READY wave 3 · p1 · implementation profile · parallel safe

Part of capability-graph — One capability graph, two projections, and no second inventory of what this repository can do.

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

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.

Current state

The Cockpit renders views over the registry. Deep links and source traceability are not part of the model.

Desired state

One assembly renders any node, showing only populated sections, with a stable link and a repository-relative source reference.

Scope

  • apps/majordomus-cli/src/cockpit/view.rs

Out of scope

  • A separate hardcoded template per kind unless the presentation genuinely differs
  • A machine-absolute path in any published output
  • Identity derived from a display title

Dependencies

What waits on this

Acceptance criteria

  • 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-features
  • bash test/run.sh

Evidence required

  • detail_assembled
  • deep_links_stable
  • traceability

Evidence

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

Risk

Traceability that publishes a path from the machine that built the site is a leak. Repository-relative is the only form that ships.

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