Skip to main content

​
Choose a prepared vault

Use a vault you are authorized to manage, with its setup checklist complete. Choose one configured yield source whose deposit input matches the vault underlying. Do not change a running production strategy for this exercise. Policy: deposit when idle assets exceed 10% of total assets, leaving a 7.5% reserve. These are teaching thresholds, not a production reserve recommendation. In Strategy, choose Add deposit strategy, name it Reserve deposit - inactive exercise, and select the prepared source and its asset-consuming deposit action. Leave indicators empty. The source and input token should match your selection; if the editor shows shares or an unknown size unit, stop and check Action Config.

​
Build the rule and size

In Rule tree, use an AND gate with these two conditions:
  1. vault_tvl > 0
  2. vault_free_assets > 0.10 * vault_tvl
The editor’s full-expression paste equivalent is:
Expect two comparisons joined by AND, not a JSON block or an && token. Both variables are raw underlying-asset units. Despite its name, vault_tvl is not USD TVL. Literal / Formatted changes the displayed state values, not the units of an existing expression. In Size expression, paste the complete raw-unit formula:
This deposits only the excess above the reserve. Use Copy to check the normalized expression: max ( vault_free_assets - 75 * vault_tvl / 1000 , 0 ). Whitespace may change; an extra decimals multiplier must not appear. Human-amount chips and full-expression paste are different input paths. Under Signal & risk, choose BINARY conviction and enter 60 in Cooldown (s). Set Max slippage (bps) and Signal lifespan to the approved values for your source. The editor sets per-strategy concurrency to one; there is no editable concurrency control. Cooldown starts after successful intent publication, not after the fill.

​
Review before creating

For a six-decimal underlying, these are evaluator expectations, not measured UI or transaction results: Check the selected source, input token, generated action, and reserve size together. This policy does not account for pending redemptions or other strategies spending idle assets; preserve those protections when adapting it to a real vault. Choose Create, then reopen the saved strategy. Confirm its ID/version, the two-condition rule, the normalized size, source, and action parameters. The state must be CREATED or IDLE, not RUNNING. If anything differs, leave it stopped and investigate. Saving writes configuration; it is not a test. Leave this exercise inactive. Simulation can select supported saved inactive strategies without starting them in production.

​
Update an existing strategy

  1. Open the intended strategy and record its ID, version, state, rule, size, and action plan.
  2. Before a risk-changing edit, stop new activity and check Intent History for in-flight work. Stopping does not cancel submitted transactions.
  3. Reload after the state change so the editor has the latest version.
  4. Make the bounded change. Preserve safety guards, reserve/redemption buffers, token units, and approved slippage; do not replace a production policy with this teaching example.
  5. Choose Save while inactive, reopen, and compare the saved version and complete definition. On 409 Conflict, reload and reconcile the other operator’s changes instead of blindly retrying.
  6. Review simulation and execution readiness. Start only after approval, then trace the first relevant intent and verify the resulting idle reserve.