swarmvault graph export

Export the graph workspace in one of several shareable or interoperable formats.

Usage

swarmvault graph export --html <output> [--full]
swarmvault graph export --html-standalone <output>
swarmvault graph export --report <output>
swarmvault graph export --svg <output>
swarmvault graph export --graphml <output>
swarmvault graph export --cypher <output>
swarmvault graph export --json <output>
swarmvault graph export --obsidian <output-dir>
swarmvault graph export --canvas <output>

Options

  • --html <output> — Full self-contained read-only graph workspace
  • --html-standalone <output> — Lightweight vis.js export with node search, legend, and sidebar inspection
  • --report <output> — Self-contained HTML graph report with counts, key nodes, communities, warnings, and page inventory
  • --full — For HTML exports, disable overview sampling and embed the full graph canvas
  • --svg <output> — Static shareable SVG diagram
  • --graphml <output> — GraphML export for external graph tooling
  • --cypher <output> — Cypher import script for Neo4j-style graph stores
  • --json <output> — Deterministic machine-readable graph payload
  • --obsidian <output-dir> — Markdown note bundle for Obsidian with one note per node plus community notes
  • --canvas <output> — Obsidian canvas grouped by community

What It Does

All export formats load the current state/graph.json and preserve stable node ids, edge relations, evidence class, confidence, communities, semantic-similarity metadata, hyperedges, and page metadata where the format can carry it.

For --html, SwarmVault also:

  1. Reads the current wiki pages referenced by the graph
  2. Embeds graph data, page content, and local output assets into a self-contained HTML file
  3. Inlines the graph viewer assets so the file can be opened without a server

Large HTML exports automatically enter the same overview mode as graph serve once the graph exceeds 5,000 nodes, showing the strongest communities and bridge points first. Use --full if you want the exported HTML to embed the entire graph canvas instead.

Use this when you want to share the graph workspace without running swarmvault graph serve.

Standalone exports keep graph navigation, search, page preview, project metadata, graph report pages, and chart/image previews, but review and candidate actions stay disabled because the exported file is read-only.

--html-standalone is the lightweight alternative: it writes a smaller vis.js-based file with graph search, a legend, and sidebar inspection, but without the full embedded viewer app.

--report is lighter still: it writes a static HTML status report built from state/graph.json and wiki/graph/report.json, including node and edge breakdowns, top bridge or god nodes, community sizes, warnings, and a grouped page inventory.

--json writes a normalized payload with sorted nodes, edges, communities, hyperedges, and export metadata, so downstream tools can consume the graph deterministically.

--obsidian writes an Obsidian-friendly markdown bundle with one note per node plus community summary notes that use wikilinks for graph connections.

--canvas writes a single Obsidian canvas file that groups nodes by community and preserves graph edges as canvas connections.

The deterministic graph query, graph path, and graph explain actions remain part of the live graph serve and MCP surfaces for now.

For --graphml and --cypher, SwarmVault encodes each hyperedge as a synthetic hyperedge node plus group_member relationships so external graph tooling can preserve group-pattern structure even though those formats are pairwise by default.

You can combine multiple output flags in one run to write several export formats at once.

If you want a live Neo4j sink instead of an import script, use `graph push neo4j`.