Exports: PNG, SVG, CSV
Orgonaut exports are designed for communication and follow-up analysis.
Use them to move from modeling to review conversations quickly.
Astro can also trigger these exports from the current chart or matrix surface. For example:
Export this matrix as CSV.Download this chart as PNG.
Export availability by view
Matrix
Matrix supports:
- PNG export
- SVG export
- CSV export
Access from the Matrix toolbar export menu.
Charts
Charts currently supports:
- PNG export
Access from the Charts toolbar export button.
When you ask Astro for an unsupported export format in the current view, it responds with the supported format for that surface and, when useful, a route-backed follow-up into a visualization that does support the requested export.
What gets exported
Exports represent the current visualization payload and filters.
That means:
- active filters affect what appears
- hidden branches/teams are not included
- exports reflect current context (live/scenario/snapshot)
PNG and SVG behavior
For image exports, Orgonaut normalizes rendering for clean output:
- reset to full-canvas framing
- apply export-safe background
- include padded layout for readability
This is why exported files can look broader than your current on-screen zoom viewport.
CSV behavior (Matrix)
Matrix CSV is a structured flat export of current matrix content, including key fields such as:
- team type
- team
- actor identity
- role info
- position metadata where available
- allocation and primary indicators
Use CSV when you need to audit structure outside the UI or merge with external analysis.
Astro and the change tray
Inside a mutable scenario, Astro can also bridge compatible natural-language modeling requests into the existing chart or matrix change tray instead of creating a parallel write system.
That means Astro can:
- trigger a visualization export immediately
- prepare a compatible modeled change
- send that change into the current scenario tray for human review in the existing workflow
This bridge is limited to requests the current visualization tooling already understands. Unsupported requests stay on Astro's normal governed action or read-only surfaces.
Naming and versioning
Exports use timestamped filenames so you can version review artifacts naturally.
For formal reviews, include scenario name/date in your own file management conventions.
Practical export checklist
Before exporting:
- confirm context (baseline vs scenario)
- set filters intentionally
- sanity-check unassigned and key teams
- choose format based on audience:
- PNG/SVG for slides and docs
- CSV for analysis and QA