Automations with limits: why every run in Burokku answers to you

An automation is an instruction you give once and stop watching. That's the point of it, and also the risk: the moment it matters most is usually the moment you're asleep or looking at something else. A workflow that does something you didn't mean, with your money, while you're away, is what we built Burokku's automations to prevent.

So every automation answers to a few rules. None of them is a setting you can forget to tick; they're how a run works.

Nothing runs that you haven't read

You can build a workflow on the canvas, start from a template, or describe it to Burokku AI in a sentence. Either way, you see every step first.

• A draft from Burokku AI is a proposed change. The canvas marks new, changed and removed steps, and the review lists every setting before and after. Nothing changes until you choose Accept; Discard drops it.
• Some steps Burokku AI never adds. Webhooks, transfers and exchange orders are only ever set up by you.
• History keeps each version with who made it: you, Burokku AI, or both, when you edited its change before saving. You can see what any version changed and restore it.
• A test run changes nothing. It walks every step with real prices and your portfolio and shows what each would do. Nothing is sent, signed or traded.

The guide to setting up your first automation goes through building and testing one.

Most steps get money ready instead of moving it

When a workflow reaches a step that moves money, it usually hands the decision back to you. A swap from your own wallet becomes a link to review and sign, and the run waits under "Waiting for you" for up to 48 hours. An exchange order opens for you to confirm. A repay, deposit, claim or revoke opens its review for you to sign. A transfer becomes a request you approve with your passkey, and it can only go to one of your own connected wallets.

One money step acts by itself: a trade from your trading wallet. That wallet is owned by your passkey, and Burokku can trade from it under rules only your passkey changes; it can never send funds out of it. Even then, each trade has to pass three checks every time it runs.

Three checks on every trade that runs by itself

Automations are switched on. One switch in Settings → Security covers your whole account: on, paused or off. Turning it on needs a second step (a passkey or an authenticator app), unused backup codes, agreeing to a warning about what automations can do, and a fresh check with that second step. Pausing or turning it off never asks for anything. The switch is read again before every trade. After any change to your second steps, nothing can turn automations on or confirm a trade for 24 hours, so someone who adds their own passkey to your account can't use it straight away. Locking your account pauses automations and signs out every session, without needing your second step.

The trade is confirmed as it stands. You confirm a workflow's trades with your second step, and Burokku keeps a fingerprint of each: the coins, the amount, the chain, and the trigger with its settings. Change any of them, by hand or by accepting a draft from Burokku AI, and it needs confirming again. Run now never makes a trade either; trades run only when the trigger fires, so a signed-in session alone can't make the wallet trade on demand.

It stays within your caps. Your trading wallet has a limit per trade and a limit per day. You can lower them whenever you like; raising them asks for your second step, and they never go above Burokku's own ceiling. Every quote is checked too: if the best price is more than 3% worse than the market, nothing is traded.

What a held run looks like

When a check says no, the run stops at that step and says why in a sentence: "Automations are off or paused, so nothing was traded," or that your trading wallet needs a little ETH for network fees. It shows on Automations under Runs, and you're told once. What happens next depends on the reason:

• Reasons that can clear are held. Automations paused, no gas or funds, a trade not confirmed, the day's limit reached: the trade is tried again at each check, from the step where it stopped. The messages before it aren't sent again, and you aren't told again for the same reason.
• Attempts that fail get three tries. No route, or a price too far from the market, is tried three times, so a swap that keeps failing can't keep spending network fees.
• Trades that can never work stop. One over your per-trade limit, or a pair Burokku can't trade, ends the run.
• A held trade waits a day at most. After that it's dropped with "The trade waited a day without going through, so Burokku stopped trying". By then the moment that set it off has passed.

Each trade Burokku tries for you, made or stopped by a check, goes in your account's audit log with its outcome, along with every confirmation, every change to your limits and every workflow you create or edit.

Why we built it this way

We'd rather an automation wait and tell you than act on a guess. A held trade costs you a notification. A trade you didn't mean costs you money, and no undo button gives it back.

That's also why the limits sit beneath the workflow rather than inside it. A workflow can be edited, drafted by Burokku AI or started by a webhook; the switch, the confirmation and the caps stay where they are. See automations for what you can build, and how security works for the rest of the rules. If a limit gets in the way of something you need, tell us.