Suggested Actions#

When Ava warns you, it doesn't stop at the warning. It builds a concrete, fire-time proposal — now, with the assets you actually hold right now — and shows you the simulated outcome before asking you to confirm.

This is the core difference from rule-based automation tools where you commit to a single rule months in advance ("if HF < 1.3 → repay 300 USDC with ETH") and pray your wallet still looks like it did when you wrote the rule.

How a suggestion is built#

1. Trigger fires. A risk crosses a threshold (e.g. HF dropped to 1.3).
2. Live wallet read. Ava looks at what's actually in your wallet at this moment — 500 USDC, 0.2 WETH, 50 LINK.
3. Candidate actions. Ava enumerates the fixes that would resolve the risk inside your spend caps. For HF, that's typically a top-up; sometimes a small partial repayment is cheaper.
4. Ranking. Ava prefers the simplest action that uses an asset you have plenty of, minimizes slippage, and stays well inside your caps.
5. Simulation. Ava simulates the action against the latest on-chain state and shows the result: supplying 300 USDC lifts HF 1.3 → 1.9.
6. Present. A short proposal lands in chat with [ ✅ Confirm ] and [ Adjust ].

What a suggestion looks like#

Simulated: supplying 300 USDC lifts your health factor 1.3 → 1.9 — safely clear of liquidation. Gas ≈ $0.40. Non-custodial — funds never leave your wallet.

[ ✅ Confirm ] [ Adjust amount ]

Three things to look at:

• The result. 1.3 → 1.9. Not vibes — a number, simulated against live state.
• The cost. Gas ≈ $0.40. Ava tells you the cost before the cost happens.
• The asset choice. Ava picked USDC because you have plenty. If you'd rather use WETH or LINK, tap Adjust.

Adjusting a suggestion#

Tap Adjust or just say it: "use WETH instead", "top up by 500 not 300", "do half that". Ava re-simulates and re-presents. Each re-presentation is a fresh confirmation gate. Nothing happens until you tap ✅.

Rejecting a suggestion#

Tap Adjust → Cancel, or say "no thanks". Ava goes back to watching. It will warn again if the risk gets worse, but it won't re-propose the same fix in a loop.

Why fire-time matters#

Conditions change. The 300 USDC you had last week might already be deployed elsewhere by the time HF drops. A rule that says "repay 300 USDC with ETH" breaks silently when the assumption breaks. Ava re-reads your wallet at fire time, so the proposal is always executable with what you actually have.

If you have nothing that can resolve the risk inside your caps, Ava says so:

⚠️ You're at HF 1.3 but I can't see anything in your wallet I'm authorized to use to top up. Want to add USDC, or raise the spend cap?

It will not silently fail, and it will not act outside your caps.