If you want to see how certain specialist combos will work, or how to time multiple subs for synchronous landing, or any number of "what-ifs" it's great to roll the TimeWheel forward a bit, set up the whole scenario, and see how it plays out. Then, you can simply delete all your future-set instructions.

However, if you already have actual intended pre-programmed plans, or even worse, have to modify/delete them just to see a possibility out, it's rather destructive and potentially unreproducable.

Modern databases have a facet called "transactional", where if during Alex sending Bob $100, anything goes wrong, it doesn't leave things half done (Bob is $100 richer, but Alex never lost $100 -- magic money!), it "rolls back" ALL the commands if ANY don't succeed.

I'd like to enter into a "setlocal" mode, try things out, and either Commit or Discard all entered changes. From other players'/the game's perspective, the changes are never entered at all until the Commit happens.

That way there's no rifling through a list of bonafide future orders to abort the hypotheticals, nor ruining good commands in the first place to send a specialist elsewhere, a different time, etc.

Are you referring to a sandbox mode?

we want to have that too, but it presents a bunch of challenges that make it a high hanging fruit.