← All goals

Objective: A local-only desktop tool — one downloadable file, no network, no install

Goal issue #330 · slug desktop

0/3 member issues closed

Other open members 3

no readiness label yet.

• #336 the single-file build — every script, style and the demo data inlined into one HTML file under a size budget (Backlog · safety · status: backlog)
• #337 persistence and export — save and reload a study configuration from the desktop file; export a chart as an image and its settings JSON (Backlog · safety · status: backlog)
• #338 release, guide and demo — the download on the site, a user guide page, and the talk demo run end to end on a clean machine (Backlog · safety · status: backlog)

Direction

Intent

@jwildfire, 2026-09-10: the desktop app is safety.viz-native, a self-contained local HTML and JavaScript app; the open.gismo app arc parks for the talk. A single downloadable file combines the loader and the portfolio, opens from the desktop with no network and no install, saves and reloads a study configuration, exports charts, and is released with a user guide and a rehearsed talk demo (plan, 2026-09-10, objective 5, lane A).

Definition of done

End state: a single HTML file, downloadable from the safety.viz site, inlines every script, style and the optional demo dataset; it opens from a file URL in current Chrome, Safari and Edge with no network and no install; it loads a user's files, saves and reloads a study configuration, and exports any chart as an image and its settings as the JSON that drives the static twin; a user guide page is on the site and the talk's demo script runs end to end on a clean machine.

Proof: the release on the safety.viz site carries the download and the build log prints the file's size within the stated budget; a fresh-machine test documented in the release notes, with its steps and screenshots, opens the file offline and runs the demo script; the user guide URL and the demo script are quoted in the closing comment; every requirement below is closed with its proof comment and the release tagged.

Ships in: safety.viz v2.0.0 (proposed), milestone 2026-10-talk.

Requirements

In session order:

1. The single-file build: every script, style and the demo data inlined into one HTML file under a size budget (#336).
2. Persistence and export: save and reload a study configuration from the desktop file; export a chart as an image and its settings JSON (#337).
3. Release, guide and demo: the download on the site, a user guide page, and the talk demo run end to end on a clean machine (#338).

Boundaries

• Runs on lane A, third; it composes the portfolio view (#79) and data loading (#329) objectives and does not reopen their scope.
• No Electron, no installer, no service worker that needs a server: a file URL is the whole deployment.
• Export is an image per chart and the settings JSON that the static parity objective's twins (#328) accept; no code export.
• A stated size budget is part of the first requirement's definition of done and is not raised mid-session.
• The demo rehearsal is the last requirement and is what the week 5 must-show is judged on.

This issue was drafted by Claude Code using Fable 5.1 from the plan of 2026-09-10, on @jwildfire's in-session approval to file it; the body is his to edit and the tree is signed off only by his comment here.

Members are generated from the objective issue's sub-issue links at build time; priority is the selecting session's judgment, not list order (#53 v2). The --auto policy binding — active/paused, grant profile, repo-level backlog feeds — lives in obot.agent/goals/registry.json. Readiness labels: auto = ready for autonomous implementation, draft = needs @jwildfire steering.