Usable graph foundation
Summary
The graph provides a uniform interface to expose arbitrary objects — state, code, files, world objects, conversations — through one linked structure. This goal is specifically about making graph browsing, editing, and linking feel natural, fast, and useful. It is not about the systems exposed through the graph (those are separate goals).
Why
If inspection, linking, filtering, and navigation are weak, expanding what the graph exposes will mostly create noise. We need a few strong universal interactions before building outward.
Success criteria
- Graph browsing and editing feel natural and fast
- Users can link tasks, notes, code, errors, files, and conversations seamlessly
- Graph-backed objects are easy to inspect, edit, and navigate
- The graph model stays view-agnostic so future interfaces (e.g. audio-first) can sit on the same structure
Features implementing this goal
- Graph Browsing — graph navigation and editing UX
- Graph Notebooks — notebooks exposed through the graph with identity references
Bugs
(none yet)
ADRs underlying this goal
- Graph as Universal Interface — why everything is exposed through the graph
- Composable States — input handling for graph interaction
Related
- Subsystems — Graph system, Widget system, Application model
- Project History — how the graph evolved across project phases
- Milestones (Milestone 1)
- Dev notes: Graph, Graph Identity, Graph Llm, Graph View As Widget, Graph Key Based Loaders, Graph Vs Entities