Position Memory: StormBot Now Remembers What It Holds Across Restarts

This is a Field Note about one of the most important reliability fixes in StormBot's history. It is not a flashy new feature — it is a bankroll-protection fix. In plain English: the bot used to forget what it already owned every time it restarted, and that amnesia could quietly spend more of your money than your settings allowed. We fixed it. No setting to toggle, no re-link, nothing for you to do.

The problem, in one image

Picture a storm-chaser with a strict rule: "Take at most one position on a given city today." They open the trade, then a lightning strike knocks them out cold. They come to with no memory of the last hour, glance at their empty notebook, and conclude they haven't traded this city at all — so they take it again. Another strike, another blank notebook, another duplicate. By nightfall they're stacked five-deep on the same market and the bankroll is gone, even though the rule plainly said one.

That is essentially what was happening inside StormBot. The streaming engine keeps a list of the positions it currently holds, and it leans on that list to enforce two of your most important safety rules:

• "One position per city per day" — so it never piles your whole bankroll into a single weather market.
• Your per-trade size cap — the most dollars it is allowed to commit to any one bet.

The catch: that list lived only in the engine's short-term memory. Every time the process restarted — for updates, maintenance, or a hosting blip — or whenever the streaming connection dropped and reconnected, the list got wiped. The bot woke up with a clean slate, looked at its empty list, and decided "I don't hold anything here yet," even though your real positions were sitting safely in your wallet the whole time. So it bought the same market again. And again. The rules were never wrong; the engine just couldn't remember long enough to apply them.

What we changed

We gave the engine a permanent memory. Technically: every time a position opens or closes, StormBot now writes that change to disk immediately. When the process restarts or the stream reconnects, the very first thing it does — before it considers buying anything — is read that saved list back in, with the real entry prices and rules intact.

So the new sequence is simple and safe:

• Engine restarts or reconnects → it reloads everything it already owns before doing anything else.
• Then it scans for new opportunities. Now when it asks "do I already hold New York today?" the answer is correctly yes, so the one-position rule and your size cap actually hold and it won't re-buy a market it's already in past the cap.
• The dashboard reads the same restored list, so your open positions and their value stay visible across every restart.

It's the difference between a chaser whose notebook survives the lightning, versus one who forgets the moment the bolt lands.

How this affects your profit

Honestly and precisely, because we'd rather under-promise: this upgrade does not forecast weather better and does not invent new winning trades. What it does is shut down a specific way the bot was losing money it should never have risked. In trading, not losing money you didn't mean to risk is profit. Concretely:

• Your risk limits now actually work. The per-trade cap and one-position-per-market rule were right all along — they just weren't surviving restarts. They do now. A losing market can no longer secretly compound into several times your intended stake.
• Smaller worst-case losses. The damage from any single bad call is bounded to roughly what your settings say, instead of being multiplied by however many times the engine restarted while holding it.
• More accurate position sizing. Kelly sizing depends on knowing what you already hold and how much bankroll is committed. With an accurate, persistent view, every new bet is sized off reality instead of a blank slate.
• You can actually see your money. Open positions and their value stay on the dashboard through restarts, so you're never again left wondering where your balance went.

The honest bottom line

Think of this less like a turbo button and more like fixing the brakes. It won't make the car faster — but it stops the car from rolling away on its own. For a bot whose entire job is disciplined, rules-based risk-taking, making the rules stick across every restart and reconnect is one of the highest-value things we can ship.

This fix is already live for every StormBot user. There's nothing you need to do — no setting to toggle, no re-link, no action. More bankroll-protection work is next on the roadmap, and we'll write it up the same plain-English way when it ships.

Questions about this change or your account? The only legitimate StormBot is the one you're reading this on at stormbot.ai — beware of copycats.