Support multiple saved graphs over the local corpus #53

New issue

Closed

opened 2026-07-26 01:03:43 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-26 01:03:43 +00:00

(Migrated from github.com)

Parent: #2
Related: #16

Problem

Quasar currently exposes one implicit graph projection over the entire local corpus. Investigations need multiple distinct graphs without duplicating canonical StarIntel documents.

Scope

Add a persistent saved-graph registry to Quasar application state.
Keep an initial dynamic All documents graph for backward compatibility.
Let users create, rename, switch, and delete saved graphs.
Store per-graph document membership by stable document ID.
Store per-graph positions, viewport, layout, and selection.
Start new graphs blank.
Add manual nodes, manual relations, actor output, and opened imports to the active graph.
Keep graph deletion separate from corpus document deletion.
Migrate the existing single-workspace state into the All documents graph.

Acceptance criteria

A user can maintain at least two graphs and switch between them without losing state.
The same canonical document can appear in multiple graphs without duplication.
A new graph starts blank and can be populated manually, by import, or by actor output.
Each graph restores its own membership, positions, layout, viewport, and selection.
Deleting a graph does not delete any StarIntel document.
Existing users retain their prior graph view as All documents.
Unit and browser tests cover migration, creation, switching, membership, and deletion.

Parent: #2 Related: #16 ## Problem Quasar currently exposes one implicit graph projection over the entire local corpus. Investigations need multiple distinct graphs without duplicating canonical StarIntel documents. ## Scope - Add a persistent saved-graph registry to Quasar application state. - Keep an initial dynamic All documents graph for backward compatibility. - Let users create, rename, switch, and delete saved graphs. - Store per-graph document membership by stable document ID. - Store per-graph positions, viewport, layout, and selection. - Start new graphs blank. - Add manual nodes, manual relations, actor output, and opened imports to the active graph. - Keep graph deletion separate from corpus document deletion. - Migrate the existing single-workspace state into the All documents graph. ## Acceptance criteria - A user can maintain at least two graphs and switch between them without losing state. - The same canonical document can appear in multiple graphs without duplication. - A new graph starts blank and can be populated manually, by import, or by actor output. - Each graph restores its own membership, positions, layout, viewport, and selection. - Deleting a graph does not delete any StarIntel document. - Existing users retain their prior graph view as All documents. - Unit and browser tests cover migration, creation, switching, membership, and deletion.