Portable HTML artifacts

One file.
Still semantic.

Orbweaver can package a complete interactive diagram into one durable HTML artifact—no framework, server, account, or host application required.

Authoritative source on GitHub ↗

Share a diagram without sharing its surrounding product. The portable artifact keeps the renderer, SVG, semantic inspector, selection behavior, provenance, and theme controls together in one file.

npx orbweaver-html graph.json
Semantic graph JSONmeaning, evidence, provenanceorbweaver-htmlderives layout and packages the artifactOne interactive HTML fileopen locally, share deliberately, archive durably
01

Generate an artifact

The command is already included with @semanticintent/orbweaver. Give it a graph JSON file and a destination; no separate CLI package is needed.

npm install @semanticintent/orbweaver

npx orbweaver-html northwind.json \
  --output northwind.html \
  --theme dark
Small distribution surface

The portable artifact is fully self-contained. Its recipient does not need Node.js, npm, Orbweaver, a network connection, or access to this website.

Download the generated Northwind example ↗
02

What travels with the diagram

  • Derived accessible SVG with the graph title and description.
  • Selection, relationship emphasis, keyboard interaction, and the semantic inspector.
  • Normalized graph semantics, annotations, provenance, and artifact version metadata.
  • Optional light and dark theme controls, all embedded in the file.
03

What stays behind

  • WebMCP site tools, model credentials, and host application callbacks.
  • Browser-local workspace state and any proposal acceptance decision.
  • Any claim that the static artifact can mutate its semantic source.

The artifact stays intentionally small: it explains and inspects already-derived meaning. Authoring, acceptance, and application workflows remain with the host.

04

Use it when the artifact needs to outlive the app