01
Prepared
An action is assembled with route, accounts, amount, quote age, and expected output.
Security model
FlowVault is the review layer around the signing moment. It stores policy, action metadata, simulation output, and receipts. It does not custody funds, hold seed phrases, or replace the wallet as signer.
Boundary summary
Transaction path
The reviewer sees risk and context before the wallet prompt, and the record is written after the decision.
01
An action is assembled with route, accounts, amount, quote age, and expected output.
02
FlowVault presents expected balance changes, fees, failure states, and route warnings.
03
Workspace policy decides pass, review required, or blocked before signing.
04
The connected wallet signs. FlowVault does not receive private keys or seed phrases.
05
Decision context and transaction signature become a receipt for later review.
Storage boundary
The wallet remains the authority for signing. FlowVault explains the request and records the decision.
Expected token deltas, fees, quote age, and failure conditions are surfaced before a reviewer approves.
Amount, token, route, quote freshness, and slippage rules determine whether the action proceeds.
Reviews, policy state, signer, transaction signature, and rejection reasons stay attached to the action.
policy gate
Checks that run before the wallet prompt
before wallet prompt: require simulation.status == 'ok' require route.quote_age < 30s review if route.price_impact > 0.30% block if token_mint not in allowlist record reviewer + signer + signaturereceipt trail
The decision record after signing
receipt 5xK...9Qa action: Raydium swap reviewed_by: you policy: review_required -> approved signer: connected_wallet saved: route + simulation + tx signatureRead next
Continue with review card anatomy, Raydium route evidence, and policy examples.