Scopes

A Scope controls which graph nodes are available to its representations. It is separate from those representations, so the same nodes can be arranged on several Canvases without being copied.

Start with Global

Every project has one Global Scope. It is the default unfiltered view and always includes every current project node. New nodes appear in Global automatically.

Global cannot be renamed, deleted, or have nodes added or removed manually. It can have any number of Canvas representations.

Create a focused Scope

Open Scopes in the sidebar and choose New Scope. Enter a name and choose Create Scope, or press Cmd/Ctrl+Enter. Names are required and can contain up to 200 characters. If the name is empty, the form focuses Name so you can fill it in.

The form locks while saving. If creation fails, it focuses a readable error and keeps your name so you can try again. Before saving, Cancel or Esc closes the form without creating a Scope.

If you leave while creation is pending, a successful request adds the Scope to the list without reopening it over your current page.

The new Scope starts empty and opens on its Nodes tab. Creating a Scope does not create a Canvas automatically. Add only the nodes and representations you need.

The Scopes list shows node and representation counts. Select a Scope to open it. Global is always first. For other Scopes, use the trash action to delete the Scope after confirmation. This also removes its Canvas representations from the workspace, but graph nodes and their data remain.

Temporary refresh failures keep rename drafts, the selected tab, and open creation forms. Choose Retry in the notice to reload saved data without submitting your edits. In New Scope and New Canvas, the notice appears inside the dialog.

Initial load failures offer Retry before editing. Access denials or missing required data block editing.

Manage nodes

For a focused Scope, use Add node on the Nodes tab to open a centered modal and pin an existing project node or create a one-off node. Search filters the current Scope by node name, type, or ID. Global’s Nodes tab is read-only because its membership follows the graph automatically.

Selecting a node closes the picker and moves focus to Search Scope. The page shows Adding node to Scope… and disables membership actions while saving. If adding fails, the page shows the error. Choose Add node again to retry. A newly created node remains in the project if adding it to the Scope fails; select that existing node to retry without creating another.

Removing a pinned node from a Scope asks for confirmation. It also removes that node’s placement from every Canvas representing the Scope unless a dynamic rule still includes it. The graph node and its data remain in the project.

Nodes marked Dynamic are controlled by a rule and cannot be removed individually. Open Rules to remove the rule instead.

Edges between Scope nodes are included automatically. They are not separate Scope entries.

Add nodes with a query

Choose Add with query on Nodes, or New rule on Rules, to open a fresh whole-graph query. Build the question, choose Find nodes, then use Add to Scope beside the results below it. The Scope you came from is selected automatically. If you edit the question, results show Query changed until you choose Update results; Add to Scope uses the last successful question.

The complete query contributes every anchor and connected node, including matches beyond the currently loaded result page. Returned edges are not stored as Scope members.

• Add once evaluates the query in its selected Scope or Atlas context and at the currently viewed project time. Its matches become pinned members that you can remove individually.
• Keep updated saves a dynamic rule. It is available only for Global queries and evaluates the all-time graph. When the Scope is loaded or used, new matches join and nodes that no longer match leave.

Dynamic membership does not place new nodes on a Canvas automatically. It makes them available to every representation of the Scope. When a node leaves a Scope, its placements are removed from those Canvases; the graph node remains.

The Rules tab shows each live query and its current node count. Deleting a rule removes nodes included only by that rule, along with their Canvas placements. Pinned nodes and nodes included by another rule remain. If a rule cannot be evaluated, the tab shows the error and keeps its last successful membership until the query can run again or the rule is deleted.

Add Canvas representations

Open Representations and choose New Canvas. Enter a name and choose whether the Canvas uses All time or Follow project. All time is selected initially. Choose Create Canvas or press Cmd/Ctrl+Enter to save.

Canvas names are required and can contain up to 200 characters. An empty name returns focus to Name. Saving locks the name and time controls; a failed request focuses the error and keeps both choices so you can try again. Before saving, Cancel or Esc closes the form without creating a Canvas. If you leave while creation is pending, a successful request adds the Canvas to the Scope’s representations without reopening it over your current page.

Each Canvas keeps its own positions, connector routes, and viewport. Adding a node to a Canvas also adds it to the Scope. Removing a placement from one Canvas keeps the node in the Scope and does not affect other Canvases.

Use the pencil action to rename a Canvas. Deleting a Canvas leaves the Scope and its nodes intact.

For a focused Scope, use the pencil beside its title to rename it without renaming any of its Canvases. Global keeps its fixed name.

For either rename, choose Save or press Enter. Cancel or Esc keeps the previous name. Enter and Escape ignore modifier keys and wait until text composition has finished. Saving locks the name and rename controls. A failed save keeps your draft and focuses a scrollable error; correct the name or press Enter on the error to retry. Finishing or cancelling returns focus to that rename action unless you have moved to another control.

See Relational Canvases for editing controls, or run a Query against the Scope.