← Back to home

General plan / The policy

What an owner draws.

One policy sheet governs the whole yard. The fields, an example sheet, and the order in which rulings are made. This example is for a trading agent — it is not a default.

Sheet 03 · The policy
Scale 1 : vault
Fields 7
Revisions on-chain

Example sheet

# a RAILS policy — drawn once by the owner, revisable on-chain owner 0xYour…Owner # the key that draws agent 0xYour…Agent # the key that works inside halt disarmed # owner-only switch, outside reach routes allow swap dex.router # path: USDG → listed token allow collect pool.manager # harvest fees only deny * # everything else reverts axle per-tx 0.40 ETH per-hour 1.00 ETH per-day 2.00 ETH loop hold-above 0.50 ETH wait 6h # owner may cancel in-window

Values are an example for a trading agent — not defaults. If you can read this sheet, you can read the vault.

Fields

FieldWhat it setsExample
ownerThe key that draws rules, seals, unseals and cancels. Two-step transfer.0xYour…Owner
agentThe one key allowed to submit calls through the yard.0xYour…Agent
haltMaster switch. Sealed = nothing crosses, from either side.disarmed / armed
routesNamed contract + function pairs. Everything unnamed reverts.allow swap dex.router
axleThree ceilings: per-transaction, per-hour, per-day. Fixed clock buckets.0.40 / 1.00 / 2.00 ETH
loopHold-above threshold and delay. Owner may cancel queued calls in-window.> 0.50 ETH · 6h
revisionIncrements every time the owner redraws any field. Public history.rev 3

Order of ruling

  1. Buffer stop

    Sealed? Refused — for anyone but the owner.

  2. Interlocking

    Unnamed target or infinite approval? Refused.

  3. Axle limit

    Over a ceiling? Refused until the clock refills.

  4. Loop line

    Above hold? Queued for the delay window.

  5. Land

    The call crosses to the chain. Ruled, logged, public.

Every refusal reverts with the lever named — an agent always knows which signal stopped it. Ask any vault how it would rule on the table →