Exits
The exit is placedwith the entry,not after it
A stop that exists only in the software that is currently running is not protection. Where a venue can hold the exit natively, it does. Where it cannot, the platform holds it and says so — and the difference is visible, not hidden behind one word.
Two kinds of protection, told apart
Native, when the venue supports it
On venues that accept an attached stop or take-profit, the exit is submitted with the entry and lives at the exchange. It survives this platform being restarted, disconnected, or switched off entirely, which is exactly the scenario protection exists for.
Software, when it does not — and labelled as such
Where a venue has no native attached exit, the platform watches the price and sends the closing order itself. That is real protection with a real dependency: it needs this service to be running and the market data to be flowing. It is shown as a software stop rather than as a stop, because the two fail differently and you should know which one you have.
Every rung is checked, not just the first
A laddered take-profit is several targets, and it is possible to write one where a later rung sits on the wrong side of the market. That reaches the venue as an instant loss. Every rung is validated before the entry is sent — wrong side, zero size, a ladder summing past the position — and a bad rung refuses the whole order rather than arming a ladder with a hole in it.
Moving a stop is an order, and it is treated as one
Amending a protective exit is validated before the existing one is cancelled. The alternative — cancel, then fail to place — leaves a position with nothing behind it, and it is worst precisely when the order being moved is a stop.
What will not happen
- A take-profit priced on the wrong side of the market reaching a venue.
- A ladder whose rungs sum to more than the position.
- A rung with no size quietly arming for the full position.
- A stop cancelled before its replacement is known to be placeable.
- A software stop presented as if the venue were holding it.
Questions about exits
What happens if the platform is down when my stop should fire?
A native exit fires — it is at the exchange. A software stop does not, and that is the honest reason the distinction is shown on every position rather than averaged into one comforting word.
Can the assistant move my stop?
It can propose moving it. The move is an order, it passes the risk gate like any other, and it needs your confirmation. There is a deliberate grace window after an entry so that a freshly opened, still-settling position is not closed by a re-check that arrived before the fill did.
Do trailing stops work?
Where the venue supports a trailing callback rate natively, yes, and the parameter goes to the venue. Where it does not, the platform will not invent one silently — an unsupported feature is reported as unsupported rather than approximated.
Arm an exit and watch it hold
Paper positions carry the same protective machinery, including the refusals.