AI assistants and vault requests: previewing data before signing

A Desk request has more moving parts than a sentence such as “deposit into a vault.” There is a provider snapshot, an asset and amount, a wallet transaction, a settlement record, and possibly a later activity credit. An assistant is most useful when it keeps those layers separate.

Start with the provider view

Before discussing a request, read the fields the service actually publishes: configured state, collateral asset, positions, performance values, history range, and any unavailable fields. The participant kit’s suibrokers_get_desk tool reads the public Desk snapshot and a bounded history range. If the provider or ledger cannot supply a value, the tool preserves that gap as unavailable; it does not turn a missing NAV, APR, PnL, or cashflow into zero.

Ask the assistant to repeat the source.origin and source.asOf values beside the summary. That small detail prevents a yesterday’s snapshot from sounding like a live quote.

Prepare a request without pretending to execute it

For a possible deposit or withdrawal, suibrokers_prepare_action can create a review plan for desk_deposit or desk_withdraw. It includes the app route, whether a wallet signature will eventually be needed, and the next review steps. It does not choose the collateral asset, build a transaction, sign, submit, activate a referral, or request an instant payout.

A good preparation prompt is:

Read this Desk snapshot. Separate provider facts, missing fields, request inputs, wallet checks, and settlement evidence. Prepare a review-only deposit plan for the amount I supplied. Do not estimate a return or claim that a withdrawal will be immediate.

The reader still chooses the configured asset in the app, connects the intended wallet explicitly, and reads the final transaction in the wallet. A withdrawal request is a request to the service, not proof of immediate payment.

Keep Points out of the preview

An estimated activity value can help with planning, but it is not a verified credit. Desk Points belong to a service ledger record that ties the action to the wallet, provider evidence, and the relevant stage. A model cannot make a preview authoritative by repeating it.

This is also why Desk performance and seasonal progress need separate labels. A performance figure describes the provider-backed position or history available at the time of reading. Points describe an eligible activity record after confirmation. Neither number guarantees a return, liquidity, qualification, or Broker NFT allocation.

Suppose a snapshot shows a position and a blank APR field. The correct explanation is “APR is unavailable in this response.” Suppose a later history row is marked pending. Keep it pending until the service records settlement. The Points and Broker NFTs guide explains the qualification boundary; the Desk comparison explains why similar words can describe different managed-exposure jobs.

What the assistant can add

Use it to translate “share balance” or “history range,” compare two dated snapshots, prepare questions for the provider, and format a journal with amount, asset, digest, status, and readback time. Ask it to quote the source field for each conclusion. If data is partial or unavailable, make that the conclusion.

The safe workflow ends with a human review of the app and wallet prompt, followed by confirmed service readback. A clear preview helps you decide what to inspect. It does not turn provider data into a promise or a draft into a settled Desk action.