Wealth Desk

get_dashboard

Read the Wealth Desk dashboard — the JSON payload the wealth.q5m.io SPA renders directly. Returns the current snapshot or null if no dashboard has been written yet. Scope resolves automatically from the session (household when bound, personal otherwise).

update_dashboard

Update the Wealth Desk dashboard with a JSON merge-patch (RFC 7396). Top-level keys merge recursively, arrays and scalars replace wholesale, null deletes a key. **Calling convention:** the merge-patch document goes inside a single `patch` argument — DO NOT spread `meta`, `netWorth`, etc. at the top level of the tool arguments. Correct shape: ```json { "patch": { "meta": { "asOfLabel": "...", "refreshedAtTitle": "..." }, "netWorth": { "value": "...", "delta": "..." }, "balanceSheet": { ... } } } ``` Wrong: `{"meta": {...}, "netWorth": {...}}` — that sends `patch=null` and the call is rejected. Send only the sub-trees you actually changed; siblings you omit (`tech`, `drawdown`, copy) stay intact. Scope resolves from the session automatically.

init_dashboard

Create the starting Wealth Desk dashboard. Use this once during onboarding when `get_dashboard` returns null — the SPA needs a fully-shaped payload to render at all, even before any real numbers are loaded. The tool writes a zero-state scaffold (empty rows, $0 totals, placeholder editorial) with the household identity values from `seed` applied. The first refresh fills in real balances. Refuses to overwrite an existing dashboard. If one already exists, the call returns an error and you should ask the user whether they want to reset (they almost never do).

get_refresh_log

Read the refresh history for this household / user. Returns the last entries (newest first) recorded by past Tier 1/2/3 refreshes — each entry includes `as_of`, `tier`, and a free-form `diff_summary`. Empty list if no refreshes have run.

append_refresh_log

Record a refresh in the household / user refresh-log. The store keeps only the most recent 30 entries — older ones are trimmed automatically. Use this once per refresh after writing the dashboard, so reviewers can see what changed and when.