DVT DASHBOARDS
The saved answers, on a wall. Every asset you SAVE in Chat with Martin appears as a card; RERUN LIVE executes its SQL through the same guarded virtualization path the chat uses — the databases answer now, so the number on the card is never stale. Saved charts render as charts (bar, line, pie, scatter); everything else renders as a table.
STARTING
dvt serve # the suite, dashboards included dvt dashboards # just dashboards (46108) dvt kill -s dashboards # stop it
WHERE ASSETS COME FROM
Dashboards is deliberately basic in v1: it does not edit, arrange, or create — the chat is where assets are born; this is where they live. Ask Martin something worth keeping, press SAVE ASSET on the result, name it, and it lands here (stored per project in .dvt/chat_saved.json — the query and the chart spec, never cached rows). REMOVE on a card deletes it from the same store the chat reads.
SECURITY POSTURE
Like every DVT app: binds 127.0.0.1 by default, and the actions that execute SQL or delete assets answer loopback only — even when the page is exposed with --host, a remote viewer can look but cannot run.