I1014 — The relation view reads the graph and holds no data of its own
Render the relation graph interactively from the generated data, with filters, focus, neighbour highlighting and deep links, loaded only where it is used and bounded in cost.
BLOCKED wave 4 · p2 · implementation profile · parallel safe
Blocked. This issue cannot start until I1007 is done. The status is derived from that, not declared.
Objective
Render the relation graph interactively from the generated data, with filters, focus, neighbour highlighting and deep links, loaded only where it is used and bounded in cost.
Why
The edges are the reason the model exists, and a static list cannot show them. But a visualisation with nodes written into a script is a second inventory in the least maintainable place available.
Current state
The layer's graphs are derived and rendered for the site. There is no interactive relation view over the composed model.
Desired state
One view reads the artifact, filters by the model's own fields, and is not loaded by pages that do not use it.
Scope
- share/cockpit/src
Out of scope
- Nodes or edges written into JavaScript
- A visualisation library loaded on pages that do not render a graph
- A three-dimensional rendering that replaces rather than supplements the accessible information
Dependencies
- I1002DONE Relations are typed, inferred from stable identities, and never dangle
- I1007READY The site renders the same graph, generated once
What waits on this
- I1021BLOCKED A browser proves the interface, at the widths people use
- I1024BLOCKED The interface has a weight, and it is measured
Acceptance criteria
- Every node and edge comes from the generated data
- Filters operate on the model's fields — kind, category, source, surface, availability, relation type and the evidence flags
- Zoom, pan, selection, neighbour highlighting, a detail panel and deep links all work, and a selected node resolves to its detail view
- The library is lazily loaded and absent from pages without a graph
- A textual equivalent of the same relations is available for anyone who cannot use the graph
- Initialisation cost on this repository's data is measured
Validation
- bash test/run.sh
- cargo test --workspace --all-features
Evidence required
- graph_from_data
- filters_work
- textual_equivalent
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Risk
Rendering every node at once is slow and unreadable at the same time. The default view is filtered, and expansion is progressive.
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/I1014.yaml. Read it back with majordomus plan show I1014.