Tessera Viz
PX-02
Intelligence and law enforcement
Connect the dots faster — who, what, where and when.
The product of this work is a briefing, and a briefing has to leave the building. That shapes everything: what the chart can show, what it can export, and where it is allowed to run.
01
03
Everything a briefing needs, on one screen.
01
What the analyst gets
Entity-link charts, combos for grouping, narrative annotations for briefing products, and export to PNG, SVG and PDF for the report that leaves the building.
02
Combos
Group entities into a single node, expand and collapse, and drill down. The grouping is computed over your data rather than baked into it, so a different grouping is a different call and not a different dataset.
03
Air-gapped is the headline
Not a footnote. No third-party runtime dependencies means an install is a file copy and a security review is one review of one codebase.
04
Including the map
Offline tile packs ship with the application, so the geographic view draws from disk. This is the deployment most mapping vendors cannot do, because their renderer phones home.
05
Vector export that is really vector
A PDF that goes into a briefing pack is read at whatever size the reader chooses. Export is geometry, not a screenshot at a fixed resolution.
06
An honest limit
The Canvas and WebGL renderers draw pixels, not elements. For a screen-reader-critical surface use the SVG renderer, or the grid as a table alternative. We would rather say so here than have it found in an accessibility audit.
02
And with an agent
03
Ask in words. Get the link chart back.
01
What it changes here
A briefing product that took an afternoon of layout work becomes a request. The analyst still decides what is true; what goes away is the hour between deciding it and having a chart that shows it.
02
A document, not a picture
The model returns one JSON document — the graph, the layout, the algorithm, the theme — and the library draws it in the page. Nothing renders server-side, so there is no image to regenerate when the next question changes the filter.
03
Checked before it draws
The document is validated first. A field the model invented comes back as a list of issues rather than as a blank panel or a thrown error, which is the difference between an agent that can be trusted in front of an analyst and one that cannot.
04
It can arrive as it is written
The stream reader takes the document while the model is still producing it, so a large graph starts appearing at the first complete object instead of after the last token.
05
MCP carries it; this draws it
Expose that document as the return value of an MCP tool and an agent draws straight into the conversation. The library does not implement MCP, any more than an image decoder implements HTTP — it is the renderer at the end of whichever transport you already run.
06
Why this is possible at all
Because the drawing runs in the browser and takes its instructions as data. A library that renders server-side hands an agent a picture; this one hands it a surface that the next question can change.