Export JSON
The web frontend exports a single JSON payload that combines semantic graph state and render state. It is meant for debugging, offline inspection, and interop with other tools.
Top-Level Shape
{
"exported_at": "...",
"semantic": { ... },
"render": { ... }
}
semantic
The semantic section captures the logical graph state used by the explorer:
- active filters
- summary metadata
- currently visible nodes and edges
- query-context metadata such as
node_appearance
This is closer to the backend query result shape than to the rendered canvas.
render
The render section captures frontend-specific layout information:
- positioned nodes
- routed edges
- viewport-oriented export fields
This is what lets the exported payload preserve the current visual state.
Difference From Live Query Responses
Live query responses are backend protocol payloads.
Export JSON is a frontend artifact that intentionally combines:
- backend-derived semantic state
- frontend-derived render state
That makes it suitable for debugging and artifact sharing, but it is not the canonical backend protocol.