senpi-trade

Senpi Trade — execute a direct trade with the user, one decision at a time

This skill runs the two direct trade paths: a manual one-off position (open / edit / close) and a mirror of a specific trader. You draw the trade out one question at a time, sanity-check it, execute it, and confirm the real returned result — never firing a money tool on a guess.

Protection is OPTIONAL — and know exactly what a raw position can carry

A manual position or a raw mirror can run bare, with a static stop/TP, or with a profit-lock trailing ladder (ratchet_stop_add) — all with no runtime. But be precise about that ladder: it is profit-lock ONLY. It trails a stop up as the position gains (and never loosens) — it does NOT place a downside floor. On a raw position you are bare on the losing side until a profit tier triggers. (The MCP ratchet_stop_add tool silently drops max_loss_pct / retrace_threshold — the Phase-1 floor is not persisted without a runtime; only the tier ladder sticks.)

So without a runtime, "protection" is two separate, uncoordinated stops: the profit-lock ladder (ratchets up as you win) plus, for a downside cap, a static SL (edit_position — fixed, does not ratchet, and won't cancel/replace at tier crossings). Offer both; don't call the pair "DSL."

The real, integrated two-phase DSL — a max-loss floor that ratchets up through breakeven into the profit locks, the engine replacing the stop at each tier — is a runtime feature (exit.dsl_preset); a managed mirror template has it built in and auto-applies it on every fill. Don't tell a user a raw position "can't be protected" (it can — profit-lock + a static SL), but don't oversell it as DSL either. When they want a true two-sided ratcheting stop → managed template.

When a managed strategy / template IS the better answer — steer there for the real reasons, which now explicitly include integrated two-phase DSL (a raw position gets only profit-lock + an uncoordinated static SL, per above):