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
I1014
The relation view reads the graph and holds no data of its own
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
4- Waiting on
- Holds back
- Behind it in all
4- Evidence
0of3
| In the way | Subject | Detail |
|---|---|---|
| issue | I1007 | I1007 is not DONE |
Moves
plan.transitionWhat it is
- 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.
- Now
- The layer's graphs are derived and rendered for the site. There is no interactive relation view over the composed model.
- Wanted
- One view reads the artifact, filters by the model's own fields, and is not loaded by pages that do not use it.
- Done when
- unknown: the record declares no `completion`
- Risk
- Rendering every node at once is slow and unreadable at the same time. The default view is filtered, and expansion is progressive.
Acceptance
- 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.shcargo test --workspace --all-features- Evidence required
graph_from_datafilters_worktextual_equivalent- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
share/cockpit/src- Not
Nodes or edges written into JavaScriptA visualisation library loaded on pages that do not render a graphA three-dimensional rendering that replaces rather than supplements the accessible information- Depends on
- Priority
- p2
- 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.